Organisational change management is the discipline that decides whether a transformation — a new tool, a restructuring, a merger, a technology migration — translates into real results or remains an announcement that nobody adopts. Various sector studies put the failure rate of change initiatives at around half, and the cause is rarely technical: it is human. This article develops the most proven change management models, the levers of adoption and the mistakes that derail even the best-designed transformations on paper.
Why changes fail: the human factor
An organisational change fails when the new process exists on the diagram but people keep working as before. Resistance to change is neither irrationality nor bad faith: it is a predictable response to uncertainty, to the perceived loss of competence or status, and to a lack of understanding of the "why". Treating resistance as an obstacle to overcome is the first mistake; understanding it as information about what has not been communicated or designed well is the first success. Professional change management starts by recognising that people do not resist change in the abstract, but rather resist being changed without taking part.
The change curve, inspired by Elisabeth Kübler-Ross's work on transition, describes the emotional states a person goes through when facing an imposed change: initial denial, resistance and frustration, a valley of low productivity and discouragement, and only then exploration and commitment. Knowing this curve has an important operational consequence: the drop in performance during the transition is not a symptom that the project is going badly, but an expected phase that must be planned for and accompanied. Projects that interpret that valley as a failure and reverse course just before the recovery are the ones that end up cementing the idea that "changes never work here", poisoning future transformations into the bargain.
It is useful to distinguish rational resistance (the person sees a real design problem that is worth listening to and correcting) from emotional resistance (fear of the unknown, mitigated with information and participation) and from political resistance (defence of interests or power bases, requiring explicit negotiation). Applying the same recipe to all three is ineffective: rational resistance is addressed by redesigning, emotional resistance is accompanied by communicating, and political resistance is managed by aligning incentives. Confusing them is one of the most frequent causes of deadlock.
Kotter's model: eight steps to lead change
John Kotter, of Harvard Business School, proposed an eight-step model that remains the reference for far-reaching changes. It begins with creating a sense of urgency, without which the organisation does not mobilise energy. It continues with forming a guiding coalition of people with power and influence, developing a clear vision and communicating it in a massive and coherent way. The following steps — removing obstacles, generating short-term wins, consolidating gains and anchoring the change in the culture — address the most dangerous moment: when the initial enthusiasm runs out and the organisation tends to return to its old habits. Short-term wins are not cosmetic: they are the tangible proof that keeps the project's credibility alive.
The ADKAR model: change is managed person by person
While Kotter looks at the organisation from above, the ADKAR model from Prosci looks at each individual. It holds that no person adopts a change without going through five states in order: Awareness (of why it is necessary), Desire (to take part and support it), Knowledge (of how to change), Ability (the real capacity to do it) and Reinforcement (which sustains it over time). Its practical use is diagnostic: when an adoption stalls, ADKAR makes it possible to pinpoint the state at which people have got stuck. If results fall short, it is usually due to a lack of Ability (not enough training); if people "know but do not want to", the blockage is in Desire, and no additional training will resolve it.
Lewin's model: unfreeze, change, refreeze
Kurt Lewin contributed the oldest and still valid conceptual model. Unfreeze consists of questioning the status quo and creating readiness for change. Change is the transition, the uncomfortable period in which the old no longer works and the new is not yet mastered. Refreeze is stabilising the new state so that it becomes the new "normal". Its most valuable contribution is to warn against rushing to refreeze: if you stabilise before the change has truly taken root, you crystallise a half-baked version. And conversely: if you never refreeze, the organisation lives in a perpetual transition that exhausts people.
Communicating change: the circulatory system
Communication is not a phase of change: it is its circulatory system. It must be frequent, honest and two-way. Frequent because a message gets diluted and must be repeated across multiple channels. Honest because hiding the difficulties destroys trust as soon as reality reveals them. And two-way because the organisation needs to listen in order to detect where adoption is getting stuck. A good practice is to structure the message by always answering the three questions every affected person asks: why are we changing, what does it mean for me specifically, and what am I expected to do differently from tomorrow.
Comparison table: change management models
| Model | Focus | Strength | Best use |
|---|---|---|---|
| Kotter (8 steps) | Organisational, top-down | Mobilises and maintains momentum | Far-reaching transformations |
| ADKAR (Prosci) | Individual | Diagnoses where each person gets stuck | Adoption of tools and processes |
| Lewin (3 phases) | Conceptual | Simple, robust mental framework | Understanding the dynamics of change |
| McKinsey 7S | Systemic | Aligns the seven elements of the organisation | Complex structural changes |
Measuring adoption: from enthusiasm to data
A change is not managed by gut feeling. It is wise to define adoption indicators from the outset: usage rate of the new system, percentage of processes executed according to the new standard, number of exceptions or reversions to the old method, and the business results the change promised to improve. The ISO 9001:2015 standard, in its clause 6.3, also requires that changes to the management system be planned in a controlled way, considering their purpose, their consequences, the integrity of the system and the availability of resources. Measuring adoption is what turns change management into a discipline rather than an exercise in motivation.
The role of middle management
Senior management sponsors the change, but the one who makes or breaks it is the middle manager. It is the direct boss, not the CEO, whom people watch to decide whether the change is serious. That is why one of the highest-return investments is enabling middle managers as change agents: giving them the "why" before anyone else, training them to answer their team's questions and publicly recognising those who lead the transition well. When the middle manager keeps working the old way, their team imitates them above any official communication.
Common mistakes in change management
- Starting with the tool and not the why: the system is rolled out before generating urgency and desire.
- Communicating only once: the message gets diluted and it is assumed that "it has already been said".
- Ignoring middle managers: the change is sponsored at the top but is not sustained on the front line.
- Not measuring adoption: the launch is confused with real adoption.
- Refreezing too soon or never: a half-baked version is crystallised or you live in a perpetual transition.
Frequently asked questions
Which change management model is best?
There is no universally best one. Kotter works well for mobilising large transformations, ADKAR for diagnosing individual adoption and Lewin as a mental framework. In practice they are usually combined: Kotter for the strategy and ADKAR for managing people.
How do you overcome resistance to change?
You do not overcome it: you manage it. Resistance is reduced by involving people in the design, honestly explaining the why and addressing the real losses the change imposes on them. Treated as information, resistance improves the change itself.
How long does a change management process last?
It depends on the scope, but the most common mistake is to underestimate it. The adoption and reinforcement phase, which is the decisive one, usually extends for months after the technical launch, and abandoning the support at that moment is the most frequent cause of regression.
Who should lead the change?
Senior management sponsors and gives legitimacy, but the guiding coalition must include leaders at different levels, especially middle managers, because they are the ones who translate the vision into everyday behaviour for their teams.
Conclusion
Organisational change management is not a soft layer added at the end of a technical project: it is what determines whether that project produces results or remains an intention. The Kotter, ADKAR and Lewin models do not compete, they complement each other, and they all agree on the essentials: change is won person by person, with honest communication, with short-term wins that prove it is serious and with support that is not withdrawn the moment the launch ends. At Summum Consulting we design change plans in parallel with the technical project from day one, measuring adoption with concrete indicators, because a transformation that is not adopted is not a transformation: it is a cost with no return.