How Change Management Delivers Benefits
Change management delivers benefits by helping people adopt a change, use it fully and use it well, because most benefits of a new system, process or structure appear only through changed behavior. Going live is not the same as realizing benefits. Change management raises the speed and depth of adoption, and so the share of expected benefits achieved.
Quick facts
- Type
- Concept (link between change management and benefits realization)
- Origin
- Benefits management practice, e.g. Ward & Daniel's benefits dependency network; project and programme management
- Used when
- Building a business case, planning adoption, or explaining why benefits are lagging
- Related models
- Kelman's levels of adoption · Diffusion of innovations · Readiness and adoption metrics
- Exam relevance
- APMG CM Foundation, Organizational Context & Approach (OA0201)
Why do the benefits of a change depend on people?
A project delivers a capability: a system, a process, a structure. The organization gains value only when people work differently because of it. A reporting tool that nobody trusts saves no time, and a new process that teams work around improves no results.
Benefits management writers make this point explicitly. Ward and Daniel map the changes that must happen for a technology investment to produce benefits. Many of those changes are changes in behavior: new routines, decisions made with new information, old workarounds given up. A business case that lists benefits without naming who must work differently is missing its main assumption.
The benefits of change management therefore come from closing the gap between what a project delivers and what people actually do.
How do adoption, utilization and proficiency affect benefits?
Three questions, which echo Prosci's speed of adoption, ultimate utilization and proficiency, describe how far a change has taken hold:
- Adoption: are people using the new way at all, and how quickly did they start?
- Utilization: are they using it fully, or keeping old methods alongside it?
- Proficiency: are they using it well, with few errors and workarounds?
A shortfall in any of the three reduces the benefits. Slow adoption delays them; partial utilization caps them; low proficiency erodes them.
At Larchfield Logistics, a new warehouse picking system goes live on time. Six weeks later, most pickers use it, but some still print paper lists for busy shifts, and new starters make frequent scanning errors. The expected gains in accuracy and speed appear only in part.
Benefits therefore track how people use a change, not whether it was installed.
Where does change management contribute to benefits realization?
- Business case: identify which benefits depend on behavior change, and who has to change.
- Planning: plan the readiness, training and support those people need.
- Transition: build understanding and skills, and remove barriers to using the new way.
- After go-live: track adoption, reinforce the new behaviors and retire old methods.
- Handover: pass ownership of benefits and of continued support to line managers.
Benefits often appear after the project has closed, so this support must not stop at go-live. Each benefit usually has a business owner, often a senior line manager; the change team supports that owner rather than taking the role over.
Change management therefore contributes to benefits across the whole life of a change, not only at launch.
What are common mistakes in linking change management to benefits?
- Treating go-live as success. Delivery on time and within budget shows that the project was completed, not that benefits were achieved.
- Treating adoption as the benefit. Adoption is a leading indicator; benefits still need their own tracking.
- Claiming all the credit. Benefits depend on the solution, the market and many other factors, so change management contributes to them rather than producing them alone.
- Stopping support too early, before new behaviors are stable and before line managers are ready to own them.
Linking change management to benefits therefore needs honest measures for both adoption and outcomes.
Benefits of change management vs. readiness and adoption metrics: what is the difference?
| How change management delivers benefits | Readiness and adoption metrics | |
|---|---|---|
| Question | Why does change management add value? | How do we measure progress toward that value? |
| Focus | The causal link from behavior to benefits | Indicators before and after go-live |
| Main use | Business case and planning | Steering the change and reporting results |
| Typical output | The behavior changes each benefit depends on | Readiness scores, usage data and benefit measures |
The first explains why benefits depend on people; the second measures whether that dependency is being met.
Exam focus
At Foundation level (OA0201) expect comprehension of why change management contributes to benefits: most benefits are realized only when people adopt the change and use it fully and well. A common trap assumes benefits arrive at go-live, treats adoption and benefits as the same measure, or casts change management as a cost-cutting function.
Practise this syllabus area →FAQ
How does change management contribute to benefits realization?
Change management helps people adopt a change, use it fully and use it well. Because most benefits of a new system, process or structure depend on that behavior, raising the speed and depth of adoption raises the share of expected benefits the organization actually achieves.
Are benefits realized when a system goes live?
Usually not. Going live means the capability exists. Benefits such as time saved, fewer errors or better service appear only when people use the system as intended, which can take weeks or months. That is why support and tracking should continue after go-live.
Is adoption the same as benefits?
No. Adoption measures whether and how people use a change; benefits measure the outcomes the change was meant to deliver. Adoption is a leading indicator of benefits, but a change can be widely adopted and still fall short, so both need to be tracked.
What happens to benefits if people keep using the old way?
Benefits are put at risk. If people run old and new methods side by side, the change is used only partly, so expected gains in time, accuracy or cost are unlikely to appear, and running two ways of working can even add cost.
Sources
- Ward, J. & Daniel, E. (2012). Benefits Management: How to Increase the Business Value of Your IT Projects (2nd ed.). Wiley.
- Serra, C. E. M. & Kunc, M. (2015). Benefits Realisation Management and its influence on project success and on the execution of business strategies. International Journal of Project Management, 33(1), 53–66.
- APMG International — Change Management certification (syllabus topic OA0201)
- Last reviewed