Project One Programme Assurance v1.1

The reality of transformation today

Modern programmes are:

Multi-year and multi-vendor Deeply integrated across business and technology Dependent on scarce skills Exposed to regulatory, cyber and operational risk Highly visible at board and executive level.

Why programmes fail

When programmes struggle, the root causes are rarely technical. In our experience, failure most often stems from a combination of human, structural and commercial factors that go

At the same time, reporting has become more polished than ever. Dashboards are slick. Status papers are reassuring, but milestones are often presented as binary events rather than indicators of true readiness. This creates a dangerous gap between perceived control and actual control. Many programmes report “green” right up until the moment they no longer are, when costs escalate, delivery slips or confidence collapses. By then, the options available to leadership are limited and expensive. Transformation rarely fails suddenly. It drifts. And drift is hard to spot when you’re so close to the programme.

unchallenged for too long. Common patterns include:

Optimism bias: progress believed to be further along than it is Confirmation bias: reports reinforcing the narrative people want to hear Supplier dependency: delivery partners marking their own homework Decision avoidance: complex issues repeatedly escalated but not resolved Weak benefits ownership: outcomes assumed rather than actively driven. None of these are signs of incompetence. They are natural by-products of pressure, complexity and proximity. The closer teams are to delivery, the harder it becomes to step back and ask the most important question: “Are we genuinely on track, or just busy?”

4

5

real change • real difference

Made with FlippingBook - PDF hosting