The Dysfunction Cascade

Definition

Lencioni's core structural claim is that the five dysfunctions — absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results — are not five separate problems a team can fix independently. They form an "interrelated model, making susceptibility to even one of them potentially lethal for the success of a team," because each dysfunction is the direct cause of the next: no trust means no real conflict; no real conflict means no genuine commitment; no commitment means nothing concrete to hold each other accountable to; no accountability means individuals drift toward personal status instead of collective results. The book's own image: "like a chain with just one link broken, teamwork deteriorates if even a single dysfunction is allowed to flourish."

In the Book

The model is presented as a pyramid (Trust at the base, Results at the peak) and walked through twice in "An Overview of the Model" — once as a negative chain of failure, once inverted as a positive chain of behaviors (trust one another, engage in unfiltered conflict, commit to decisions, hold one another accountable, focus on collective results). Each of the five detailed sections later in the book ends with an explicit "Connection to Dysfunction N+1" passage, making the causal link the organizing device of the entire second half, not just a diagram. The fable itself is structured to demonstrate the cascade in order — the Napa trust-building work precedes the team's first real fights, which precede their ability to commit to a hard product decision, which precede Kathryn confronting Martin on accountability, before the team finally aligns around a single results metric.

Why It Matters

This is a diagnostic reframe: a team with a "conflict problem" or an "accountability problem" is usually misdiagnosing a downstream symptom of a trust problem underneath it, and interventions aimed at the visible symptom (a facilitator to manage meetings, a scorecard to enforce accountability) will not hold if the foundational layer is untouched. The cascade structure generalizes past teams to any layered system where a surface failure is actually the output of an unaddressed failure lower in the stack — treat the symptom you can see, and the same failure reappears one layer up.