ProjectManager.co

When a project goes sideways, the difference between recovery and collapse comes down to diagnosis speed and honest conversations. This episode breaks down exactly what to do — and what not to do — when the warning signs are already flashing.

Show Notes

Project recovery is one of those topics that makes everyone in the room uncomfortable — yet it's a situation most experienced project managers will face more than once. This episode cuts through the instinct to replan immediately and instead lays out a structured, honest approach to pulling a troubled project back from the edge before the options run out.

The episode walks through the full arc of a real recovery effort, from the moment you acknowledge the project is in trouble to the cadence you need to hold the new plan in place. Key topics covered include:

  • Why replanning too soon is the most common recovery mistake — rebuilding the schedule before diagnosing the root cause almost always leads back to the same position weeks later.
  • A three-question diagnostic framework — identifying what was true at the start and no longer is, what was never true but treated as if it were, and what the team now knows that it didn't before.
  • Matching the fix to the actual fracture — whether the core problem is resource fragmentation, runaway scope creep, or undocumented dependencies, the intervention has to address the one structural issue that caused the slip, not a checklist of symptoms.
  • How to frame the stakeholder conversation — presenting two or three recovery options with clearly articulated trade-offs across scope, timeline, and cost, so executives can make a real decision rather than absorb bad news with no path forward.
  • Knowing when to stop — recognizing that cancelling a project cleanly is a legitimate and sometimes better outcome than dragging it to a painful end.
  • Post-recovery discipline — using a tighter reporting cadence and faster escalation of blockers for a defined period after the recovery plan is agreed, to prove the new baseline is holding. Tools like automated status reports can help teams maintain that tighter visibility loop without adding manual overhead.

For project managers who want to go further, the project recovery advisory resources at ProjectManager.co cover the governance and health-diagnostic models that support close project watching after a recovery is underway. For a related skill that feeds directly into recovery planning — specifically the estimation failures that often contribute to a project going sideways in the first place — the episode How to Estimate Work Without Lying to Yourself or Your Stakeholders is essential listening.

ProjectManager.co

What is ProjectManager.co?

Project management for people who deliver, not people who certify. Estimation that survives contact with reality, scope and dependency management, status reporting nobody has to decode, and where self-hosted and AI-assisted tooling genuinely helps.

Each episode takes one practice — a re-estimate mid-project, a dependency nobody owns, a status meeting that produces nothing — and works through a better way to handle it. Written for delivery leads and PMs running real projects, with no methodology evangelism. Five or six minutes, one practice at a time.

Topics include estimation that survives reality, dependency and critical path management, scope negotiation, status reporting nobody decodes, resource planning, retrospectives that change something, and self-hosted versus SaaS tooling.

Produced by ProjectManager.co, self-hosted AI project management. Full details, services and further reading at https://projectmanager.co