Would I recommend it? 100%
Some management books explain a framework. Others change the way you look at organisations. The Phoenix Project firmly belongs in the second category.
What makes the book particularly refreshing is that it is written as a novel rather than a traditional management book. Instead of introducing theories or models chapter by chapter, the authors tell the story of Bill Palmer, an IT manager who unexpectedly finds himself responsible for rescuing a struggling IT department while the future of the company hangs in the balance. That storytelling approach makes the lessons remarkably accessible. Rather than reading about organisational dysfunction, you experience it alongside the characters.
Although the book is often recommended within IT, I believe its relevance reaches much further. At its core, it is a book about how organisations function under pressure, how complexity gradually takes over, and how well-intended people can become trapped in systems that prevent them from succeeding.
A storytelling approach that makes the lessons remarkably accessible
What resonated for me
One of the reasons the book resonated so strongly with me is how recognisable the environment feels. Throughout my career I have worked closely with IT organisations, and many of the situations described could easily have taken place in almost any large company. Everyone is working incredibly hard. Calendars are full, projects continue to multiply and people regularly work evenings and weekends. Yet despite all that effort, progress remains frustratingly slow. The organisation feels permanently busy without ever really moving forward.
The book illustrates beautifully that this is rarely a people problem. It is a system problem.
Energy is spread across too many priorities, teams optimise for their own objectives, and constant interruptions prevent meaningful progress. Everyone is busy, but few people have the time or space to improve the way work actually gets done.
Another theme that stood out to me is the dependence on individual expertise. Almost every organisation has people who seem indispensable because they are the only ones who understand a critical system or process. They become the people everyone turns to when something goes wrong. At first glance, they appear to be the organisation's safety net. In reality, they often become its greatest vulnerability, not because they lack capability, but because critical knowledge has never been shared, documented or passed on. The organisation depends on what they know rather than ensuring others can do the work too.
That observation particularly resonated with me. We often celebrate these individuals as heroes, while unintentionally creating an organisation that becomes increasingly dependent on them. True resilience comes when knowledge is shared, processes are understood by more than one person and success no longer depends on a handful of individuals carrying the weight of the organisation.
The book also offers a compelling reminder that complexity rarely arrives overnight. Organisations seldom decide to become complicated. Complexity accumulates gradually through years of well-intended decisions. Another urgent request is accepted, another workaround becomes permanent, another exception is introduced because there simply isn’t enough time to solve the underlying issue. Before long, the organisation resembles what many IT professionals jokingly describe as "spaghetti": a tangled web of dependencies where even a minor change can have unintended consequences throughout the system.
My Energy Perspective
Perhaps that is why I enjoyed this book so much. Beneath the story about IT lies a much broader lesson about leadership. It reminds us that leadership is not simply about motivating people to work harder; it's about creating the conditions that allow people to do their best work.
Sustainable improvement rarely comes from asking people to work harder. It comes from improving the system within which they work. Once priorities become clearer, bottlenecks are addressed and teams understand how their work contributes to the bigger picture, performance improves naturally; not because people suddenly become more capable, but because their effort finally creates the greatest value.
Reading The Phoenix Project reinforced something I have come to believe over the years and is a theme I repeat often: organisations rarely struggle because they lack talented people, more often, they struggle because talented people are working within systems that no longer support the outcomes they are trying to achieve. It's easy to see delayed projects, missed deadlines and constant firefighting as isolated problems. This book reminds us that they are often symptoms of something much deeper: unclear priorities, fragmented ownership and unnecessary complexity. I believe organisations unlock their potential when people understand what matters most, collaborate across organisational boundaries and focus their limited time and energy on improving the system rather than constantly compensating for it.
A final reflection
If I had to summarise The Phoenix Project in a single sentence, it would be this: organisations become high-performing not because exceptional people solve endless problems, but because leaders create systems in which exceptional people no longer have to.
For anyone involved in technology, transformation or organisational change, I would wholeheartedly recommend this book. Not because it teaches you how to manage IT, but because it changes the way you think about organisations.
