Five Dysfunctions Team

---
name: five-dysfunctions-team
description: Hierarchical model identifying five interconnected team dysfunctions with systematic remediation strategies
---

# The Five Dysfunctions of a Team

## Overview

Patrick Lencioni's The Five Dysfunctions of a Team (2002) presents a hierarchical model of team failure modes, where each dysfunction builds upon the previous. The insight: team problems are interconnected and must be addressed in order - you can't fix accountability issues if there's no trust. The five dysfunctions form a pyramid: Absence of Trust (foundation) leads to Fear of Conflict, which causes Lack of Commitment, enabling Avoidance of Accountability, culminating in Inattention to Results. Fixing teams requires working bottom-up through this hierarchy.

## When to Use

- Diagnosing why a talented team underperforms despite individual competence
- Building new teams with healthy dynamics from the start
- Turning around dysfunctional teams with chronic interpersonal issues
- Training managers to recognize and address team problems systematically
- Facilitating team retrospectives or offsites focused on team health
- Merging teams from different organizations or cultures
- Addressing symptoms (finger-pointing, missed deadlines) by finding root causes

## The Process

### Step 1: Assess Current State Against Five Dysfunctions

Evaluate team against each dysfunction level. Start at the foundation (trust) - problems at higher levels often stem from unresolved issues below. Use team assessment surveys, observe meetings, conduct 1-on-1 interviews. Identify which dysfunction is the primary blocker. **Example:** Team avoids conflict in meetings (Dysfunction 2), but root cause is team members don't know each other personally and fear judgment (Dysfunction 1 - Trust).

### Step 2: Build Vulnerability-Based Trust (Foundation)

Trust isn't prediction of behavior - it's vulnerability. Team members must feel safe admitting mistakes, weaknesses, and asking for help. Build through: personal histories exercise (share background, challenges), team effectiveness exercise (each member identifies what others do well/need to improve), personality assessments (Myers-Briggs, DISC). Leader must model vulnerability first. **Example:** CEO opens leadership retreat by sharing his biggest failure and what he learned from it.

### Step 3: Master Productive Conflict (Level 2)

Teams that trust each other can engage in unfiltered, passionate debate about ideas without personal attacks. Distinguish between ideological conflict (good - about ideas) and interpersonal politics (bad - about ego). Mine for conflict - draw out disagreements rather than avoiding them. Real-time permission: call out when team is avoiding necessary conflict. **Example:** In product debates, facilitator asks: "Does anyone disagree with this direction? If so, let's hear why - we need all perspectives."

### Step 4: Achieve Genuine Commitment (Level 3)

Commitment requires clarity and buy-in, not consensus or certainty. After productive conflict, team must commit to decisions even if they initially disagreed. Two requirements: (1) Everyone's input was genuinely heard; (2) Decision is clear and explicit. Cascading communication: team members communicate decisions consistently to their teams. **Example:** After 2-hour debate, leader says: "We're going with Option B. Even those who preferred A, are you committed to making B succeed?"

### Step 5: Embrace Peer-to-Peer Accountability (Level 4)

Accountability isn't just manager-to-direct-report - peers must hold each other to commitments. Requires: clear standards of behavior, team agreements on deliverables, willingness to call out peers when standards slip. Publication of goals and standards. Regular progress reviews where peers evaluate each other. **Example:** Team agrees on specific weekly commitments. In weekly meeting, each member reports on commitments; peers provide direct feedback on what was missed.

### Step 6: Focus on Collective Results (Apex)

Teams must prioritize collective outcomes over individual/departmental goals. Status and ego are enemies - team members must be willing to sacrifice personal wins for team success. Declare collective goals publicly. Tie rewards to team outcomes, not just individual metrics. **Example:** Sales team compensated on team quota attainment, not individual numbers. Engineering team celebrates feature launches, not individual PR counts.

### Step 7: Reinforce Through Ongoing Practice

These dysfunctions never fully disappear - they require constant attention. Build practices into team rhythms: start meetings with personal check-ins (trust), explicitly invite dissent (conflict), end meetings with clear commitments (commitment), do peer reviews (accountability), review team metrics weekly (results). Leader's job is to model and reinforce at every level. **Example:** Quarterly team health assessments scoring each dysfunction level, with action items for areas below target.

## Example Application

**Situation:** Executive team of 7 leaders avoiding hard conversations. Board requests being deflected with "we're working on it." Finger-pointing between departments. Company results declining despite individual department metrics looking fine.

**Application:**
- Step 1: Assessment revealed severe trust deficit (team members didn't know personal backgrounds, wouldn't admit weaknesses), leading to conflict avoidance on strategic issues
- Step 2: Two-day offsite with personal history exercise - each leader shared upbringing, career challenges, biggest professional failure. CEO shared first, modeling vulnerability
- Step 3: Introduced "real-time permission" - anyone can call out when team is avoiding necessary debate. Designated "miner of conflict" role for difficult discussions
- Step 4: Changed meeting structure: decisions end with commitment statement from each member, even those who disagreed
- Step 5: Implemented peer accountability: each leader publicly committed to 3 quarterly priorities, reviewed monthly with peer feedback
- Step 6: Defined company-level success metrics. Tied 30% of bonus to company results, not just department performance

**Outcome:** Over 6 months, executive team meetings transformed from polite status updates to passionate strategic debate. Cross-functional projects that had stalled for years got resolved. Company results improved 25% as departments optimized for company success rather than departmental metrics.

## Anti-Patterns

- Trying to fix accountability issues when trust foundation is missing
- Confusing "nice" with "trust" (artificial harmony is dysfunction, not health)
- Forcing consensus instead of requiring commitment after debate
- Manager-only accountability (peers never confront each other)
- Individual metrics that undermine collective results
- One-time offsite without ongoing reinforcement practices
- Skipping levels - jumping to results focus before building trust
- Punishing vulnerability (team member admits mistake, gets criticized)
- Avoiding conflict to preserve relationships (destroys real relationships)

## Related

- Radical Candor - framework for direct feedback that complements accountability layer
- High Output Management - complementary framework for team performance optimization
- Psychological Safety (Amy Edmondson) - academic research supporting trust foundation
- Team Topologies - organizational design that enables team health
- The Advantage (Lencioni) - organizational health framework building on Five Dysfunctions
- Crucial Conversations - communication skills for productive conflict
- DACI/RACI - decision frameworks that clarify commitment expectations