There is a statistic that gets cited so regularly in organisational management that it has almost lost its ability to shock: somewhere between 60 and 70 percent of major change initiatives fail to achieve their stated objectives. Depending on the study, some estimates go higher.
This number has been sitting in the research for the best part of thirty years. And yet the way most organisations approach change has not materially shifted in that time. The planning gets more sophisticated. The documentation gets more thorough. The failure rates remain stubbornly consistent.
The reason for that is that most organisations are trying to solve a human problem with a structural solution.
The planning layer and the people layer
A well-run change programme has a lot going for it. A clear case for change. Defined milestones. A communication plan. Training materials. A steering group. KPIs to measure success. These things matter. They are not sufficient.
What they address is the formal system: what the organisation is officially going to do differently. What they rarely address with any precision is the informal system: what the people in the organisation actually believe, how they feel about the change, what they stand to lose, what they fear, and whether they trust the people asking them to change.
The informal system is where real organisational behaviour lives. And in any significant change programme, the informal system is where the change will succeed or fail. The formal layer sets the direction. The informal layer determines what actually happens on a Tuesday afternoon when nobody is looking.
What resistance actually is
The word resistance does a lot of work in change management conversations, and it is worth being precise about what it usually means.
In most organisational change contexts, resistance is not obstruction. It is not sabotage. What gets labelled resistance in the vast majority of cases is a rational response to uncertainty from people who do not yet have enough information to feel safe.
When people resist change, they are almost always protecting something. A way of working they are good at. A status or identity tied to a particular role. Relationships built around a particular structure. None of those things are irrational. From inside the experience of the person holding them, they are entirely reasonable.
The problem with the conventional change management approach is that it treats this as a communication problem. If people understood the case for change better, they would get on board. So the communication plan gets more detailed. The town halls get more frequent. The leadership team repeats the rationale more clearly. And the resistance continues, because understanding the rationale for change is not the same thing as feeling safe enough to embrace it.
The three things that actually determine whether change sticks
After watching a lot of change programmes succeed and fail, the variables that consistently make the difference are not the ones that appear most prominently in the methodology.
The first is whether people believe the change is actually going to happen. Change announced from the top of an organisation meets immediate scepticism in most cultures, particularly if previous changes have been announced and then quietly dropped. Until people believe that this change is real and will be sustained, their rational response is to wait it out.
The second is whether people can see their own place in the new world. Abstract benefits of change are easy to articulate. What is much harder, and much more important, is giving each person a concrete picture of what their working life looks like after the change is complete. The organisations that do this well, at the individual level rather than the organisational level, see dramatically different engagement.
The third is whether the people asking for the change are visibly living it themselves. No amount of communication overrides what people observe.
Where change programmes go wrong in practice
In smaller organisations, the most common failure mode is not a lack of planning. It is a lack of honest diagnosis about what the change actually requires from the people involved.
I have worked with founders who have initiated significant operational changes while significantly underestimating the degree to which those changes would feel threatening to established members of the team. The change was objectively correct. The business needed it. But the implementation created a level of anxiety and uncertainty that produced more disruption than the original problem.
The corrective is not to make change more palatable by softening it. It is to do the diagnostic work upfront: who does this change affect, and how? What are they likely to feel about it? What do they stand to lose, even if the net effect for them is positive? What information do they need, and when? Where are the likely flashpoints? That diagnostic does not slow change down. It speeds it up, because it means the change you implement is the change that actually sticks.
The question most change plans do not ask
The most useful single question I have found in working through any significant organisational change is this: if this change fails, what will we wish we had done differently?
It sounds simple. Most leadership teams, when they sit with it honestly, come up with answers that are not in the plan. And those answers are usually where the work is.