Episode 13 · 17 minutes

The Five Dysfunctions of a Team: A Leadership Fable

by Patrick Lencioni, 2002

The pyramid every executive can draw, built on a novel about a company that never existed. For neurodivergent leaders: keep the goal of the trust layer and drop the prescribed method, because mandated personal disclosure is a tax collected unevenly and reliability is a legitimate form of trust.

Find The Five Dysfunctions of a Team: A Leadership Fable at Bookshop.org Affiliate link. It supports the show at no cost to you.

Transcript

The whole episode in text, 88 lines. Miles and Nora are synthetic voices reading a script approved by Logan Williamson, LPC.

Read the full transcript

Miles: A technology company has more money, more experience, and a better board than anyone it competes with. Two years in, it's losing to firms with a fraction of its resources. The executives are individually excellent and collectively useless. They sit in meetings agreeing with each other and then leave and do whatever they were going to do anyway.

Miles: A new chief executive arrives and spends her first weeks doing something the board finds alarming. She holds offsite meetings and asks people where they grew up.

Miles: Today: The Five Dysfunctions of a Team, by Patrick Lencioni. In two sentences: teams fail in a predictable sequence that starts with the absence of trust and ends with people caring more about their own status than the collective result. Fix them in order, because each one rests on the one below it.

Miles: Sixty Books. Presented by Stoar Consulting and Coaching.

Miles: Here in the reading room, it's Sixty Books, and I'm Miles. Sixty management books, the best the last hundred years produced, one per episode, and every one of them read for leaders and teams who think differently and for work where AI now has a seat at the table. Nora's brought the research.

Miles: Nora, this book is written as a novel, which is unusual for the shelf.

Nora: It's a business fable. Roughly two thirds is a made up story about a made up company, and the model is explained in about twenty pages at the back. That format is a large part of why it sold, and it's also the first thing we'll have to be plain about.

Miles: Give me the pyramid.

Nora: Five layers, bottom to top. Absence of trust. Fear of conflict. Lack of commitment. Avoidance of accountability. Inattention to results.

Miles: Start at the bottom.

Nora: Trust, and Lencioni is unusually specific about what he means. He's not talking about predictive trust, the confidence that a colleague will do what they said. He means vulnerability based trust: the willingness to say I was wrong, I don't know, I need help, in front of the people you work with.

Miles: And the mechanism.

Nora: Without it, people spend energy managing impressions rather than doing work. His exercises are things like having each person describe where they grew up, how many siblings they have, and the hardest challenge of their childhood. Low stakes disclosure to make higher stakes disclosure normal.

Miles: Okay.

Miles: Layer two.

Nora: Fear of conflict, which produces what he calls artificial harmony. Meetings that are pleasant and decide nothing, followed by the real meeting in the parking lot. His claim is that a team incapable of open ideological disagreement can't make a decision anyone believes in.

Miles: And that connects up.

Nora: Directly to layer three, commitment. His argument is that people don't need to get their way in order to commit. They need to have been genuinely heard. Which is the classic disagree and commit, and it only works if there was a real disagreement to begin with.

Miles: Layer four.

Nora: Accountability, and his claim on this one is that it has to run peer to peer rather than flowing only from the leader. If the only person who calls out a missed commitment is the boss, the team is a hub and spoke arrangement rather than a team.

Miles: And the top.

Nora: Attention to collective results rather than individual status or departmental outcomes. He wants a small number of shared, visible measures that everyone is judged against.

Miles: Who's this?

Nora: Patrick Lencioni, born nineteen sixty five in California. He worked at Bain, then Oracle, then was a vice president of organizational development at a software company, and in nineteen ninety seven founded a consultancy called The Table Group.

Miles: And the books.

Nora: A great many, nearly all in fable form. The Five Temptations of a CEO, Death by Meeting, The Advantage, The Ideal Team Player. He's one of the most commercially successful management authors alive, and this book has sold in the millions.

Miles: Now the neurodiversity turn, and I want to start at the bottom of the pyramid, because that's where I think this book has a real problem.

Nora: Vulnerability based trust. And I want to be careful, because the underlying insight is sound. A team where nobody can admit error will hide errors, and that's genuinely fatal.

Miles: But.

Nora: But the mechanism he prescribes is group emotional disclosure, performed on demand, in front of colleagues. Tell the room about the hardest part of your childhood. And there are people for whom that isn't a small ask, and the reasons have nothing to do with whether they're trustworthy.

Miles: Say who.

Nora: Anyone whose personal history is genuinely difficult. Anyone who has learned that disclosure at work has costs, which includes a great many neurodivergent adults who have watched a disclosure change how they were treated. And anyone for whom performing spontaneous personal warmth in a group is effortful in a way it isn't for others.

Miles: And what happens to those people in this framework?

Nora: They get read as low trust, which in this model is the foundational dysfunction. The person who's entirely reliable, who says what they'll do and does it, and who declines to discuss their childhood with the sales director, has been placed at the bottom of the pyramid.

Miles: Now, he explicitly dismisses the alternative.

Nora: He does, and this is where I'd push back hardest. He calls predictive trust insufficient, almost a lesser form. But predictability based trust, meaning I know what you'll do and you do it, is more accessible, more verifiable, and arguably more robust than disclosure based trust. It doesn't depend on how anyone felt in a room on a Tuesday.

Miles: So what's the repair?

Nora: Keep the goal and widen the routes. The actual objective is that people can say I was wrong and I don't know. You can build that with structure instead of intimacy. Written pre-mortems. Blameless post mortems, which we met with Collins in episode one. A standing agenda item where the leader goes first and says what they got wrong. Those produce the same behavior without requiring anybody to perform openness.

Miles: Right.

Miles: Layer two is friendlier to us.

Nora: Much. Fear of conflict and artificial harmony describe an organization that has trained everyone to nod. And the person most likely to break artificial harmony is the person who says the true thing without checking the room first.

Miles: Which is the trait that gets penalized.

Nora: Under this framework it's the trait the team needs. Lencioni would call that person a resource for mining conflict. Most performance reviews call them abrasive. Same behavior, and the difference is entirely in whether the organization has read this book.

Miles: Fair enough.

Miles: What about accountability?

Nora: This is the layer I'd flag as risky. Peer to peer accountability is powerful and it's also social pressure without a formal process. If the standards are written down, it's fair. If the standards are unwritten norms about tone, responsiveness, or how present someone seems, then peer accountability is a mechanism for enforcing conformity, and it'll land hardest on whoever is already visibly different.

Miles: And there's a tool in the book I want to name.

Nora: He recommends personality profiling to help teams understand each other, and a personality indicator you'd recognize turns up. We're not in the business of grading instruments here. What I'd say is that nothing at work should be resting on one, and that profiling is the sort of thing that gets used to reframe an access need as a personality quirk, which is the exact downgrade we warned about in episode twelve.

Miles: There's a second book's worth of material he folds in about meetings, and I want it because it's the most concrete thing he offers.

Nora: His argument is that meetings are terrible because we run one undifferentiated kind for every purpose, so a five minute administrative item and a strategic decision compete for the same attention. He wants them separated by type. A short daily check in. A weekly tactical meeting for metrics and obstacles. A separate monthly strategic meeting for the two or three hard questions. And a quarterly offsite.

Miles: And the rule that makes it work.

Nora: That the strategic topics are never allowed into the tactical meeting, because they'll eat it and be handled badly.

Miles: Now the neurodivergent version.

Nora: Enormously helpful. A meeting with one declared purpose, a known length, and a known format is something a person can prepare for. The undifferentiated meeting, where the agenda drifts and the mode shifts without announcement, requires continuous real time recalibration, which is expensive for anyone and very expensive for some.

Miles: And the preparation point.

Nora: Worth stating plainly. If topics are published in advance, the people who think well slowly arrive with their thinking done. If they're not, the meeting systematically rewards whoever thinks fastest out loud, which is a trait rather than a qualification.

Miles: Mm-hm.

Miles: What would you strike?

Nora: Begin with what it is. The evidence in this book is a novel. The company is invented, the executives are invented, and the turnaround is written by the person proposing the model. That isn't a criticism of fables as teaching tools, and it does mean there's no case here at all in the evidentiary sense.

Miles: Has the model been tested?

Nora: Not meaningfully as a causal hierarchy. There's no good evidence that the five sit in that order, that fixing one unlocks the next, or that the sequence matters. The assessment instrument is a commercial product from the author's own firm. The pyramid is a teaching device that has been mistaken for a finding.

Miles: And the overlap with real research.

Nora: This is the part worth keeping. The strongest layers, trust and conflict, are gesturing at psychological safety, which has been studied properly and which we'll do carefully when we reach Amy Edmondson. When this book gets quoted in a room, the useful move is to translate it into that literature, where the ground is firmer.

Miles: One more criticism, which is about the fable itself.

Nora: In the story the resistant executive is eventually removed, and the team improves. That's a very tidy resolution, and it teaches a lesson the author may not intend: that the person who won't participate in the trust exercises is the problem to be excised.

Miles: And in a real organization.

Nora: The person declining the exercise may be protecting themselves for excellent reasons, or may simply be someone for whom the format doesn't work. A framework that ends with removing the holdout is a framework with a disparate impact, and nobody running it'll describe it that way.

Miles: And the shelf it belongs on.

Nora: A fable with a memorable model, no empirical support for its structure, and one genuinely valuable idea, which is that pleasant meetings are frequently a symptom rather than a sign of health.

Miles: Here's the recap, run through our usual frame. Five Dysfunctions says teams fail from the bottom up, starting with trust. For anyone whose thinking runs differently, or who leads people whose thinking does, the operating instructions run like this. Keep the objective of the trust layer and drop the prescribed method, because reliability is a legitimate form of trust and mandated personal disclosure is a tax collected unevenly. Treat the person who breaks artificial harmony as the asset the model says they are. Insist that peer accountability runs against written standards rather than unwritten norms about tone. And keep personality typing out of decisions about people, because it isn't measuring what it claims to measure.

Miles: And the tools.

Nora: The useful angle is that most of this book is about what happens inside meetings, and meetings are the least accessible artifact in an organization. The disclaimer has been moved to the end of the episode, in one wording that stays put between offsites.

Miles: Off you go.

Nora: The mechanism the book wants is that disagreement surfaces before a decision rather than in the parking lot afterward. Written pre-reads and asynchronous comment do that better than a room does, and these tools lower the cost of producing them. A person who can't get a word in during a fast meeting can put a considered disagreement in the document the night before, and it can't be talked over.

Miles: And on the accountability layer.

Nora: Commitments in writing, with owners and dates, generated from the meeting rather than remembered from it. That removes the working memory tax and it also removes the argument about who agreed to what.

Miles: Where's the risk?

Nora: Two. If the model's answer to distrust is more disclosure, a tool that drafts your disclosures for you produces performed vulnerability, which is worse than none. And the second is the book's own diagnosis turned on the tool. Minutes generated from a meeting are only as good as the meeting. If the room was artificial harmony, the summary is artificial harmony with headings, and Lencioni's whole point is that the pleasant meeting was the symptom. A tool can transcribe that. It can't treat it.

Miles: That's The Five Dysfunctions of a Team.

Miles: Next time: The Culture Code, by Daniel Coyle, and the uncomfortable question of what a group is actually reading when it decides you belong.

Nora: Eye contact, mirroring, turn taking. I've already got a list of who those cues miss.

Miles: Thanks, Nora. That was thorough.

Nora: Happily.

Miles: That's the book. Tomorrow.

Miles: Sixty Books is a production of Stoar Consulting and Coaching. Logan Williamson is a Licensed Professional Counselor in Texas and Louisiana. Today's episode was one book, discussed for leaders and teams, as education. It coached nobody, counseled nobody, and judged nobody listening.

Nora: The episode page holds the transcript, and every claim on it links to its source. Another book tomorrow.

Miles: A word about us. Miles and Nora are voices, synthetic ones, not people, and neither carries a license of any kind. Nothing said here was about you. Each script is drafted with AI assisting, and Logan Williamson, a Licensed Professional Counselor in Texas and Louisiana, at Stoar Consulting and Coaching, edits them and gives each one his approval.

Nora: And one note about the AI segment. The evidence that these tools help neurodivergent people at work is early. There are controlled trials now, but they measure things like conversation skill rather than how a job actually goes, and for work itself most of what exists is individual providers reporting success. So take it as promising and not proven. The tools also get rebuilt every few months, so whatever you set up today is built on something that moves.

Sources

The claims in this episode, in the order they come up, with where each comes from. These were sourced after the episode was published, and a claim we could not trace to a source is left off rather than guessed at. 9 claims. Studies in psychology and medicine were checked on PubMed; everything else against the publisher, the paper or the original record.

See the sources
  1. The fable's company, DecisionTech, is a Silicon Valley start-up with ample capital, an experienced executive team and leading technology, yet it is missing deadlines and falling behind; its board replaces the chief executive with a new leader, Kathryn Petersen.

    Shortform, summary of The Five Dysfunctions of a Team, https://www.shortform.com/summary/the-five-dysfunctions-of-a-team-summary-patrick-lencioni : startup capital, an experienced executive team, a solid plan and leading technology, alongside missed deadlines, rising turnover and an eroding cash position; the board replaces the chief executive.

    Four Minute Books, https://fourminutebooks.com/the-five-dysfunctions-of-a-team-summary/ : "all the investors and well-qualified executives you would ever need".

    Wikipedia, https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Team : Kathryn Petersen, newly appointed chief executive of the fictional DecisionTech.

  2. The new chief executive takes the team to offsite meetings and has its members share their personal histories as a first step toward trust.

    SuperSummary, https://www.supersummary.com/the-five-dysfunctions-of-a-team/summary/ : the Napa Valley retreat where Kathryn has members share personal histories to build trust.

  3. The book's thesis: teams fail through five dysfunctions, from absence of trust at the base to inattention to results at the top.

    Lencioni, P. (2002). The Five Dysfunctions of a Team: A Leadership Fable. Jossey-Bass. ISBN 9780787960759. 229 pages (Wikipedia, as in item 1).

    The Table Group, "The Five Dysfunctions of a Team," https://www.tablegroup.com/topics-and-resources/teamwork-5-dysfunctions/ , the author's firm's statement of the model.

  4. Patrick Lencioni, born about 1965 and raised in California, worked at Bain, at Oracle, and as vice president of organization development at a software company, before founding The Table Group in 1997.

    Patrick Lencioni, Wikipedia, https://en.wikipedia.org/wiki/Patrick_Lencioni : born c. 1965; grew up in Bakersfield, California; Bain & Company, Oracle Corporation, and Sybase as VP of Organization Development.

    The Table Group, "About," https://www.tablegroup.com/about/ : "In 1997, we started The Table Group".

  5. This book has sold in the millions.

    The Table Group book site, https://fivedysfunctions.tablegroup.com/ : over five million copies sold.

  6. Lencioni's meeting model separates four kinds of meeting: a daily check-in, a weekly tactical meeting on metrics and obstacles, a monthly strategic meeting on critical issues, and a quarterly off-site review.

    The Table Group, "Managing People," https://www.tablegroup.com/topics-and-resources/managing-people/ : daily check-in, weekly tactical, monthly strategic, quarterly off-site review, with their purposes; the page lists the model under Death by Meeting.

    Lencioni, P. (2004). Death by Meeting. Jossey-Bass (year per Wikipedia, as in item 10).

  7. The book is fiction and not a research study, and its recommendations have not been shown to work as described; one review notes that personal disclosure exercises are unlikely to build trust in a dysfunctional team.

    Curphy, G., & Hogan, R. (2012). The Rocket Model: Practical Advice for Building High Performing Teams. Hogan Press. ISBN 9780984096985, pp. 19-21, as summarized in Wikipedia, as in item 1: the book is "explicitly a work of fiction", not research based, and its recommendations lack empirical support; disclosure exercises are unlikely to build trust; real work together is what builds it.

  8. Psychological safety, a shared belief that a team is safe for interpersonal risk taking, has been studied directly in the field: in 51 work teams at a manufacturing company, it was associated with learning behavior, which in turn was associated with team performance.

    Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. DOI: 10.2307/2666999 . Abstract read through the OpenAlex record, https://api.openalex.org/works/doi:10.2307/2666999 . Not indexed on PubMed.

  9. Next book: The Culture Code: The Secrets of Highly Successful Groups, by Daniel Coyle (2018).

    Coyle, D. (2018). The Culture Code: The Secrets of Highly Successful Groups. Bantam Books. ISBN 9780804176989. 280 pages (Open Library record).

All Sixty Books episodes · Subscribe by RSS