For Leaders & Executives Article · November 2026 ~7 min read

The Five Dysfunctions of a Team, Explained, and How to Diagnose Them on Yours

Patrick Lencioni's Five Dysfunctions of a Team is one of the most widely used models of why leadership teams stall: absence of trust at the base, inattention to results at the top. Here is a fair summary, the signs of each dysfunction, and a practical way to diagnose which one your team actually has.

By Jeff Morris, "The High Trust Guy" DreamSmart Behavioral Solutions

Most leadership teams that are struggling do not look broken from the outside. Meetings happen, decisions get announced and the quarter closes. The dysfunction shows up elsewhere: in the decision that gets reopened a week later, the risk everybody saw and nobody raised, the commitment that quietly slid. Patrick Lencioni gave that pattern a name, and his model is still the first one many executives reach for.

This page does two things. The first half summarizes the model in its own terms, credited to its author. The second half shows how DreamSmart diagnoses team dysfunction in practice, by scoring the specific behaviors underneath each level of the pyramid. DreamSmart has no affiliation with Patrick Lencioni, The Table Group or Wiley.

What are the five dysfunctions of a team?

The five dysfunctions of a team are absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results. Patrick Lencioni described them in his 2002 book The Five Dysfunctions of a Team as a pyramid: each dysfunction makes the one above it more likely, so teams fix them from the bottom up.

The book is written as a business fable. A new chief executive, Kathryn Petersen, takes over a struggling technology company whose executive team is talented, well paid and unable to work together, and the model is explained through what she does about it. The fable format is a large part of why the book has stayed popular: the dysfunctions are easy to recognize in characters before you recognize them in your own team.

The pyramid, level by level

Read the table from the bottom up. That is the order Lencioni argues they build on each other.

DysfunctionWhat it looks likeThe healthy version
5. Inattention to resultsPeople protect their own function, status or ego ahead of the team's collective goalsThe team cares most about shared results
4. Avoidance of accountabilityPeers do not call each other out on behavior or performance; the leader is the only enforcerPeers hold each other to agreed standards
3. Lack of commitmentDecisions are ambiguous; people nod in the meeting and hedge afterwardsClear decisions with genuine buy-in, even after disagreement
2. Fear of conflictMeetings are polite and dull; real disagreement happens in corridorsProductive, open debate about ideas
1. Absence of trustPeople hide mistakes and weaknesses and do not ask for helpVulnerability-based trust: people admit mistakes and ask for help

The word doing the most work is vulnerability. Lencioni’s trust is not confidence that a colleague will deliver. It is confidence that you can admit a mistake, a weakness or a need for help without it being used against you. Without that, he argues, nobody will risk open disagreement, and without disagreement, decisions do not get real commitment.

Signs of team dysfunction, one level at a time

1. Absence of trust

People do not admit mistakes or ask for help. Updates are polished. Problems are discovered by others rather than disclosed by the owner. In meetings, the same two or three people talk and the rest wait to see which way the senior voice goes.

2. Fear of conflict

Meetings feel calm and achieve little. Disagreement happens after the meeting, in direct messages and side conversations. Decisions that looked settled are reopened by people who never objected in the room.

3. Lack of commitment

Decisions end without a named owner or a date. People leave a meeting with different understandings of what was agreed. Priorities change quietly because nobody felt bound by the original choice.

4. Avoidance of accountability

Missed commitments go unmentioned. Standards slide because raising a miss feels awkward between peers. The team leader becomes the only person who ever follows up, which turns every slip into an escalation.

5. Inattention to results

Each executive reports on their own function’s numbers. Shared goals have no single owner. Individual wins are celebrated while the team misses the target that mattered most.

What the model gets right

The pyramid has lasted because three of its ideas hold up well.

  • Trust is the foundation. Research supports putting trust first. A meta-analysis of 112 studies covering 7,763 teams found that trust within a team predicts team performance, and that the effect holds after controlling for other factors (De Jong, Dirks and Gillespie, Journal of Applied Psychology, 2016).
  • Conflict is a skill, not a failure. The idea that a healthy team argues openly about ideas lines up with Amy Edmondson’s work on psychological safety, which found that teams learn more when members believe it is safe to take interpersonal risks (Administrative Science Quarterly, 1999). DreamSmart’s psychological safety guide covers that research.
  • Peer accountability beats leader accountability. A team where only the boss follows up has one enforcer and a lot of waiting. A team where peers hold each other to agreed standards moves faster.

Where teams get stuck applying it

The model is easy to understand and hard to act on. Three gaps come up often.

  • The levels are broad. “Absence of trust” describes a condition, not a behavior. A team can agree it has the problem and still not know what to do differently on Tuesday.
  • Trust means one thing. The model focuses on vulnerability-based trust. Teams also lose trust when people are unreliable, unclear about ownership, or inconsistent under pressure, and those causes need different fixes.
  • Progress is hard to see. Unless the team re-measures on the same instrument, it is difficult to tell whether a workshop changed anything a month later.

None of this is a criticism of the book. It is a description of the gap between a model and a weekly practice, and it is the gap DreamSmart works in.

How to diagnose team dysfunction with the 12 Cs of Trust

The 12 Cs of Trust break trust into twelve observable behaviors, each one rated 1 to 5. Mapping each dysfunction to the behaviors that sit underneath it turns “we have a trust problem” into “our lowest score is Clarify, so decisions leave meetings without an owner.” This mapping is DreamSmart’s own, not Lencioni’s.

DysfunctionCs to score firstOne activity to run
Absence of trustCharacter, Connection, CaringThe Load Round (who is carrying more than the team knows)
Fear of conflictCourage, CollaborationThe Written First Pass before a contested decision
Lack of commitmentClarify, CommitmentThe Dependency Round: yes, no, or by when
Avoidance of accountabilityCommitment, Coaching, ConsistencyThe Commitment Round: landed, late or never
Inattention to resultsCompetence, CloseoutThe Handoff Map, rated by sender and receiver

The activities are described in full, with timings and debrief questions, in team building activities for work. The point of the mapping is sequence. Score all twelve behaviors, find the lowest, and work there first. A team that scores high on Courage and low on Closeout does not have a conflict problem; it has a follow-through problem, and a conflict workshop will not fix it.

For a side-by-side comparison of the two approaches as assessment programs, including when to use each, see the 12 Cs of Trust vs the Five Behaviors.

A ten-minute team dysfunction self-check

Ask each member to answer these five questions privately, yes or no, about the last month. Then compare. The spread between answers is often more useful than the answers themselves.

  1. Did anyone on this team admit a mistake in a meeting before someone else found it?
  2. Did we have a real disagreement in the room, rather than afterwards?
  3. Did every decision leave the meeting with one named owner and a date?
  4. Did a peer, not the team leader, raise a missed commitment?
  5. Did we review a shared result before reviewing our individual functions?

Each “no” points to one level of the pyramid. For a scored version, the free Trust Score takes about three minutes and returns the one behavior to work on first.

What this looks like with a real leadership team

In DreamSmart’s California North case study, a regional leadership team at a Fortune 500 homebuilder started from a Five Behaviors assessment. Trust, conflict and commitment were mid-range and accountability was in the low range. The work that followed used TrustFlow™ coaching sprints on real cross-functional issues, from land to construction to sales, rather than a one-off workshop. The case study reports the before-and-after results.

The lesson is the order of operations: start with a baseline, work the weakest behavior on live problems, and measure again on the same instrument. For leadership teams, the executive team accelerator and the trust building workshop are the usual starting points, and the team charter builder helps a team write down the decision rights and norms that keep commitment and accountability from sliding back.

The Five Dysfunctions of a Team: A Leadership Fable is a book by Patrick Lencioni (Jossey-Bass, 2002). The Five Behaviors is a program published by Wiley. DreamSmart Behavioral Solutions is not affiliated with, or endorsed by, Patrick Lencioni, The Table Group or Wiley. TrustFlow™ and the 12 Cs of Trust are DreamSmart’s.

Frequently asked questions

What are the 5 dysfunctions of a team?

Absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results. Patrick Lencioni described them as a pyramid in his 2002 book, with absence of trust at the base.

What is the root cause of team dysfunction?

In Lencioni's model the root is absence of trust, specifically the unwillingness to be vulnerable with colleagues. In practice teams also lose trust through unclear ownership, unreliable follow-through and inconsistency, which is why DreamSmart scores twelve separate trust behaviors rather than one.

What are the signs of a dysfunctional team?

Common signs are polished updates that hide problems, meetings without real disagreement, decisions reopened after the meeting, commitments with no owner or date, peers who never raise a missed commitment, and executives who report only on their own function.

How do you fix a dysfunctional team?

Start with a baseline, find the weakest behavior and work on it with live problems rather than a one-off workshop. Make decisions leave meetings with one owner and a date, invite disagreement before decisions, and re-measure after six to eight weeks on the same instrument.

Is the Five Dysfunctions model evidence-based?

The book is a business fable rather than a research study. Its central claim that trust underpins team performance is consistent with research, including a 2016 meta-analysis of 112 studies by De Jong, Dirks and Gillespie that linked intrateam trust to team performance.

What is the difference between the Five Dysfunctions and the Five Behaviors?

The Five Dysfunctions of a Team is Lencioni's 2002 book. The Five Behaviors is an assessment-based team program published by Wiley that is built on the same model, framed positively as trust, conflict, commitment, accountability and results.

Name the dysfunction.
Then measure the behavior.

Score your team on the twelve trust behaviors underneath the pyramid, fix the lowest one first, and re-measure in six weeks.