When to Stop a Transformation Programme

Sometimes the right answer is to stop. Here's how to recognize when continuing is throwing good money after bad.

Lumina Advisory
5 February 2024
5 min read
Leadership

The hardest decision in transformation: knowing when to stop.

Everyone wants to believe the programme can be saved. Sunk costs make stopping feel like admitting failure. Political pressure demands visible progress.

But sometimes continuing is worse than stopping.

Here are the warning signs.

Red Flag 1: Benefits Are Unachievable

Sign: Original business case assumed 40% cost reduction. Six months in, analysis shows maximum achievable is 15%.

Question: Is 15% reduction worth the remaining £8M investment?

Often: No. But political pressure says "we've come this far."

Right answer: Stop if ROI doesn't stack up with realistic benefits.

Red Flag 2: Scope Creep Has Made It Unfundable

Sign: Original scope: £5M. Current scope: £14M. Budget: £5M.

Options:

  1. Find £9M (usually impossible)
  2. Reduce scope to affordable level
  3. Stop programme

Often: Wishful thinking that £9M will appear.

Right answer: Reduce to achievable scope or stop.

Red Flag 3: Leadership Has Lost Confidence

Sign: Ministers/leadership no longer attend governance meetings. Questions are skeptical, not supportive.

Implication: Political capital is gone. Even if you deliver, it won't be valued.

Right answer: Sometimes programmes become politically un survivable regardless of delivery.

Red Flag 4: Vendor Relationship Has Failed

Sign: Contract disputes, missed milestones, blame culture, commercial standoff.

Reality: Vendor relationships that fail rarely recover.

Options:

  1. Change vendor (expensive, time-consuming)
  2. Commercial reset (requires leverage you might not have)
  3. Stop programme

Often: Better to stop, learn lessons, start fresh.

Red Flag 5: Key Assumptions Have Changed

Sign: Programme assumed legacy system support until 2027. Vendor just announced end-of-support 2025.

Implication: Timescales, dependencies, and sequencing all now wrong.

Question: Does the programme still make sense with new assumptions?

Often: No, but nobody wants to admit it.

The Sunk Cost Fallacy

Bad logic: "We've already spent £4M, we can't stop now."

Question: Would you start this programme today knowing what you know now?

If no: Continuing is throwing good money after bad.

Hard truth: £4M already gone. Question is whether spending £4M more delivers value.

The "Salvage What We Can" Approach

Better than total write-off: Reduce scope, save what's achievable, stop the rest.

Example: (From our Gibraltar case study)

  • Original programme: £12M, 7 workstreams
  • £7M spent, nothing delivered
  • Recommendation: Stop 3 workstreams, focus on 4 achievable ones
  • Outcome: Saved £4M, delivered 70% of original benefits vs 0%

Key: Honest assessment of what's salvageable vs what's lost.

How to Make the Decision

Step 1: Honest diagnosis (usually needs external eyes)

Questions:

  • Are benefits still achievable?
  • Is scope affordable?
  • Is leadership supportive?
  • Can vendor relationship work?
  • Do assumptions still hold?

Step 2: Options analysis

Don't just ask "continue or stop?"

Ask: "Continue as-is, reduce scope, pivot approach, or stop?"

Step 3: ROI calculation with realistic assumptions

  • Sunk cost: £X (gone, ignore it)
  • Remaining investment: £Y
  • Realistic benefits: £Z
  • ROI: Z/Y

If ROI < acceptable threshold, stop.

Step 4: Political assessment

Even if ROI works, if political capital is gone, delivery won't be valued.

Step 5: Decide and communicate

Worst option: drift. Decide and act.

The Courage to Stop

Why it's hard:

  • Admitting previous decisions were wrong
  • Political visibility of "failure"
  • Sunk cost fallacy
  • Hope it might still work

Why it's sometimes right:

  • £2M lost is better than £6M lost
  • Resources freed for higher-value work
  • Organizational learning captured
  • Future programmes benefit from honest lessons

What We Do Differently

Most consultancies won't recommend stopping (because they lose revenue).

We do (because it's sometimes the right answer).

Example: Malta case study - we told client not to start one procurement because benefits didn't stack up. Cost us £200K in potential fees. Saved them £2M.

Example: Gibraltar case study - we recommended stopping 3 of 7 workstreams. Reduced our scope. Right answer for client.

The Question to Ask

To your consultants: "Under what conditions would you recommend we stop this programme?"

Good answer: Specific conditions, honest assessment, no BS.

Bad answer: "We never recommend stopping" (translation: we'll take your money regardless).

Related:

Tags

programme managementleadershipdecision makingprogramme recovery

Discuss this with us

Want to explore how these ideas apply to your organization? Let's talk.

Get in touch