Chapter 2 of The Phoenix Project shows what happens when you inherit a broken system: endless emails, unclear priorities, and pressure from all sides. Bill’s promotion to VP of IT Operations reveals a harsh truth—leadership doesn’t fix chaos; it exposes it. This chapter highlights why managing work flow, not just doing work, is critical for survival.
Chapter 1 of The Phoenix Project throws us straight into the chaos of IT operations—where outages are routine, blame is inevitable, and the business is already falling behind. Through Bill Palmer’s stressful morning, we see a familiar reality: IT isn’t broken because of technology, but because of how organizations manage it. This opening chapter sets the stage for why DevOps isn’t optional—it’s survival.
Most developers build features. I wanted to build systems. So instead of another CRUD app, I started building a real-time chat backend in Go—something simple on the surface, but brutal underneath.