The Five Dysfunctions of a Team
by Patrick Lencioni
A thin fable wrapped around one genuinely useful model — read the model, skim the story.
- Status
- Read · May 2026
- Bought
- May 22, 2026
- For
- Engineering managers and tech leads · Anyone inheriting a team that isn't gelling · First-time leaders who want a shared vocabulary for dysfunction
Where it earned its place
The one-paragraph verdict
Lencioni’s claim is that team dysfunction stacks: without trust nobody will have real conflict, without conflict you get fake consensus instead of commitment, uncommitted people won’t hold each other accountable, and unaccountable teams quietly optimize for personal status over results. That chain is genuinely good — it turns “the team feels off” into a specific layer you can point at. The recurring praise for the leadership-fable format is half right: it makes the ideas memorable. The recurring criticism is also right — the story is thin, the characters are cardboard, and the actual content fits in about fifteen pages. I read the fable once, then go back only to the model.
Who should read it
Engineering managers, tech leads, and anyone who just inherited a team that isn’t gelling. It gives you shared language fast, which matters more than the prose quality. If you already run healthy teams on instinct and just want frameworks, skip the novella and read a chapter summary — you’ll lose nothing.
Where it earned its place
The “absence of trust → fear of conflict” layer is exactly what I was fighting when building a low-drama engineering team: low drama is not the absence of conflict, it’s making disagreement cheap. The same model shaped building a blameless on-call — you can’t get honest incident retros until people trust that being wrong in public won’t be held against them.
Skip it if…
You dislike business-fable packaging and would rather read a tight essay. The signal-to-page ratio is low, and a good summary delivers most of the value in a tenth of the time. [The Five Dysfunctions of a Team on Goodreads]