The Five Dysfunctions of a Team: A Leadership Fable, 20th Anniversary Edition (J-B Lencioni Series)

11 highlighters490 highlights1 note4.3 / 5

About This Book

Patrick Lencioni's The Five Dysfunctions of a Team uses a leadership fable about Kathryn, a new CEO of a struggling Silicon Valley company called DecisionTech, to illustrate why even talented executives fail to function as a team. The book argues that teamwork remains the ultimate competitive advantage because it is both powerful and rare, and that dysfunction stems from a set of interrelated, predictable behaviors.

The model is built as a pyramid of five dysfunctions, each enabling the next.

Absence of trust — team members fear being vulnerable and hide weaknesses and mistakes.
Fear of conflict — without trust, teams settle for artificial harmony instead of productive, unfiltered debate.
Lack of commitment — without honest debate, members never truly buy in, even when they feign agreement.
Avoidance of accountability — without commitment and clarity, peers won't hold each other to high standards.
Inattention to results — without accountability, individuals prioritize ego, status, and personal goals over collective outcomes.

Lencioni shows that the cure runs in the same order: leaders must model vulnerability first, encourage healthy ideological conflict, drive for clear decisions and deadlines, let the team itself be the primary accountability mechanism, and relentlessly focus rewards on collective results. Recurring lessons include that conflict underlies commitment, that ambiguity is the enemy of accountability, that peer pressure outperforms bureaucracy, and that teams saying "we'll do our best" are preparing to fail.

The second half of the book abandons the narrative for a practical model with diagnostics (Myers-Briggs, DiSC, 360-degree feedback used purely for development) and tools like cascading messaging and public commitment to specific goals. Ultimately, Lencioni insists, teamwork is not sophisticated theory but common sense applied with uncommon discipline and persistence.

Key Takeaways

1.Trust through vulnerability is the foundation—members must openly admit mistakes, weaknesses, and requests for help without fear of reprisal.
2.Teams that fear conflict settle for artificial harmony, then turn to back-channel attacks that are nastier than any open debate.
3.Commitment requires clarity and buy-in, not consensus; reasonable people support a decision once they know their views were genuinely heard.
4.The enemy of accountability is ambiguity—people can't be held to standards that were never clearly committed to in the first place.
5.Peer pressure is the most effective way to maintain high performance and reduces the need for bureaucratic oversight.
6.Teams that publicly commit to specific results outperform those that say "we'll do our best," which subtly prepare for failure.
7.The ultimate dysfunction is inattention to collective results, when ego, status, or departmental needs override the goals of the whole team.

Top Highlights

you could get all the people in an organization rowing in the same direction, you could dominate any industry, in any market, against any competition, at any time.”

Highlighted by 2 people

“Trust is the foundation of real teamwork. And so the first dysfunction is a failure on the part of team members to understand and open up to one another.

Highlighted by 2 people

“Politics is when people choose their words and actions based on how they want others to react rather than based on what they really think.”

Highlighted by 2 people

“If we don’t trust one another, then we aren’t going to engage in open, constructive, ideological conflict. And we’ll just continue to preserve a sense of artificial harmony.”

Highlighted by 2 people

“Once we achieve clarity and buy-in, it is then that we have to hold each

Highlighted by 2 people

AI Review

4.3/ 5

Glasp's analysis of highlights from 9 readers shows strong, consistent engagement with Lencioni's five-dysfunction model, with the heaviest highlighting clustered around commitment, accountability, and conflict. The consensus signals a memorable, highly quotable framework that readers find practical.

Pros

+A simple, memorable pyramid model that links five dysfunctions causally
+Heavily highlighted, quotable insights on conflict, commitment, and accountability
+The fable format makes abstract team dynamics concrete and easy to apply
+Practical tools—cascading messaging, public goal commitment, developmental 360s
+Reframes conflict as productive and peer pressure as a feature, not a flaw

Cons

−Concepts are intentionally simple and may feel like common sense to experienced leaders
−The fable is somewhat idealized and resolves more neatly than real workplaces

Glasp AI analysis based on highlights from 9 readers.

Who Should Read This

This book is for executives, managers, and team leaders who sense their group is talented yet underperforming, especially those navigating politics, silent meetings, or missed goals. It suits new leaders inheriting a fractured team, founders building their first leadership group, and HR or organizational-development professionals running offsites. No prior management theory is required—the fable format makes the ideas accessible to anyone, from project leads to nonprofit and volunteer-team coordinators, who wants a simple, actionable framework for diagnosing and fixing dysfunction.

Frequently Asked Questions

What is The Five Dysfunctions of a Team about?

It is a leadership fable about a new CEO turning around a dysfunctional executive team, framed around five interrelated dysfunctions: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. Each dysfunction feeds the next, and fixing them requires working through them in order.

Who is the book for?

It is aimed at executives, managers, and anyone leading or serving on a team. New leaders inheriting a divided group and professionals running team offsites will find it especially useful.

What are the key lessons?

Trust built on vulnerability is the foundation; healthy ideological conflict enables commitment; ambiguity is the enemy of accountability; and teams must make collective results more important than individual ego or status.

Is it worth reading?

Yes—readers highlighted its insights heavily, and its clarity and brevity make it a fast, high-leverage read. As Lencioni notes, success comes not from sophisticated theory but from common sense applied with uncommon discipline.

Why does the book say conflict is necessary?

Because commitment depends on it: information often resides in team members' minds and must be extracted through unfiltered debate. Teams that avoid conflict to spare feelings end up with back-channel attacks that are far more damaging.

What does the book say about accountability?

It argues the team itself, through peer pressure, should be the primary accountability mechanism—not the leader alone. The leader must avoid creating an accountability vacuum while still being willing to step in as the ultimate arbiter.

Is the book a story or a how-to guide?

Both. The majority is a narrative fable about DecisionTech, followed by a concise model section with diagnostics, exercises, and tools you can apply to your own team.

How to Apply What You Read

1.Model vulnerability first as a leader—admit your own weaknesses and mistakes to make it safe for others to do the same.
2.Schedule conflict into meetings and remind the team afterward that the debate they engaged in was healthy and necessary.
3.Set clear deadlines for decisions and honor them with discipline, even without perfect information, to break commitment paralysis.
4.Clarify publicly what the team must achieve, who delivers what, and how everyone must behave, then revisit these agreements openly.
5.Define collective results in simple, actionable terms and reserve rewards only for behaviors that advance them.

Discussion Questions

Q1.Which of the five dysfunctions is most present in a team you belong to, and how does it enable the next one?
Q2.What would it take for your team's leader—or you—to demonstrate genuine vulnerability first?
Q3.Does your team experience productive ideological conflict, or does it settle for artificial harmony? What drives that?
Q4.How does your team handle decisions when there is no consensus and incomplete information?
Q5.Is accountability in your team driven mainly by peer pressure or by the leader alone, and what are the consequences?
Q6.How clearly are your team's collective results defined, and could individual ego or status be quietly competing with them?
Q7.Do you agree with Lencioni that teamwork is common sense applied with discipline rather than sophisticated theory? Why or why not?