Lencioni’s Five Dysfunctions of a Team
Lencioni proposed that dysfunctional teams typically suffer from five interrelated problems building on one another, absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results, though the model is a practitioner framework presented through a business fable, not an empirically derived or tested causal sequence.
What Is It?
Business consultant and author Patrick Lencioni presented the model in his 2002 book The Five Dysfunctions of a Team, written as a business fable rather than a research report. He described five dysfunctions as forming a pyramid, each building on the one below it: absence of trust, specifically vulnerability-based trust, team members willing to admit mistakes, weaknesses, and ask for help with one another, not trust in the sense of reliability or competence; fear of conflict, which produces artificial harmony rather than genuine, productive disagreement about ideas; lack of commitment, since without real conflict, decisions tend to happen without buy-in, leaving ambiguity about what was actually decided; avoidance of accountability, since without genuine commitment, team members hesitate to call out peers on behavior or performance that doesn’t serve the team; and inattention to results, since without accountability, individuals tend to prioritize personal status, ego, or their own department’s interests over the team’s collective outcomes. Lencioni framed these as causally connected, with absence of trust as the foundational problem that makes the other four more likely. That each of these five things, trust, productive disagreement, commitment, accountability, and a focus on collective results, is worth examining in a struggling team is plausible and overlaps with constructs that do have independent research traditions. But that plausibility is not the same as evidence that they form one validated causal pyramid in this specific order, reasonable ingredients don’t automatically validate the architecture connecting them.
Why Does It Matter?
Teams and leaders often try to address visible symptoms, missed deadlines, finger-pointing, disengagement, without asking what’s underneath them. Lencioni’s framework prompts a useful line of questioning even without being a rigorously validated model: when accountability is weak, is commitment also unclear? If commitment is weak, did the team ever engage in enough real disagreement to produce it? The pyramid encourages a team to test whether a visible problem has contributing dynamics elsewhere in the model, rather than assuming the visible symptom is self-contained, that’s a useful hypothesis-generating habit distinct from treating the specific causal order as established fact.
What Changes Once You See It?
You start asking what else might be contributing to a visible team problem rather than assuming it’s self-contained, a results problem might have an accountability, commitment, conflict, or trust dynamic contributing to it, worth checking rather than assuming. You get more attentive to whether a team’s harmony is genuine or reflects avoidance of real, productive disagreement about the actual substance of a decision, since that’s exactly the kind of suppressed disagreement covered elsewhere in this Field Guide, though you stay specific about what kind of conflict is missing, task-related disagreement about ideas, not conflict in general. You also treat the model as a useful diagnostic vocabulary for talking about team dynamics, not as a scientifically validated sequence that always applies in the stated order.
Common Misunderstandings
- It isn’t an empirically derived or rigorously tested academic model. It’s a practitioner consulting framework, developed and popularized through a business fable, useful as a diagnostic vocabulary, not as a scientifically validated causal chain, and its five ingredients being individually plausible doesn’t establish that the specific pyramid connecting them is correct.
- It isn’t the same as Psychological Safety. Lencioni’s vulnerability-based trust overlaps conceptually with psychological safety, but psychological safety is a separately developed and independently studied construct, evidence supporting psychological safety shouldn’t be treated as validation of Lencioni’s entire five-stage pyramid.
- It doesn’t mean every team dysfunction traces back to trust in a strict, linear way. Real teams can have overlapping or differently ordered problems, and treating the pyramid as a rigid diagnostic checklist can miss dysfunctions that don’t fit the stated sequence.
- It isn’t the same as simply getting people to be nice to each other or avoid conflict. The model explicitly argues that avoiding productive task disagreement, not engaging in it, is the dysfunction, healthy teams need real disagreement about ideas, not conflict of every kind or intensity.
- It doesn’t mean addressing results and accountability directly is always wrong. In practice, teams often need to work on multiple layers simultaneously, the model’s usefulness is as a lens for asking what’s underneath a symptom, not as a strict prerequisite sequence that must be followed in order.
Diagnostic Question
What team dynamic might be contributing to this visible symptom, trust, conflict, commitment, accountability, or focus on collective results, and what evidence do we actually have for that, rather than just Lencioni’s proposed order?
Explore Further
Field Notes
- None yet.
Related Field Guide
Origin
Patrick Lencioni, The Five Dysfunctions of a Team: A Leadership Fable (2002).