"Change management" means two different things in delivery — and great PMs handle both. One protects the plan; the other makes the outcome stick.
1. Change control (managing changes to the project)
As soon as a plan is baselined, requests to alter scope, time or cost will arrive. Change control is the process that stops these becoming chaos:
- Raise a change request (what, why, requested by).
- Assess the impact on the Iron Triangle (scope, time, cost) and risk.
- Decide — a Change Control Board (CCB) or the sponsor approves, rejects or defers.
- Update the baseline and communicate. Change control doesn't block change — it makes it visible and deliberate, protecting the project from silent scope creep.
2. Organisational change management (making change stick)
Delivering the product is only half the job — people have to adopt it. Change management is the discipline of moving people from the current to the future state. Two widely used models:
ADKAR — individuals change in a sequence:
- Awareness of the need to change, Desire to support it, Knowledge of how, Ability to do it, Reinforcement to sustain it. If adoption stalls, diagnose which step is missing.
Kotter's 8 Steps — for leading organisational change:
- Create urgency, 2. Build a guiding coalition, 3. Form a vision, 4. Communicate the vision, 5. Remove barriers/empower action, 6. Generate short-term wins, 7. Sustain acceleration, 8. Anchor the change in the culture.
Why it matters
Most "failed" projects delivered the product but failed on adoption — people carried on the old way. Planning for the human side (communication, training, reinforcement) is what turns a delivered output into a realised benefit.
Put it to work
For a change you're delivering, run a quick ADKAR check — which step is weakest for your users? — and add actions to your communication plan to close the gap.
