The Five Dysfunctions of a Team
Teamwork fails one layer at a time — and the bottom layer is always trust.
The big idea
Lencioni delivers his framework as a leadership fable rather than a textbook. Kathryn Petersen, a former engineer from a wartime cruiser-builder turned CEO, is hired to fix DecisionTech, a Silicon Valley startup with the best executive team and worst results in its category.
Absence of trust is the foundation — without vulnerability-based trust, nothing above it works.
Kathryn Petersen takes the CEO job at DecisionTech in mid-1999, replacing a founder pushed out by the board. On her first day she walks into an executive team meeting and watches as eight smart people execute the choreography of teamwork — present updates, nod politely, leave — without saying anything that mattered. The CTO, Martin, types on his laptop the entire time. The head of marketing, Mikey, makes pointed comments about other functions. Nobody disagrees, and nobody decides anything.
Fear of conflict produces artificial harmony — and artificial harmony kills decisions.
On day two of the Napa off-site, Kathryn asks the team how they handled disagreement. Nick, head of business development, says they were 'good about not letting things get personal.' Kathryn replies that this is exactly the problem. She has watched them avoid every meaningful disagreement for two weeks. The harmony in the room is artificial — a substitute for the productive conflict that produces real decisions.
Without commitment, smart decisions die in the parking lot — disagree and commit beats consensus.
By the second off-site, six weeks in, DecisionTech's executives have learned to fight productively. But Kathryn notices a new failure mode. The team will argue something through in the conference room, reach what looks like a decision, and then, in the weeks that follow, each executive will subtly steer their own function in a different direction. The decision made in the room wasn't actually a decision — it was a polite tabling.
Peer-to-peer accountability is the rarest team behavior — and the leader can't substitute for it.
Three months into Kathryn's tenure, DecisionTech still misses commitments. Sales targets slip. A product launch lags. In the executive meeting, Kathryn watches the pattern: when one executive falls behind, the others say nothing. The accountability conversation, when it happens at all, happens in 1:1s between Kathryn and the underperformer. Her peers — the people most affected by her slippage — stay silent.
Inattention to results: the team must care about the team's score, not their function's score.
By Kathryn's fourth month, DecisionTech is competing again. But Lencioni saves the most subtle dysfunction for last. Even on teams that have built trust, fight productively, commit to decisions, and hold each other accountable, executives will quietly prioritize their own function's metrics, their own status, or their own ego over the team's collective result. The CFO measures success by department spend ratios. The head of sales measures success by individual booking numbers.