Change management is the craft of getting people to move from an old way of working to a new one — and making the new one last. Not the technology, not the project plan, not the org chart: the people. That is where most changes are won or lost, and that is where this site helps you. This page is your way in: what change management is, why it is needed, and where to start.
What change management really is
A simple definition: change management is the structured work of helping people through a change so that the intended benefit is actually achieved. A new system, a new organisation, a new way of working — it does not matter how good the solution is if no one uses it the way it was meant to be used.
That is why change management is not the same as project management. The project builds and delivers the solution; change management makes sure it is adopted and used. One way to remember it: the project delivers the solution, change management delivers the adoption. Here I go through the difference in detail.
Why it is needed
Most changes that fail do not fail on the technical side — they fail because the people never really came along. A technically perfect system that is barely used, a new organisation on paper but the old ways of working in practice. The solution was delivered, but the benefit never materialised.
And people rarely resist change as such — they resist loss and uncertainty: losing something they are good at, not understanding why, not knowing what happens to me. Change management is the work of meeting that for real — not persuading, but creating understanding, desire and ability.
Change happens on two levels
A change happens in the individual and in the organisation at the same time, and the best approaches hold both in mind at once:
- The individual — every person makes their own journey: understand why, want to take part, know how, be able to in practice, and keep it up. That is the journey the ADKAR model describes.
- The organisation — at the same time the whole organisation needs to be mobilised: direction, leadership, communication and reinforcement. That is what frameworks like Kotter and Prosci help with.
Miss the individual level and the change becomes an empty directive; miss the organisational level and it runs out of steam. You need both.
The best-known models — in brief
- Lewin — the simplest frame: unfreeze, change, refreeze. Good for explaining the logic of a change.
- ADKAR (Prosci) — the individual’s journey in five steps. Diagnostic: you can see where someone gets stuck.
- Kotter — eight steps for mobilising an entire organisation from the top.
- Prosci — a larger methodology that ties together the individual (ADKAR) and the organisation (a 3-Phase Process).
They are often set up as rivals, but they actually answer different questions. Here I compare Lewin, ADKAR and Kotter — what each is best at, and how they fit together.
What a change journey looks like on this site
I have built the site as a journey you can follow in order — or jump into wherever you are:
- Resistance — why people resist, and what you do about it.
- Motivate — how you create desire and momentum for the change.
- Plan — the frameworks and tools for structuring the work (Prosci, PCT, Kotter).
- Choose — a method for matching the right strategy and model to your specific project.
Conclusion
Change management is not fluff, and it is not a phase you bolt on at the end. It is what decides whether your investment has an effect — because it is people, not technology, who have to carry the new way of working in everyday work. Start with them, and the rest follows.
Where should I start? If you want concrete help matching the right strategy, model and tools to your specific change project, head over to Choosing the right strategy and model.