Why change programmes fail

You'll have heard the number. Seventy percent of change programmes fail. It gets cited in boardrooms, slide decks, and consulting proposals so routinely that it barely registers any more. The statistic originated with John Kotter in 1996 and has been circulating ever since - repeated, rarely questioned, occasionally updated.

McKinsey's own research, drawn from a database of over a thousand transformations surveyed between 2015 and 2021, puts the figure at less than 30% succeeding. The CIPD's 2024 Change Management Conference opened with the observation that organisational change is still more likely to fail than succeed. The numbers shift depending on who's counting and how they define success, but the direction is consistent: most change programmes don't deliver what they set out to.

What's strange is how little curiosity that number seems to generate. It gets used as a warning - "the odds are against you, so you'd better get this right" - but rarely as a genuine question. If most change programmes fail, and most of them are being run by intelligent, experienced people using well-established frameworks, then perhaps the interesting question isn't about execution. Perhaps it's about what the frameworks themselves are missing.

Because here's the thing: change management as a discipline has improved enormously over the past two decades. The tools are better. The training is better. Project governance is more sophisticated. Communication strategies are more nuanced. And yet the failure rate hasn't shifted meaningfully. If better execution isn't moving the needle, something else is going on.

The programme that should have worked

Consider a pattern that shows up repeatedly in organisations going through planned change. A new system, a restructure, a process redesign, a shift in operating model. The case for change was clear and evidence-based. The project plan was thorough, with milestones, governance, and clear accountability. Communication was frequent and multi-channel. Training was provided. Senior sponsorship was visible.

On paper, this was textbook. And for a while, it felt like it was working. The early milestones landed. The steering group reported green. People attended the workshops and nodded along.

Then something started to shift. Not dramatically - not a revolt or a walkout. More like a slow loss of traction. Engagement in the programme meetings dipped. The people who'd been enthusiastic early on started hedging. The new processes were being followed, technically, but the old ways persisted underneath. Workarounds appeared. Teams had adapted to the change on the surface while preserving what they could of how things used to work. Twelve months later, a candid assessment would say: the change happened, but something important didn't land.

This isn't a story about a failed project. The project was well-managed. It's a story about a gap between what the plan addressed and what the change actually required.

What the plan addressed and what it didn't

Most change programmes are designed around the change itself. What needs to be different? What's the timeline? Who's affected? What needs to happen when? This is necessary work. But it treats the change as the primary variable and the organisation as a stable container that the change is being introduced into.

The plan addresses the initiative. It rarely addresses the conditions the initiative is entering.

Think of it like planting. You can have healthy seedlings, a clear layout, and a solid planting schedule. But if you don't understand the soil - its composition, drainage, what's already growing in it, what has been grown there before - you can do everything right and still watch things struggle to take root.

Organisations have their own soil. It's made up of trust levels, decision-making patterns, how knowledge moves between teams, how much capacity people have for something new, whether previous changes left scar tissue or confidence. These conditions existed before the change programme started, and they shape how the change is received in ways that project plans don't typically account for.

McKinsey's 2023 State of Organizations research found that 72% of transformations fail because either management does not fully support the change or employees resist it. Both of these - insufficient support and resistance - are symptoms of conditions, not failures of planning. They tell you something about the environment the change entered: how trust is held, how decisions flow, what people's relationship with change already looks like.

Why well-managed change still gets resisted

Resistance to change is usually treated as a problem to solve - a barrier between the current state and the desired one. But when a change programme is well-designed and well-communicated and people still aren't engaging with it, the resistance is worth listening to rather than overriding.

Sometimes what looks like resistance is actually a lack of capacity. People are already carrying three other change initiatives, and this one - however well-intentioned - arrives as yet another demand on limited bandwidth. The plan didn't fail. It just didn't account for the fact that the organisation was already full.

Sometimes it's a trust deficit. The organisation has been through changes before that were communicated as opportunities but experienced as losses. People learned that the official narrative and the lived experience don't always match. That learning doesn't reset because a new programme has better slides.

Sometimes it's about meaning. People can understand what's changing without understanding why it matters - not why it matters strategically, but why it matters for the work they do every day. A new system might make perfect sense from an enterprise perspective while making an individual team's work harder in the short term. A restructure might be strategically sound while asking someone to give up a role they'd spent years growing into. When a change doesn't connect to people's sense of purpose or professional identity, it gets compliance rather than commitment. And compliance without commitment is exactly the gap between a change that happens on paper and one that happens in practice.

And sometimes - perhaps most commonly - it's a combination of all three. Capacity, trust, and meaning aren't separate variables that can be addressed independently. They interact. Low trust reduces people's capacity for change because they spend energy on self-protection rather than adaptation. Low capacity makes it harder to find meaning in yet another initiative. And when meaning is absent, even high-trust environments struggle to generate the energy that change requires.

Julia Balogun and Gerry Johnson's research, published in Organization Studies, showed how intended strategies reliably lead to unintended outcomes. The mechanism was informal, lateral sensemaking between people - the conversations where middle managers and their teams tried to work out what a change actually meant for them. The resulting change was always, they found, a blend of what was planned from above and what emerged from these conversations. No plan, however thorough, could fully determine how the change would be interpreted and enacted.

This isn't an argument against planning. It's an observation that planning addresses one set of variables while another set - the conditions that determine how a change is received, interpreted, and absorbed - operates alongside it, often invisibly. The plan and the conditions exist in the same organisation at the same time. Attending to one while ignoring the other is how well-managed programmes produce disappointing outcomes.

What changes when you look at conditions

The shift from "managing the change" to "understanding the conditions it's entering" doesn't require dismantling what already works. It requires adding a dimension that's typically missing.

Before launching a change initiative, assessing readiness means looking beyond whether the business case is sound and the stakeholders are mapped. It means understanding the state of the environment the change will land in.

How much change is already in flight? Not just the change programmes with names and governance - but the accumulation of smaller shifts, adjustments, and re-prioritisations that people are navigating daily. Change capacity isn't unlimited, and most organisations underestimate how much of it is already committed.

What's the trust balance? Every organisation has one. It's built through consistency between what's said and what happens, through leaders following through, through previous changes being handled in ways that respected people. If the trust balance is low, even well-designed change meets friction - not because the plan is flawed, but because the environment isn't ready to receive it. Trust doesn't appear in a Gantt chart, but it determines more about the outcome than almost anything that does.

How does knowledge move? In organisations where information flows freely across teams, people can make sense of change more quickly. They can compare notes, check assumptions, and build a shared understanding of what's happening. In organisations where teams operate as islands, each pocket of the organisation constructs its own interpretation of what's happening. The same change announcement produces five different understandings, and nobody discovers the misalignment until it shows up operationally - in conflicting priorities, duplicated effort, or teams working against each other without realising it.

What's the history? Organisations carry their change stories the way individuals carry memories. A restructuring that went badly ten years ago is still shaping how people respond to the word "restructure" today. A merger that was described as a partnership but experienced as a takeover leaves traces in the culture long after the leadership that oversaw it has moved on. These stories aren't irrational - they're learned responses to real experiences. A plan that ignores the organisation's relationship with its own history is building on ground it doesn't fully understand.

From programme management to condition awareness

None of this means change programmes are futile or that project management is irrelevant. The discipline and structure of good change management still matters. Milestones, governance, communication, training - these are all necessary. But they're not sufficient.

The missing piece, in most of the change programmes that look right on paper but don't land in practice, is attention to the conditions the change is entering. Not as an afterthought or a risk assessment line item, but as a fundamental part of how the change is designed and led.

This is the difference between a programme that addresses the change and one that also addresses the environment the change needs to succeed in. The first can be technically perfect and still not land. The second starts from a different set of questions entirely - questions about capacity, trust, meaning, and readiness that most project plans never ask.

The organisations where change does stick tend to be the ones where leaders have developed a feel for the environment they're working within - where they can sense capacity, read trust, notice how meaning is forming, and adjust the approach accordingly. Not because they've abandoned planning, but because they've added a layer of awareness that planning alone can't provide. They've learned that the plan and the conditions are two different things, and that attending to only one of them is how you end up with change that delivers on paper but not in practice.

Change that genuinely lands doesn't require a different framework. It requires a different starting question. Not "what needs to change?" but "what are the conditions this change is entering, and what do those conditions need in order for this change to take root?"