Embracing Change: The Framework Is Not the Point
Nothing endures but change. Heraclitus said it first. Marcus Aurelius wrote it into his private journal at the edge of an empire that was already slipping. Observe constantly that all things take place by change. Nature loves nothing so much as to alter what exists and to make new things in its likeness.
Two thousand years later, we have given the oldest idea in philosophy a budget and a steering committee. We call it digital transformation. We resource it. We govern it. We pin it to a wall in swimlanes and dependencies.
And then, most of the time, it fails.
Around seventy percent of digital transformations do not meet their objectives. That figure has barely moved in a decade. McKinsey reports it. Boston Consulting Group, reviewing seventeen hundred programmes last year, found only about a third created value in a way that actually accelerated growth. The number is stubborn because we keep misreading what it is telling us.
Here is the misreading. We assume the failure is technical. A bad platform. A botched integration. A vendor who overpromised. It is almost never that.
When McKinsey examined why corporate transformations collapse, the breakdown was plain. Thirty-nine percent failed on employee resistance. Thirty-three percent on a lack of support from managers. Only fourteen percent came down to inadequate resources or anything resembling a technical constraint. The system did not break. The people did not move.
This is the part we find hard to sit with. The hard problem in transformation is not the migration. It is the person who has done the job the same way for nine years and has been handed a new screen and a fortnight to love it.
So delivery leaders do a reasonable thing. They reach for a framework. And then they have the wrong argument.
You have seen the argument. Kotter or ADKAR. Lewin or McKinsey 7-S. People defend their model the way they defend a football club. The debate feels like rigour. It is mostly decoration.
The academic work is clearer than the LinkedIn debate. A comparative review out of Corvinus University in Budapest studied the major models side by side and reached a conclusion worth holding onto. There is no single optimal approach to change management. Each model draws attention to a different face of the same problem. They do not exclude each other. They complement.
This is not a soft point. It is contingency theory, and it has been settled management science since the 1970s. There is no one best way to organise. And no two ways are equally effective. The right structure is the one that fits the situation in front of you. Dunphy and Stace made the same argument for change specifically. The change agent varies the strategy to suit the conditions. The work is not choosing the one true framework. The work is diagnosing the friction, then reaching for the tool that meets it.
So here is the map I actually use. Not a religion. A toolbox.
When the friction is individual. People do not understand why, or they understand and do not want to. This is an adoption problem, one person at a time. Use ADKAR. Awareness, desire, knowledge, ability, reinforcement. It is the model that focuses hardest on the human side, and it is the one we run on the programme I am leading now. It tells you exactly where a person is stuck. Most resistance is a missing D, not a missing system.
When the friction is inertia. The organisation is comfortable and sees no reason to move. Use Kotter. Its first acts are urgency and a guiding coalition, and its real gift is the short-term win. Large programmes die in the long flat middle. Kotter exists to manufacture momentum across that middle.
When the friction is the snap-back. The change goes in and quietly reverts. Old habits return the moment attention moves elsewhere. This is a Lewin problem. The lesson sits in the third step, the one everyone skips. Refreeze. Reinforce the new state until it becomes the default, or it will thaw.
When the friction is misalignment. Strategy says one thing, the incentives reward another, the structure fights both. Use McKinsey 7-S as a diagnostic. It will show you which of the seven elements is pulling against the change before that misalignment hardens into a slipped date.
When the friction is fatigue. People are not resisting your change. They are exhausted by the last five. Research from the Everest Group names change fatigue as a leading cause of failure. No model fixes this on its own. A rigid waterfall plan makes it worse. An adaptive cadence, smaller increments, and a vision worth the cost are the only honest answer.
Notice what every one of those frameworks shares. Not one of them is about technology. They are all about the human standing in front of the change.
This is where the Stoics earn their place on a delivery wall. You do not control whether people resist. You control how well you prepared for the resistance you knew was coming. You do not control the budget cut or the resource gap. You control whether the change was reinforced well enough to survive one. The framework is the plan. The discipline is everything the plan cannot do for you.
Marcus did not resist change. He studied it, expected it, and met it without flinching. Amor fati. Not love of an easy fate. Love of the one in front of you.
Embracing change is not optimism. It is the refusal to be surprised by the only constant there is. Pick the framework that fits the friction. Then hold the human line long after the technology is live.
That is the work. Everything else is a swimlane.
This week, name the single friction blocking your hardest workstream. Individual, inertia, snap-back, misalignment, or fatigue. The framework you need is usually obvious the moment you name the friction honestly.