We were three weeks from go-live.
Eighteen months of work. A meticulously built system. A team that had given everything to get to this moment. And then — a full stop.
The resistance hadn’t appeared overnight. It had been building for months, quietly, just beneath the surface. Every warning sign was there. The hesitation in status calls. The “concerns” that got tabled for later. The key stakeholders who showed up to meetings but never really showed up. We saw it. We all saw it.
And we kept building anyway.
Because the technology was on track. The timeline was on track. And somewhere along the way, the project had become about the system, not the people who were going to have to live inside it every day.
Three weeks before go-live, the project collapsed. Resistance that had never been addressed had been organizing in the background. There were individuals at the client’s organization that never wanted the implementation to succeed. They had their reasons; territory, control, fear of what the new system would reveal about performance, a change in how power moved through the organization. And because we never named it, never walked toward it, never built a communication environment that could hold that kind of tension, they won.
Eighteen months of work. Sitting completely still.
Not because the technology failed. Because the humans were never part of the plan.
The Real Reason Transformations Fail
Here’s what most organizations believe: if you build the right system, train your people, and document the processes, adoption will follow.
Here’s what I’ve learned after 15+ years inside Salesforce implementations: adoption is a communication problem, not a technology problem.
When people resist change, they’re not always resisting the software. Sometimes they’re resisting uncertainty. Sometimes they’re resisting what the new system threatens to take from them — influence, autonomy, the ability to control information. And sometimes, there are people inside an organization who are actively working against a change initiative while the project team keeps its head down and hits its milestones.
That client had invested millions in the architecture of the system — and nothing in the architecture of the communication environment around it. No one had designed a way to surface resistance early. No one had mapped who held informal power and what they stood to lose. No one had created space for the hard conversations before they became impossible ones.
That’s the gap Communiscape was built to close.
What I Mean by “Communication Architecture”
Most organizations treat communication as a campaign — a series of announcements, training sessions, and emails that surround a change initiative. You launch it, you send the messages, you check the box.
But communication architecture is something different entirely. It’s the intentional design of the environment in which people receive, process, and respond to change. It’s the difference between throwing information at people and actually building the conditions for adoption — including the conditions that allow resistance to surface, be heard, and be addressed before it becomes a weapon.
Over a decade of leading change initiatives, I developed a framework built around five interconnected domains. I call it the 5-Terrain Framework, and it’s the foundation of everything we do at Communiscape.
The Five Terrains
Mindscape is where it all begins — inside the minds of the people you’re asking to change. Before anyone will adopt a new system or process, they need psychological safety, a clear understanding of why, and a belief that this change is possible for them. We assess cognitive and emotional readiness before a single training session is scheduled — because unaddressed fear doesn’t disappear. It goes underground.
Speakscape is the language environment of your organization. Every company has one — the words, phrases, and narratives that either create alignment or quietly reinforce resistance. We audit and redesign the actual language being used around a change initiative so that it builds momentum instead of eroding it. Language that minimizes human concerns doesn’t eliminate them. It teaches people to hide them.
Voicescape examines who is speaking, when, and with what authority. Change doesn’t travel through organizational charts — it travels through trust networks. We map those networks and equip the right voices to carry the right messages at the right moments. When informal power holders aren’t brought into the conversation, they often lead the opposition instead.
Listenscape is perhaps the most overlooked domain — and the one that failed most visibly in that implementation. It’s not enough to communicate well. Organizations must create structured channels for people to be heard throughout a change process. Resistance that has somewhere to go can be transformed. Resistance with nowhere to go organizes quietly, and by the time you see it, it has already built a coalition.
Impactscape is where we measure what matters. Not just adoption rates, but the downstream impact on productivity, culture, and revenue. We help organizations articulate the story of their transformation — including the hard parts — so it can be learned from, replicated, and celebrated.
What Changes When You Design the Environment
That implementation? We eventually went back in. Not to rebuild the system — it was already built. We went back to rebuild the communication environment around it.
We spent six weeks working through all five domains. We named the resistance instead of managing around it. We identified who held informal power and what they actually needed to feel safe moving forward. We created channels for the real conversations to happen — the ones that had been avoided for eighteen months. We restructured the narrative so that adoption felt like a path forward rather than a verdict on the past.
Twelve weeks later, the system went live. Adoption reached 91%.
Same system. Same people. Different communication environment.
The difference wasn’t the technology. It was that, this time, we refused to let the human side of the project be optional.
Why This Matters Now
The Microsoft 2022 Work Trend Index documented a 153% increase in weekly meetings — and yet, organizational change initiatives continue to fail at staggering rates. We are communicating more than ever and connecting less than ever.
More information is not the answer. More meetings are not the answer. A deliberately designed communication environment — one that accounts for human psychology, informal power, organizational culture, and the very real possibility that not everyone wants you to succeed — is the answer.
At Communiscape, we believe that communication architecture is not a soft skill. It is a strategic infrastructure. And organizations that invest in designing it deliberately will achieve outcomes that those relying on legacy approaches simply cannot match.
This Is Just the Beginning
If you’re a leader navigating a technology implementation, a change initiative, or simply a team that isn’t communicating at the level it needs to, I’d love to connect.
Because the resistance you’re seeing? It didn’t start where you think it did. And the solution isn’t more technology. It’s a better-designed environment for the humans inside it.