Organizations routinely invest heavily in the technical design of a change (the new system, the new process, the new structure) and comparatively little in managing how people actually move through it. This asymmetry is a large part of why McKinsey's frequently-cited figure that roughly 70% of change initiatives fail to achieve their intended outcomes has remained stubbornly consistent for decades, across dramatically different kinds of change.
Why a good plan isn't enough
A change plan can be technically excellent, the new system genuinely better, the new process genuinely more efficient, and still fail, because organizational change isn't primarily a technical problem. It's a problem of getting a large number of individual people to alter established habits, give up familiar routines, and trust that the disruption will be worth it before they've seen the payoff. A plan that's silent on how that happens is a plan that's solved the easier half of the problem and left the harder half to chance.
What change management actually does
At its core, change management addresses three things a purely technical rollout plan doesn't:
It manages the emotional and psychological experience of change, not just its logistics. People experiencing significant change go through a genuine adjustment process, something like the stages Kübler-Ross originally described for grief, later adapted to organizational contexts: initial resistance, gradual exploration, and eventual commitment. Organizations that expect immediate enthusiasm and treat early resistance as a discipline problem rather than a normal phase tend to manage it badly, extending the disruption rather than shortening it.
It builds genuine buy-in rather than mere compliance. There's a real difference between people following a new process because they've been told to and people following it because they understand why it exists and believe it will actually help. Compliance is fragile. It evaporates the moment enforcement relaxes. Buy-in survives because it doesn't depend on enforcement. Change management done well invests specifically in building the latter, which takes more upfront communication and involvement than simply issuing the new process and expecting adoption.
It addresses the specific fears that block adoption, rather than assuming resistance is irrational. Most resistance to change is a rational response to genuine, specific concerns: will I still be competent at my job under the new system, will my role still exist, will the disruption during transition damage my performance metrics before the new way is fully working. Change management that identifies and directly addresses these specific fears, rather than issuing generic reassurance, resolves resistance faster than change management that treats all resistance as an attitude problem to be overcome through better messaging.
The actual cost of skipping it
Skipping change management doesn't make a change initiative simpler or cheaper. It shifts the cost from a planned, managed investment upfront to an unplanned, larger cost later: lower adoption, workarounds that undermine the new system's intended benefits, and a demoralized workforce that's now warier of the next change initiative because the last one was handled badly. The 70% failure statistic isn't primarily a story about bad technical decisions. It's a story about organizations that solved the technical half of the problem and treated the human half as an afterthought.