Five Dysfunctions of a Team

---

Origins

Patrick Lencioni published The Five Dysfunctions of a Team in 2002¹. The book is structured as a leadership fable — a fictional Silicon Valley CEO inheriting a dysfunctional executive team — followed by a compact model section that distills the lessons into a pyramid of five interconnected problems.

The format made the book unusually durable. Models presented as fables tend to stick where dry frameworks fade. Two decades on, Lencioni's pyramid is one of the most-cited tools for diagnosing team dysfunction across software, leadership, and organizational coaching contexts. Its enduring usefulness comes not from any single dysfunction, but from the relationship between them: each one is caused by the one below it, and each one enables the one above it.

The Pyramid

Lencioni's five dysfunctions are stacked from foundation to peak. The base must be addressed first; otherwise the layers above it cannot be repaired.

1. Absence of Trust

The foundation. Trust here is not predictability or competence — it is vulnerability-based trust: the willingness to be honest about weakness, mistake, or limitation in front of teammates. Without it, team members protect their image rather than engage with the work, and every conversation carries an undercurrent of guarded self-presentation.

2. Fear of Conflict

When trust is absent, real disagreement feels too risky. The team produces what Lencioni calls artificial harmony: meetings end with apparent agreement, the real conversations happen in side-channels, and decisions get made without the team's full perspective ever surfacing. Productive conflict over ideas is replaced by passive-aggressive workarounds.

3. Lack of Commitment

Decisions made without real conflict produce shallow commitment. Team members nod at the outcome without truly buying in, because they never had the chance to argue for or against it. The result is ambiguity — people leave the meeting with different interpretations of what was decided, and the team's actions diverge from there.

4. Avoidance of Accountability

Without clear commitment, peers cannot hold each other accountable. Calling someone out for behavior the team never explicitly agreed to feels unfair, so it does not happen. Standards quietly drop. The team relies entirely on the leader for accountability, which scales poorly and creates dependence.

5. Inattention to Results

At the top of the pyramid, individuals optimize for their own goals — status, ego, career, departmental success — rather than the team's results. This is the visible failure mode that observers usually notice first, but it is downstream of everything below it. Treating it directly without addressing the foundation rarely works.

Why the Order Matters

The pyramid is not a checklist. It is a causal model: trust enables conflict, conflict enables commitment, commitment enables accountability, accountability produces results. Skipping a level is the most common way teams misuse the framework.

Leaders who try to fix "lack of results" by setting tougher targets, or "lack of accountability" by adding performance reviews, treat symptoms while the root cause continues to produce them. The team that cannot disagree productively cannot commit; the team that cannot commit cannot hold itself accountable; the team that cannot be accountable will optimize for individual rather than collective results, no matter what the dashboard says.

Diagnosing a Team Against the Pyramid

A team using the model usually starts with a self-assessment: where on the pyramid does dysfunction first appear? Lencioni's book includes a 15-question diagnostic, but team conversations often produce richer signal.

• Trust signals: Does anyone admit a weakness or a mistake out loud? Do people ask for help across roles?
• Conflict signals: Are meeting discussions richer than meeting summaries suggest? Do real disagreements surface in the room, or only afterward?
• Commitment signals: When the team leaves a decision meeting, would each member describe the decision the same way?
• Accountability signals: Do peers challenge each other's behavior, or is that work outsourced to the leader?
• Results signals: When team goals and individual goals conflict, which wins?

The lowest level where weakness appears is where the work needs to start.

Repairing the Pyramid

Each dysfunction has its own repair pattern. Lencioni's Overcoming the Five Dysfunctions of a Team² details exercises and team workshops; in practice, the most common moves look like this:

• Trust: structured vulnerability exercises (personal histories, behavioral self-assessments). Leader goes first.
• Conflict: explicit working agreements about how disagreement happens. Conflict-norming conversations.
• Commitment: cascading communication after decisions ("here is what we agreed, here is what changes Monday"). Disagree-and-commit norms.
• Accountability: team scorecards visible to everyone. Peer-to-peer feedback practices.
• Results: shared team metrics. Recognition tied to collective rather than individual outcomes.

Common Misuses

The framework gets misused in two predictable ways.

The first is treating the pyramid as a one-time diagnosis. Lencioni's model describes patterns of behavior, not states a team passes through and graduates from. Trust erodes; conflict slides back into harmony; commitment fades with personnel changes. The pyramid is a recurring lens, not a checkpoint.

The second is using the model as a stick. "We have a lack of accountability problem" can become a way to blame individuals rather than examine the trust and conflict layers below. The framework's value is diagnostic, and diagnoses point at systems, not people.

Coaching Tips

Find the Lowest Crack

Diagnose down the pyramid until you find the first place dysfunction appears. Spending effort above it will not produce lasting change.

Trust Starts with the Leader

Vulnerability-based trust is impossible to coach into a team whose leader will not model it first. If the leader will not go first, start there before you start with the team.

Notice the Side Conversations

If the real opinions show up in DMs and hallway chats but not in the meeting, the team has artificial harmony. Make that observation out loud in a retro.

Test Commitment Explicitly

At the end of a decision, ask each member to state in their own words what was decided. The variance in answers is the missing commitment.

Resist Diagnosis as Blame

"We have an accountability problem" can become a way to single out individuals. Steer the conversation back to systems — what makes accountability hard here, not who is failing.

Revisit the Pyramid

Schedule a re-diagnosis quarterly. Trust drifts, new members shift dynamics, accountability erodes with role changes. Make checking the foundation a habit.

Summary

The Five Dysfunctions of a Team has endured because its structure mirrors what actually happens when teams break down. The performance problem you can see is rarely the one to solve. The team that consistently misses results is usually one whose individuals are protecting their own positions; that protective behavior comes from a team where accountability is the leader's job alone; that absence of peer accountability comes from commitments nobody truly made; those weak commitments come from meetings without real disagreement; and that artificial harmony comes from a team where it is not safe to be wrong.

The repair work has to start at the bottom of the pyramid. It is slower and more uncomfortable than fixing the visible symptom directly, but it is the only path that holds.

Back to Team Dynamics, Health & Coaching