The Five Dysfunctions of a Team

Lencioni's claim is that the five dysfunctions are a single structure rather than a list. Each one is produced by the one below, so treating the symptom at the top without addressing the base is why so many team interventions fail.

The model, read from the bottom: absence of trust → fear of conflict → lack of commitment → avoidance of accountability → inattention to results.

It is a chain, not a list. Fix the top and it re-forms; fix the bottom and the rest becomes possible.

Devmark’s reading — not a quotation from the book

Most of the book is a story about a fictional executive team and a new chief executive. The model itself occupies a short section at the end.

The form divides readers sharply. It makes the dynamics recognisable and memorable in a way a framework alone would not, and it is also thin as fiction and a little convenient in its resolutions. Read it for the recognition, not the plot.

Lencioni means something specific and narrower than the usual sense: vulnerability-based trust, the willingness to admit a mistake, a weakness or a gap in knowledge without calculating how it will be used.

Without it, people spend energy managing impressions rather than doing work. His point is that this is invisible on any dashboard and is the single largest tax a team can carry.

Teams without trust manufacture artificial harmony. Meetings are polite, nothing is resolved, and the real disagreement moves to corridors and private messages afterwards.

Lencioni's position is that productive ideological conflict — direct argument about ideas, not about people — is a requirement rather than a risk, and that a team which never argues in the room is not aligned but silent.

People do not commit to decisions they have not had a chance to argue with. This is the hinge connecting conflict to execution, and the book's most practically useful observation.

Lencioni distinguishes consensus from buy-in: the requirement is not that everyone agrees, but that everyone was genuinely heard. He is direct that waiting for certainty is a common failure, and that a clear decision made on incomplete information beats an unresolved one.

Without commitment, no one can hold anyone to anything, because the standard was never really agreed. Peer accountability then collapses into escalation to the manager.

Lencioni argues that peer pressure is the most effective accountability mechanism a team has, and that its absence is what turns a manager into a bottleneck for every difficult conversation.

A team that escalates every difficult conversation to its manager has not delegated authority. It has delegated discomfort.

Devmark’s reading — not a quotation from the book

The top of the pyramid is the point where individual status, career advancement or departmental goals displace the team's collective outcome.

Lencioni's remedy is unglamorous: make the collective result public and specific, so that it is harder to quietly substitute a personal one. He is also clear that this is the only dysfunction whose cost is usually visible from outside the team, which is why it is the one most often treated first.

This should be stated directly. The model is drawn from consulting experience, not research. There is no study behind it, the causal ordering between the five is asserted rather than demonstrated, and the fable provides illustration rather than evidence.

That does not make it useless — practitioner models often encode real pattern recognition — but it should not be cited as a finding, and a reader should notice that its plausibility comes from recognition rather than from data.

The most common failure is running a trust exercise and declaring the base addressed. Lencioni's trust is built by leaders going first with genuine vulnerability, repeatedly, over time — not by an offsite.

The second is using the model to pathologise a team whose actual problem is structural: unclear ownership, conflicting incentives, or too little authority to act. The framework has no vocabulary for those, and will misdiagnose them as behavioural.

As a shared vocabulary it is genuinely valuable. Naming artificial harmony in a meeting, or the distinction between consensus and buy-in, lets a team discuss its own dynamics without it becoming personal.

It is short, it is honest about being a model rather than a science, and its central insight — that unspoken disagreement becomes uncommitted execution — is one most people recognise immediately from their own experience.