Your Project Is Red. What Decision Will Actually Help It Recover?
A practical approach to diagnosing project problems, comparing recovery options and building a measurable 30-60-90-day recovery plan.
The project is behind schedule.
Costs are rising. Critical milestones have slipped. The sponsor wants a recovery plan before the next steering committee.
The first suggestions arrive quickly:
“Add more people.”
“Run activities in parallel.”
“Escalate to the vendor.”
“Move the deadline.”
Each might help. Each also carries costs, assumptions and consequences.
Before committing more money or promising another delivery date, answer one question:
Which recovery approach is feasible, addresses the underlying problem and protects enough value to justify its cost?
That is where a structured project recovery process becomes useful.
1. Establish what happens if nothing changes
A recovery proposal needs a clear point of comparison.
Start with the current forecast completion date, estimated final cost, remaining work and critical milestones. Then examine the exposure associated with continuing on the current trajectory.
That may include:
Forecast cost overrun.
Additional time-dependent costs.
Potential delay penalties.
Business benefits at risk.
Keep the assumptions visible. For example, do not add extended project overhead again if it is already included in the cost forecast.
This baseline gives leadership something concrete to evaluate: what might the proposed intervention improve, and at what additional cost?
2. Separate the symptom from the cause
“Behind schedule” describes a result. It does not explain the reason.
The underlying problem could be unstable scope, unresolved decisions, missing skills, vendor performance, rework or unrealistic planning.
The intervention should follow the diagnosis.
Adding resources may help a genuine capacity constraint. It may achieve little when the team is waiting for an architectural decision or approved requirements.
For each suspected cause, document:
The evidence.
The business impact.
The urgency.
How much control the team has.
Whether management has validated the finding.
A diagnostic score helps prioritise investigation. It does not prove causation.
3. Compare recovery options using the same criteria
A recovery meeting can become a contest between confident opinions. A common comparison framework makes the trade-offs easier to examine.
Question | What the recovery proposal should show |
Will it improve the finish date? | Recoverable days supported by milestone evidence |
What will it cost? | One-time and recurring recovery expenditure |
What value could it protect? | Delay costs avoided, benefits protected and other justified savings |
Can it start in time? | Lead time, resource availability and feasibility |
What new risks does it introduce? | Quality, burnout, customer and execution risks |
How reliable is the estimate? | Confidence level and key assumptions |
The fastest option may be too expensive. The cheapest may recover too little time. A high-scoring option may still fail a basic viability test.
Agree the limits before selecting the answer.
4. Check whether combined actions overlap
Recovery usually involves several interventions.
But their estimated benefits cannot always be added directly.
Two actions may accelerate the same work. Additional specialists and parallel execution may depend on the same scarce resource. Some activities may already overlap in the schedule.
Compare alternative packages and challenge the combined assumptions.
For example, a conservative package may minimise disruption, while an accelerated package may recover more time at greater cost or risk.
Validate the proposed schedule improvement against the actual project schedule before committing to a revised date.
5. Turn the decision into a 30-60-90-day plan
“Improve delivery performance” is too broad to manage.
An executable recovery plan connects each action to a cause, an owner, a due date and evidence of progress.
A practical structure is:
First 30 days — stabilise. Resolve critical decisions, validate the remaining work and address immediate blockers.
Days 31–60 — execute. Implement approved interventions and check whether milestones and performance are
responding.
Days 61–90 — sustain or revise. Confirm whether the recovery is holding, close outstanding gaps and revisit the baseline if the evidence requires it.
These are planning stages, not a promise that every project can recover within 90 days.
6. Track whether the intervention is working
An approved recovery plan is still a forecast.
During each review, compare actual progress with the recovery plan. Look at schedule movement, cost performance, overdue actions and pending decisions together.
If the schedule improves while costs continue to deteriorate, leadership needs to see both.
If progress remains insufficient, the response may need to change. Sometimes a transparent re-baseline is more credible than repeating an unsupported recovery date.
Before your next recovery review, ask these five questions
What is our exposure if we take no action?
Which causes have evidence and management validation?
Which options meet our cost, benefit and schedule requirements?
Who owns each recovery action and decision?
What evidence will tell us the intervention is working?
If those answers are scattered across presentations, trackers and emails, bringing them together can make the decision easier to assess.
Put the recovery discussion into one structured Excel model
The PMO Champion Project Recovery Decision Engine connects the diagnostic, recovery decision and follow-through in one workbook.
It includes:
Project Diagnostic: cost and schedule indicators, forecasts, health, urgency and financial exposure.
Root-Cause Analyzer: prioritised diagnostic findings, category heatmaps and an impact-versus-control view.
Recovery Options: comparisons using editable criteria, costs, confidence and viability gates.
Scenario Comparison: Conservative, Recommended and Accelerated packages, with a best-value indicator based on the model’s rules.
30-60-90 Plan: owned, dated actions and executive decisions.
Recovery Tracker: checks on progress and signals for escalation or re-baselining.
Executive Command Center: a leadership view designed to print on one landscape page.
The package includes a fictional demonstration workbook, a blank working edition, a User Guide and a Methodology document explaining the calculations.
It is designed for Excel 2019, Excel 2021 and Microsoft 365 on Windows or Mac, without macros or external links.
The model supports judgement: it does not calculate the network critical path, prove root causes or guarantee recovery outcomes. Its recommendations depend on your evidence, estimates and assumptions.
Bring a recovery decision to your next steering committee—with the options, economics and execution plan ready to discuss.
Explore the Project Recovery Decision Engine at PMOChampion.com.
Comments