The Five Dysfunctions of a Team
Patrick Lencioni
The Five Dysfunctions of a Team is Patrick Lencioni's fable about an executive team that cannot work together, and the model beneath it: a pyramid of five layers, each resting on the one below. Absence of trust, specifically vulnerability-based trust, leads to fear of conflict and artificial harmony, which leads to lack of commitment, avoidance of accountability and inattention to results. The leader builds the pyramid from the bottom, and goes first.
Your meetings are polite, run to time and end in agreement, and nothing decided in them happens. Lencioni's model explains why the politeness is the problem, and what the leader has to do first, which is admit a mistake out loud.
The book in essence
The first two-thirds of the book is a story: a new chief executive, Kathryn, inherits a talented, dysfunctional leadership team and takes it through a series of off-sites. The last third is the model the story illustrates. At the base is trust, and Lencioni is precise that he means vulnerability-based trust, the willingness to say I was wrong, I need help, I do not know, in front of peers. Without it comes fear of conflict, whose symptom is artificial harmony: agreement in the room, disagreement in the corridor. Without healthy conflict there is no commitment, because people who were not heard cannot support a decision they lost; Lencioni's alternative to consensus is disagree and commit, with decisions stated aloud and cascaded. Without commitment there is no accountability, and Lencioni insists that on a healthy team peers hold each other to account rather than waiting for the boss. And without accountability, attention drifts from collective results to individual status. The leader's job is to build each layer by going first: admitting mistakes, mining for conflict, forcing clarity and closure, and confronting difficult issues.
Published in 2002, the book became one of the most widely used team texts in business, with a field guide and assessments following. It is a fable and reads like one; the model is simple enough to draw on a napkin and hard enough that most teams live in the bottom two layers.
Who it's for
- Managers whose team meetings are quiet and whose decisions do not stick
- New leaders inheriting a team that was peers with them last month
- Anyone who wants a model of team health they can draw and explain in a minute
Who it's not for
- — Readers who dislike business fables; the story is most of the book
- — Teams whose problem is skill rather than trust; the model does not address competence
Key lessons
01
Trust means admitting weakness, and the leader goes first
Not trust that colleagues will do their jobs, but vulnerability-based trust: saying I was wrong, I need help, in front of the team. A team whose members are protecting themselves cannot do anything else on the pyramid. It is built by the manager admitting a real mistake before asking anyone else for candour.
A product lead at a bank in Istanbul opens a meeting by admitting she pushed an unrealistic launch date to avoid looking slow, and asks what else she has been getting wrong. After a long silence, the most junior analyst names a spec everyone knew was unbuildable.
02
A quiet, unanimous meeting is a warning sign
Fear of conflict produces artificial harmony: agreement in the room, argument in private messages, decisions quietly not carried out. Healthy conflict is passionate argument about ideas, not people, and the output of a good meeting is that the best objection was heard before the decision. The leader mines for it and rewards the objector.
The same product lead asks, at each decision, for the strongest case against it, and thanks whoever makes it. The meetings become less comfortable and the decisions start to stick.
03
Disagree and commit, then read the decisions aloud
Commitment is clarity and closure, not consensus. After the full argument the accountable person decides and everyone, including those who lost, commits. Every meeting ends with decisions read aloud, owners and dates named, and the same list sent to those not in the room.
Two engineers who lost an argument keep building the cut feature. Their manager adds a closing ritual: decisions read aloud and the question, can everyone commit, including those who wanted the other way? One says no; five minutes later he commits, and the feature stays cut.
04
Peers hold each other to account
If the only person who ever says 'you said Thursday' is the manager, every miss becomes a discipline problem and the team learns to manage the manager. The manager's job is to make peer accountability safe and expected: public standards, progress reviewed in the group, and visible approval the first time one member challenges another.
In the sprint after the closing ritual is introduced, a designer reminds an engineer of a date before the manager does. The manager says, out loud, that this is exactly right.
Try this today
In your next team meeting, open by naming a mistake you made this month, then ask for the strongest case against the first decision on the table and thank whoever makes it.
Quick check
What kind of trust sits at the base of the pyramid?
Whose job is accountability on a healthy team?
Selected quotes
“Not finance. Not strategy. Not technology. It is teamwork that remains the ultimate competitive advantage, both because it is so powerful and so rare.”
“Trust is the foundation of real teamwork.”