Somewhere in the last board pack, someone used the word "red" next to the program name. The steering group has stopped asking when it will land and started asking whether it will land at all. The vendor blames the business for scope creep; the business blames the vendor for underdelivery. Nobody in the room has run a recovery before, and everybody in the room is aware of that.
Program recovery consultants exist for exactly this moment. They are independent specialists brought in when a transformation or systems program has missed milestones, overrun budget, or lost the confidence of the people funding it. The job is not to defend the plan that got you here. It is to find out, fast and honestly, whether the program can be saved, and if so, how.
Program recovery consultants are independent specialists brought in when a transformation or systems program has missed milestones, overrun budget, or lost board confidence. Good recovery starts with an honest review, not a rescue plan: it establishes whether the program should be stabilized, rescoped, or closed, before any further money is spent.
This is what a proper recovery review looks like, and what to expect from a project rescue consultancy operating in the UK mid-market.
The signs of a red program
Most transformation and ERP programs that end up needing recovery show the same pattern, whichever system or supplier is involved.
Milestones slip once, get rebaselined, then slip again against the new baseline. The steering group starts meeting weekly instead of monthly, which everyone reads as a bad sign because it is one. Budget conversations move from "on track" to "we need a bit more" to "we need a lot more, and we're not sure that's the last time." The delivery team and the business start keeping their own separate versions of what "done" means. And at some point, someone senior enough to matter says out loud what everyone has been thinking: we don't actually know if this is recoverable.
Gartner research has reported that more than 70% of ERP implementations fail to reach the goals set out in their original business case. Gartner has also reported that broader transformation programs miss their stated objectives at a similar rate, with around 70% falling short to some degree. None of that is a comment on any one supplier or team. It is a structural fact about how these programs are run, and it is why an outside view matters more than another internal steering meeting.
Why recovery rarely comes from inside
The people closest to a struggling program are usually the wrong people to diagnose it. Not because they lack competence, but because they are inside the sunk cost. The PM who built the plan is reluctant to say the plan was wrong. The sponsor who championed the business case is reluctant to say the case no longer stands. The vendor is, understandably, reluctant to say the problem sits with them.
A recovery review works because it sits outside all three of those incentives. It asks the questions nobody currently in the room can ask without political cost: is the original scope still the right scope, is the delivery model capable of the remaining work, and is the reason for the delay technical, organisational, or both. Answering those honestly from the inside is rare. It usually needs someone who has no stake in having been right six months ago.
What do program recovery consultants actually do in a review?
A good program recovery review is short and forensic. It is not a re-plan, and it is not a governance workshop. In a matter of weeks, it should give the board a clear diagnosis of why the program is where it is, plus a view on whether the original objective is still achievable and worth pursuing. Then it needs a specific set of recommendations for what happens next, with the reasoning shown so the board can test it for themselves.
That diagnosis has to go past the symptom layer. Missed milestones are the symptom. The cause is usually one or more of: a business case that was optimistic from day one, a delivery model that assumed capability the organization didn't have, requirements that kept moving because nobody owned the decision to stop them moving, or a vendor relationship structured in a way that rewarded activity over outcomes.
The output is a recovery plan only if recovery is actually the right call. That distinction matters more than most recovery reviews admit.
When the right answer is to stop
Sometimes the honest recommendation is not a turnaround plan. It is scope redefinition, or it is closure. A program built on a business case that no longer holds, chasing a scope that has drifted well past what the organization can absorb, does not get fixed by better project management. It gets fixed by someone willing to say the case for continuing isn't there anymore.
This is the recommendation most rescue consultancies are reluctant to make, because it is the one that ends the engagement rather than extending it. It is also, in a meaningful minority of red programs, the right one. A CFO who has just heard "close it down, here's why" from an independent adviser has something a lot more useful than another rebaselined plan: a decision they can defend to the board.
What a turnaround needs from week one, if recovery is the call
Where recovery is genuinely achievable, the shape of a good program turnaround is consistent. Governance gets simplified, not added to: fewer forums, clearer decision rights, one version of what "done" means. Scope gets triaged hard, with anything not essential to the original business case parked rather than quietly carried forward. The vendor relationship gets reset around outcomes, not activity, with the commercial terms adjusted if they were part of the problem. And someone senior takes day-to-day accountability for delivery who was not the person accountable for the plan that failed.
None of that is complicated to describe. It is hard to do inside an organization that is still absorbing the fact its flagship program is in trouble, which is the practical reason external recovery leadership tends to outperform an internal reset.
How Assured Velocity approaches recovery
The market for program recovery in the UK is not short of names. Most recovery firms run some version of a structured, time-boxed review, and a few say so publicly: Intology, for instance, publicly frames its work as a 30-day reset. The instinct across most of them is broadly right: get in fast, get honest. Then simplify the governance, because a red program rarely needs more process, it needs less.
Where Assured Velocity differs is in who does the work. Our senior partners lead the recovery review and the turnaround themselves; there's no pyramid of juniors handing the difficult conversations down to a graduate analyst while a partner reports up from a distance. And the entry point is deliberately small: a fixed-scope Business Review from £5k, delivered in 14 days, that tells you plainly whether the program is recoverable, what it would take, and what it's likely to cost, before you commit to anything larger.
We are a young firm and we are not going to claim a track record we haven't earned yet. What we will commit to is the thing that actually matters in a red-program conversation: an honest answer, delivered by the person who will be in the room if you act on it, including the answer nobody wants to give when it's the right one.
If your program has reached the point where someone used the word "red" in the last board pack, the useful next step is not another internal review. Read more on how we run transformation programs on the Transformation Design & Delivery page, or skip straight to the diagnostic: book a Business Review and get a straight answer inside 14 days.
Is the word "red" in your board pack?
A fixed-scope Business Review tells you plainly whether the program is recoverable, what it would take, and what it's likely to cost. Senior-led throughout.
