The Recovery Roadmap.
When a technology program starts showing signs of trouble, the instinct is to act fast. But speed without structure often makes things worse—more meetings, more pressure, more resources thrown at a problem nobody has actually diagnosed yet.
The result is a program that feels like it's moving, but is actually drifting further from control.When is it Time to Step in?
Certain signals tend to show up well before a program reaches crisis point. Milestones get rebaselined again and again. Vendors become harder to hold accountable. Confidence in status reports starts to erode—numbers look fine, but nobody quite believes them. Sponsors escalate more frequently, and risk exposure grows faster than anyone is mitigating it.
None of these signals mean a program is beyond saving. But the earlier they're addressed, the cheaper and less disruptive recovery becomes.Establishing the Ground Truth.
Before anything changes, the priority is understanding exactly where things stand. This means reviewing contracts, statements of work, risk logs, financial forecasts, and delivery plans—not as a paperwork exercise, but to build an accurate picture of commitments versus reality.
Just as important are structured conversations with the sponsor, delivery leads, and key vendors. People closest to a struggling program often have the clearest sense of what's wrong, but rarely get asked directly. This phase also looks at governance maturity, the integrity of existing reporting, exposure on the critical path, and any technical shortcuts that have quietly accumulated.The outcome is an honest health check: a clear picture of risk across governance, commercial, delivery, and technical dimensions, plus an initial list of what needs to be contained immediately. At this point, transparency goes up and emotion comes down—which is exactly the shift needed before any decisions are made.
Stop the Bleeding.
With a clear picture in hand, the next priority is to stop things getting worse before working on making them better. This means freezing any non-essential scope changes, locking down the critical path once it's been validated, and replacing complicated or unreliable reporting with something simple and objective.
Material risks get escalated to the sponsor with actual decision deadlines—not left to drift. And critically, a single person is made accountable for delivery, rather than responsibility being spread so thin that no one really owns it.
By the end of this phase, executives have real visibility again, and decisions are being made deliberately rather than reactively.
Resetting the Foundations.
This is often where recovery efforts stall—because it requires leadership to make hard calls rather than soft compromises. The delivery plan gets rebuilt around what the team can actually deliver, not what was originally hoped for. Vendor expectations and acceptance criteria are reset to reflect reality, and payment milestones are tied to outputs that have actually been verified.
Scope boundaries are reconfirmed and properly governed going forward, and cost and timeline forecasts are rebuilt from the ground up—based on evidence, not optimism.
What comes out of this phase is a genuinely executable plan; a reset agreement with vendors, a realistic financial forecast, and a governance structure with a proper reporting rhythm behind it.Relaunching Execution.
Control on its own isn't recovery—a program also needs to start moving again. This phase relaunches delivery under the new governance model, with a structured weekly cadence that keeps everyone aligned. Progress is tracked against the new baseline, high-impact dependencies are resolved quickly rather than left to linger, and stabilisation progress is communicated clearly to executives and the board.None of this is Heroics.
It requires sequence: understand before acting, contain before resetting, and reset before relaunching. Done in that order, even a seriously destabilised program can be brought back under control within 30 days—and be set up to stay that way.
By the end of the process, a recovering program should be transparent, under control, commercially aligned, and working to a delivery plan grounded in reality rather than hope.
A structured intervention offers a disciplined sequence that restores control, rebuilds confidence, and relaunches execution on a foundation of truth rather than assumption.
