The Five Dysfunctions of a Team: Lencioni's Model Explained

The Five Dysfunctions of a Team is a leadership model by Patrick Lencioni that explains why capable teams still fail. It stacks five problems in a pyramid: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. Each one grows out of the one beneath it, so you fix the base first.

If your team has talented people, a clear strategy, and still produces mediocre work, this model is a good place to start looking. It doesn't tell you who is to blame. It tells you which layer of the team is cracked.

What are the five dysfunctions of a team?

Patrick Lencioni introduced the model in his 2002 book The Five Dysfunctions of a Team: A Leadership Fable. The Table Group, his consulting firm, says the book has sold several million copies worldwide, and the model is still one of the most widely used team-building frameworks in business.

The book is a fable: a fictional CEO takes over a struggling executive team and works through each problem. The model sits inside that story. That matters for how you use it, and we'll come back to it in the limits section below.

The core idea is simple. Dysfunction isn't random. According to The Table Group's overview, Lencioni argues that every team is potentially dysfunctional because teams are made up of imperfect people, and that the causes of dysfunction are identifiable and curable. But they take courage and discipline, and they don't die easily.

Key Facts

Key Facts

• Patrick Lencioni published The Five Dysfunctions of a Team in 2002, and The Table Group says it has sold several million copies worldwide.
• The five dysfunctions, from the base of the pyramid up: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results (The Table Group).
• Google's Project Aristotle studied 180 teams (115 engineering project teams and 65 sales pods) and ranked psychological safety first of five dynamics of effective teams.
• The Table Group offers a confidential team assessment where each member rates the team on all five behaviors.
• The model comes from a business fable and consulting practice, not from a peer-reviewed study. Treat it as a diagnostic lens, not a measurement standard.

The pyramid, level by level

Picture a pyramid. Absence of trust sits at the bottom, inattention to results at the top. Lencioni's logic is that a team can't reach the top without a solid base. Each dysfunction has a flip side, which is the behavior of a cohesive team: trust, healthy conflict, commitment, accountability, and a focus on collective results.

Level 1: Absence of trust

This is the foundation. The Table Group describes it as team members being reluctant to be vulnerable with one another and unwilling to admit mistakes, weaknesses, or a need for help.

Notice what kind of trust this is. It isn't "I believe you'll deliver on time." It's the willingness to say "I got this wrong" or "I don't know how to do this" in front of peers without bracing for the consequences.

Signs you'll see:

• People hide mistakes until they can't anymore
• Few people ask for help or offer it
• Teammates jump to conclusions about each other's intent
• Meetings are guarded, and the real talk happens in the hallway

This is close to what Amy Edmondson calls psychological safety, which she describes as a safe space for people to speak up and make mistakes. We cover that idea in depth in our guide to psychological safety.

Level 2: Fear of conflict

When trust is missing, people avoid honest debate. The Table Group says that in this situation, conflict turns into veiled discussions and back channel comments, and the decisions that come out are inferior.

The word "conflict" is the sticking point for most leaders. Lencioni isn't talking about personal attacks. He means productive, ideological conflict: arguing about the merits of an idea, a priority, or a plan. A team that never argues about substance usually isn't aligned. It's polite.

Signs you'll see:

• Meetings are boring, and nobody pushes back on the boss
• The same issue gets "resolved" three times
• People send private messages after the meeting saying what they really think
• Decisions feel smooth but fall apart in execution

Level 3: Lack of commitment

Without airing disagreement, people don't buy in. The Table Group's summary says teams fail to fully commit to decisions even when they appear to agree. Commitment here has two ingredients: clarity about what was decided, and buy-in from people who were heard, even if they lost the argument.

Signs you'll see:

• "Yes" in the room, quiet resistance afterward
• Decisions get revisited again and again
• Teams wait for perfect information or full consensus before moving
• Two people leave the same meeting with different versions of what was agreed

Note the difference between commitment and consensus. People can commit to a decision they argued against, as long as they got a real hearing.

Level 4: Avoidance of accountability

Once people haven't committed to a clear plan, there's nothing concrete to hold each other to. And even when there is, peers hesitate to call out problem behavior because it's uncomfortable. The Table Group frames it as a need to avoid interpersonal discomfort that stops members from holding one another to account.

The telling detail is who does the accountability. In a healthy team, peers hold each other to standards, not just the manager. If every performance conversation has to go through the leader, this layer is weak.

Signs you'll see:

• Missed commitments get a shrug
• The manager is the only one who ever pushes on quality or deadlines
• High performers get resentful of low performers who face no consequence
• Standards slip quietly over time

Level 5: Inattention to results

At the top, the pursuit of individual goals and personal status erodes focus on collective success. People protect their own department, title, or ego instead of the shared outcome.

Signs you'll see:

• Each function celebrates its own metrics while the company misses its goal
• Team members compete for credit
• Meetings are about positioning, not the scoreboard
• Talented people leave for teams with a clearer sense of shared purpose

How the five dysfunctions connect

The model is a chain reaction. You can't hold people accountable for a plan they never committed to. They won't commit to a plan they never got to argue about. And they won't argue honestly with people they don't trust.

That's why the common fix of "just hold people accountable" fails. If the real problem is at level 1, adding performance metrics only produces more defensive behavior. The better move is to diagnose from the bottom up.

How it compares with other team frameworks

Lencioni's model is one of several lenses on team behavior. They answer different questions, so they work better together than as rivals.

A useful way to combine them: Tuckman tells you what stage you're in, Lencioni tells you which behavior is failing, Edmondson explains the climate under it, Belbin helps with who should do what, and the Johari window gives you a way to practice openness.

What the research says (and doesn't)

Be honest about the evidence. The Five Dysfunctions of a Team is a leadership fable. It grew out of Lencioni's consulting work, not out of a controlled study, and we're not aware of a peer-reviewed validation of the exact five-layer ordering. That doesn't make the model useless. It makes it a hypothesis that many leaders find useful, not a proven law.

What gives it support is its overlap with research from elsewhere. Google's Project Aristotle examined 180 teams and found five dynamics of effective teams, in order of importance: psychological safety, dependability, structure and clarity, meaning, and impact. Psychological safety came out on top, which echoes Lencioni's choice of trust as the foundation. Dependability and structure and clarity line up loosely with accountability and commitment.

The takeaway: use the model for the questions it generates, not as a score you defend. If your team recognizes itself in the description, that conversation is the value.

How to run the model with your team

Here's a practical sequence you can run over a few weeks. It works best when the team leader participates as a member, not as a judge.

Step 1: Set the purpose and ground rules

Tell the team why you're doing this: to make the team better at working together, not to find a culprit. Agree on confidentiality, and be clear that nothing said here gets used in performance reviews.

Step 2: Run an anonymous diagnostic

Have each person rate the team on the five behaviors. You can use The Table Group's official assessment or the free template below. Anonymity matters, because the point is to get honest answers from people who might not say them out loud.

Step 3: Share the results and find the lowest layer

Show the average scores and the spread. Start at the base. If trust scores low, don't jump to accountability, even if that's where the pain feels sharpest.

Step 4: Pick one dysfunction to work on

Teams that try to fix all five at once fix none. Choose the lowest layer, agree on one or two behaviors to change, and write them down.

Step 5: Build habits, not events

An offsite can start the conversation, but behavior changes through repetition. Add short routines: a check-in at the start of meetings, a "disagree and commit" close to each decision, a monthly peer review of commitments.

Step 6: Revisit in 60 to 90 days

Run the diagnostic again. Compare. Celebrate what moved, and pick the next layer.

Template: team diagnostic you can copy

Ask each member to score each statement from 1 (almost never) to 5 (almost always). Average the scores per row, and look at the lowest first.

Scoring guide: an average of 4 or more suggests a layer is healthy. Between 3 and 4, watch it. Below 3, that layer is your starting point. This is a conversation tool, not a statistically validated instrument.

Examples by business function

These scenarios are hypothetical, written to show how each pattern shows up in practice.

Sales leadership team. The regional sales directors never disagree in the weekly forecast call. Numbers get rounded up, and surprises show up at quarter end. The dysfunction is fear of conflict, rooted in low trust: nobody wants to be the person whose number is questioned. A fix: have each director present the riskiest deal in their pipeline first, and make the VP go first with their own miss.

Product and engineering. The product manager and the engineering lead agree on a roadmap in the planning meeting. Two weeks later, engineers are building something different. This is lack of commitment: the roadmap was never actually argued over. A fix: end each planning session by having each person restate the decision in one sentence.

Marketing. A marketing team has a shared campaign target, but every channel owner reports on their own metric. The paid owner brags about cost per click while pipeline stays flat. That's inattention to results. A fix: replace channel dashboards with one shared pipeline number the whole team reviews first.

Operations. Warehouse and customer service teams each have service-level commitments, but nobody confronts the shift lead who keeps missing handoffs. The supervisor does all the chasing. That's avoidance of accountability. A fix: introduce peer-to-peer handoff reviews, where teammates give each other direct feedback with a simple structure, like the one in radical candor.

Project teams. On cross-functional projects, unclear ownership often looks like an accountability problem when it's a clarity problem. A RACI matrix makes decisions and ownership explicit, which gives accountability something to hold on to.

Do's and don'ts

Common mistakes with the model

Treating trust as friendliness. A team can be warm and still fail the trust test. The trust that counts is the willingness to be vulnerable about mistakes and gaps, not social comfort.

Mistaking healthy conflict for hostility. Some leaders hear "embrace conflict" and read it as permission to be harsh. Productive conflict stays on the idea, not the person.

Treating it as a one-time event. Teams revert. New members, new managers, and pressure all push a team back down the pyramid. That's normal. Plan to revisit.

Ignoring the leader's part. The model puts heavy weight on the leader's behavior. If the leader never shows vulnerability, the team won't either. Research on how managers shape team climate, such as leader-member exchange theory, is a useful complement.

Putting it into practice

Start small. Pick one team, one dysfunction, and one meeting. At your next team meeting, ask one trust-building question and watch what happens: "What's one thing you got wrong this month that the rest of us could learn from?" Then answer it first.

The pyramid can sound like a lot of work for a simple idea. It is. But most teams don't fail because they lack skill. They fail because the people on them don't feel safe enough to say what they think. That's a fixable problem, and this model gives you a map for fixing it.