Why transformation programmes stall at month nine

Executive summary

Most multi-year programmes do not fail. They stall — and stalling is worse, because a failed programme is cancelled and a stalled one keeps consuming budget while everyone involved privately re-forecasts the date. This report describes the pattern we see most often, why it clusters around the third quarter of a programme, and the three governance decisions that separate the programmes that recover from those that quietly reset.

A programme that cannot change scope is not a programme. It is a schedule with a budget attached.

The pattern

Months one to six run close to plan. Somewhere in months seven to nine the reported status stops matching the felt status. Decisions begin to queue. The programme enters a phase in which everyone knows the date has moved and nobody has the standing to say so in the room where it would matter. The Standish data is blunt about how this ends: fewer than one in ten large projects finish on time, on budget and on scope, and half of all projects are classed as challenged rather than failed — which is the polite word for stalled.

Why the third quarter

Because that is roughly when the first genuinely hard trade-off arrives — the decision where something has to give and the person with authority to give it is not present. Before that point every decision has sat inside someone's delegated authority. EY and Oxford's Saïd Business School found that 96% of transformation programmes experience at least one such turning point. What distinguished the programmes that went on to beat their KPIs was not the absence of a crisis but how leadership behaved inside it — those that kept people at the centre were almost twice as likely to outperform.

What it is not

It is almost never the technology. Vendor platforms are, by month nine, either working or visibly not working, and both are manageable. What is not manageable is a decision queue with nobody empowered to clear it. BCG's finding that only one transformation in four delivers enduring value is not a statement about software. It is a statement about the governance that surrounds it.

Adding reporting does not help. The information is already in the deck, in a colour nobody escalates.

The three decisions

First, a cadence that surfaces slippage in weeks, not quarters. Not more reporting — a shorter loop between a variance appearing and a named person seeing it. Second, one person with the authority to change scope, who attends. In most programmes there is a steering committee and no one whose job it is to say the date has moved. Third, business acumen inside the delivery team rather than above it. PMI's 2025 data shows only 18% of project professionals rate highly on business acumen — and that the teams that do meet their business goals 83% of the time, on schedule 63% of the time, on budget 73% of the time. The gap between those two groups is most of the gap between stalled and delivered.

What a CEO should ask this quarter

Who, by name, can change the scope of our largest programme without convening a committee? When did the reported status and the felt status last disagree, and who noticed first? What decision has been waiting longest, and why? If the answers are 'the steering committee', 'they have not', and 'nothing', the programme is at month nine whatever the calendar says.

The uncomfortable part

Somebody has to tell the steering committee the date has moved. In most programmes there is no one whose job that is — a structural gap, not a personal failing. It is also one of the more valuable things an outside firm can do, precisely because we are not staying.