Recover or Write Off a Failing Programme

There is a moment in the life of every troubled programme when the question changes. For months the question has been "how do we get this back on track". Then, usually in a board paper or an investor call, it becomes something harder: is this recoverable at all, or are we funding a write-off?

Programme recovery is the structured intervention used when a major change programme has stopped delivering: an independent party establishes what is actually true, stabilises the programme, and rebuilds the plan on evidence rather than optimism. It is distinct from a review, which produces a document, and distinct from closure, which is the decision to stop. The first job of a recovery engagement is to work out which of those three the situation actually calls for.

That question is one most organisations are badly equipped to answer. The people closest to the programme cannot answer it objectively, because they have spent two years of their career on it. The systems integrator cannot answer it objectively, because the honest answer may end their contract. And the board is being asked to decide using reporting that has been optimistic for long enough that nobody now trusts it.

This is the decision Intology is called in to inform. Not "sell us a recovery", but "tell us whether recovery is the right answer, and give us something we can defend".

Why the recover-or-stop question rarely gets asked honestly

Four forces conspire to keep a failing programme alive past the point of rationality.

Sunk cost. Twelve million spent feels like a reason to spend the thirteenth. It is not. The only economically relevant number is the cost to complete against the benefit still available, and almost nobody calculates it cleanly once the emotional investment is large.

Reporting drift. Status does not go from green to red. It goes from green, to green with a caveat, to amber with a recovery plan, to amber with a second recovery plan. Each step is individually defensible. The cumulative effect is that the board has not seen the real position for two quarters.

Misaligned incentives. The integrator's revenue depends on the programme continuing. The programme director's reputation depends on it succeeding. Neither is acting in bad faith, and both are structurally unable to tell you to stop.

Career risk. In most organisations the executive who recommends stopping a flagship programme carries more personal downside than the executive who lets it drift for another six months. Until the board removes that asymmetry, it will not hear the truth.

None of this is unusual. It is the normal physics of a large programme under pressure. It is also why the assessment has to come from someone with no stake in the answer.

The four numbers a CFO needs before the decision

A recover-or-stop decision cannot be made on a RAG chart. It needs four numbers, evidenced rather than asserted.

1. Earned value against spend to date. Not invoiced effort. What proportion of the committed scope is actually built, tested and demonstrably working? On the programmes we are called into, the gap between spend and earned value is routinely the single most uncomfortable number in the diagnosis.
2. Realistic cost to complete, expressed as a range. A single-point estimate at this stage is a work of fiction. The range should be built on the delivery velocity the programme has actually demonstrated, not on the velocity the original plan assumed.
3. Benefit still genuinely available. Business cases age. Some benefits have been overtaken by process change, headcount reduction or a market shift, and some were never real. The question is what remains, discounted for the delay already incurred.
4. Write-off exposure. Capitalised programme costs, contractual exit positions with the integrator, licence commitments already signed, and the cost of running the legacy estate for longer. Finance directors are frequently surprised by how much of the "saving" from stopping evaporates once these are totalled.

Put those four numbers in front of a board and the decision usually makes itself. The difficulty is almost never the decision. It is getting to numbers the board believes.

What makes a programme recoverable

In our experience, recoverability turns on five conditions. The more of these that hold, the stronger the case for recovery rather than closure.

• The business outcome is still valid. If the organisation still needs the capability, the case for finishing survives even a badly run delivery.
• The root cause is structural, not technical. Governance failure, unclear accountability, scope indiscipline and weak vendor management are all fixable. A platform that fundamentally cannot do what was promised is a different matter.
• Something usable has been built. Working data migration, a tested integration layer, a configured core: real assets that a re-baselined plan can stand on.
• The organisation has the appetite for another attempt. Recovery requires the business to re-engage, not just IT. If the operating divisions have privately written the programme off, recovery will fail regardless of the plan.
• The funding case survives honest arithmetic. Cost to complete plus the recovery investment, against benefit still available, at a discount rate the board would accept for any other investment.

Where those conditions do not hold, the responsible recommendation is a controlled stop: salvage what has value, close the contracts properly, and protect the balance sheet. We have made that recommendation, and we would rather make it than take a recovery fee for a programme that should be closed. That is the practical meaning of independence.

What recovery actually looks like

Recovery is not a review. A review produces a document. Recovery produces a programme that delivers. Our programme recovery practice works to a fixed 30-day shape, because boards under investor or regulatory pressure cannot wait a quarter for a position.

Days 1 to 10, diagnose. Direct access to the delivery team rather than the reporting line. A full read of the artefacts that show real progress: test results, defect trends, environment readiness, data migration status. You get a written position on root cause, earned value and the realistic range of outcomes.

Days 11 to 20, stabilise. Scope is frozen, the critical path is re-established, and governance is cut back to the decisions that genuinely need making. Where leadership gaps are the root cause, we fill them directly rather than advising someone else to.

Days 21 to 30, re-baseline. A plan you can defend to your board, your investors or your regulator, built on measured delivery velocity rather than restated optimism. Re-baselining is where most recovery attempts fail, because the new plan carries the same assumptions as the old one.

Beyond day 30, embed. Under the Embedded Change Model, capability transfers to your team as the work proceeds. The exit is designed from week one. We are not building a dependency, and the test of the engagement is whether your organisation is more capable when we leave.

The private equity view: the same decision, on a shorter clock

In a PE-backed portfolio company, a drifting programme is rarely just an operational problem. It is usually sitting inside a value creation plan, with a hold period attached to it.

Three things change the calculation for a sponsor. First, the timetable: a twelve-month slip against a four-year hold is not a delay, it is a material reduction in the value available at exit. Second, the diligence exposure: an unfinished finance transformation becomes a buyer's negotiating lever, and an EBITDA adjustment that was never in the model. Third, the credibility question: lenders and LPs draw conclusions from a management team that has reported green for three quarters on a programme that is visibly not delivering.

Sponsors typically want three things quickly, and want them from someone outside the portfolio company: an independent read on whether the plan is achievable, a defensible view of the capital still required, and a judgement on whether the management team can deliver it. We do that work across portfolios, and it sits alongside the wider technology levers in private equity value creation and our private equity transformation practice.

Why independence is the thing you are buying

Intology does not implement software, does not resell licences, and takes no commission from any systems integrator or vendor. That is deliberate, and it is the whole product. When we tell you the integrator is the problem, or that the integrator is not the problem, there is no commercial reason for us to say either.

Two further points matter to the boards we work with. The person who runs your diagnosis is the person who runs your recovery: there is no pyramid and no handover to a delivery team you have not met. And where recovery requires someone to hold a programme leadership role while the permanent structure is rebuilt, we take that accountability rather than advising from the side. Advisory-only recovery rarely works, because the hard part is not knowing what to do. It is having the standing to make it happen.

If you are not yet sure whether the situation warrants intervention, the warning signs that a programme needs recovery are a reasonable place to start, and our view of the Embedded Change Model explains how we make the change hold once the immediate crisis has passed.

Frequently asked questions

How do we decide whether to recover or cancel a failing programme?

Establish four things first: earned value against spend to date, a realistic cost-to-complete range based on demonstrated velocity, the benefit still genuinely available, and the full write-off exposure including capitalised costs and contract exits. Then test the five recoverability conditions: valid outcome, structural rather than technical root cause, usable assets already built, organisational appetite, and a funding case that survives honest arithmetic.

Who should carry out the assessment?

Someone with no stake in the answer. The programme team, the integrator and the sponsoring executive all have structural reasons to favour continuation. An independent assessor with no implementation revenue and no vendor alignment is the only party able to recommend stopping.

How long does an independent assessment take?

Intology produces a written position on root cause, earned value and the realistic range of outcomes within ten working days, and a defensible re-baselined plan within thirty. The programme does not need to stop while the assessment runs.

What if the honest answer is that the programme should be stopped?

Then we say so, in writing, with the evidence behind it. A controlled closure that salvages usable assets and exits contracts cleanly protects far more value than a second failed recovery attempt.

What does this mean for a private equity sponsor?

A slipping programme inside a value creation plan compresses the value available at exit, creates a diligence exposure the buyer will price, and raises a credibility question about management reporting. Sponsors usually need an independent read on achievability, the capital still required, and whether the current team can deliver it.

Talk to us about your programme

If you are weighing up whether a programme is recoverable, that question is usually its own answer. A conversation costs nothing and will tell you quickly whether this is something we can help with. Book a recovery call with a senior Intology consultant.