I have run or overseen organizational transformations at five Fortune 50 companies. I have also watched, from the inside, how those same companies approached change management. The gap between what works and what gets funded under the change management banner is one of the widest I have encountered in corporate operations.
Here is the uncomfortable pattern: an enterprise announces a major transformation — a new operating model, a technology migration, a post-merger integration. A change management team is stood up or a consultancy is engaged. Within weeks, the organization has a communication plan, a stakeholder map, a resistance assessment matrix, and a town hall schedule. Six months later, the transformation has stalled, adoption is uneven, and the change management team is producing increasingly creative dashboards to explain why the metrics have not moved.
Most change management programs fail because they manage communication about change, not the structural conditions that determine whether change takes root.
The tools are not the problem. Prosci's ADKAR model is sound. McKinsey's 7-S framework captures the right interdependencies. Kotter's eight steps sequence the work correctly. The problem is that organizations use these frameworks to build communication programs rather than structural interventions — and then wonder why awareness did not translate into adoption.
The Three Structural Failures
After twenty-five years of leading transformations across healthcare, financial services, retail, automotive, and construction, the failure modes have been remarkably consistent. They are not about hearts and minds. They are about incentives, authority, and systems.
An organization asks middle managers to adopt a new cross-functional workflow while continuing to measure and compensate them on functional output. A company launches an innovation initiative while penalizing the first team whose experiment fails. A healthcare system asks clinicians to embrace a new EHR while measuring their productivity by pre-migration throughput standards. In every case, the change management team is broadcasting the message that the new way is better while the incentive system is broadcasting the message that the old way is safer. The incentive system always wins. Not because people are cynical — because people are rational. They do what they are rewarded for doing.
Every significant transformation redistributes authority. A shift to agile delivery moves decision-making from project managers to product owners. A decentralization initiative shifts resource allocation from corporate to business units. An AI deployment creates new decisions (model governance, data access, exception handling) that did not exist before. When the transformation plan redesigns the work but not the decision architecture, people revert to the old authority structure because the new one was never made explicit. They are not resisting change. They are navigating ambiguity by defaulting to what they know. The fix is not more communication. It is a decision rights matrix that names who decides what, by when, with what information, subject to what escalation path. This is organizational design work, not change management work — and it is the piece most change programs skip.
The change management field has a tendency to pathologize the people who are not adopting. They are resistors. They are in the denial phase. They need more coaching, more engagement, more town halls. In my experience, at least half of what gets labeled as resistance is actually a capability gap. The new process requires skills the team has not been given time to develop. The new tool requires a workflow change that no one has practiced in a low-stakes environment. The new operating model requires collaboration patterns that the team has never built the muscle for. The diagnostic question is simple: If this person wanted to do the new thing perfectly, could they? If the answer is no, the problem is not motivation. It is enablement. And enablement requires investment — in training, in practice time, in the permission to be temporarily slower while competence develops.
What Effective Transformation Actually Looks Like
The organizations that transform successfully do not do it through better communication plans. They do it by aligning four systems simultaneously: structure, incentives, capabilities, and accountability. Miss any one of the four and the transformation stalls — regardless of how polished the town halls are.
Redesign incentives before you launch the communication
The single highest-leverage action in any transformation is to align compensation, performance metrics, and recognition systems with the desired end state before you ask anyone to change their behavior. This is not optional. It is the difference between asking people to do something and making it rational for them to do it. The Lean Six Sigma principle applies here: if you want a different output, change the system, not the people operating within it.
Publish the decision rights on day one
Before the transformation launches, every affected team should know: who now owns which decisions, what the escalation paths are, and where the boundaries of their new authority begin and end. This is not a RACI chart buried in a SharePoint folder. It is a living document that leadership actively references in meetings, uses to resolve disputes, and updates as the transformation evolves. Ambiguity in decision rights is the number one predictor of transformation stall that I have observed across industries.
Build capability before you measure adoption
Give people the skills before you hold them accountable for the outcomes. This means structured practice environments, not just training sessions. It means protected time to learn, not the expectation that people will absorb new methods while maintaining full operational output. And it means measuring competence development as a leading indicator, not just adoption rates as a lagging one. The organizations that rush to measure adoption before investing in capability end up with a different problem: compliance without competence. People check the boxes but the quality of execution is degraded — which generates its own cycle of disillusionment.
Make accountability visible and bilateral
Accountability in a transformation cannot flow only downward. If leadership is asking the organization to change while leadership's own operating rhythms, resource allocation decisions, and meeting structures remain unchanged, the organization will correctly interpret the transformation as performative. The most effective accountability structures I have built include explicit leadership commitments — named behaviors that executives commit to changing — published alongside the expectations for the rest of the organization. This is not symbolic. It is the mechanism that makes the transformation credible.
The Practitioner's Diagnostic
If you are leading or planning a transformation, run this four-question diagnostic before you invest in the communication plan:
One: Do the incentive structures reward the behavior we are asking for — or do they punish it?
Two: Can every affected person name who owns the decisions that the transformation creates or redistributes?
Three: Have we invested in building the capabilities the new way of working requires — or are we assuming people will figure it out?
Four: Has leadership changed its own behavior in visible ways that signal this transformation is real?
If you cannot answer yes to all four, you do not have a change management problem. You have a change architecture problem. The communication plan can wait. The structural work cannot.