The Five Dysfunctions of a Team

About the book

Patrick Lencioni presents a model of why teams underperform and delivers it as a leadership fable rather than a conventional management manual. A narrative follows a newly appointed chief executive as she works with a struggling leadership group, and the friction in that story carries the argument. The model identifies five failures that build on one another, beginning with an absence of trust and moving through fear of conflict, lack of commitment, avoidance of accountability, and inattention to results.

The fable format shapes how the book reads. Ideas arrive through meetings, disagreements and decisions rather than through numbered exposition, and the model is drawn out as the characters confront their own behavior. Readers who want the framework stated plainly will find it summarized toward the end, but the story does most of the teaching. The book sits in a long tradition of business parables, and it shares their strengths and limits: memorable situations, simplified people, and a clean diagnostic vocabulary.

Lencioni writes for managers and executives rather than for scholars. The prose is plain and quick, the scenes are short, and the emphasis falls on practical recognition: how a team's meetings, silences and evasions reveal which dysfunction is operating. The book's subject is the leadership team specifically, not project groups or frontline staff, and its examples stay inside that frame.

How to read it

Read the fable first and resist the urge to skip to the model. The story is where the five failures acquire texture, and the later summary lands better once you have watched a group argue past each other. Pay attention to how the chief executive diagnoses problems and how often her own conduct is part of the difficulty.

The model is sequential, so test it in order. Ask whether the trust problem described matches what you see, then conflict, then commitment. The book is short enough for one or two sittings, and its simplicity is deliberate. Treat the framework as a lens for conversation rather than a checklist to apply mechanically, and notice where the fictional scenes smooth over complications that real teams face.

Who it suits

Managers leading a team, executives new to a leadership group, and facilitators looking for shared language will get the most from this book. It suits readers who prefer a story to a textbook and who want a compact vocabulary for naming why meetings feel cautious or decisions fail to stick. Consultants and coaches can use the five failures as a discussion prompt with clients. Readers skeptical of business parables may still find the diagnostic sequence useful, provided they read it as a starting point rather than a complete account of team behavior.

Reading considerations

The fable format simplifies people and situations, and the model offers little on structural constraints such as budgets, cross-team dependencies or organizational politics. The workplace examples reflect the period in which the book was written, and companion workbooks exist, so check which version you have. The central question worth testing is whether the five failures explain your team's difficulties or merely describe their symptoms.