Why change management isn't just a tick in a box
Change management is often treated as a box to tick before go-live: send the announcement email, run the training, done. That's the version that doesn't work. A project only pays off if people actually change how they work, and that takes more than a tick.
It went live. Nobody used it.
You've probably seen this already, or you will soon:
- The new system goes live on time and on budget.
- Six months later, half the team still does the real work in a spreadsheet.
- Someone starts a second project to "fix adoption".
Nothing was wrong with the technology. What went wrong was that the people who had to use it were treated as an afterthought. That's the part change management covers, and it's why it matters as much as the build itself.
The numbers your manager will want
If you need to justify spending time on the people side, two figures do most of the work.
Most big changes fall short. McKinsey has said for years that about 70% of large transformations fail to deliver what they promised (McKinsey). The reasons it lists are mostly about people: they weren't convinced, didn't buy in, or slid back into old habits.
Doing the people side well changes the odds. Prosci's research found that 88% of projects with excellent change management met or beat their objectives. With poor change management, it was 13%, about one in eight (Prosci).
You don't need to be excellent to see a difference. The same research shows success jumping from 39% to 73% just by going from fair to good. Doing the basics properly is most of the gain.
Resistance is normal, and predictable
When people push back on a change, it's tempting to read it as a bad attitude. It usually isn't. People rarely resist the change itself. They resist what it costs them, and those costs are easy to predict:
- Competence. The expert in the old way becomes a beginner in the new one.
- Control. Decisions they used to make get made by a system or someone else.
- Status. The "go-to person" loses the reason people came to them.
- Workload. Learning the new way is extra work on top of the day job.
- Certainty. Nobody has told them what their role looks like afterwards.
If you can name what each group is losing, you can do something about it before it turns into workarounds and complaints. That is most of the job.
One more thing to watch: the people others listen to aren't always the ones on the org chart. A respected supervisor or long-serving team member can carry a change, or quietly sink it.
What to do tomorrow
You don't need a methodology to start. Five things will put you ahead of most projects:
- Find the business case and note which benefits depend on people working differently.
- List every group affected and write one line on what each one loses.
- Name three people outside the formal hierarchy whose opinion others follow.
- Ask your sponsor what they will personally say about the change in the next month.
- Agree one measure of whether people are actually using the change after go-live.
That last one matters most. "Training delivered" tells you what you did. Usage tells you whether it worked.
More than a tick
Change management done as a box to tick happens anyway, just later and at a higher price, under names like "adoption issues" or "phase two". Done properly, it's the part of the project that decides whether the rest pays off.
Want to see where your people stand? Try the free Readiness check on ChangeOS.
Taking this to your board? Read The Hard Math of Soft Skills next. It covers the business-case arithmetic, where the evidence is weaker than it looks, and a one-slide framework for sponsors.