One-page summary · 2 min read
The Five Dysfunctions of a Team
A Leadership Fable
by Patrick Lencioni
The big idea
Team dysfunction is hierarchical, a team's five failures, absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results, stack on top of each other like a pyramid, so a leader must repair the foundation before higher-level problems can ever be fixed.
A short, low-risk trust-building activity for a team's first meeting: each person answers five prompts aloud, where they grew up, number of siblings, a childhood challenge, their first job, and one unique fact nobody else knows, while the rest of the team listens without interrupting or reacting. It typically takes under an hour and is designed to build vulnerability-based trust before deeper conflict work is attempted.
Lencioni presents this as an entry point, not a fix on its own; teams with deep-seated distrust may need repeated or more structured exercises to get real traction.
Key ideas
Vulnerability-based trust
Trust here isn't about predictability or competence, it's teammates being willing to say I was wrong, I need help, or I don't know, without fear of judgment.
Mining for conflict
Teams that avoid disagreement aren't harmonious, they're unhealthy; leaders must actively surface buried disagreements through structured, ideological debate rather than personal attacks.
Commitment comes from being heard, not consensus
People will commit to a decision they disagree with if they know their view was genuinely considered, ambiguity, not disagreement, kills buy-in.
Peer-to-peer accountability
The most effective accountability isn't top-down from the leader; it's team members holding each other to shared standards directly and uncomfortably.
Inattention to results
When individuals protect personal ego, status, or their own department's metrics over the team's collective scoreboard, the whole team's outcomes suffer.
The cascading pyramid model
Each dysfunction causes the one above it, so diagnosing where a team is stuck matters more than attacking symptoms at the top.
Try it this week
- Run the Personal Histories Exercise at your next team meeting, giving each person 2-3 minutes to answer the five prompts.
- Before ending your next decision-making meeting, explicitly restate the decision reached and ask each person to voice any lingering disagreement in the room, not later in the hallway.
- Identify one issue your team has been avoiding and put it on the agenda as a structured debate, not a passing comment.
- Create one shared, visible team scoreboard metric and review it as a group weekly.
Is it for you?
Best for
- New leaders standing up a team from scratch
- Leaders who sense artificial harmony, a team that never disagrees but also never gets much done
Less useful if
- The fable format, roughly two-thirds of the book is a fictional story, can feel slow for readers who want a dense, non-narrative how-to guide
- The model is built around a single intact team with one clear leader, so it translates less directly to loosely-coupled cross-functional groups