Cited from real sources 7 min read Written by Arun Agrahri Updated September 2026

A framework by Patrick Lencioni

The Five Dysfunctions of a Team: Patrick Lencioni's Pyramid

Patrick Lencioni stacks five team failures into a pyramid. No trust at the base. Then fear of conflict. Then no real commitment. Then no accountability. At the top, nobody watches the results. Each one rests on the one below. So the base is the only place to start work.

What builds trust, and what does not

you can build trust with somebody in a matter of weeks if you work on it. You can work with somebody for years and never have trust.

Time on the team is not the variable. Lencioni says the variable is whether anyone lets the team see them get something wrong.

Patrick Lencioni Young and Profiting Watch at 16:00

The framework

The Lencioni pyramid

The Lencioni pyramid stacks the five dysfunctions of a team from the base up: absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results. He calls it a triangle or a pyramid, whichever you prefer, and teaches it from the bottom up.

At the base of the triangle or pyramid, however you want to describe it, is trust. And that is if people don't trust each other, the other four dysfunctions are not going to be overcome.
Lencioni, on the order of the pyramid Watch at 15:14
  1. Inattention to results
  2. Avoidance of accountability
  3. Lack of commitment
  4. Fear of conflict
  5. Absence of trust
Layer names from Lencioni's 2013 talk Watch at 0:40

Each layer makes the next one possible. Trust enables conflict. Without it, he says, you are only trying to win the argument or manipulate the other person. Conflict is what allows commitment. You argue, and at the end you either convince someone or the leader breaks the tie, and people buy into that. As he says in the 2013 talk, people who don't weigh in don't buy in.

Lencioni calls accountability the hardest dysfunction, and it depends on commitment. You won't tell a peer they fell short on something they never agreed to. On his team assessment it is the lowest score by far, lower even than conflict. The top layer is people watching their own results over the team's: their department, career, reputation, status or bonus.

He closes the 2013 talk by running the chain backward, from results to accountability to commitment to passionate disagreement, and down to a team that trusts each other and is vulnerable.

The base

Vulnerability-based trust, the base of the pyramid

Trust is the base of the pyramid, and Lencioni means something narrower than the everyday word. You cannot patch the third layer while the first still fails.

when we talk about trust, we're talking about vulnerability-based trust
Lencioni, defining the base of the pyramid Watch at 15:28

Not predictability. He is explicit about this. Knowing someone a long time and forecasting their behaviour is a different thing, and it does not do the job. What does is a willingness to say the unflattering sentence out loud. His own examples are plain: I do not know the answer. I think you are smarter than me. I screwed up. I am sorry I was rude yesterday.

That is why the pyramid has a direction. Trust is not a nice-to-have at the bottom; it is the thing that makes the next layer possible.

without trust without vulnerability based trust conflict becomes politics I'm trying to manipulate you to win but with trust conflict is nothing but the pursuit of truth or the best possible answer
Lencioni, on what trust converts conflict into Watch at 13:32

Same argument. Same disagreement. Two different rooms. Politics is what a debate becomes when nobody can afford to be wrong in public. That is the mechanism the pyramid describes. It is also why Lencioni treats team health as the thing that decides whether a smart strategy survives the people who have to run it.

Practice

How do you fix the base first?

The order matters as much as the list. Working on accountability while the base has already failed produces compliance, not commitment.

1

Go first, and go first as the leader.

Vulnerability-based trust starts with the person who has the most to lose by showing weakness. Say the hard sentence in the meeting, about your own work.

2

Treat the smiling meeting as a symptom.

When everyone nods and nobody decides, that is the tell. Lencioni's marker is simple. Does anyone still have something to say when people walk out? Then the team never made the decision.

3

Aim the conflict at ideas, not people.

He draws a hard line between mean-spirited interpersonal conflict and productive ideological conflict around issues. The second is the one you are trying to increase, and the first is what people fear when you ask for more debate.

4

Move accountability sideways.

When only the leader holds people to account, you get a parent and children. Peer-to-peer accountability is the target. It only works once the first two layers hold.

5

Overcommunicate the decision after the argument.

Clarity at the leadership table is worth nothing if it stops there. Lencioni's view is that leaders underestimate how much repetition a decision needs before the organization can act on it.

6

Judge the top layer by collective results.

The final dysfunction is people optimizing their own status over the team's outcome. His hiring answer is humble, hungry and smart. Humble does most of the work.

Boundary conditions

When does the pyramid fail?

The failure mode Lencioni spends the most time on is the one that looks like success. A team that never argues reads as aligned, right up to the moment nothing ships.

when we get together and we think, "My job is to affirm that person and make them feel good and to avoid any discomfort here." The problem is then there's something left to be said.
Lencioni, on artificial harmony Watch at 12:01

He calls that artificial harmony, and he thinks it is worse now than it has ever been. His example of the worst offenders is not the one you would expect: churches, because the group already expects itself to be nice. Any culture with a norm of pleasantness carries the same exposure. That covers a lot of startups that call themselves low-ego.

Works best when

  • The group is a real team with shared outcomes, not a set of people reporting to one manager
  • The leader is willing to be the first one seen getting it wrong
  • You can work the layers in order instead of jumping to the one that hurts most
  • People are in the room often enough for a norm to form

Fails when

  • You ask for more conflict without building the trust first, which produces the interpersonal kind
  • The culture prizes niceness, so artificial harmony reads as a healthy team
  • You run it as a one-off offsite exercise instead of a standing practice
  • The leader wants the team vulnerable while staying invulnerable

The first one is the expensive mistake. Conflict is the second layer for a reason. A manager who reads the book and opens with a demand for candour gets the failure the framework predicts. For the interpersonal half of that problem, Kim Scott's radical candor sequences the same move at the level of one conversation.

Primary sources

Where Lencioni discusses this

Two recordings of Lencioni teaching the model himself. The Young and Profiting interview runs 72 minutes and is the more conversational. The 2013 talk is where he walks the pyramid front to back for a room.

Where experts disagree

Where operators disagree: is a torn-up team a failure, or the price?

Patrick Lencioni

treats team health as the precondition for everything above it. Build vulnerability-based trust first and debate becomes the pursuit of the best answer; skip it and the same debate becomes politics, where people manoeuvre to win rather than to be right.

Andy Grove

ran Intel's RISC debate to a correct conclusion and accepted the wreckage. Half the people who had worked on the processor left, and by his own account those relationships never healed. He calls the debate itself one of the most important ways of handling the question.

The condition is what is at stake in the argument. Lencioni is describing the standing operating state of a team, where artificial harmony compounds quietly for years. Grove is describing a one-off bet-the-company call under a deadline. Note Grove is not disagreeing that the cost is real: he names it plainly and says these are not fun and easy processes even among people who know each other well.

Useful? Send it to whoever runs the meeting where everybody agrees and nothing moves.

Want the full playbook?

Get 370 leadership & management frameworks.

54 frameworks 107 rules 201 heuristics & principles 8 operators

From Brené Brown, Ed Catmull, Tony Robbins, and 5 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

New experts every week

Know when the next expert lands.

Gavel adds new operators to the database every week, each one with cited frameworks you can check and a note on where they disagree with the others. You found this page by searching. Get the next one by email instead.

65 experts 84 cited frameworks

Latest: Gary Klein on The Premortem

One email a week, only when new experts shipped. Unsubscribe with one click. We never sell or share email.

Related frameworks