Org, people & execution
The Five Dysfunctions of a Team
Lencioni's pyramid of five cascading team dysfunctions, from absence of trust at the base to inattention to results at the top, used to diagnose why a leadership team underperforms and to decide where the repair work has to start.
Also known as Lencioni model, Lencioni's pyramid. First set out by Patrick Lencioni in 2002; the primary source is cited in full below.
- Format
- Structural model
- Level
- Team
- Best for
- Plan execution
- Decision stage
- Diagnose · Execute
- Difficulty
- Introductory
- Time to apply
- A day to run the initial diagnosis; the repair work the model prescribes runs over months.
Plate · The model
The components
Absence of trust
The base of the pyramid, and in prose the place to start: members are unwilling to be vulnerable, to admit weakness, error or need for help. Without this safety, every layer above is compromised.
Signals of strength
Mistakes concealed or spun · Nobody asks for help · Grudges held and offence assumed · Meetings dreaded, energy spent on impression management
Fear of conflict
Teams without trust cannot debate. Disagreement moves out of the meeting and into corridors, and artificial harmony replaces the open contest of ideas that good decisions need.
Signals of strength
Meetings boring and agenda-driven with no real argument · Back-channel politics and post-meeting lobbying · Contentious topics quietly kept off the agenda · Direct challenges treated as personal attacks
Lack of commitment
Without genuine debate, members do not buy in. Decisions are nominally agreed and privately doubted, and ambiguity about direction spreads down through the organisation.
Signals of strength
Decisions revisited repeatedly · Different accounts of what was agreed · Analysis prolonged to avoid committing · Second-guessing among members after the fact
Avoidance of accountability
Members who never truly committed will not challenge peers who underdeliver. Standards drift, deadlines slip, and the leader becomes the sole enforcer of performance.
Signals of strength
Missed deadlines pass without comment · Peers complain about each other to the leader instead of to each other · Visible double standards between members · Mediocrity tolerated to preserve comfort
Inattention to results
The top of the pyramid: members put individual goals, ego, career or departmental interests ahead of the team's collective outcome, and the team stops measuring itself by what it achieves together.
Signals of strength
Departmental wins celebrated while team goals slip · Status and title arguments absorbing energy · Achievement-oriented people leaving · No single shared scoreboard anyone can name
When it earns its keep
- A senior team is polite in the room and political outside it, and you need a shared language to name what is actually going wrong.
- Decisions keep being revisited after meetings, and you suspect the cause sits below the surface of the decision process itself.
- You are taking over a team with visible friction and want a structured first conversation rather than a vague away-day.
- Individual members are capable and motivated, yet the team's collective results lag, which points at the dynamics rather than the people.
And when it doesn't
- The team's problem is structural: unclear mandate, wrong composition, no real interdependence. Hackman's research suggests fixing design conditions before working on interpersonal dynamics, and no amount of trust-building repairs a team that should not exist.
- You need an evidence-graded instrument for research or high-stakes selection. The model is a practitioner heuristic and its assessment was never built to psychometric standards.
- The dysfunction is really one individual's behaviour. The model diagnoses collective patterns; a single toxic or misplaced member needs direct management, and the pyramid can become a way of avoiding that conversation.
- Conflict is already open and destructive. The model's push towards more conflict assumes a baseline of safety that a genuinely hostile team does not have.
How to run it
Before starting, gather the inputs the analysis depends on:
- Honest observation of the team in action: how meetings run, what gets debated, what gets settled in corridors afterwards.
- The team's actual collective results against its goals, since the top of the pyramid is only visible against evidence of performance.
- Candid input from members, gathered individually, about what they hold back and why.
- A leader willing to be part of the diagnosis. If the leader models invulnerability or ducks conflict, the analysis will find it, and the exercise fails if that finding is unsayable.
- 1
Assess the team against each dysfunction
Work up the pyramid from the base, using observed behaviour rather than self-report alone. Lencioni's team assessment gives a rough profile, but the behavioural signals in meetings are usually more telling than the questionnaire.
- 2
Locate the lowest broken layer
The model's central claim is that each dysfunction enables the one above it. A team that cannot commit usually cannot commit because it never really debated; a team that never debates usually fears exposure. Find the deepest layer that is broken and start there.
- 3
Build vulnerability-based trust
Trust in this model means willingness to be seen to be wrong, uninformed or struggling. Lencioni's tools include personal histories, behaviour profiles and leaders going first in admitting error. This is slow work and cannot be delegated to a facilitator.
- 4
Legitimise productive conflict
Make disagreement about ideas an explicit norm: mine for dissent, name artificial harmony when it appears, and distinguish ideological conflict from personal attack.
- 5
Force clarity and closure on decisions
End debates with an explicit decision, deadline and owner, even without consensus. Lencioni's phrase is 'disagree and commit'; ambiguity after the meeting is the tell that commitment was never achieved.
- 6
Shift accountability to peers and results to the team
Publish goals and standards so members can challenge each other directly rather than routing everything through the leader, and make the collective result, visible on one page, the score that matters over individual status.
Reading the result
A profile of the team against the five layers, an identification of the deepest broken layer, and a repair sequence that starts at that layer rather than at the most visible symptom.
- Read from the base upwards. Symptoms usually present at the top (poor results, missed commitments) while causes sit lower; the model's value is forcing the search downwards.
- Treat the cascade as a hypothesis to test, never as proof. The causal chain is Lencioni's assertion, and a team can plausibly lack commitment for reasons other than suppressed conflict.
- A clean bill of health on the questionnaire with poor results in reality means the diagnosis is wrong or the honesty is missing. Believe the behaviour.
A worked example
The executive team of a caravan manufacturer confronts its own politeness
A Yorkshire manufacturer of touring and static caravans has missed its production and margin targets for three consecutive quarters. The executive team of six (MD, operations, sales, finance, design and HR directors) is experienced and individually strong. Board meetings are courteous and short. Meanwhile sales blames operations for twelve-week lead times, operations blames sales for accepting bespoke specifications, and both cases are made to the MD privately. The HR director facilitates a Five Dysfunctions review.
- Absence of trust
- Present. The operations director has been hiding the true state of the fit-out bottleneck for months rather than admit his recovery plan failed. Directors describe pre-meeting alignment calls to avoid being caught out in front of the MD. Nobody has said 'I need help' in the room in living memory.
- Fear of conflict
- Severe, and the most visible layer. The lead-time argument, the single most important commercial issue, has never been debated by the full team. It runs as two private lobbying tracks to the MD, who arbitrates. Meetings finish early because nothing contentious is tabled.
- Lack of commitment
- Follows directly. The 'standard specification' policy agreed in January has been quietly ignored by sales, who never believed in it and never argued against it. Three directors give three different versions of what the policy actually requires.
- Avoidance of accountability
- Established. When sales accepted forty non-standard orders against the policy, no peer said anything; the finance director logged it and briefed the MD. Standards are enforced vertically or never.
- Inattention to results
- Emerging. Sales celebrates record order intake while the order book is precisely what is breaking production. Each function hits its own dashboard; the company misses its targets. No director could state the team's single most important shared number when asked.
The read. All five layers show damage, but the review places the root at trust and conflict: this team settles everything through the MD because open disagreement feels dangerous, and every downstream failure follows from that. The repair starts small, with the MD admitting his arbitration habit has made things worse and the lead-time question debated, at length and in the room, until a decision everyone has actually contested can be committed to. The team also adopts one shared number, contribution margin per production slot, as the scoreboard. The model has done its job if the fights move into the meeting.
Pitfalls
- Starting at the top by exhorting people to 'focus on results'. The model exists precisely to argue that the top of the pyramid cannot be fixed at the top.
- Confusing vulnerability-based trust with predictive trust. Teams often score themselves well because they can rely on each other's competence, while remaining unable to admit weakness, which is the trust the model means.
- Running the diagnosis as a one-off away-day. The behaviours regress under pressure, and the model's tools assume months of repetition, principally by the leader.
- Using the pyramid to pathologise a team whose real problem is design: wrong people, no shared task, no reason to be a team at all.
- Letting the leader administer the diagnosis to everyone but themselves. In Lencioni's own account the leader's willingness to go first is the hinge of the whole model.
What the critics say
The model is a practitioner fable with thin peer-reviewed support. It was derived from Lencioni's consulting experience and presented through a fictional narrative rather than research, and the accompanying team assessment was never validated to psychometric standards. Reviewers note the absence of the sampling, controls and falsifiability expected of credible team research.
Lencioni, P. (2002) The Five Dysfunctions of a Team, Jossey-Bass; limitations discussed in academic reviews of the book and of Lencioni's model in the management education literature.
Where the model overlaps with the research literature, the evidence-backed version is Hackman's: team effectiveness is driven principally by design conditions (a real team, compelling direction, enabling structure, supportive context, competent coaching) rather than by interpersonal dynamics. Hackman was openly sceptical of team-building interventions aimed at trust and harmony, noting that harmony is as plausibly a consequence of performance as a cause of it.
Hackman, J. R. (2002) Leading Teams: Setting the Stage for Great Performances. Boston: Harvard Business School Press; Coutu, D. (2009) 'Why Teams Don't Work' (interview with J. R. Hackman), Harvard Business Review, May 2009.
The causal cascade the pyramid asserts is untested. The academic literature does find a real relationship between intrateam trust and performance, but it is moderate in size and correlational, which falls well short of the model's claim that trust is the foundation on which all team performance rests.
De Jong, B. A., Dirks, K. T. and Gillespie, N. (2016) 'Trust and Team Performance: A Meta-Analysis of Main Effects, Moderators, and Covariates', Journal of Applied Psychology, 101(8), pp. 1134–1150.
Sources and further reading
- Lencioni, P. (2002) The Five Dysfunctions of a Team: A Leadership Fable. San Francisco: Jossey-Bass.
- Lencioni, P. (2005) Overcoming the Five Dysfunctions of a Team: A Field Guide. San Francisco: Jossey-Bass.
- Hackman, J. R. (2002) Leading Teams: Setting the Stage for Great Performances. Boston: Harvard Business School Press.
- Coutu, D. (2009) 'Why Teams Don't Work', Harvard Business Review, 87(5), May 2009. ↗