Why Transformation Programmes Stall, And What Nobody Wants to Name

When a multimillion euro transformation stalls, the instinct is to fix the execution. Sometimes the harder question is whether the organisation is ready at all.

We were recently brought in to fill two roles inside a program, a running multiyear multimillion euro effort to move a company off its legacy infrastructure. The program had delivered early milestones, but had stalled. The question on the table was how to fix it. Within weeks, we realised that was the wrong question entirely.

Instead of filling the roles focused on program and product delivery, we assessed the whole program and identified 30+ structural risks and limitations that held the program back. During a four week period we interviewed product managers, architects and business representatives to come up with the risk overview, and an adjusted-for-risks roadmap. The biggest conclusions didn’t point to technical failures, but to organisational readiness, change capacity, leadership alignment and priority setting. The program had its technical challenges, but the organisation wasn’t in a position to absorb what the program required. That was an outcome that was commercially uncomfortable to deliver, but needed to be shared.

Our observations triggered a broader conversation with the MT, and shifted the nature of questions to entirely different ground. Questions shifted to: Are we ready for a change of this magnitude at all? What actually drives our competitive advantage, and do we need this new platform to protect it? The client’s MT took a brave decision to change the mindset and investment decision, the initiative’s scope and setup, which ultimately gave them a choice about how to approach the company’s future ambitions that the original program framing had closed off.

This pattern is more common than organisations admit. Digital transformations often underdeliver, and when they do are treated as execution problems: wrong methodology, wrong team, wrong vendor. The harder diagnosis is that more often than not, the organisation itself isn’t ready for the changes that are needed. Unfortunately, this rarely gets named, because naming it requires someone with no stake in the program to ask the very difficult questions. That’s precisely where an external perspective changes the outcome.

When programs aren’t delivering, is your organisation asking questions on how to fix it, or whether it should be running at all? And are you asking those questions of the vendors with a thick stake in continuation, or an independent advisor with nothing to protect?

If this pattern sounds familiar, we'd welcome the conversation.