Project Rescue and Recovery

The difference between a project that can be rescued and one that should be terminated — and how to tell the difference fast.

Knowledge Check: When is termination the right answer instead of rescue?

How to conduct a rapid diagnostic: stakeholder interviews, document review, and root-cause analysis in five business days.

Knowledge Check: What three root cause categories account for most project failures?

Includes: Diagnostic Interview Guide

Apply root cause analysis to project failures: governance failures, stakeholder failures, vendor failures, and scope failures.

Knowledge Check: What is the most common governance failure in troubled projects?

Includes: Root Cause Analysis Template

Build the recovery plan: new baseline, governance reset, revised scope, and vendor accountability restructure.

Knowledge Check: Why is defending the original baseline the wrong rescue strategy?

Includes: Recovery Plan Template

How to rebuild sponsor and executive confidence through honest assessment, credible reporting, and reliable communication.

Knowledge Check: What is the first step to rebuilding stakeholder trust after a project failure?

Fix the structural failures: implement change control, establish escalation paths, restructure vendor accountability.

Knowledge Check: How do you introduce change control on a project that has never used it?

Run the recovery engagement: weekly cadence, milestone tracking, escalation management, and stakeholder reporting.

Knowledge Check: How often should a recovery PM communicate with the sponsor?

Includes: Recovery Status Report Template

Transfer governance to the internal team, document lessons learned, and build the prevention playbook for the organization.

Knowledge Check: What must be in place before a rescue PM hands off to the internal team?

Includes: Rescue Handoff Checklist