Why most change programmes fail, and what capability has to do with it

Walk into almost any failed change programme after the fact and you will find the artefacts of a well-run project. There was a steering committee. There was a communications plan with key messages and a cascade. There was training, a milestone chart, a RACI, a dashboard that went green. Every box that change management orthodoxy asks you to tick was ticked. And the change still did not hold. This is the puzzle worth sitting with, because the usual explanation, that the firm did not manage the change well enough, is almost always wrong.

The conventional view treats change as a process to administer

The dominant model of change management treats change as something you do to an organisation through a sequence of managed steps. Set the vision, build the coalition, communicate it widely, remove obstacles, generate short-term wins, consolidate, anchor it in the culture. The steps are sensible. The trouble is what they quietly assume: that if you run the process competently, the change will take. Decades of evidence say it does not.

The most-cited figure in the field, that roughly 70% of change programmes fail to achieve their goals, has been repeated since the 1990s and traces back to John Kotter's work and to McKinsey's own research on transformation. The exact number is contested, and the methodologies behind it are uneven, so it is worth treating as a directional signal rather than a hard statistic. But the direction is not in dispute. More recent McKinsey research on organisational transformations has continued to find that a large majority fall short of their stated ambitions, and that the differentiator is rarely the technical plan. It is the human and behavioural side: whether leaders model the new behaviours, whether people at every level actually change what they do.

That last point is the tell. If the failure were procedural, better project management would fix it, and it does not. The programmes that fail are frequently the well-administered ones. What they lack is not a tighter plan. It is the thing the plan cannot supply: leaders who can hold themselves and others steady through the disorientation that real change produces, make sound calls without a complete picture, and bring people with them when the destination is not yet clear. That is not a process. It is a capability, and capability is built, not scheduled.

Change is a capability before it is a project

CapabilityFX's work, grounded in Dr Eric Albertini's doctoral research into how leaders actually change, starts from a different premise than the orthodox model. The premise is that durable change is an inside-out phenomenon. It holds or collapses at the level of who a leader is under pressure, not at the level of what the project plan instructs them to do.

This reframes what a change programme is actually asking of people. A restructure, a new operating model, a merger, a strategy pivot: each of these is, beneath the slideware, a sustained period in which the people leading it do not fully know how it will land, are watched closely for signals, and are required to make consequential decisions on incomplete information while staying credible. The comms plan does not help them with any of that. The training does not either. What carries them through is internal: their capacity to stay settled when the ground is moving, to be honest about what they do not yet know without destabilising the people around them, and to keep acting with judgement rather than reverting to control or avoidance.

The DUAL model and the disorientation of change

The DUAL model (Discover, Understand, Accept, Lead) describes how a leader moves through any genuinely hard situation, and a real change effort is exactly that, sustained over months. The reason most programmes stall maps cleanly onto where leaders skip movements.

They skip Discover when they accept the official version of how the change is landing rather than seeing the awkward reality on the ground. They skip Understand when they collapse a complicated, contested situation into the tidy narrative the steering committee wants to hear. The movement they skip most, and the one that matters most, is Accept. Real change asks leaders to own uncomfortable truths out loud: that the original plan was partly wrong, that the timeline was optimistic, that resistance in a particular function is legitimate and not just obstruction. Leaders who cannot do Accept defend a comfortable version of the programme right up until it visibly fails. Only then can the organisation finally Lead, by which point trust has usually been spent.

This is why a change programme can be flawlessly project-managed and still die. The project plan operates entirely in the territory of Lead: actions, owners, dates. It has nothing to say about whether the leaders running it have done the Discover, Understand, and Accept work that makes their Lead worth following. Behaviour change, which is what a change programme is ultimately chasing, follows the sequence or it does not happen. Edgar Schein's work on organisational change made a related point decades ago: durable change requires a period of genuine disconfirmation and the psychological safety to move through it, not just a communicated vision. The disorientation is not a bug in the process to be smoothed over with better messaging. It is the work itself.

What it looks like in practice

A group operations director at a South African retail business was given a major supply-chain restructure to lead. He ran it by the book. The communications were clear, the training was scheduled, the milestone tracker was immaculate, and for the first quarter the dashboard stayed green. What the dashboard could not see was that the regional managers had quietly concluded the new model would not work in their conditions and were running the old process in parallel while reporting compliance with the new one. The director's instinct, under pressure from the executive to show progress, was to treat the early green dashboard as proof the change was taking. He had skipped Discover entirely: he was managing the report of the change, not the change. When the parallel running surfaced two quarters later, the credible response was not a firmer mandate or a refreshed comms push. It was the harder, inside-out work of going to the regions, hearing the parts of their objection that were legitimate, accepting publicly that the rollout had moved faster than the evidence justified, and rebuilding the plan with them. The observable shift was specific: he started a programme meeting by naming what was not working before anyone else had to, and the room's willingness to tell him the truth changed within weeks. Nothing in the original change-management toolkit had asked anything of that capacity. It was the only thing that saved the programme.

A chief executive at a financial services firm led a strategy pivot that looked, on paper, like a model change effort. The vision was compelling, the coalition was built, the early wins were real and well-publicised. The capability gap showed up not at the start but in the long, unglamorous middle, where the initial momentum faded and the change had to survive contact with ordinary organisational fatigue. Under that slower pressure, her default reasserted itself: she was superb at projecting confidence and far less comfortable holding visible uncertainty. So as the harder questions arrived, questions she genuinely could not yet answer, she kept projecting the same polished certainty she had used to launch the programme. Her senior team, who could see the uncertainty plainly, read the gap between her message and the reality and quietly stopped believing the message. They did not push back. They simply withdrew discretionary effort, and the change lost its carriers. The intervention was not a relaunch. It was developing her capacity to hold confidence and candour together, the same capacity we examine in the piece on what to say when you do not know the answer. When she began telling her team what was genuinely settled and what was still open, rather than performing certainty over both, the senior layer re-engaged. The strategy had not improved. Her ability to lead it through ambiguity had.

Both efforts were competently administered. Both stalled on the same fault line: a leadership capability the programme structure never named, let alone built. And in both cases the recovery came from inside-out work, not from a better plan.

The question to ask before the next programme

Most organisations, before a major change, ask whether the plan is sound, whether the resourcing is adequate, and whether the governance is in place. These are reasonable questions. They are also the wrong first questions, because they all sit downstream of a more fundamental one.

Questions for sponsors and executives

On the leaders, not the plan. Do the people sponsoring and carrying this change have the demonstrated capacity to stay settled when it gets genuinely uncertain? Can I point to a recent moment where one of them named an uncomfortable truth about a programme early, while it could still be acted on, rather than defending a green dashboard?

On honesty under pressure. When this change starts landing differently from how we planned, and it will, who on this team can say so out loud without it reading as disloyalty or panic? If the honest signal has nowhere safe to arrive, the plan's quality will not save us.

On where the budget goes. How much of our change investment is going into the process, the comms, the training, the tooling, and how much into the capability of the people who have to hold the whole thing through the disorientation? For most organisations the honest answer is heavily weighted towards the former, which is precisely the half that the evidence says does not determine whether change holds.

If those questions are uncomfortable to answer, that discomfort is useful information. It usually means the change is being set up as a project to administer rather than a capability to lead, which is the most reliable predictor of the 70% outcome.

Build the half that makes change hold

None of this is an argument against good change management. Plans, communications, and governance are necessary. They are simply not sufficient, and treating them as if they were is why so much sincere effort and budget produces so little durable change. The half that gets administered is the half that gets the attention. The half that gets neglected, the leadership capability to carry people through real uncertainty, is the half that decides the outcome.

That capability is developable. It is not a fixed trait of the personalities in the room, and it does not come from another workshop bolted onto the programme. It is built inside-out, over time, in the work itself, which is what the 4D method is designed to do. If you have a significant change ahead, or one that has already stalled in a way a better plan does not seem to fix, the most valuable move is to look honestly at the capability of the people leading it. You can see how CapabilityFX approaches that in our services, and if you want to talk through what it would mean for your specific change, you can contact us directly.

The leaders and organisations described here are representative composites drawn from patterns we observe in practice, not identifiable individuals.