Why 70% of Transformations Fail - and What the Data Actually Shows

The Number Everyone Quotes

When you've spent time in organizational change and leadership like I have, you have undoubtedly heard this statistic hundreds if not thousands of times: 70% of change initiatives fail. McKinsey said it. Kotter said it. You can't go to a conference where the topic is change management and not hear it at least once. Tired trope? Or reality? For me, it's reality. And, with AI (change for a thing that itself is constantly changing) I would challenge that number is actually going up.

But here's the question almost no one asks: what does it actually mean to "fail" at something?

In most cases, you will find failure defined as not achieving stated objectives on the original timeline and budget. I'd call that a "miss" because by that definition, don't we all fall short time-to-time. Especially during transformation, which is RARELY linear? The "failure" framing misses a more important question and it's not "why." The question is: what can we do differently?

The People Variable

When researchers dig into root causes, the answer is remarkably consistent: it comes back to people.

It's not strategy, technology, or process design.

It's people, all day long.

Specifically:

• •Resistance to change: Because dang it, change is scary. So if they don't understand it and are communicated to, they will resist either actively, passively, where you can see it or where you don't until its too late.
• •Leadership misalignment: Sometimes the right hand doesn't know where the left is going. This isn't because of bad intention. It's about mismatched goals. Each department has a different story about what it takes to win. Meanwhile, middle management says yes not to make waves, while they quietly resist, comply, or fail to reinforce change through communication with their teams.
• •Communication gaps: When employees who don't understand why the change is happening, they are more likely to be resistant to it. People, sending an email is not change management. It's a checkbox.
• •Culture drag: You have a culture in your company. If you haven't intentionally shaped it, your people have created it. Existing norms supersede and begin to contradict the new behaviors required to make the change stick. So guess what? It doesn't.

These aren't soft issues. These are primary and predictable failures in change leadership that cost your company money. I've seen some companies lose MILLIONS because someone in charge of changing something decides to move fast and break things rather than consider all of the components of a successful change.

The Signals Are Always There First

What 20+ years of transformation work has taught me is this: organizational failure doesn't happen suddenly. It announces itself. Sometimes, you can see the signs months in advance. If you are collecting requirements for a technology purchase, this is one of the first places it will show up. These questions, light concerns, or outright comments signals that leaders fail to listen to and walk past every day in the name of progress.

I'm an innovation strategist. But I'm also a mitigator of human risk. And yes, I feel one supports (versus holds back) the other.

So what are the signs you've accidentally ignored a signal?

Turnover spikes in a key department. Decision-making slows down. Hallway conversations contradict the official narrative. Engagement survey scores drop in one team while holding steady everywhere else. Unfortunately, since you do engagement surveys once per year, your change has had months upon months to cost your company money.

These are signals. They aren't noise or coincidence.

The organizations that navigate change successfully aren't the ones with better strategies. They are simply better at listening and reading the signals they see and hear. And then, when they see or hear something, they process and course correct if need be. That's right, they are agile and responsive WHILE changing strategically.

What "Failure" Really Looks Like

In my experience, when a transformation really hits the skids, it rarely announces itself as a catastrophic event. It accumulates bit by bit. Here's the story I see often:

1. 1.The initiative launches with high energy
2. 2.Early resistance is dismissed as "normal pushback"
3. 3.Progress slows and is attributed to "the complexity" or "market conditions," sometimes someone is to blame
4. 4.Key people quietly disengage, join the blame squad, or start looking for new jobs
5. 5.The initiative is quietly rescoped, timeline extended, or its quietly shelved as a mea culpa (this one is happening A LOT in AI)

At each step, the people signals were there. The questions are: Was anyone watching for signals? Whose job is it to watch and listen? Does leadership have the framework to act on what it sees?

Assessing Your Readiness

Before any major change initiative, the single most important question is not "Is our strategy right?" Or even "Do we have the right system, policies, processes."

It's "Are our people ready to actually adopt this?"

How does this change impact our ability to win, at its best execution and at its worst?

How can we be ready if the worst occurs?

Yes, I'm proposing you keep a change risk register. A risk register is basically contingency plans. Your risk manager should have them for all sorts of scenarios in the organization where steps A, B, C, D, and sometimes all the way down to Z have been thought out. I might write another article on that in the future. But back to the assessment.

Your honest responses on your change assessment will deliver truth in structured and diagnostic way. Many of my partners, including Cloud Tech Gurus use them. Honest assessment and the willingness to keep asking questions during the change is what separates organizations that manage change from organizations that actually lead it.

The tools exist. The frameworks are proven. What's missing is the discipline to apply them before the launch, not after the first failure.

If you want to know where your organization stands, our Change Readiness Assessment takes 5 minutes and gives you a structured diagnostic across the signals that matter most.