Programme Recovery
IT programmes fail. Industry data consistently shows that more than half of all large technology programmes will exceed their budget, miss their timeline, or fail to deliver expected benefits. When a programme stalls or starts to spiral, the organisation faces a choice: continue with the same approach and hope for different results, or bring in independent programme leadership that can diagnose the problem and deliver a structured recovery.
Elisabeth Butler specialises in stepping into programmes that have gone wrong and getting them back on track. She has recovered programmes across heritage, retail, financial services, public sector, and enterprise technology, turning around situations where vendor relationships have broken down, governance has collapsed, stakeholders have lost confidence, and budgets have spiralled.
How Programme Recovery Works
Every recovery starts with an honest assessment. Elisabeth conducts a rapid programme health review that examines governance structures, vendor performance, stakeholder alignment, scope management, risk exposure, and financial status. This review typically takes two to three weeks and produces a clear picture of what went wrong, what can be salvaged, and what needs to change.
From that assessment, she builds a recovery plan with defined milestones, realistic timelines, and clear accountability. She then takes ownership of programme governance and delivery, implementing the changes needed to restore momentum and rebuild confidence.
Common Recovery Scenarios
- Vendor breakdown: When the supplier relationship has deteriorated to the point where delivery has stopped. Elisabeth separates contractual disputes from delivery work and rebuilds productive working relationships.
- Governance failure: When scope has drifted, decisions are not being made, and nobody has clear accountability. Elisabeth implements structured governance with decision making authority and change control.
- Stakeholder misalignment: When different parts of the organisation are pulling in different directions. Elisabeth realigns stakeholders under unified programme objectives.
- Budget overrun: When costs have exceeded forecasts and the board has lost visibility of where the money is going. Elisabeth conducts financial audit and implements transparent budget management.
When a Programme Needs Recovery
Programmes rarely announce that they are failing. They deteriorate through a pattern that is recognisable long before anyone uses the word recovery, and the earlier the intervention the more of the investment survives.
- The delivery date has moved more than once and nobody genuinely believes the current one.
- Status reporting says green while the people doing the work describe it privately as red.
- The same risks and issues appear in consecutive steering meetings without ever being resolved.
- Costs have moved materially beyond forecast and no one can explain precisely where.
- The vendor relationship has turned contractual and defensive rather than collaborative.
- Decisions that need a senior owner sit unmade for weeks.
- Good people have started to disengage, and some have already left.
Any two of those together usually means the programme will not correct itself.
The First Thirty Days of a Recovery
The opening phase is deliberately about diagnosis rather than action, because acting on the wrong root cause wastes the one window where the organisation is willing to accept change.
Weeks one and two are the health review: governance, vendor performance, scope control, financial position, risk exposure and stakeholder confidence, assessed independently rather than through existing reporting. That means talking to the people doing the work, not only the people reporting on it.
Week three produces the honest picture and a costed recovery plan, including what is salvageable and what is not. Week four is where governance is reset and the plan starts running, with decision making authority and change control in place before delivery is asked to accelerate.
Measurable improvement in vendor performance and reporting accuracy usually shows within the first two months. Full recovery depends on programme size and how far it has drifted.
Recovery Versus Starting Again
Boards frequently ask whether it is cheaper to stop and restart. It usually is not. The investment already made in design, configuration, data and process work normally retains real value, and a restart repeats that spend while carrying the same organisational problems into the new attempt.
What matters is that the assessment of what is salvageable is made independently, by someone with no stake in either defending the existing work or winning the rebuild.
Why Independent Recovery Works
Internal programme managers often cannot lead recovery because they are too close to the existing dynamics. The vendor sees them as part of the problem. Stakeholders have already lost confidence in their reporting. The programme manager themselves may be reluctant to deliver the honest assessment that recovery requires.
An independent programme manager brings objectivity, authority, and fresh perspective. Elisabeth has no allegiance to any vendor, no political position to protect, and no reason to tell the board anything other than the truth. This independence is what makes recovery possible.
Common Questions
What is programme recovery?
Programme recovery is the process of taking a stalled, delayed or failing programme and returning it to controlled delivery. It starts with an independent diagnosis of what has actually gone wrong, then a restructure of governance, vendor management and scope, followed by hands on leadership of the recovery through to delivery.
When should we bring in independent programme recovery?
The usual trigger points are a second slipped delivery date, a vendor relationship that has become adversarial, costs materially above forecast with no clear explanation, or a board that no longer trusts the status reporting. If the same issues appear in consecutive steering meetings without resolution, the programme is unlikely to correct itself.
How long does programme recovery take?
The diagnostic phase is typically two to three weeks and produces a costed recovery plan. Measurable improvement in vendor performance and reporting accuracy usually appears within the first two months. Full recovery depends on the size of the programme and how far it has drifted.
Is it cheaper to restart a failing programme?
Rarely. The investment already made in design, configuration, data and process work usually retains real value, and a restart repeats that spend while carrying the same organisational problems into the next attempt. The assessment of what is salvageable should be made independently before any decision.
Why can our own programme manager not lead the recovery?
Not because they lack ability. They are too close to the existing dynamics, the vendor already regards them as part of the dispute, and stakeholders have usually stopped trusting their reporting. Asking a team to diagnose its own programme rarely produces the honest assessment recovery depends on.
What sectors do you recover programmes in?
Elisabeth has recovered programmes across enterprise technology, retail, financial services, heritage and the public sector, working with organisations across the UK.
Related reading:
Related case studies:
Related services:
Need programme recovery for your programme?
Get in touch