Patrick Lencioni’s The Five Dysfunctions of a Team is one of the most widely read leadership books of the past two decades – and for good reason. It cuts through management theory to name something most leaders already sense but struggle to articulate: that talented, well-resourced teams routinely fail not because of strategy or capability gaps, but because of specific, predictable behavioral patterns.
Published in 2002, the book has sold over seven million copies worldwide. It is taught in business schools, referenced in boardrooms, and has shaped the team development industry in ways that are still being felt today. More importantly, it is genuinely useful – the kind of book that makes leaders recognize their own teams on every page.
This post summarizes the book’s core model, unpacks each dysfunction, and explains what the research means for real teams trying to move from dysfunction to cohesion.
What Kind of Book Is It?
Table of Contents
The Five Dysfunctions of a Team is structured as a leadership fable – a format Lencioni pioneered and has used across most of his twelve books. The story follows Kathryn Petersen, a newly appointed CEO brought in to rescue a struggling Silicon Valley technology company. Her team is composed of individually impressive executives who cannot function as a unit.
The fable format is deliberate. Lencioni uses it to show the dysfunctions in action — how they look and feel in real organizational life – before presenting the underlying model. The result is a book that is unusually readable for a business text, and unusually memorable: the model sticks because readers have already watched it play out in the story before it’s explained.
The final section of the book presents the model directly, with practical guidance on how leaders can apply it. Most summaries of The Five Dysfunctions of a Team skip the fable and go straight to the model. That’s fine for efficiency, but it loses something – the fable is where the emotional truth of the framework lives.
The Five Dysfunctions of a Team: The Model
Lencioni presents the five dysfunctions as a pyramid. Each dysfunction enables the one above it. A team that hasn’t addressed the bottom layer cannot genuinely resolve the layers above it, regardless of how much effort it invests.
The five dysfunctions, from the base up, are:
Dysfunction 1: Absence of Trust
The foundational dysfunction – and the root cause of every other failure on the list.
Lencioni is specific about what he means by trust here. It is not confidence in each other’s competence or reliability. It is vulnerability-based trust: the willingness to be genuinely open about mistakes, weaknesses, blind spots, and the need for help – without fear of judgment or political consequence.
Teams that lack this kind of trust spend enormous energy on self-protection. Members are guarded in meetings, reluctant to ask questions that might make them look uninformed, and unwilling to admit when they’ve gotten something wrong. The result is a team where every interaction carries a hidden cost – the cognitive and emotional overhead of managing impressions rather than solving problems.
According to Lencioni, this dysfunction is so foundational that no meaningful progress on any of the others is possible without addressing it first.
Dysfunction 2: Fear of Conflict
Teams without trust cannot have genuine conflict. And teams without genuine conflict cannot make genuinely good decisions.
This is the dysfunction that most surprises leaders when they first encounter Lencioni’s model. The instinct in most organizational cultures is to view conflict as inherently negative – a sign of poor relationships or poor management. Lencioni argues the opposite: the absence of conflict is the real warning sign.
Teams that avoid conflict don’t eliminate tension. They suppress it, where it resurfaces as passive aggression, political maneuvering, and the quiet sabotage of decisions that were never truly agreed upon. The meetings become performatively harmonious while the real conversations happen in corridors and car parks afterward.
Productive conflict, in Lencioni’s model, is unfiltered debate focused entirely on ideas – direct, sometimes uncomfortable, always purposeful. It is the mechanism through which a team surfaces the best thinking in the room rather than defaulting to the path of least resistance.
Dysfunction 3: Lack of Commitment
Without conflict, there is no genuine commitment – only the appearance of it.
This is one of Lencioni’s sharpest and most practically useful insights. He distinguishes carefully between consensus and commitment. Consensus requires everyone to agree with the outcome. Commitment requires only that everyone felt genuinely heard during the discussion.
When teams avoid conflict, decisions are never truly debated. People leave meetings having said yes but privately reserving their objections. They didn’t commit – they acquiesced. And acquiescence has a short shelf life. The moment execution gets hard, the quiet reservations surface, and the team finds itself relitigating decisions it thought it had already made.
Genuine commitment – even to decisions individuals didn’t initially prefer – only emerges when trust and conflict have done their work first.
Dysfunction 4: Avoidance of Accountability
Accountability in most organizations flows vertically – from manager to report. Lencioni argues that this is insufficient, and that the most damaging accountability failures are peer-to-peer: team members who see a colleague underperforming or behaving inconsistently with agreed standards and say nothing.
Why don’t they say something? Because it’s uncomfortable. Because it risks the relationship. Because it’s easier to let the leader handle it. And underneath all of those reasons: because the commitment wasn’t genuine to begin with, so there’s nothing concrete to hold each other to.
When commitment is real – when the team has genuinely agreed on a course of action through honest debate – peer accountability becomes both possible and natural. Without it, the leader becomes the sole enforcer, which is exhausting, inefficient, and ultimately ineffective.
Dysfunction 5: Inattention to Results
The apex dysfunction – and the most visible symptom of everything below it.
When the four preceding dysfunctions are in place, team members default to focusing on whatever serves them individually: personal recognition, departmental metrics, career advancement, status. The team’s collective goal becomes secondary to individual agendas.
This is not primarily a motivation problem. People aren’t choosing to be selfish. It’s a structural problem: when trust, conflict, commitment, and accountability are absent, there is no shared goal strong enough to pull individuals away from what they can control and measure for themselves.
Lencioni’s insight is that inattention to results is always a downstream symptom. Leaders who try to fix it directly – through incentive structures, performance frameworks, and rallying speeches – are treating the surface while the root causes remain untouched.
Key Lessons from The Five Dysfunctions of a Team
The dysfunctions are a system, not a list. Each one enables the next. Leaders who try to fix accountability without addressing trust are working on the wrong level. The pyramid is the point.
Harmony is not health. Teams that never argue, never push back, and never surface disagreement are not cohesive – they are avoidant. Real cohesion requires the capacity for productive conflict, which requires real trust underneath it.
Commitment requires debate, not agreement. The fastest way to get genuine buy-in is to ensure every voice is genuinely heard before a decision is made – not to engineer consensus through compromise.
Peer accountability is the hardest behavior to build. Most teams never fully achieve it. But it is the behavior that most distinguishes high-performing teams from merely functional ones.
The leader sets the ceiling on trust. Lencioni is clear on this: the level of vulnerability-based trust on a team is largely determined by the leader’s willingness to be vulnerable first. Teams take their cue from the top.
From Dysfunctions to Behaviors: The Five Behaviors® Program
The Five Dysfunctions of a Team identifies the problem. The Five Behaviors® of a Cohesive Team, developed by Wiley in partnership with Lencioni’s work, is the operationalized solution – an assessment-based team development program that gives intact teams a structured path from dysfunction toward cohesion.
The program combines Lencioni’s pyramid model with Everything DiSC® behavioral insights, producing personalized reports for each team member and a facilitated experience that translates the model into concrete behavioral commitments.
FocusU is an authorized delivery partner for the Five Behaviors® program in India, working with corporate teams across sectors to build the trust, conflict capacity, commitment, accountability, and results focus that Lencioni’s research identifies as the foundation of genuine team performance.
Frequently Asked Questions
What is the summary of The Five Dysfunctions of a Team?
Lencioni’s book argues that teams fail not because of talent gaps but because of five interconnected behavioral dysfunctions: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. Each dysfunction enables the next, forming a pyramid where trust is the foundation. The book presents the model through a leadership fable before offering practical guidance on how teams can address each layer.
What are the five dysfunctions described by Lencioni?
The five team dysfunctions described by Lencioni are:
(1) Absence of Trust – the unwillingness to be vulnerable with teammates;
(2) Fear of Conflict – avoiding genuine debate in favour of artificial harmony;
(3) Lack of Commitment – ambiguity about decisions because all voices weren’t truly heard;
(4) Avoidance of Accountability – reluctance to call out peers on behavior inconsistent with agreed standards; and
(5) Inattention to Results – prioritizing individual or departmental goals over team outcomes.
What books explain the five behaviours of a cohesive team with case studies?
The foundational text is Lencioni’s The Five Dysfunctions of a Team (2002), which uses a leadership fable as its primary vehicle. For application, Wiley’s Five Behaviors® program materials – including team assessment reports and facilitation guides – provide case-level specificity. Lencioni’s The Advantage (2012) extends the framework to organizational health more broadly.
What is the difference between the five dysfunctions and the five behaviors?
The five dysfunctions name what goes wrong. The Five Behaviors® model names what to build instead – Trust, Conflict, Commitment, Accountability, Results – and the Five Behaviors® of a Cohesive Team program gives teams a structured, assessment-based path to building them.
Is The Five Dysfunctions of a Team still relevant?
Yes. The behavioral dynamics Lencioni identified in 2002 – self-protection, conflict avoidance, false consensus, passive accountability, individual agenda – are if anything more prevalent in today’s hybrid and matrix organizations. The model has aged well precisely because it addresses human behavioral patterns, not organizational structures or market conditions.
