Why most change initiatives fail (and it’s not the strategy)

I have sat in the room where a beautiful change plan died.

Crisp deck. Clear rationale. A roadmap with phases and owners and dates. The leadership team nodded along, somebody said “exciting,” and we shipped the announcement. Three months later, almost nobody had changed how they actually worked. The old process limped on in spreadsheets and side-channels and “let me just do it the way I always do.” The strategy was sound. The strategy was, honestly, the easy part.

I’ve been on every side of this — as the employee quietly ignoring a mandate, as the founder banging the drum, as the leader who finally understood why the drum wasn’t working. And the pattern is almost embarrassingly consistent. We fail at change not because we picked the wrong direction. We fail because we treated deciding as the finish line, when it was barely the starting gun.

The plan is the cheap part

Here’s the uncomfortable truth I keep relearning: the challenge is rarely identifying what needs to change. It’s implementing it. Knowing is not doing. Everyone in that room knew the new way was better. They could recite the benefits. And they still went back to the old way the moment they were busy, tired, or under pressure.

That’s not a strategy gap. That’s an adoption gap.

When I look back at the transformation initiatives I’ve been part of — the good, the bad, and the genuinely ugly — the ones that died didn’t die at the whiteboard. They died at the desk, in the thousand small moments where a real person had to choose the new behaviour over the comfortable old one. And in that moment, the old way almost always had the better experience.

A change initiative isn’t won in the strategy meeting. It’s won or lost a thousand times a day, in the gap between deciding and doing.

Adoption is an arc, not a memo

This is where the lens I keep coming back to changes everything. I think of every real behaviour change as an arc — the one I call DFRM: from effort to effortless. The name is a reminder of the order: Discomfort, Focus, Resilience, Mastery — DeFeRred Mastery. Mastery comes last on purpose. You defer the payoff to the end of the arc; you don’t deny it, and you never defer the work that gets you there. A change initiative has to carry people through all four stages, not drop them at the start.

Discomfort. The new way is hard the first time. New clicks, new logins, “where do I even find that now.” This is the price of admission, and it’s real. Most initiatives announce the change and then act surprised that people flinch at the discomfort — as if naming the destination removed the cost of the journey.

Focus. People can only redirect a thin sliver of energy at any one time. If you ask someone to change six habits at once, you’ve guaranteed they change none. The job is to point that limited energy at the few behaviours that actually matter and protect them from everything else competing for the same attention.

Resilience. This is the valley nobody plans for — the messy middle where effort is still high and the reward hasn’t arrived yet. The benefit of most change shows up quarters later; that’s the whole problem. People are paying the full cost up front for a payoff they can’t feel. Resistance lives here, and so does every quietly abandoned initiative.

Mastery. Eventually, with enough repetition, the new behaviour stops costing willpower. It becomes the default — the thing you’d do even if nobody was watching. This is the deferred payoff finally arriving, and the only place a change is actually done. Not when it’s approved. When it’s automatic.

Here’s the part most leaders miss: the goal of all that discipline is to make itself unnecessary. You push the new behaviour only until it becomes the easy default — and then you stop pushing, because the design is now carrying the weight instead of your willpower. A change you still have to enforce hasn’t reached mastery. It’s stuck in the valley.

So hold your last failed initiative up against that arc. For the people you asked to change, did you carry them across the valley — or did you announce the destination, skip the discomfort and the resilience, and assume mastery would happen on its own?

What resistance is actually telling you

Early on, I treated resistance as an obstacle to push through. More communication, more town halls, more “this is the new normal, folks.” It rarely worked, because I was answering a question nobody was asking.

When you peel that onion — and you have to keep asking why — the resistance is almost never about the headline change. Underneath it is fear of the unknown, a perceived loss of control, a worry about job security, a past initiative that was announced with the same confidence and then quietly abandoned. People aren’t saying “I disagree with the strategy.” They’re saying “I don’t see what’s in this for me, and I’ve been burned before.”

Which means the real work of adoption is shrinking the cost of crossing the valley — making the discomfort survivable and the payoff arrive sooner. Three things I now do deliberately:

1. Cut the friction in the new path. Every extra step is a tax you’re charging people to comply. Pre-fill the templates. Remove the redundant approval. Make the new tool the default, not an additional thing to remember. You’re not adding motivation; you’re lowering the discomfort at the start of the arc.
2. Make the payoff arrive sooner. This is how you get people through the resilience valley. Borrow a win from the present. Celebrate the first small successes out loud, publicly, by name. As I’ve seen again and again: like a ball gaining momentum, once people feel the benefit, resistance quietly fades on its own.
3. Recruit your early adopters first. In every org there are people open to new ideas and willing to take a risk — often your high performers and quiet hidden leaders. Win them, let them reach mastery first, and let proof spread sideways. A peer doing the new thing well is worth more than ten slides from leadership.

”Hope is not a strategy”

There’s a line I scribbled down years ago that still keeps me honest: hope is not a strategy. We announce a change and then hope people adopt it. We give the directive to “make it happen” and forget that a directive without support and follow-through is just pressure. If you can’t see whether the change is actually being adopted — adoption rates, real usage, honest feedback — you’re baking a cake with no recipe and no timer. You won’t know if it’s working until it’s already failed.

So I’ve stopped measuring my change initiatives by whether the plan was approved. I measure them by whether the new behaviour became the easy one — whether it crossed from effort to effortless for the person living it. That’s the whole spine of how I think about change now. Not by demanding more discipline from people forever, but by carrying them through the arc until the right thing is also the lazy thing — and then getting out of the way.

The strategy was never your problem. Your problem is that you stopped working the moment the decision was made — which is exactly the moment the hard part began.

Stop polishing the plan. Start engineering the adoption. The plan was never going to die on its own.