Transformations fail when the "why" is missing

Why most ways of working transformations fail

The reason your digital, cultural, or ways of working transformation is failing (or has already failed) probably isn’t because you chose the wrong framework. It is far more likely that the case for change was never clear enough in the first place.

Across organisations I work with, I see familiar patterns. The change is often:

• Not emotionally compelling
• Not operationally grounded
• Not measurable

A couple of weeks ago at the #AgileNotts meetup, I was talking with a technology leader and an experienced transformation consultant. Over pizza and a beer we ended up in a passionate discussion about why transformations feel so hard and why so many of them fail. Since then, I’ve seen similar debates play out online and in conversations with leaders across industries.

It feels like a common problem and the data backs it up.

• Around 70% of digital transformations fall short of their objectives according to McKinsey & Company and Boston Consulting Group.
• The State of Agile report from Digital.ai shows that while over 90% of organisations say they use Agile, far fewer report meaningful improvements in time-to-market, predictability, or strategic alignment.
• Billions are spent each year on change initiatives that underdeliver.

Adoption is widespread. Outcomes are not.

That aligns closely with what I see in large, complex organisations.

Where it goes wrong

In my experience, most transformations start with “how”. Leaders announce that they are:

• Implementing some framework (e.g. SAFe)
• Becoming product-led
• Adopting OKRs
• Launching an AI strategy

These may or may not be sensible decisions. But they are implementation choices, not a case for change.

What is often missing is a much simpler question: What measurable problem are we trying to solve?

Without clarity on that point:

• There is no clear purpose.
• There is no anchor for prioritisation.
• Trade-offs become political rather than strategic.
• Success cannot be objectively assessed.

As Peter Drucker famously said, “What gets measured gets managed.” If nothing meaningful is being measured, it is unsurprising that nothing meaningful changes.

The result is a transformation that becomes activity-led rather than outcome-led. There are workshops, new job titles, re-labelled artefacts, training programmes and consultants. Lots of money is invested. People are very busy and often working hard. Yet the underlying performance of the organisation does not materially shift.

Eventually someone senior asks, “What has actually improved?”

When there isn’t a clear answer, the energy drains away. The transformation is labelled a failure. And whatever framework was being implemented becomes “dead”. You’ve all seen the posts.

What a real “why” looks like

A serious transformation starts with a performance gap, not a framework.

For example:

• Time-to-market is 14 months. Competitors deliver in 6.
• 40% of released features see little or no customer adoption.
• Delivery predictability varies by ±35%.
• Employee engagement is at 30% and declining.

Those are tangible problems. People understand them.

From there, the organisation defines what will be different:

• Cut concept-to-cash by 50%
• Increase feature adoption to 75%
• Reduce delivery variance to under 20%
• Achieve this within an 18-month horizon, with quarterly evidence of progress

At that point, the transformation has a spine. It becomes about improving business capability in measurable terms, not about installing a method.

Communication and understanding shifts. Instead of “we’re implementing Agile at scale”, it becomes “we are too slow, too unpredictable, and delivering too much low-value work. Now we are going to fix that.”

That clarity creates focus. It creates urgency. And in my experience, it leads to better decisions because people understand the outcomes they are trying to achieve.

The takeaway

Ways of working are means, not ends.

If the measurable ambition is not explicit:

• Teams optimise locally (AKA The Wild Wild West).
• Leaders revert under pressure.
• Governance remains output-focused.
• Resistance grows because the benefits are abstract.
• People stay busy, but performance does not materially improve.

And eventually the story becomes familiar. Think of how many times you hear something like: “We tried Agile. It didn’t work here.” Then, the inevitable "Agile is dead" sentiment.

More often than not, Agile wasn’t the issue.

The why was never defined clearly enough to matter. The governance still rewarded the old behaviours. The system stayed the same.

If it doesn’t change measurable outcomes, it isn’t transformation.

It’s just new labels on old ways of working.

#BusinessTransformation #AgileLeadership #DigitalTransformation #StrategyExecution #EnterpriseAgility