Five Dysfunctions of a Team

Theory & origin

Patrick Lencioni published the model in 2002 as a business fable, and it spread because it names what everyone in the room already feels. The base is absence of trust, meaning vulnerability-based trust: the willingness to admit mistakes, ask for help, and be wrong in public. Without it, conflict feels unsafe, so teams develop artificial harmony where the real argument happens after the meeting. People who never argued never bought in, so decisions stay ambiguous and get relitigated forever. Without commitment there is nothing to hold peers accountable to, so accountability gets delegated up to the boss, who becomes the team's only enforcement mechanism. And at the peak, individual goals, department budgets, and careers quietly outrank the shared result. Two honesty notes for the educated reader. The evidence base is practitioner experience and the fable's enduring resonance, not peer-reviewed research, and the trust and conflict layers overlap heavily with psychological safety, which has the research pedigree this model lacks. Use the pyramid as a working vocabulary, and borrow Edmondson's evidence when the CFO asks for proof.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

How a consultant runs it

1. 01 Survey the team anonymously against all five layers before the offsite. The scores rarely surprise the room. Seeing them written down does.
2. 02 Start at the base regardless of where the pain presents. Relitigated decisions are usually a trust problem wearing a commitment costume.
3. 03 Have the leader go first on vulnerability: personal histories, own mistakes, own development gaps. Nobody opens up below their boss's level.
4. 04 Install conflict norms that make debate safe and finite: disagree in the room, on the merits, then commit outside it.
5. 05 Convert commitment into peer accountability: decisions leave the room with owners, dates, and the explicit permission for peers to call slippage.

Worked example

An insurer's nine-person executive committee has flawless meetings and a war by email. The anonymous survey scores trust at 2.1 and conflict at 1.7, the artificial-harmony signature. The offsite starts with personal histories and the CEO going first on the year's worst call. Conflict norms follow: disagreements get fought in the room on the merits, and every decision leaves with an owner, a date, and explicit permission for peers to call slippage. Two quarters later the relitigation habit is gone, and the clearest win takes 40 minutes: a strategy proposal that would previously have died slowly over six polite months gets argued down and killed in a single session, in the room, with its sponsor agreeing.

Common pitfalls

1. 01 Running the offsite without the leader going first, which teaches everyone the real rules
2. 02 Treating the pyramid as five separate workshops instead of one causal chain from trust
3. 03 Using it where the real dysfunction is structural, then blaming the team for the design
4. 04 Confusing artificial harmony with health because the meetings feel good
5. 05 Quoting it as research. Its power is vocabulary and sequence, not evidence.

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.