Lencioni's Five Dysfunctions of a Team

Patrick Lencioni is an American management consultant and author. In 2002 he published *The Five Dysfunctions of a Team* as a business fable: a story about a new chief executive who rebuilds a struggling executive team. The model is set out in a short section at the end of the book.

Lencioni's core claim is that teams fail less because of strategy or skill than because of predictable patterns in how members behave toward each other. He names five such patterns and arranges them in a pyramid, because each one creates the conditions for the next.

The model is aimed mainly at leadership teams, but it is widely used for project and change teams.

Lencioni's model is therefore a practitioner diagnostic, presented through a story rather than through research data.

From the base of the pyramid upward:

1. Absence of trust. Members are unwilling to be vulnerable: to admit mistakes, weaknesses or the need for help. Lencioni means vulnerability-based trust, not trust that a colleague will be reliable.
2. Fear of conflict. Without trust, people avoid open, productive debate about ideas. Lencioni calls the result artificial harmony: polite meetings, with disagreement moved into corridors and private conversations.
3. Lack of commitment. If people have not voiced their views, they do not truly buy into decisions. Lencioni argues that people can commit to a decision they disagree with, provided they have been heard. The visible sign is ambiguity.
4. Avoidance of accountability. Without real commitment, members hesitate to call out peers whose behavior hurts the team. Standards drop.
5. Inattention to results. When no one holds others to account, individual status, ego or departmental goals displace the team's collective results.

The order matters. Swapping commitment and accountability is a common slip; commitment comes first, because people cannot be held to a decision they never bought into.

Lencioni's five dysfunctions therefore form a chain that starts with trust and ends with results.

At Brightwater Health, the steering group for a new patient-records system meets every two weeks. The meetings are calm and short, and decisions are agreed without objection. Yet the same decisions are reopened in private conversations afterward, and two directors quietly continue planning around the old system.

In Lencioni's terms, the polite meetings are the symptom of fear of conflict. Decisions are reopened because no one argued them through in the room, which leads to weak commitment.

What helps:

• The chair asks each member for the strongest objection before a decision is closed.
• Disagreements are treated as useful information about risks, not as disloyalty.
• Each meeting ends with a check that everyone can commit to what was decided, and to what will be communicated.

Artificial harmony is therefore a warning sign: a change team that never argues is often a team that does not really agree.

The model works in three ways during change:

• Diagnosis. Ask which level is weakest. A project team that misses deadlines may look like an accountability problem, while the root cause sits lower: decisions nobody really committed to.
• Team development. Build from the base up. Activities that let members share backgrounds, working styles and mistakes build vulnerability-based trust; agreed rules for debate make conflict productive; clear decisions and shared metrics support commitment and accountability.
• Leader behavior. Lencioni gives the leader a central role: going first in showing vulnerability, drawing out hidden disagreement and focusing the team on collective results.

The model links to psychological safety: both say that a team needs to feel safe to disagree before it can perform. It also links to Tuckman's storming stage, where productive conflict is part of development.

Lencioni's model is therefore most useful as a shared language that lets a team discuss how it works.

The model's strengths are clarity and practicality. It names behaviors that teams recognize, and it gives a sequence for working on them.

Its limits:

• Evidence base. The model comes from Lencioni's consulting experience and is told as a fable, not backed by research data; independent tests of the five dysfunctions and their order are scarce.
• Linearity. Real teams can show several dysfunctions at once, and the causal chain is a simplification.
• Scope. The model focuses on behavior inside the team. It says little about structure, resources, incentives or the wider organization, which also shape team performance.
• Context. It was written for senior leadership teams; cross-functional or temporary change teams may need adaptations.

Lencioni's five dysfunctions are therefore best treated as a practitioner framework for reflection, not as a validated measurement of team health.