How to Recover a Failing Project Before It’s Too Late (And the Warning Signs Most Boards Miss)

Paul Thomas • May 4, 2026

Share this article

Failing projects don’t announce themselves. By the time a board paper flags red, the slippage has been building for months. Sometimes longer. The team knows. The PMO knows. The project manager has been quietly working weekends to stop the wheels coming off.


The board is the last to find out. And by the time they do, the recovery options have already started narrowing.


After 21 years of being called in when projects must not fail, the pattern is always the same. The warning signs were there. They were just being explained away.


Why Most Recovery Efforts Start Too Late


There is a window of roughly the first 90 days of drift, when a failing project can still be recovered with the team in place, the budget largely intact, and the scope mostly preserved. Outside that window, recovery means something harder. Re-baselining. Re-scoping. Hard conversations with the steering committee about what the programme will actually deliver.


The cost of inaction compounds quickly. A project that slips by three weeks in month one slips by three months by month four. Burnout sets in. Your strongest people start updating their CVs. Suppliers start hedging their commitments. The longer the drift, the fewer levers you have left to pull.


Most boards don’t intervene because the warning signs look like normal project noise. They’re not. They’re a pattern.


Seven Warning Signs Your Project Is Failing


These are the signals we see, in this order, almost every time we’re called in for a rescue.


1. Status reports stop telling you anything new

The RAG status has been amber for six weeks. The narrative is identical week-on-week. The risks list hasn’t been updated. When a status report becomes a ritual rather than a tool, the project has stopped self-correcting.


2. Milestones quietly move

Not once. Repeatedly. A delivery date slips from June to July, then July to September, with no formal change control. The team has stopped believing the plan, so they’re managing to a private timeline rather than the published one.


3. Your best people are working the hardest

Two or three names appear in every escalation. They’re in every workshop. They’re fixing other people’s deliverables in the evening. When delivery depends on heroics from a small group, you don’t have a project. You have a temporary arrangement that will collapse the moment one of them leaves.


4. The PMO has stopped pushing back

A healthy PMO challenges plans, flags risks, and refuses to accept poor-quality status updates. When the PMO is reduced to chasing inputs and producing decks, governance has quietly broken down. The board is now reading a summary of a summary.


5. Suppliers and partners are going quiet

Slower response times. Vague commitments. A reluctance to commit to dates in writing. Suppliers know when a programme is wobbling, often before the client does, and they protect themselves accordingly.


6. Decisions take three meetings

Issues that should take a day to resolve are bouncing between forums. Nobody is empowered, or nobody wants to own the call. Decision latency is the cleanest leading indicator of programme failure we know of.


7. The benefits case has gone quiet

Nobody is talking about the outcome any more. Conversations are about scope, dates, and budget. The inputs. When the team stops referencing why the project exists, the project has lost its anchor.


How to Recover a Failing Project: The First 30 Days


Recovery doesn’t start with a new Gantt chart. It starts with telling the truth.


Week 1: Stop and assess

Pause non-critical workstreams. Run a structured health check covering scope, plan, resourcing, governance, supplier performance, and benefits alignment. Talk to the practitioners, not just the leads. They’ll tell you where the project actually is. Produce one document, no more than ten pages, that names the gap between where the project is and where the board thinks it is.


Week 2: Re-baseline honestly

Strip the plan back to what can credibly be delivered with the team you have. If scope needs to come out, name it. If budget needs to grow, say so. If the original benefits case can no longer be met, raise it now, not in six months. A re-baselined plan that the team believes in is worth more than an aspirational plan that nobody trusts.


Week 3: Fix governance

Tighten the decision-making loop. Reduce the number of forums. Empower a single accountable owner for each workstream. Set a cadence the board can rely on, with status reports that show movement rather than narrative.


Week 4: Stabilise the team

Identify the two or three people the project cannot afford to lose. Take pressure off them. Bring in experienced reinforcement where the gaps are real. Make it visible to the team that the project is being run differently from now on. That visibility is what restores momentum.


When to Recover, and When to Stop


Not every failing project should be saved. Some have lost their business case. Some have technology choices that can’t be unwound at an acceptable cost. Some have lost the trust of the sponsor permanently.


An honest recovery assessment names both options on the table. Recover, or wind down with dignity. It gives the steering committee the evidence to choose. The worst outcome is a project that limps for another twelve months before being quietly cancelled. The cost of that drift is almost always greater than the cost of stopping now.


What Changes When the Right Help Arrives


Three months in. The plan is credible. The team is steady. Suppliers are responding again. The board paper tells the truth, and the truth is improving week by week.


That is what recovery looks like. Not a hero project manager riding in to save the day. A small, experienced team embedded alongside yours, working the plan, restoring confidence, and finishing what others started.


Your project may not be failing yet. But if three or more of the warning signs above are familiar, the next ninety days will determine whether it can still be recovered. The first conversation is always free.


Free Project Assessment & Audit, Tailored to You

Not sure where your project really stands? We assess what's happening, and give you a clear and honest picture at no cost. Every engagement starts with understanding your specific situation, because no two organisations are the same.

Totally free. No commitment needed.

Recent Posts

Hand circling a date on a desk calendar with a pen beside a laptop
By Paul Thomas July 16, 2026
Planning a PMO setup? This guide walks through the realistic 3-6 month timeline phase by phase, plus a free assessment to find your own number.
By Paul Thomas July 15, 2026
Most consultancies won't answer the cost question directly. Ask, and you'll typically get "it depends" and a form to fill in. It does depend, but that's not an excuse to be vague about what it depends on. If you're a COO trying to build a business case for the board, three variables actually set the price, and none of them are secret. What actually drives the number Programme size is the first. A single at-risk workstream costs less to stabilise than a portfolio of twelve, scope drives everything downstream. A workstream with one team, one sponsor, and one clear deliverable is a contained diagnostic exercise. A twelve-workstream portfolio with overlapping dependencies and multiple sponsors is a different order of problem entirely, because stabilising one workstream in isolation without understanding its dependencies on the other eleven risks solving the visible symptom while the underlying cause resurfaces somewhere else three months later. Embed duration is the second: recovery engagements typically run three to six weeks, and a straightforward stabilisation, credible plan, honest reporting, a functioning team, costs less than a six-week turnaround with practitioners embedded across multiple workstreams. The difference between the two isn't really about calendar time so much as coverage, how many people need to be physically present, in the room, for how many of those weeks, before the organisation can run the plan on its own. Seniority is the third, and the one most likely to be quietly reduced to save money. We only deploy practitioners with 15+ years of experience, never graduates running a template, and that's a deliberate cost floor, it's also why the fix tends to hold. It's worth being honest about why seniority costs more and is still worth it: a junior consultant working from a template can produce a plan that looks credible on paper. A senior practitioner who has seen a dozen versions of this specific failure pattern before knows which parts of that plan won't survive contact with the actual organisation, and can say so in week one rather than week five. What that seniority actually costs, in public numbers You don't have to take a consultancy's word for what senior delivery talent costs in the UK market. The Association for Project Management's 2025 Salary and Market Trends Survey, the UK's largest annual study of the profession, puts the average project management salary at £52,500, up 10% on 2023, with practitioners in consultancy and energy/utilities sectors averaging £62,500, per the APM Salary Survey 2025 . Embedded recovery work commands more than that average because it's compressed: fifteen-plus years of pattern recognition delivered on a timeline measured in weeks, not spread across a year. There's a useful way to think about what's actually being purchased here. A permanent hire's salary buys a year of their time, spread across whatever the organisation needs that year. A recovery engagement's cost buys weeks of concentrated attention on one specific problem, from someone whose entire value is having seen that problem before. The hourly economics look expensive next to a permanent salary until the comparison is corrected for what's actually being delivered in that window. The cost that never makes it onto an invoice Every cost conversation focuses on what recovery costs. The number that's harder to see, and usually larger, is the cost of inaction. A project drifting for another quarter doesn't just slip its date, it compounds in several distinct ways. The team burns out chasing an unrealistic plan, because nobody has told them the plan is unrealistic, so they keep trying to hit dates that were never achievable in the first place. The best people quietly start looking elsewhere, because skilled practitioners can generally tell when a programme has lost its way faster than the sponsors funding it can, and they don't wait around to find out how it ends. Stakeholder trust erodes in a way that outlasts the project itself, a sponsor burned once by an over-promised, under-delivered programme brings that scepticism into the next funding conversation, and the next, long after the specific project is closed. And the eventual fix costs more because the drift has to be unwound before recovery can even begin, every extra week of a bad plan being followed is a week of decisions made on false assumptions that now need to be found and corrected. By the time a board asks how much it will cost to fix, the more useful question is how much it has already cost to wait. Why nobody publishes a rate card A three-week reporting fix and a six-week multi-team turnaround are different projects with different costs, and any headline number would be wrong for most people who read it. That's not evasion. It's the same reason a surgeon doesn't quote a price before the scan — not because the price is a secret, but because quoting it before the diagnosis would mean quoting the wrong number to almost everyone who asked. Where to start Cost climbs with the number of embedded practitioners, the complexity of stakeholder alignment, and how far a programme has already drifted before anyone calls for help. It does not climb because of methodology, tooling, or brand name. Agile Minds gives every prospective client a free, two-week assessment before any number gets discussed. If you need a figure you can actually take to the board, we should talk .
Blue infographic chart with numbered hexagons and a pencil on a desk
By Paul Thomas July 14, 2026
Not every project needs the same delivery model. This step-by-step guide shows you how to build the right one for yours, then offers a free assessment.
Jaguar and Land Rover logos on a gray building facade
By Paul Thomas June 1, 2026
How AgileMinds built JLR a working agile framework through a real product, not a workshop. A 16-week app and guilds that kept it alive after we left.
Halfords storefront with glass entrance, orange logo, and parked bicycles outside
By Paul Thomas June 1, 2026
How AgileMinds delivered Halfords' unified ecommerce platform on Salesforce Commerce Cloud. Two brands, one basket, over 100 integrations, nine months.
Three people in red helmets and jackets stand outdoors at dusk, looking serious.
By Bernadine Dela Cruz May 29, 2026
How AgileMinds helped E.ON take a virtual power station from proof of concept to commercialised, award-winning solution in six months.
Stressed person at desk with laptop, head in hand, reviewing charts in a bright office
May 24, 2026
Uncover the hidden costs of project team burnout, like knowledge loss & attrition. Contact us for strategies to mitigate these issues.
Hands holding a tablet with a to-do checklist and red markings on a desk, lit by blue and warm light
By Paul Thomas May 4, 2026
More than half of PMOs are shut down within two years. Here are the five reasons mid-market PMOs fail, and what to do differently. Free PMO assessment.
Colleagues in a meeting, leaning over documents and pointing at a chart on a conference table.
By Paul Thomas May 4, 2026
Explore why 70% of digital transformations fail due to middle management issues. Contact us for tailored solutions today!