The Five Dysfunctions of a Team: Summary, and What the Research Says

What the book argues

The Five Dysfunctions of a Team: A Leadership Fable is by Patrick M. Lencioni. Jossey-Bass published the hardcover in April 2002 (Wiley, n.d.; Open Library, n.d.). Wiley now lists a 20th anniversary edition, and describes Lencioni as a pioneer of what he calls the organizational health movement (Wiley, n.d.).

The publisher describes the book as equal parts leadership fable and business handbook, revealing five behavioral tendencies at the heart of why even the best teams struggle, with a model and step-by-step guide for overcoming them (Wiley, n.d.). The author's firm sets out the five: an absence of trust, rooted in people's fear of being vulnerable with one another; fear of conflict, where the wish to keep an artificial harmony stifles productive debate; a lack of commitment; avoidance of accountability; and inattention to results, when individual goals and status pull attention away from the team's (The Table Group, n.d.). A 2023 review describes the fable's plot, in which the new chief executive of an underperforming start-up called DecisionTech works with the executive team, and the model as a pyramid in which each level is the foundation for the next (Tolbert, 2023).

In my words: the book's claim is that most team problems further up, such as missed results, trace back to people not trusting each other enough to argue.

Who it is for

Leadership teams that want a shared vocabulary for why they struggle. It is written as an easy-to-read fable (The Table Group, n.d.). It is a weaker guide for teams whose problem is not interpersonal at all, such as unclear roles or too much work.

What the research says

The book is a fable, and its model was not built from published studies. The evidence I use can check two of its claims: that trust matters for team performance, and that working on a team's relationships improves its results.

Trust and performance go together. Breuer, Hüffmeier and Hertel (2016) pooled 52 studies of team trust. According to their abstract, trust was positively related to team performance, and the link was stronger in virtual teams (ρ = .33) than in face-to-face teams (ρ = .22). It was weaker where team interactions were documented, which the authors read as documentation being a useful complement to building trust. The abstract does not say which designs were pooled, so read this as association. Still, it supports the weight the book puts on trust.

Generic team building did less than its reputation. Salas and colleagues (1999) pooled studies of team-building interventions. According to their abstract, team building had no significant overall effect on performance, with a small gain only on subjective measures. Interventions that focused on clarifying roles were more likely to improve performance than those focused on goals, problem solving or interpersonal relations, and effects shrank as teams got bigger. That is older evidence, but it is a caution for any team that reads the book and then runs a trust-building exercise expecting results to follow.

Harsh leadership goes with less speaking up. Liu and Ling (2025) pooled 354 articles and, according to their abstract, found authoritarian leadership and abusive supervision linked to employees speaking up less, through weaker relationships and lower psychological safety. This is correlational evidence that fits the book's link between fear and the absence of productive conflict.

Where the evidence is thin

The pyramid itself, the claim that each dysfunction depends on the one below it, is untested in the evidence I use. Tolbert's (2023) review notes the model's lack of stated or implied academic validation, and calls the story formulaic. The research I could find supports trust as important, not the specific sequence, and the strongest older evidence on team building is mixed at best.

How it maps to the Unfrozen Loop

This mapping is my judgment. Trust and productive conflict are the culture ring of the Unfrozen Loop: safe to speak, and speaking changes something. Commitment fits Make sense together, top included, where a team works out what a change means for its own work before signing up to it. Accountability and attention to results fit Review on a rhythm, then hold the pace, where each review ends with one named fix and one owner. The Salas finding on role clarity is a reminder that some team problems are structural, not about trust.

What I take from it

The book is a good conversation starter, and it is right about trust. The research adds a practical warning: in one older meta-analysis, team building overall did not reliably improve performance, so a trust exercise on its own may not change results. If your team reads it, follow up with something structural. End every team meeting for a month with one decision, one owner and one date, and review them at the next meeting. For a researcher's book on the same ground, see The Fearless Organization, and for more options, the reading list for managers.