Topic
Lencioni five dysfunctions of a team
Weak Weak
Patrick Lencioni's The Five Dysfunctions of a Team (2002) presents a pyramid of five stacked dysfunctions, each enabling the one above it. It is widely used with leadership teams because it is memorable and it names the avoidance patterns executives recognize in themselves.
Evidence: Weak. A business fable, not research: no validation, no sample, no measurement. It remains popular because executives recognize themselves in it, which is a fact about resonance rather than about accuracy. Its first level overlaps heavily with psychological-safety, which covers similar ground with far better evidence, and the commitment principle — people commit to decisions they disagree with if they were genuinely heard — is consistent with procedural justice research.
Use when: working with an intact leadership team that is polite, busy, and not achieving much together.
Do not use when: the problem is structural, or the "team" is actually a collection of individuals with no shared work. Many executive groups are the latter, and no amount of trust work makes them a team.
The pyramid, bottom up
Absence of trust. Specifically vulnerability-based trust: the willingness to say "I was wrong", "I need help", "I don't know". Its absence produces invulnerability — people manage impressions instead of working.
Fear of conflict. Without trust, teams create artificial harmony. Real disagreement moves to corridors and side channels. The tell is the meeting that ends with agreement and is relitigated by email that evening.
Lack of commitment. Without open conflict, people do not buy in. They comply. Lencioni's key claim: people will commit to a decision they disagree with if they believe they were genuinely heard. Consensus is not required; being heard is.
Avoidance of accountability. Without commitment, peers will not challenge each other's behavior or performance. Everything routes to the leader, who becomes the sole source of accountability and therefore the bottleneck.
Inattention to results. Without peer accountability, individuals pursue their own unit's status, budget, or ego over the collective result. This is the visible symptom that usually prompts the call for help.
The diagnostic sequence
Work bottom up. Attacking inattention to results directly — with dashboards, targets, and exhortation — fails when the cause is three levels below. Ask:
- Do people admit mistakes in front of each other? (1)
- Does the team have real, unscripted arguments about important things? (2)
- Can everyone state the last three decisions and why they were made? (3)
- Does anyone challenge a peer without going to the boss first? (4)
- Do people prioritize their function over the shared goal? (5)
Interventions per level
| Dysfunction | Practical moves |
|---|---|
| Trust | Personal histories exercise; leader goes first with a real admission; behavioral profiles used for understanding, not labelling |
| Conflict | Name conflict as a norm; assign a devil's advocate; "mining" for buried disagreement; explicitly ask the quiet person |
| Commitment | Cascading messaging at the end of every meeting: what we decided, what we tell our teams; deadlines forced; worst-case scenario analysis |
| Accountability | Publish goals and standards; regular peer progress reviews; team rewards rather than only individual ones |
| Results | A single, visible scoreboard of collective outcomes; reward team results |
Examples by audience
Health care: a hospital executive team where each director defends their directorate's budget is at level 5, caused by level 2 — nobody will say aloud that one service is over-resourced relative to need. The finance meeting cannot fix that.
Software: an engineering leadership group that agrees on a technical direction in the meeting and whose teams then continue as before is at level
- The decision was never actually made; it was announced into silence.
Executive: Lencioni's most useful question for a CEO — "which team is your first team: the one you lead, or the one you're a member of?" Executives who answer "the one I lead" are describing level 5, and the answer is usually honest and usually the problem.
Limitations
- No empirical validation; a business fable, not research. See evidence-based-practice.
- Overlaps heavily with psychological-safety, which has far better evidence for the same first level.
- Assumes a real team with genuine interdependence. Applying it to a group that merely reports to the same person produces frustration.
- The vulnerability exercises can be intrusive and coercive if run badly, particularly where there is a real power gradient in the room. Participation must be genuinely optional. See od-ethics.