McKinsey puts the failure rate of change programs at 70 percent.
Seven out of ten.
Sit with that number for a second.
Most leaders assume failure comes down to strategy.
A weak plan, a rushed timeline, the wrong technology. Sometimes that's true. But across the transformations I've worked inside, the plan is rarely the actual problem.
The problem is what happens in people's heads and hearts while the plan is being executed.
You can build the most technically sound rollout on paper and still lose your people somewhere between the announcement and the first hard week.
The Real Reason Change Initiatives Fail
Change fails when the emotional layer gets ignored.
Leaders roll out a new system, a new structure, a new strategy, and treat resistance like a compliance issue, something to manage, minimize, or push through.
That approach might get short-term compliance. It rarely gets lasting adoption.
Here's what that looks like in practice:
Communication stops after the kickoff meeting and restarts only when adoption numbers start to look bad.
Resistance is treated as a disciplinary problem rather than a signal that something needs attention.
Managers are expected to enforce the change without being given the language or tools to process it themselves.
Success gets measured by the rollout completion date, not by whether people actually changed how they work.
Feedback loops close early.
Leadership stops asking how it's going the moment the system goes live.
The Rollout That "Worked"
Picture a mid-size healthcare system switching to a new scheduling platform.
This is a composite example, not a specific client story, but the pattern will be familiar to anyone who has run a change initiative.
The go-live date lands on schedule.
Training sessions get marked complete.
The dashboard shows 100 percent adoption within two weeks.
Leadership calls it a win and moves on to the next initiative.
Six months later, half the staff has built a workaround.
A shared spreadsheet nobody approved.
A group text thread that routes around the new system entirely.
Nothing in the original rollout data caught any of this, because adoption looked complete.
Staff logged in. They clicked the required buttons.
Nobody measured whether the change actually stuck, or whether people trusted the new system enough to stop working around it.
This is what failure looks like when a company only tracks operational metrics.
The rollout succeeded. The change didn't.
Three Patterns That Predict Failure
1. No reinforcement after go-live
Most change initiatives get heavy investment right up to launch day, then almost nothing after. Training ends.
Communication tapers off. The assumption is that people will figure out the rest on their own. Some do. Many quietly revert to old habits the first time the new way gets inconvenient.
2. Resistance treated as noise
When someone pushes back on a change, the instinct in many organizations is to shut down the objection and move forward.
That objection is usually information. It might point to a real gap in the plan, an unaddressed fear, or a past change that never got followed through on. Dismissing it doesn't make it go away.
It just makes it harder to see.
3. Managers left to absorb pressure alone
Middle managers get squeezed from both directions during a transformation.
Leadership expects them to drive adoption. Their teams expect them to have answers.
Most managers get none of the support they need to do either well, and they end up absorbing the emotional weight of the entire initiative with nowhere to put it.
What Change Enthusiasm® Does Differently
The Change Enthusiasm® methodology starts from a different premise: emotion isn't the obstacle to change. It's the fuel.
When people can name what they're feeling- fear, frustration, or genuine excitement- they move through it faster.
When leaders skip that step and go straight to execution, resistance goes underground instead of disappearing. It shows up later as slow adoption, disengagement, or attrition.
This is part of why CEG structures engagements in phases rather than as a single event.
A keynote or activation experience opens the door and builds shared language.
A Change Growth Scorecard™ assessment and leadership interviews surface where the real friction lives, by region, function, or team, instead of guessing.
Curriculum and coaching build the skill over time, so the change has somewhere to land after the initial excitement fades.
Organizations that get this right build structure for the emotional side of change, not just the operational side. Real communication, real listening, and real reinforcement after the initial rollout, not just before it.
Where to Start
You don't need to redesign your entire change management process to see a difference. Start smaller.
- Ask your team how they're actually feeling about the change, not just whether they understand it.
- Build a check-in cadence that continues well past the first 30 days after launch
- Give managers language and tools to process their own resistance before asking their teams to move through it.
- Track adoption the way you'd track a habit, not a one-time event. Are people still using the new process at 90 days, or have they drifted back?
If you want a clearer read on where your organization stands right now, the Resistance Score self-assessment takes a few minutes and gives you a starting point instead of a guess.
