The Five Dysfunctions of a Team
A Leadership Fable
by Patrick Lencioni
The 60-Second Take
The Five Dysfunctions of a Team is Patrick Lencioni's model of why teams underperform, presented mostly as a fable about a new CEO inheriting a dysfunctional executive group. His five dysfunctions form a pyramid: absence of trust at the base, then fear of conflict, lack of commitment, avoidance of accountability, and inattention to results at the top. The sequence is the point, since each one is produced by the one below it, which means visible symptoms almost always trace to a foundation problem nobody is addressing.
The Team Where Everyone Gets Along and Nothing Ships
Ask people to describe a dysfunctional team and they'll usually describe conflict: arguments, factions, someone storming out.
Patrick Lencioni's observation is that the more common and more damaging version looks entirely different. Meetings are civil. Nobody raises their voice. Decisions get discussed and quietly not made, and the actual conversation happens in the corridor afterward among people who agreed to nothing in the room.
The Five Dysfunctions of a Team, published in 2002, is built from Lencioni's consulting work with executive teams, and roughly two-thirds of it is a fable about a new chief executive inheriting a talented, well-funded, and thoroughly broken leadership group. The model arrives afterward. This summary covers the five dysfunctions and, more importantly, the order they come in.
What You'll Learn
Why vulnerability-based trust is different from trusting someone's competence
How the absence of conflict produces worse decisions than too much of it
Why commitment requires being heard rather than agreeing
What peer accountability is and why it beats managerial accountability
Why the visible problem is almost never the one to fix
One: Absence of Trust
The foundation, and Lencioni is precise about which kind of trust he means.
It isn't predictive trust — believing a colleague will deliver what they said. It's vulnerability-based trust: the willingness to say I was wrong, I don't know, I need help, or I'm not good at this, in front of peers, without expecting it to be used against you later.
Teams lacking it behave in recognizable ways. People conceal weaknesses and mistakes. Nobody asks for help or offers it. Feedback is withheld. Colleagues assume the worst about each other's intentions. And meetings are dreaded, because they're occasions for exposure rather than for work.
The leader's role here is unusually specific: they have to go first. A team will not become vulnerable in front of a leader who never is, and the fastest way to establish that admitting error is safe is for the most senior person to demonstrate that it is. Lencioni's exercises — sharing personal histories, or naming each person's single most important contribution and single most damaging behaviour — work only in that context.
Two: Fear of Conflict
Without trust, nobody risks disagreement. What follows is what Lencioni calls artificial harmony: veiled comments, careful hedging, and the absence of any real debate.
His argument is that this produces measurably worse decisions, because the objections and alternatives that would have improved them never enter the room. It also produces the corridor conversation, where people who said nothing in the meeting say what they actually think to the two colleagues they trust.
The conflict he wants is specifically about ideas rather than personalities, and the distinction is what makes it safe. Teams that can argue hard about a decision, and then leave the room without residue, make better decisions faster.
His practical tools are unglamorous: mining for conflict, meaning someone explicitly digging out disagreements the team is avoiding, and real-time permission, meaning reminding people mid-argument that this discomfort is what they agreed to and is productive. The observation that boring meetings are a symptom rather than a fact of corporate life is one of the more useful things in the book.
Three: Lack of Commitment
People who never got to voice their objection don't commit to the decision. They comply, which looks similar and behaves very differently under pressure.
Lencioni's correction to a common misunderstanding is important: commitment does not require consensus. Most reasonable people will get behind a decision they disagree with, provided their view was genuinely heard and considered. What they won't get behind is a decision that appeared without their input, or one so vaguely stated that nobody is sure what was actually decided.
The two enemies here are the desire for consensus, which produces either paralysis or a watered-down compromise nobody wants, and the need for certainty, which delays decisions until information arrives that never will. His answer is that a clear decision made with imperfect information usually beats a delayed one, because a team can adjust course but can't act on ambiguity.
The mechanism is simple and widely skipped: at the end of every meeting, state explicitly what was decided, who owns it, and what will be communicated to whom. Teams routinely leave a room with three different understandings of what just happened.
Four: Avoidance of Accountability
If commitment is unclear, nobody can be held to anything, because there's no agreed standard to hold them to.
Lencioni's focus is peer-to-peer accountability, which he considers both the hardest form and the most effective. People will tolerate a great deal rather than tell a colleague their work isn't good enough, out of a desire to preserve the relationship. His argument is that the avoidance damages the relationship anyway, more slowly, while also lowering the team's standards.
The counterintuitive point is that peer accountability works better than managerial accountability. Nobody wants to disappoint colleagues they respect, and that pressure is more immediate and more consistent than a manager's periodic review.
The enabling mechanisms are publication and regularity: goals and standards visible to everyone, and simple progress reviews frequent enough that a slipping commitment is noticed in weeks rather than quarters.
Five: Inattention to Results
The top of the pyramid, and the symptom everything else produces.
When accountability is absent, people default to what they can control and be recognized for: their own status, their department's numbers, their career. Lencioni's framing is that the ultimate dysfunction is caring about something other than the team's collective result — and that this is rarely malicious. It's what a rational person does in a system where the collective goal is unclear and individual performance is what gets rewarded.
You see it when departments compete with each other more vigorously than with actual competitors: sales blames product, product blames sales, and both are performing well by their own measures while the organization loses.
The fixes are structural. Make the collective result public. Reward against it. And be clear that for a leadership team, the first team is the leadership team itself, not the function each member runs — which is a genuinely difficult reorientation for anyone who was promoted for running that function well.
The Five Dysfunctions at a Glance
Absence of trust. Unwillingness to be vulnerable — to admit error, ignorance, or need — in front of peers.
Fear of conflict. Artificial harmony that suppresses the debate that would improve decisions.
Lack of commitment. Compliance rather than buy-in, produced by unheard objections and ambiguous decisions.
Avoidance of accountability. Reluctance to hold peers to standards, which lowers the standard for everyone.
Inattention to results. Individual and departmental goals displacing the team's collective outcome.
The pyramid. Each dysfunction produces the next, so the visible problem is rarely the one to address.
A Quick Start Guide to Fixing a Team
Go first as the leader. Admit a specific mistake in front of the team, since nobody will be vulnerable in front of someone who never is.
Name the avoided argument. Identify the disagreement everyone is stepping around and put it on the agenda.
Close every meeting with a decision review. State what was decided, who owns it, and what gets communicated, before anyone leaves.
Publish the goals. Make commitments and standards visible to the whole team so peer accountability becomes possible.
Diagnose from the bottom. When results slip, check trust and conflict before adding targets or reviews.
Who Should Read The Five Dysfunctions of a Team (and Who Can Skip It)
Read it if you lead a team whose meetings are polite and whose decisions don't stick, which is the specific pattern the model explains.
Read it if you want something you can hand to a whole team. The fable format makes it readable for people who don't read business books.
Read it if you need a shared vocabulary. Being able to say "this is a trust problem, not an accountability problem" is most of the value.
Skip it if you dislike the fable format. Two-thirds of the book is narrative, and readers who want the model directly can get it from the final section.
Skip it if you want depth or evidence. The model comes from consulting experience rather than research, and it's asserted rather than demonstrated.
Skip it if you're not in a position to change how the team operates. The interventions assume authority to reset norms and meeting structure.
Final Reflections
The ordering is what makes this model more than a list. Plenty of writing tells you teams need trust and accountability. Lencioni's contribution is the claim that they arrive in sequence, and therefore that most attempts to fix a team fail because they target the visible symptom. Adding metrics to a team that won't hold each other accountable produces better dashboards and no change; the problem sits two levels down.
The definition of trust is the second real contribution. Distinguishing "I believe you'll deliver" from "I can admit I'm struggling in front of you" locates the problem precisely, and explains why teams full of capable, reliable people can still be unable to make a decision.
Worth being clear about what this is: a consultant's model presented in a fable, not a researched finding, and the neatness of the pyramid is partly a presentational choice. It also assumes a leader with the standing and safety to make vulnerability go first, which isn't available in every organization; attempted in a genuinely political environment, the exercises can expose people who then pay for it. Used with that judgment, it remains one of the most practically useful team frameworks available, largely because it's simple enough that a whole team can hold it in mind at once.
The Bottom Line
The five dysfunctions stack, so the problem you can see is rarely the one to fix. Boring meetings and missed results usually trace back to whether people can say "I was wrong" in front of each other, and that starts with the leader.
Frequently Asked Questions
What are the five dysfunctions of a team?
Absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. They form a pyramid in which each dysfunction is produced by the one below it, so the sequence matters as much as the list.
What is vulnerability-based trust?
The willingness to admit mistakes, weaknesses, and gaps in knowledge in front of colleagues without fear it will be used against you. Lencioni distinguishes it from predictive trust, which is simply believing a colleague will do what they said.
Does commitment require consensus?
No, and Lencioni is emphatic on this. Most people will commit to a decision they disagree with provided their view was genuinely heard and the decision is stated clearly. What prevents commitment is being ignored, or ambiguity about what was actually decided.
Business Floss is reader-supported. When you use our links we may earn an affiliate commission that helps us keep the site running. Thank you for your support!
