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 23 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.
