Delivery leadership: Why transformation programmes go wrong – and what the best leaders do differently

At a glance

Transformation programmes rarely fail because of technology. They fail when alignment across stakeholders, priorities and business outcomes is assumed rather than actively maintained. Drawing on more than 25 years of delivery experience, Sullivan & Stanley's Delivery Director Richard Emmett sets out why delivery is fundamentally about trust, why large programmes carry exponential rather than incremental risk and why the best leaders think slow before they act fast, then move faster with fewer setbacks once execution begins.

Key terms

The Six Rs of Delivery: a framework describing the organisational assets that successful delivery strengthens: Relationships, Reliability, Reputation, Revenue, Recognition and Rewards.

Fat-tailed risk: a statistical pattern where most outcomes cluster around a modest range, but a small number of extreme outliers occur far more often than a normal distribution would predict. In transformation programmes, this means most overruns are manageable, but a small proportion escalate catastrophically.

Benefits realisation: the ongoing work of converting a delivered output (a platform, migration or product) into measurable business value through adoption, behavioural change and operational improvement.

For all the advances in technology, delivery remains one of the biggest challenges facing organisations.

Digital transformation has been a boardroom priority for well over a decade, yet the success rates remain stubbornly low. McKinsey estimates that fewer than 30% of digital transformations succeed.¹ Sullivan & Stanley's own 2026 research found that just 7% of organisations consistently realise the value set out in their original business case,² while MIT research suggests that 95% of generative AI pilots fail to scale into meaningful business outcomes.³

These aren't simply statistics. They represent delayed strategies, frustrated teams, unrealised investment and leaders under increasing pressure to deliver measurable outcomes.

These themes formed the basis of our Community virtual event, where Delivery Director, Richard Emmett, shared practical lessons from more than 25 years leading complex transformation programmes across industries.

Rather than discussing project management techniques, the session explored a more fundamental question:

Why do so many delivery programmes still fail, and what can leaders do differently?

Delivery is ultimately about trust

Projects are often measured by time, cost and scope. They're useful metrics, but they rarely capture what successful delivery creates.

Richard introduced what he describes as the Six Rs of Delivery, arguing that every successful programme strengthens six organisational assets:

• Relationships
• Reliability
• Reputation
• Revenue
• Recognition
• Rewards

When delivery succeeds consistently, organisations earn trust. Teams become more confident, leaders make decisions with greater certainty, customers stay loyal and future investment becomes easier to secure.

The opposite is equally true. Failed delivery doesn't just consume budget. It erodes confidence. By the time a programme appears in the board report as "red", much of the damage has already been done.

The causes of failure are rarely technical

One of the most valuable parts of the session came from the audience itself.

Senior delivery and transformation leaders reflected on recent programmes and shared what had caused projects to drift off course.

Although every organisation was different, remarkably similar themes emerged:

• Stakeholders becoming misaligned as programmes progressed
• Leadership priorities changing midway through delivery
• Benefits becoming secondary to delivering outputs
• Teams implementing technology before the business was ready to adopt it
• Organisational resistance slowing decision making
• Constant reprioritisation creating uncertainty
• Unrealistic timescales and optimistic planning assumptions

Very few people cited technology as the primary issue. Instead, the discussion repeatedly returned to something more human. Delivery problems are often symptoms rather than causes. Beneath missed milestones usually sit competing priorities, unclear expectations, organisational politics, behavioural challenges and a gradual loss of alignment across the programme.

These are significantly harder to identify than a delayed sprint or an overspent budget, but they are often the factors that determine whether a transformation ultimately succeeds.

The uncomfortable reality about large programmes

Richard drew on research from Bent Flyvbjerg and Dan Gardner's How Big Things Get Done, which analysed more than 16,000 projects across 136 countries and 25 industries. Their findings challenge many of the assumptions leaders make about delivery performance.

Only around 9% of projects were delivered on time and on budget, while just 0.5% achieved all three measures of success: on time, on budget and delivering their intended benefits.

Perhaps even more striking was the discussion around risk. Most organisations plan around average cost overruns. The problem is that transformation programmes don't behave like averages.

Large programmes are what statisticians describe as fat-tailed. Most projects may experience relatively modest overruns, but a small number become catastrophic, with costs escalating far beyond anything originally anticipated. Examples such as Boston's Big Dig, the James Webb Space Telescope and Scotland's Parliament building demonstrate that the greatest delivery risks are rarely incremental. They are exponential.

For delivery leaders, this changes the conversation. The objective isn't simply to manage delivery more efficiently. It's to recognise risks earlier, while changing direction is still relatively inexpensive.

Think slow. Act fast.

One of the central ideas throughout the session was a deceptively simple principle:

Think slow. Act fast.

It challenges one of the most common behaviours seen across transformation programmes. Under pressure to deliver quickly, organisations often rush into mobilisation before sufficiently understanding the problem they're trying to solve.

• Discovery is compressed.
• Stakeholder alignment is assumed.
• Business cases become optimistic.
• Programmes begin before the organisation is ready.

Ironically, this urgency frequently creates slower delivery.

The most successful programmes spend more time upfront aligning objectives, testing assumptions, understanding risks and defining outcomes. Once that thinking has been completed, execution accelerates because fewer fundamental decisions need revisiting later.

As Richard explained during the session, slowing down at the beginning often allows organisations to move significantly faster once delivery starts.

Alignment is a leadership discipline

If one word consistently surfaced throughout the discussion, it was alignment.

Alignment is often treated as something that happens during programme initiation before attention shifts to delivery. In reality, alignment requires continual maintenance.

Leaders must continually ensure that multiple elements remain connected:

• Strategic objectives
• Stakeholder expectations
• Benefits and business outcomes
• Financial assumptions
• Programme scope
• Delivery plans
• Team capability

These elements rarely drift apart overnight. Misalignment develops gradually as organisations change, priorities evolve and external conditions shift. Strong delivery leaders don't assume alignment continues but actively create it through regular conversations, governance, transparent decision making and continual communication.

Great delivery extends beyond implementation

One observation resonated strongly throughout the audience discussion.

Many organisations remain excellent at delivering outputs but far fewer consistently realise outcomes. Projects successfully deploy new platforms, complete migrations or launch products, yet months later the expected business value has still not materialised.

Benefits realisation often receives considerably less attention than delivery itself. That creates an important shift in how delivery should be viewed.

The objective isn't simply to finish programmes but to create measurable organisational value. That requires continued focus after implementation through adoption, behavioural change, operational improvement and continuous learning.

Delivery doesn't end when the technology goes live. In many ways, that's where value creation truly begins.

If the themes explored here sound familiar, you're not alone. Almost every organisation we work with is under pressure to deliver more change, more quickly, while proving tangible business value.

At Sullivan & Stanley, we help organisations improve delivery capability, recover struggling programmes and build the leadership, governance and ways of working needed to deliver transformation with greater confidence. Whether you're establishing a new delivery function, strengthening programme leadership or looking to realise more value from your existing portfolio, we'd be delighted to continue the conversation.

To learn more about how we help organisations deliver successful transformation, explore our Change & Delivery services or get in touch with one of our team.

About Richard Emmett

Richard Emmett is Delivery Director at Sullivan & Stanley, with more than 25 years leading complex transformation programmes across industries. He is a regular contributor to Sullivan & Stanley's Community events, sharing practical, experience-led perspectives on why delivery succeeds or fails.

¹ McKinsey & Company, Unlocking Success in Digital Transformations, 2018
² The Intelligent Enterprise: Turning Ambitions into Outcomes that Last, Sullivan & Stanley, 2026
³ MIT, State of AI in Business 2025, 2025
How Big Things Get Done: The Surprising Factors Behind Every Successful Project…”, Flyvbjerg & Gardner, 2024