The five dysfunctions of a team

Lencioni published The Five Dysfunctions of a Team in 2002. Most of the book is a fable about a fictional executive team; the model arrives near the end, drawn as a pyramid with trust at the base. That format is why it spread so widely, and why it gets quoted rather than tested. Treated as a diagnostic checklist rather than a law of nature, it remains one of the most useful things to put in front of a stuck leadership team.

The five dysfunctions at a glance

Absence of trust

Lencioni is specific about the kind of trust he means, and this is the part people miss. He is not talking about predictive trust, where you can forecast a colleague's behaviour because you have worked with them for years. He means vulnerability-based trust: the confidence that saying "I need help" or "that was my error" will not be used against you later.

Teams without it burn enormous energy on impression management. People prepare for meetings by rehearsing how they will look rather than what they will decide. It is close to psychological safety, though Lencioni arrived at it from consulting practice rather than research.

• Go first, as the leader, and go specific. "I misjudged that timeline and it cost the team three weeks" does more than any team-building exercise.
• Watch for the tell: a review where nobody asks a question is not a well-prepared review, it is a silent one.
• Give people something to be competent at in front of each other. Trust follows shared work more reliably than disclosure.
• Do not run a deep personal-disclosure exercise on a team whose manager punishes candour. You will only collect the evidence used against them next.

Fear of conflict

The symptom Lencioni calls artificial harmony: meetings that are comfortable, brief and useless. Nothing is contested, so nothing is examined. The debate still happens, it just moves to corridors and side channels where it can never be resolved.

If the two most important people in the room have never openly disagreed, the team has not achieved alignment. It has achieved avoidance.

The leader's job here is closer to mining than refereeing. Disagreement is buried, and someone has to dig it up and make it safe in the open. In practice: "there are two views on this and we have heard one", then wait through the silence.

• Assign someone to argue the other side, and rotate the role. It gives dissent a job title so it stops being a personal risk.
• Ask for written positions before the discussion. Quiet people commit their view to paper before the loudest voice sets the frame.
• Interrupt personal attacks immediately, and let the argument about the work run hot. Teams conflate the two, then ban both.
• Debrief the argument, not only the decision. "That was uncomfortable and it was the right conversation" is what makes the next one possible.

Lack of commitment

Commitment fails for two reasons: ambiguity and lack of buy-in. Ambiguity is when people leave the room with different accounts of what was decided. Lack of buy-in is when someone never voiced an objection, so they never let go of it.

Buy-in is not consensus. Waiting for everyone to agree is a reliable way to stall a team. People need to be genuinely heard, then given a decision. Most adults will back a call they argued against if they believe the argument landed.

1. Spend the last five minutes of every meeting on one question: what did we decide, and what do we each tell our teams tomorrow? The disagreements it exposes are worth the time.
2. Set a deadline and decide on imperfect information. A team that decides and adjusts beats a team that waits and hedges.
3. Ask each person directly: can you live with this and defend it publicly? A pause is data.
4. Re-opening a decision should require new information, not renewed enthusiasm.

Avoidance of accountability

Lencioni means peer accountability, not managerial follow-up. The test is whether one member will tell another their work is slipping without routing it through the boss. In most teams that conversation feels like an act of aggression, so it never happens and standards drop to the level of the slowest person.

• Publish goals, owners and dates where every member can see them. Peer accountability is impossible when only the manager knows who owes what.
• Review progress as a team rather than one-to-one. Public commitments create social pressure that private ones do not.
• Teach people to raise it cleanly. Most avoidance is a skills gap, not a willingness gap, and constructive feedback is learnable.
• The leader is the backstop of last resort. Stepping in early trains the team to wait for you; never stepping in tells them standards are optional.

Inattention to results

The top of the pyramid is about what people substitute for the collective result: individual status, or the performance of their own function. It hides best of the five, because everyone involved is working hard and hitting targets. They are just hitting the wrong ones.

• Define a small number of shared results the whole team wins or loses on together, and keep the list to one page.
• Score them somewhere visible and talk about them first in every meeting, before departmental updates.
• Look at what your reward system pays for. If it pays for individual heroics, no amount of trust work will change behaviour.
• Praise whoever gave up their own priority to unblock someone else's. That is the behaviour you need, and it is usually invisible.

Where the model breaks down

This is where most summaries of Lencioni stop and simply agree with him. Four honest limits:

1. It is a fable, not a study. The model comes from Lencioni's consulting practice, distilled into a story. It is a well-organised set of practitioner observations, not peer-reviewed research, and should not be cited as though it were.
2. The strict sequence is doubtful. The book implies you must fix trust before anything else. In practice, shipping something difficult together often builds trust faster than any conversation about trust. Sequence is a default, not a rule.
3. It individualises structural problems. Plenty of teams that look low-trust are responding rationally to unclear roles, competing incentives or a manager who punishes bad news. Run a vulnerability exercise there and you treat the symptom while leaving the cause.
4. It assumes a stable team with one leader. Matrixed organisations, rotating project teams and distributed groups lack the shared history the model quietly depends on. The dysfunctions still show up; the fixes need adapting.

None of that makes it useless. It makes it a lens. The pyramid's value is that it stops a team arguing about symptoms and gives them a vocabulary for what is going wrong, which is usually further down than they think.

A quick self-diagnosis

Take your last three team meetings and answer honestly:

• Did anyone say "I don't know" or "I was wrong"? If not, start at the base.
• Was there a real disagreement in the room, or only afterwards?
• Could every person write down the same list of decisions?
• Has one member challenged another directly in the past month, without you present?
• When your function hits its numbers and the business misses, does it feel like a good quarter?

The pattern is easier to see from outside than inside, which is why this model pairs so well with experiential learning. Put a team into a short, real challenge with a deadline and the dysfunctions surface within minutes: who hedges, who stops the argument to keep things pleasant, who quietly protects their own scoreboard. Nobody needs persuading that trust matters after watching their own team lose because of it. Read it alongside Tuckman's stages for the other half of the picture: where a team is in its life, rather than what is broken in it.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.