The Phoenix Project

OMG I loved the chaos of the Phoenix Project! Reading this, you’ll find a resemblance to The Goal and… Spoiler Alert! It is inspired by it. I think I loved reading this because I could relate so well to the $hit-show that the main character gets put into and it reminded me of joining a place where it was chaotic.

The Phoenix Project is based off DevOps principles, lean manufacturing, and the theory of constraints. This book touts 3 foundational principles which are:

The First Way: Flow (Left-to-Right)
Accelerating the movement of work from Development into IT Operations. This means reducing work-in-process, eliminating handoff friction, automating build and deployment pipelines, and ensuring non-bottleneck steps don’t overload downstream systems.

The Second Way: Feedback Loops (Right-to-Left)
Creating rapid, real-time feedback from Operations back to Development. This involves continuous monitoring, immediate automated testing, and fast error detection so issues are caught instantly rather than during a risky production deployment.

The Third Way: Continual Learning and Experimentation
Fostering a culture of high trust, continuous practice, and taking calculated risks. It emphasizes learning from failures (like post-mortems without blame) and constantly improving daily work.

After this book, Gene Kim wrote The DevOps Handbook and the Unicorn Project.