Change management and project management are often confused – or one is assumed to contain the other. But they answer two different questions. Project management is about building and delivering the solution: the right thing, on time, within budget. Change management is about getting people to actually adopt and use that solution. Two disciplines, one goal – and it is only when both are in place that the change delivers the benefits you counted on.
The difference in short
Project management is the technical side. It answers the question of what is to be built and delivered – the new system, the new organisation, the new process. The focus is on scope, timeline, resources, dependencies and deliverables. The project is done when the solution is in place.
Change management is the people side. It answers the question of how people move from the old to the new – understand why, want to take part, know how, be able to in practice, and keep it up over time. The focus is on understanding, motivation, resistance management, communication, training and reinforcement. The change is done only when the new way of working has truly taken hold.
One way to remember it: the project delivers the solution, change management delivers the adoption.
The PCT Model – why you need both
Prosci’s PCT Model puts its finger on exactly this. PCT is a triangle with three sides that must all be present for a change to succeed: leadership and sponsorship at the top (direction and mandate), project management on one side (the technical solution) and change management on the other (the people’s journey). Remove one of the sides and it collapses: a solution without buy-in goes unused, buy-in without a solution is just talk, and both without clear leadership lose momentum.
The point is that project management and change management do not compete – they are two sides of the same triangle. You can read more about the PCT Model and the whole Prosci methodology in the Plan section.
What the project manager owns – and what the change manager owns
The project manager is responsible for:
- scope, objectives and boundaries
- timeline, milestones and budget
- resources, roles and dependencies
- the technical delivery and the quality of the solution
- project risk and steering towards the goal
The change manager is responsible for:
- urgency and understanding – why are we doing this?
- desire and motivation among those affected
- communication and dialogue throughout the journey
- training so that people are able to work the new way
- resistance management and support for front-line managers
- reinforcement so the new way lasts after the project closes
If you recognise the steps understand – want – know – able – last, that is no coincidence: it is the ADKAR model, which describes precisely the individual’s journey through a change.
What happens when one is missing?
The most common – and most expensive – mistake is to run the project management flawlessly but forget the change management. The result is the classic story: 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.
Prosci’s research is clear on this point: projects with good change management meet their objectives to a significantly greater degree than those without it. That is hardly surprising – after all, it is people, not technology, who have to carry the new way of working in their everyday work.
Same person or two roles?
In smaller projects the project manager often wears both hats, and that works fine as long as the person is aware that the people side needs its own time and its own activities – not just a line in the project plan.
But the larger and more people-affecting the change is, the stronger the case for separating the roles. The project manager has their hands full getting the solution in place; that is when you need someone who genuinely owns adoption. My rule of thumb: when the change affects many people’s everyday work, stirs emotions or requires new behaviours – then change management needs its own owner and its own plan.
How I work
I see change management as something that runs in parallel with the project from day one – not as an implementation phase you bolt on at the end. While the project builds the solution, change management works on urgency, communication and the managers’ role, so that the organisation is ready when the solution finally lands. In practice I like to use a selected change management model (e.g. Kotter) for the organisational leadership and ADKAR for the individuals’ journey, side by side with the project timeline.
Conclusion
Project management delivers the solution. Change management delivers the adoption – and with it, the benefit. They are not the same thing, and one does not replace the other. If you want your investment to have an effect, you need both sides of the triangle – and leadership that holds them together.
Which model should I choose? 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.