# Project Recovery: A Practical Playbook for Salvaging Value

> This review isolates the mental models Harold Kerzner offers for diagnosing and repairing failed projects. It assesses the book as a toolkit for decision architecture, triage, and governance reset rather than a narrative or checklist catalog.

- **Author**: Blookmark
- **Published**: 2026-04-27T17:03:31
- **Canonical URL**: https://www.blookmark.com/book-reviews/project-recovery-a-practical-playbook-for-salvaging-value

## Content

## Relevant For:
- Senior project managers and PMO leaders who must decide whether to salvage, restructure, or close troubled efforts
- Recovery consultants and interim leaders tasked with rapid stabilization of large projects
- Executives needing frameworks to judge project health and recovery feasibility

## Remarkable Points:
- A distinct recovery lifecycle that treats failure as a separate management problem, with clear phases and gates
- Actionable health checks that translate vague risk signals into stop, stabilize, or restart choices
- Crisp guidance on stakeholder realignment and authority reset as tools to eliminate friction
- An emphasis on decision architecture that prioritizes salvage of value over heroic rescue attempts
- Integration with established project management bodies of knowledge to ground the methods

## Most Liked (As-Is Statements):
- "Treat failure as a different species of project; it needs its own lifecycle and rules."
- "A health check should produce a binary path: recover or close, with evidence for either choice."
- "Recovery is governance work first, technical work second."

## Key Themes:

### Theme 1: Root Cause Diagnosis

Kerzner insists on disciplined problem framing before action. He presents techniques to separate symptoms from structural causes so remedies target the source, not the noise.

### Theme 2: Decision Architecture

Decisions are structured into gates with explicit criteria and ownership. This reduces ad hoc rescue maneuvers and forces trade offs to be visible and accountable.

### Theme 3: Stabilize then Optimize

The book advocates containment first: secure scope, budget, personnel, and information flow; only then undertake performance recovery and value engineering.

### Theme 4: Learning and Governance

Recovery must feed organizational learning. Kerzner ties postmortem capture to policy changes so the same risks are less likely to recur under standard governance.

## Final Remark:

Project Recovery is a concentrated set of mental models for anyone who must make high stakes decisions under ambiguity. Its value lies in procedural clarity: how to triage, whom to empower, and what evidence to demand. The text favors pragmatic governance and measurable gates over inspirational rescue narratives. For teams facing frequent troubled initiatives, the book shifts thinking from firefighting to institutionalizing rescue capability.

***When a project is failing, treat the situation as a governance problem first and a technical problem second; that mindset alone changes the outcome.***

## Similar Books:
- [The Phoenix Project](/book-reviews/the-phoenix-project-a-compact-toolkit-for-systems-thinking-in-it) by Gene Kim, Kevin Behr, and George Spafford
- [Project Management Best Practices](/book-reviews/project-management-best-practices-a-tactical-spine-for-complex-work) by Harold Kerzner
- The Art of Project Management by Scott Berkun
- The Lean Turnaround by Art Byrne