The Five Dysfunctions of a Team
Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.
Find this on the mind-map
Introduction
Patrick Lencioni published this model in 2002, wrapped inside a leadership fable rather than an academic study — a fictional new CEO turning around a dysfunctional executive team. The model itself rests on human behavior rather than on strategy or product, which is exactly why it transfers across every industry you'll ever work in.
How It Works
The five dysfunctions stack on top of each other, and Lencioni draws them as a pyramid, each layer resting on the one below it.
Dysfunction 1: Absence of Trust. This isn't predictive trust ("I trust you to deliver"). It's vulnerability-based trust — the kind that lets someone say "I messed up," "I need help," "I don't know how to solve this." Without it, people put on armor, hide their weaknesses, and stop asking questions.
Dysfunction 2: Fear of Conflict. With no trust, there's no real debate. People nod along instead of disagreeing, and the honest conversation happens by the coffee machine or on an anonymous forum instead of in the room. A meeting where everyone agrees isn't harmony — it's usually fear.
Dysfunction 3: Lack of Commitment. People who never got to voice their view don't actually own the outcome. They say yes, but it's passive compliance, and weeks later it turns into "I never really agreed with that." The symptom shows up after the meeting, not during it.
Dysfunction 4: Avoidance of Accountability. With no real commitment, there's no shared standard — and with no shared standard, nobody challenges a peer who's falling short. Deadlines slip, the quality bar drops, and nobody wants to be the one who calls it out.
Dysfunction 5: Inattention to Results. Once the layers below go unaddressed, people start chasing personal wins instead: a product manager pushing their own roadmap, an engineer picking interesting problems over team velocity, a manager fighting for headcount instead of a shared cross-team result. Everyone looks busy. Nothing ships.
| Layer | Dysfunction | What it looks like | The repair |
|---|---|---|---|
| 5 | Inattention to results | Personal wins over team outcomes | Make collective results visible |
| 4 | Avoidance of accountability | Standards slip, nobody speaks up | Agree what "good" looks like |
| 3 | Lack of commitment | Fuzzy decisions, later backpedaling | Decide, summarize, write it down |
| 2 | Fear of conflict | Artificial harmony | Normalize challenging ideas |
| 1 | Absence of trust | Armor, hidden mistakes | Model vulnerability first |
Why It Matters for Leaders
The teams this model catches you off guard on are the ones that look healthy. Meetings run smoothly, people say yes, there's no visible tension — and the work still stalls. The problem usually isn't skills, strategy, or resourcing. It sits lower down than that.
Here's the practical value: this pyramid tells you which direction to look. If you're seeing weak results, your instinct is probably to push harder — more check-ins, more pressure, closer supervision. But if the real break is at the base of the pyramid, that pressure just makes the armor thicker and the results worse.
The model also reframes how you should think about conflict. Debate can look like a failure of teamwork, so a lot of leaders suppress it — and in doing so, kill off exactly what would have produced real commitment. People buy in when they've been heard, not when they've been quietly overruled.
Peer accountability is the layer most leaders skip, because accountability has always flowed through them personally. Strong teams hold each other to standards they set together — and that only works once trust, conflict, and commitment are already in place underneath it.
Two patterns show the diagnosis in action. A team that reported "on track" every single sprint and still missed its deadlines wasn't actually behind on the work — it just wasn't safe to say "I'm stuck." Changing the stand-up question to "where do you need help today?" moved delivery within weeks. A cross-functional group that spent months blaming each other for delays turned out to be working off three different definitions of "done," and a shared checklist cleared out months of tension almost overnight.
What to do next
Test your knowledge of The Five Dysfunctions of a Team
Practice The Five Dysfunctions of a Team
Apply The Five Dysfunctions of a Team to a real situation
Skills related to The Five Dysfunctions of a Team
Frameworks related to The Five Dysfunctions of a Team
Dunning-Kruger Effect
Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.
Goldilocks Principle
Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.
Hawthorne Effect
People change how they behave when they know they're watched — your attention is an intervention that changes what you see.
Maslow's Hierarchy of Needs
Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.
McKinsey 9-Box Model
A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.
Multipliers and Diminishers
Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.
Situational Leadership
There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.
The 6 Human Needs
Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.
The Architecture of High-Performing Teams
Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.
The Bannister Effect
One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.
The Inner Drive
A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.
The Pygmalion Effect
What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.
The Thomas-Kilmann (TKI) Model
Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.
Tuckman's Stages of Team Development
Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.
Books that reference this framework
Books related to The Five Dysfunctions of a Team
Coaching for Performance
Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.
Elevate
Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.
First, Break All The Rules
A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.
Multipliers
Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.
Team Topologies
Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.
The Coaching Habit
Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.
The First-Time Manager
The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.
The Five Dysfunctions of a Team
Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.
The Making of a Manager
Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?
The Manager's Path
Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.
Turn the Ship Around!
A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.