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.
Find this on the mind-map
Introduction
Lencioni builds his model as a pyramid, not a checklist, and the shape matters. Each dysfunction is actually caused by the one below it, which means you can't skip a layer and expect a fix higher up to hold. Most teams try to fix accountability or results first, because those are the symptoms that show up on a dashboard. Most of those fixes fail, because the real problem is sitting one or two layers down, underneath the thing anyone can see.
Absence of Trust
The foundation, and the one everyone claims to already have. Lencioni means something narrower than "I believe you'll do your job." He means vulnerability-based trust: being willing to say "I was wrong," "I don't know," or "I need help" in front of the team, without it costing you anything.
Manager A runs smooth, polite meetings: nobody disagrees out loud, and everything looks aligned. Manager B's meetings are messier: people admit they're stuck, call out their own mistakes first. B's team looks less polished and performs better, because the politeness in A's room is actually people protecting themselves, not agreeing with each other.
Fear of Conflict
Without vulnerability-based trust, teams fake harmony instead of having real debate: agreeing in the room and relitigating everything in side conversations afterward. Lencioni's point isn't that conflict is good; it's that productive, ideological conflict about ideas is how good decisions actually get made, and a team that avoids it isn't actually more aligned, just less honest about where it disagrees.
Lack of Commitment
Unresolved conflict produces ambiguity, and ambiguity is what kills commitment, not disagreement itself. Commitment doesn't require consensus; it requires that everyone got heard and is clear on what was decided, even if they argued against it. A decision made without real debate is a decision nobody actually bought into, which is why it falls apart without warning the moment it gets hard.
Avoidance of Accountability
Because nobody fully committed to the decision, nobody feels the standing to call out a peer who's drifting from it. Accountability here isn't the manager enforcing a deadline. It's team members holding each other to the team's own standards, directly and uncomfortably, without waiting for the boss to do it. Teams that skip this step end up with the manager as the only source of pressure on the team, which doesn't scale past a handful of people.
Inattention to Results
At the top, without peer accountability, individuals protect their own status, their department's turf, or their own ego ahead of the team's collective scoreboard, often without saying so out loud. This is the dysfunction that's easiest to see and hardest to fix directly, because it's not really a results problem. It's four layers of unresolved trust, conflict, commitment, and accountability showing up as a missed number.
Putting It Together
The pyramid reads bottom-up and top-down at once. Bottom-up: trust enables real conflict, conflict produces real commitment, commitment makes accountability legitimate, and accountability is what actually protects results. Top-down: if results are slipping, the honest diagnostic question isn't "how do we hold people more accountable." It's "where, lower in this pyramid, did we actually stop?" Most teams that feel stuck on results are standing on a foundation they never built.

Why It Matters for Leaders
The teams this model catches you off guard on are the ones that look fine. Meetings run on time, people nod along, nobody's yelling. Lencioni's point is that you can't read team health off the surface, because the surface is exactly what a team without trust learns to manage carefully.
The practical use of the pyramid is as a diagnostic, not a to-do list. When results are off, the instinct is to add a dashboard, a deadline, a check-in. But if the actual break is at the bottom (nobody's willing to say "I'm stuck" in front of the group), none of that pressure fixes anything. It just teaches people to look busier while hiding the same problem better.
The layer most leaders avoid building on purpose is peer accountability, because it means stepping back. As long as you're the only one who calls out a slipping deadline or a dropped standard, your team's accountability has a ceiling: you. The moment two peers can hold each other to a standard without you in the room, the team's capacity stops being capped at your attention span.
Picture a manager, Renata, whose team has missed the last two launch dates despite "on track" updates every single stand-up. Instead of adding another status check, she asks each person privately: "is there anything you haven't said in the group that you'd tell me one-on-one?" Two people admit they've been stuck for a week and didn't want to look behind. She changes the stand-up question from "are we on track" to "what do you need help with today," and the next launch holds its date.
What to do next
Reinforce your understanding of The Five Dysfunctions of a Team
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 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.
Skills related to The Five Dysfunctions of a Team
Frameworks referenced from this book
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 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.
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.