The Phoenix Project
Gene Kim, Kevin Behr, and George Spafford · 2013
A business novel about Bill Palmer, thrust into running IT Operations at a failing company. Guided by the Three Ways and Theory of Constraints, he learns to treat IT like a factory floor: manage flow, expose the bottleneck, and tame unplanned work.
A gripping business novel that smuggles the entire logic of DevOps and the Theory of Constraints into a story you can't put down.
Three of the ideas you’ll keep
The Clif summary of The Phoenix Project pulls out 7 insights. Here are the first three.
- There are exactly four categories of work in IT: business projects, internal IT projects, changes, and unplanned work. You can only manage what you can see, so the first job is making all four visible on a board instead of letting them collide invisibly.
- Unplanned work is the most expensive kind because it isn't work at all, it's antiwork: firefighting that steals capacity from planned commitments. Every recovery hour is an hour not spent on the projects the business is counting on.
- IT is a factory, not a mystery. Just as a plant floor has work centers, WIP, and throughput, IT has the same physics, so the plant-floor discipline of the Theory of Constraints applies directly to technology work.
The other 4 — and the full 11-minute summary — are in the app.
What’s inside: 8 chapters
The whole summary runs about 11 minutes, read or listened to.
- The 3 AM Phone Call
- Meet Erik and the Idea of the Plant Floor
- The Four Types of Work
- Brent, the Human Bottleneck
- Freezing the Work: WIP and Kanban
- The First Way: Flow
- The Second and Third Ways: Feedback and Learning
- Phoenix Rises and the Business Reborn
Finish The Phoenix Project tonight.
Read or listen to the full summary in about 11 minutes, then keep the ideas with a minute of review a day. Start with the 2-minute quiz — no card required.