# Five Dysfunctions of a Team Patrick Lencioni's framework, published in 2002, identifies five ways teams fail — presented not as a list but as a cascade. Each dysfunction is the direct consequence of the one below it remaining unaddressed. This is the model's central and most important feature: the dysfunctions have an order of operations. You cannot repair the top of the pyramid without first repairing the bottom. ## The pyramid **1. Absence of trust (base)** — team members are unwilling to be vulnerable with each other. They guard weaknesses, mistakes, and fears. Energy goes into self-protection and impression management rather than contribution. Lencioni means vulnerability-based trust specifically — not predictability trust ("I can rely on you to show up") but the willingness to say "I was wrong," "I need help," "I don't know." This is the same construct as Edmondson's psychological safety, applied at the interpersonal level. **2. Fear of conflict** — because trust is absent, teams avoid genuine ideological disagreement. Substitute: artificial harmony, polite nods, private reservations, and decisions made in corridors after the meeting. The meeting says yes; the team does not commit. Lencioni's healthy conflict is passionate debate about ideas, not escalating personal positions. Without trust, the two collapse into each other — disagreement feels like attack. **3. Lack of commitment** — without real debate, team members do not commit to decisions. They leave meetings with manufactured consensus that does not hold under pressure. Commitment without debate is submission, not agreement. The sign: decisions are revisited endlessly; there is perpetual ambiguity about what was actually decided and by whom. **4. Avoidance of accountability** — without clear commitment, people avoid holding each other to account. Peer accountability feels punitive or arbitrary when ownership was never genuinely established. Standards drift. The hard conversation is deferred. Managers fill the accountability vacuum — and accountability becomes top-down compliance rather than team ownership. **5. Inattention to results (apex)** — without accountability, individuals and functions default to their own goals, status, or departmental interests over collective outcomes. The team optimises locally. The shared goal is nominal. ## The cascade logic Working directly on accountability before trust is built will not hold — the intervention has no foundation. Working on commitment before the team can have genuine conflict produces surface agreement that evaporates. The order is not negotiable: trust → conflict → commitment → accountability → results. This explains why many team interventions fail. The presenting symptom is usually at the top (results aren't there; accountability is weak), but the cause is at the bottom (trust is absent, conflict is avoided). Intervening at the symptom level without addressing root conditions produces temporary improvement at best. It also explains why team-building activities often do not produce trust in Lencioni's sense. Improving social connection (shared meals, off-sites, personality tests) may increase liking — but liking and vulnerability-based trust are different. You can enjoy someone's company while still being unwilling to admit uncertainty in front of them. ## Coaching and facilitation application The pyramid is a diagnostic. When a team is stuck, start at the bottom: what is the actual level of vulnerability-based trust? How are disagreements handled — is conflict productive or avoided? Are decisions made once and held, or revisited? Are peers holding each other to commitments, or waiting for the manager to do it? The most common misread of the model: taking "we need more conflict" as permission for aggression. Lencioni is precise — productive conflict is about ideas, data, and direction. The facilitator's job is not to encourage conflict regardless of conditions but to create the trust conditions under which conflict is safe to have. In the absence of trust, pushing for conflict accelerates dysfunction rather than resolving it. For leaders: the entry point is almost always vulnerability. The leader who goes first — who names their own uncertainty, admits a mistake publicly, asks for help — changes what is possible for the team. Leadership vulnerability is not weakness; it is the structural precondition for trust. ## See Also - [[Psychological Safety Signals - Deep Dive]] — Edmondson's climate is the condition for Lencioni's vulnerability trust; both are needed, at different levels of analysis - [[Radical Candor - A Lens, Not a Script]] — the quality of conflict Lencioni describes is what Radical Candor is designed to produce - [[Accountability Without Shame]] — the accountability design that resolves level four without recreating fear or blame - [[Feedback Culture in Teams]] — team feedback culture is the operational expression of Lencioni's accountability level - [[Westrum Culture Typology]] — the system-level view of what Lencioni's pyramid produces or destroys; pathological cultures are Lencioni's pyramid fully inverted - [[Social Capital]] — Lencioni's base (vulnerability trust) is the bonding capital that makes everything above it possible - [[Belonging Cues]] — Coyle's micro-behavioural mechanism for building the trust Lencioni requires - [[Patrick Lencioni]] — author of the model; The Five Dysfunctions of a Team (2002)