The Five Dysfunctions You're Quietly Tolerating
Most leadership teams don't fail dramatically. They fail quietly — in the meeting where the real objection goes unspoken, the decision everyone nods at but no one owns, the missed number nobody names out loud. I've taught Patrick Lencioni's The Five Dysfunctions of a Team to enough leadership teams to know the pattern: the dysfunctions are rarely loud. They're tolerated.
Lencioni frames them as a pyramid, and the order matters, because each one grows out of the one beneath it.
The pyramid, from the ground up
Absence of trust is the foundation — and by trust, Lencioni means something specific: the willingness to be vulnerable with each other. To say “I was wrong,” “I don't know,” “I need help.” When that's missing, people spend energy managing their image instead of doing the work.
Fear of conflict grows directly out of that. Teams without trust don't have honest debate; they have careful, guarded conversations where the important disagreement happens later, in the hallway, in the parking lot — anywhere but the room where it could actually be resolved.
Lack of commitment follows. People don't truly commit to decisions they were never able to weigh in on honestly. You get nods in the meeting and hesitation everywhere after it. Compliance, not conviction.
Avoidance of accountability comes next. When no one truly committed, no one feels standing to hold a peer to the standard — so the hard conversation about a missed commitment simply doesn't happen.
Inattention to results sits at the top. When the first four are in play, people drift toward their own goals, their own status, their own departments — and the collective result quietly stops being the point.
Why naming them is half the battle
Here's what I've seen teaching this: the moment a team can name which dysfunction they're living in, the shame drops and the work can start. “We don't have a people problem — we have a trust problem, and it's making our meetings useless” is a sentence that changes a room. Lencioni's gift is a shared vocabulary for things teams usually only feel.
But naming isn't fixing. And this is where I bring in the operating-system side of the work, because vocabulary alone won't rebuild a team — rhythm will.
Where Lencioni meets the operating rhythm
The dysfunctions are a diagnosis. An operating system is part of the treatment. Consider how Gino Wickman's Traction tools quietly work against each layer of the pyramid:
Healthy conflict has somewhere to live. The weekly Level 10 Meeting's IDS discipline — Identify, Discuss, Solve — gives disagreement a structured, expected home, so the hard topic surfaces in the room instead of the hallway.
Commitment gets concrete. When decisions become owned Rocks rather than vague intentions, “we agreed” turns into “I own this, by this date.”
Accountability stops being personal. A shared Scorecard and a clear Accountability Chart mean the standard is visible and objective — you're holding each other to the number, not to a grudge.
Results stay in front of everyone. The rhythm itself keeps the collective scoreboard on the table every single week.
And underneath all of it sits the Maxwell truth we keep returning to: trust starts with the leader. Lencioni is clear that the leader has to go first — to be the one who admits the mistake, names the weakness, invites the disagreement. You cannot ask a team to be vulnerable from behind a wall of your own making. The Law of Influence again: it starts with who you are.
The honest question
You don't have to fix all five this quarter. You have to name the one you're tolerating most — and decide it's no longer acceptable. Trust is almost always the place to start, because everything above it is built on that foundation. Get honest there, give the conflict somewhere structured to go, and the pyramid starts working for you instead of against you.
Source note: Drawn from Patrick Lencioni's The Five Dysfunctions of a Team: A Leadership Fable, with connections to Gino Wickman's Traction (IDS, Rocks, Scorecard, Accountability Chart) and John C. Maxwell's Law of Influence. Original commentary by The Leadership Forge.