If you’re reading this, you’ve likely just come out of a steering committee meeting that felt more like a deposition than a strategy session.
The £50M digital transformation that was supposed to be your legacy is now a millstone. The board has lost confidence. The vendor is telling you everything is "on track" while simultaneously asking for a change request. Your internal team is burnt out, cynical, and quietly updating their CVs.
I’ve been the person called in to fix these. I don’t bring slide decks; I bring a scalpel.
Programmes don't fail because of technology; they fail because of a breakdown in delivery governance. When a £50M ship starts taking on water, you don’t need a new map: you need to plug the holes and fire the navigator.
Here is the practitioner’s playbook for rescuing a stalled programme when "failure is not an option."
Phase 1: The 48-Hour Triage (Stop the Bleeding)
You cannot fix what you cannot see. Most CIOs are managed by "Watermelon Status" reports: green on the outside, blood-red on the inside. In the first 48 hours, your job is to find the ground truth.
The Code-Level Audit
Stop looking at the PowerPoints. Look at the artifacts. I ask for three things immediately: the Jira burn-down, the Git commit history, and the QA defect log. If the "status" says 80% complete but the code hasn't been checked in for three weeks, you aren't 80% done. You are 0% done with a high burn rate.
The Three Questions
I pull the lead engineers and product owners into a room: without their managers. I ask three questions:
- What is slowing you down?
- What are you doing twice?
- What should we stop doing immediately?
The answers usually reveal that 40% of the work is "nice-to-have" fluff that is choking the critical path. Stop it immediately. Every hour spent on a non-essential feature is an hour stolen from the rescue.
Phase 2: The Uncomfortable Board Conversation
By Wednesday, you need to have the most difficult conversation of your career. You have to tell the board that the £50M they spent is a sunk cost and the "Live" date is a fiction.
Addressing the "Watermelon"
Explain why the dashboard was green and why it’s now red. Boards hate surprises, but they loathe incompetence more. Acknowledging the failure is the only way to earn the mandate to fix it.
The New Baseline
Don't ask for more time. Ask for a Re-Baseline. This isn't just a date change; it’s a scope reset. You are pivoting the programme from "everything we wanted" to "everything we need to survive."
Phase 3: The Vendor Confrontation
Your primary vendor is likely in one of two modes: defensive or predatory. Neither helps you.
Restructure or Fire?
I’ve had to tell clients to fire us before if the fit wasn't right. You must do the same with your incumbents. If the vendor is billing for "resources" rather than "outcomes," the incentives are misaligned.
Outcome-Based Commercials
Move them to an outcome-based model immediately. If they don't hit the recovery milestones, they don't get paid the margin. If they refuse, they aren't a partner: they’re a parasite. Failed IT programme recovery often starts with a commercial reset.
Phase 4: The 90-Day Recovery Sprint
Once the bleeding is stopped and the board is aligned, you enter the 90-day sprint. This is where programme rescue consulting proves its worth.
The Rescue Trio
Ditch the 20-person steering committee. Create a "Rescue Trio": The CIO (you), the Business Sponsor, and a Lead Delivery Practitioner. This group meets daily for 15 minutes. They make decisions on the spot. If a decision takes longer than 24 hours, the programme is at risk again.
Finish, Don’t Start
The rule for the next 90 days is simple: Nothing new starts until something critical is finished. We use a high-velocity delivery model to clear the "QA Debt" first. You cannot build a skyscraper on a swamp; you have to drain the swamp of bugs before you add new features.
Phase 5: Help vs. DIY (When to Call the Professionals)
Can you do this yourself? Sometimes. But there’s a reason why surgeons don't operate on their own families.
The Problem with Internal Bias
Your internal team is too close to the failure. They have "sunken cost" bias. They are protecting their reputations or their jobs. An external delivery governance consultant doesn't care about the internal politics. They care about the exit gate.
The Dark Consultancy Approach
We don't do "discovery" for six months. We do a Delivery Diagnostic in two weeks, an Execution Roadmap in one week, and then we move into Hands-on Delivery. We don’t sit in the back; we lead the stand-ups.
The Friday Deadline
By Friday, you should have:
- A paused list of non-essential work.
- A commercial ultimatum delivered to your vendor.
- A "Ground Truth" report for the CEO.
- A 15-minute daily slot booked for your Rescue Trio.
Programme rescue isn't about being liked; it’s about being effective. The board will forgive a reset, but they won't forgive a second failure.
Is your programme hitting a wall? Don't wait for the next red dashboard.
Book a 30-minute discovery call with Kunal Patel today.
FAQ: Rescuing Stalled IT Programmes
How do I know if my programme is actually "stalled" or just slow?
If you are missing milestones but your "percentage complete" is still increasing, you are stalled. If your defect backlog is growing faster than your feature completion, you are stalled. If the vendor is blaming your team and your team is blaming the vendor, you are stalled.
Can a £50M programme really be "re-baselined" in a week?
The decision to re-baseline happens in a week. The detailed planning takes longer. However, the immediate "Stop Work" order on non-essential items must happen instantly to preserve capital.
Why is delivery governance more important than the tech stack?
The best tech stack in the world won't survive a governance model that allows for scope creep, poor decision-making, and misaligned vendor incentives. Governance is the engine; technology is the fuel.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia ; ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn