Why 70% of Transformations Fall Short — and What to Do About It

Where did the 70% statistic come from?

We have all seen the statistic that suggests that around 70% of transformations fail. If you are a COO about to ask the partnership for more investment in transformation, it is an uncomfortable number.

Where does it come from, and can you trust the statistic?

The 70% number comes from a book written by Michael Hammer and James Champy in 1993 called Reengineering the Corporation. Research done since the book was published has struggled to find hard evidence to substantiate the number, yet the statistic still gets frequently quoted. McKinsey's Transformation Practice continues to use the statistic, and we believe they do because the underlying issues are real.

McKinsey's own research offers suggestions as to why this is the case. In their 2021 study, Losing from Day One: Why even successful transformations fall short, fewer than one in three executives interviewed said their transformations had succeeded at both improving performance and sustaining the value delivered. This data point hasn't really moved much across more than fifteen years of their surveys. Whether the 70% statistic is totally accurate or not, it does bluntly reflect the challenges being faced when delivering transformations.

If we look at other research, we find the picture is less dramatic and more revealing than just suggesting outright transformation failure. For example, BCG's 2020 study, Flipping the Odds of Digital Transformation Success, looked at around 900 transformations and found that only 30% of transformations meet or exceed their targets. 44% created some value but missed their targets, and the remaining 26% delivered little or no value. Deloitte's 2025 study, Bridging the Tech Value Gap, involved 314 senior executives and found that organisations miss out on up to 50% of expected value, and that value is often still missing in the systems and processes being implemented.

70% of transformations don't fail, they just leave value on the table. Failing to deliver the actual value promised is the problem, and this is what we call the value-realisation gap. Organisations see this more quietly in day-to-day operations, whether a transformation programme is underway or not.

Why the usual explanation is wrong

When a transformation programme under-delivers, the lessons learned almost always reach the same conclusion. They often suggest delivery slipped, governance was weak, change and adoption were poorly managed, and people resisted. This implies that the firm simply needs to run the next programme better with tighter project management, a stronger steering committee, enhanced change management and more disciplined reporting and risk management.

This is where many firms go wrong. If you are just delivering the wrong thing better, then this does not close the value-realisation gap. The PMI's own research study Step Up in 2025 finds that the issue most respondents named was not execution capacity but the disconnect between planning and execution. This suggests the value-realisation gap opens up before execution when the project is being defined.

The gap is structural

The value-realisation gap is structural, not operational. It is built into the way transformation is typically defined, and three key factors influence it:

1. Solution-led scoping. Transformation is often framed around a thing to be delivered, such as a new practice management system, a document-automation tool, an AI pilot, a merger or a new office, rather than around the value to be recovered. The technology or the deal becomes the objective, and value is demoted to a by-product.
2. The business case that is never revisited. A business case that articulates the value to be delivered is built once, wins approval, and is then often retired. Typically, nobody returns to it to ask whether the assumptions still hold or whether the value is being realised.
3. Real value is operational and scattered rather than concentrated in any one place. Value doesn't sit in a single system waiting to be switched on. It might be the productivity a new system was meant to deliver but never did, or the synergies a merger promised but never realised, as much as the quieter day-to-day operational leakage. These are exactly the places a single programme is least equipped to reach, because no one part of the firm owns them.

Put those three factors together, and you've got a firm committing real partner money and its scarce appetite for change before anyone has worked out where the recoverable value even is. The gap is there on day one, it's defined in the scope. Everything after that is delivery of a plan that was aimed slightly wrong from the start, which is why no amount of delivery discipline rescues it, and arguably why that McKinsey headline figure hasn't budged in fifteen years.

What actually closes the value-realisation gap?

If the gap opens when the transformation gets defined, that is where it must be closed, before the firm commits a penny to changing anything. Most COOs would agree with that in principle, but it doesn't always survive contact with the firm.

The pressure usually runs the other way. A competitor buys a new platform, a vendor runs a persuasive roadshow, a partner wants the firm seen to be doing something about AI, and the conversation reorganises itself around a system before anyone has pinned down the value the firm is chasing. The value case loses to the technology case not because it is weaker, but because it is vaguer, often because it's spread across the operation, and nobody has put a number on it.

In our view, that is the first move, and it is where an outside diagnosis earns its place.

Take two fictitious firms. The first spent well over a million pounds on a new practice management platform two years ago. It went live on time and on budget, and the efficiency it was sold on has never shown up in the numbers. The instinct is to conclude the system failed. The hard work is to find where the value actually went: some trapped in how the platform was adopted, some in the matter margin and lock-up the programme never touched, some in fee-earner hours still lost to admin the tool was meant to remove.

The second completed a merger three years ago; the combined firm is bigger, but the cross-selling and cost synergies that justified the deal have quietly failed to appear, and nobody has gone back to ask why. Here the work is the same: separate the value that is unrecoverable from the value still sitting in duplicated processes, unharmonised systems, and clients who could be served by more of the firm but are not.

In both cases, the discipline is the same, to put a number on it: the days of lock-up that could be recovered, the margin being written off, the synergy that was promised and is still within reach. A number does something a well-argued opinion cannot. It gives the partnership a baseline it can engage with, and it moves the opinion away from whoever happens to be loudest.

Then the question is why, because the why decides the solution. A margin leak that is really a pricing-governance problem needs a different answer than one rooted in a matter-opening process, or in reporting that never puts matter profitability in front of partners. Nearly every leak traces back to at least one of six places: governance, process, people, technology, data or reporting. Only rarely is the answer "buy a system," which is why leading with technology can often disappoint.

Once the leaks are named and sized, prioritisation is straightforward. Weigh each opportunity on two dimensions at once: how much value is recoverable, and the feasibility of recovering it given the firm's processes, systems, data, and appetite for change. The quick wins, the foundational fixes, the bigger investments that take a year, they all fall into a sequence: credible wins first, and an ongoing roadmap the partnership buys into and owns.

None of this is elaborate, and most of it is unglamorous, but it is the difference between committing to a transformation and knowing precisely why. Our part is to bring the independence and the rigour to get it done to a standard the partnership cannot dismiss, and to keep the value question front-of-mind while the noise argues about technology.

Where Morphis comes in

This is the job we built Morphis to do. Our Diagnostic is a structured, evidence-based way of doing exactly what we've just described above, Operational Value Recovery for professional services firms. It finds the leaks, sizes them, works out what's causing them, and hands you a prioritised Value Recovery Roadmap you can walk straight into a partners meeting with, from the fast wins through to the elements that take longer. We honestly don't mind which system you end up buying. Our job is to make sure whatever value you chase is value we've already proven is there.

Because the gap can open at almost any point, people tend to come to us at one of three moments.

1. You've already spent the money. The transformation went live, but the business case never quite showed up. We go in, find the value that's still trapped inside it, and work out how to get it out. Given 44% of programmes land some value but miss the target, there's usually more stuck in there than anyone expects.
2. You're weighing up a major decision. Before you commit money and change capacity to something new, you want to know that the value is really there and that the plan will recover it. Better to find that out now than eighteen months in when the investment has been spent.
3. You just want strategic clarity. No programme in mind at all, but the day-to-day is leaking value whether you run a transformation programme or not. We show you where, how much, and what to fix first, so the partnership can move on evidence instead of a hunch.

The firms that close this gap, in our experience, usually aren't the ones with the slickest project managers. They're the ones stubborn enough not to move until they can see where the value is that they are trying to recover. That's worth doing whether your last programme fell short, your next one is already on the table, or you've just got a nagging feeling there's value you are leaving behind.