The most expensive mistake in transformation is to treat it as a technical project. Organizations pour resources into building the new system, redesigning the process, or restructuring the function, and treat the people who must actually change as an afterthought — a training session near go-live and a hopeful email. Then they are surprised when adoption stalls and the promised benefits never arrive.
Structured change management exists to prevent exactly this. It is the discipline of preparing, supporting, and equipping people to adopt change successfully, on the understanding that a change nobody adopts delivers nothing, however well it is built. The ADKAR model offers a clear, practical framework for doing it well.
Why the people side dominates
The uncomfortable evidence from decades of transformation is that the technical solution is rarely the limiting factor. Systems get built; processes get designed. What determines success is whether people embrace the new way of working — and human beings do not change because a project plan says they should. They change when they understand why, want to, know how, are able to, and are supported in sustaining it. That sequence is the heart of the ADKAR model.
The five stages of ADKAR
ADKAR describes the five milestones an individual must pass through for a change to take hold. Each builds on the last; skip one and adoption falters at that point.
- Awareness — the person understands why the change is happening and what is at stake in not changing.
- Desire — they are personally motivated to support and participate in the change, not merely aware of it.
- Knowledge — they know how to change: the new skills, processes, and behaviours required.
- Ability — they can actually perform the new way of working, having practised it, not just learned about it.
- Reinforcement — the change is sustained through recognition, measurement, and correction of backsliding.
Diagnosing where adoption is stuck
ADKAR’s practical power is diagnostic. When adoption stalls, the model helps locate exactly why. Resistance often traces to a gap in desire — people understand the change but do not want it, usually because the case has not been made in terms that matter to them. Fumbling execution often traces to a gap in ability — people want to change and know what to do but have not been given the chance to build genuine competence. Naming the gap points directly to the remedy.
Reinforcement: the stage most often skipped
The final stage is the one organizations most reliably neglect. Once go-live passes and the project team disbands, the pressure to revert to old habits is powerful and the support to resist it evaporates. Deliberate reinforcement — measuring adoption, celebrating the people who embrace the change, and correcting quiet regression — is what turns a temporary shift into a permanent one. Without it, transformations decay back towards the old normal with dispiriting speed.
You can build the perfect system and still fail. A change that people do not adopt delivers nothing — which is why the people side is not a soft add-on but the core of transformation.
Key takeaways
- 1Transformations fail on adoption far more often than on technology.
- 2ADKAR sets out five sequential milestones: awareness, desire, knowledge, ability, reinforcement.
- 3The model diagnoses precisely where adoption is stuck and what to do about it.
- 4Reinforcement — the most neglected stage — is what makes change permanent.
Frequently asked questions
When should change management begin?
At the very start of a transformation, not near go-live. Awareness and desire must be built long before the new way of working arrives; change management introduced late is remedial and far less effective.
Who should own change management?
It requires dedicated ownership — a change lead or team — working alongside the technical delivery, with visible sponsorship from senior leaders whom employees trust. It cannot be a side duty of the project manager.
