The Five Dysfunctions of a Team
Patrick Lencioni · 2002
Editorial rating
- Evidence
- 5/10
- Actionability
- 8/10
- Originality
- 7/10
The thesis
Teamwork fails for five interconnected reasons - absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. These dysfunctions build on each other like a pyramid: fix the foundation (trust), and the others become solvable.
Who this is for
Team leaders struggling with politics and silos, executives frustrated by lack of alignment, and anyone building or inheriting a dysfunctional team.
My favorite quote
Not finance. Not strategy. Not technology. It is teamwork that remains the ultimate competitive advantage, both because it is so powerful and so rare.
Why it matters
Everyone claims to value teamwork, but few build the vulnerability and accountability it requires. The scarcity is the advantage.
Do this
Rate your team 1-10 on each dysfunction. Which is the weakest link in the chain?
Start here
Trust is the foundation - but it's vulnerability-based trust: Not "I trust you to do your job" but "I trust you enough to admit my weaknesses, ask for help, and say I don't know." Without this, teams default to political posturing, which poisons everything above it in the pyramid.
Critical summary
Lencioni, a management consultant, presents the five dysfunctions through a business fable about a fictional tech CEO (Kathryn Petersen) who inherits a dysfunctional executive team. The fable is followed by a practical framework.
What it gets right
- Clear, memorable pyramid model that builds logically
- Trust as vulnerability, not just reliability
- Conflict as necessary - artificial harmony is the problem
- "Weigh in before buy in" - commitment requires voice
- Fable format makes principles accessible and sticky
What it misses
- Fiction-based: No empirical research or case studies
- Personal history exercises may not build real trust in hostile environments
- Less applicable to remote or distributed teams
- Assumes leaders have authority to implement these changes
- Some dysfunctions (like trust) can take years to address
Evidence is primarily Lencioni's consulting experience packaged as fiction. Intuitive appeal but lacks academic validation.
Key concepts
Absence of Trust
Team members unwilling to be vulnerable - to admit mistakes, weaknesses, or ask for help. Start with personal histories to build connection.
Fear of Conflict
Avoiding productive disagreement leads to artificial harmony and inferior decisions. Encourage passionate debate about ideas.
Lack of Commitment
Without airing disagreements, people don't commit. Clarify decisions and ensure "weigh in" before expecting "buy in."
Avoidance of Accountability
When people don't commit, they don't hold each other accountable. Make expectations explicit and peer-to-peer.
Inattention to Results
Without accountability, individuals prioritize personal status over collective outcomes. Define and publicize team results.
Core insights
-
Trust is vulnerability
It's not "I trust you to perform" - it's "I trust you enough to show my weaknesses."
-
Conflict is necessary
Teams that don't fight about ideas make worse decisions and create resentment.
-
Weigh in before buy in
People commit to decisions when they've had a chance to voice their perspective - even if they disagree.
-
Peer accountability > boss accountability
The best teams hold each other accountable, not just the leader.
-
Results must be collective
When individuals prioritize their own metrics over team outcomes, the team loses.
-
Dysfunction cascades
Each dysfunction enables the next. You must fix them in order, from the bottom of the pyramid.
Implementation steps
Today
- Score your team 1-10 on each of the five dysfunctions
- Identify the weakest link - that's where to focus first
This week
- Run a "personal histories" exercise: Have each team member share non-work background (hometown, siblings, first job)
- In your next meeting, explicitly encourage disagreement on one key issue
This month
- At the end of each meeting, clarify: "What exactly did we decide? Who's doing what by when?"
- Publish team results prominently - make collective outcomes visible
Ongoing
- When conflict arises, lean in rather than smoothing over
- After decisions, ensure everyone can articulate what was decided and why
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Assess your team on all five dysfunctions (1-10 each)
- Day 2
Run a personal histories exercise with the team
- Day 3
Identify one topic where the team has avoided conflict
- Day 7
Facilitate a real debate on that topic - encourage disagreement
- Day 14
At meeting end, explicitly clarify decisions and commitments
- Day 21
Create a team scoreboard: What are the collective results we're tracking?
- Day 30
Re-assess the five dysfunctions. What's improved?
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.
