Why Your Leadership Team Knows the Pyramid and Still Can't Climb It
Every leadership team I've worked with can recite Lencioni's model. Trust. Conflict. Commitment. Accountability. Results. It's on a whiteboard in half the conference rooms I walk into. Somebody read The Five Dysfunctions of a Teamon a flight, brought it back to the team, and got everyone nodding.
Then nothing changes.
The team still avoids the hard conversation in the staff meeting and has it in the parking lot afterward. Commitments still get made in the room and quietly abandoned the moment things get uncomfortable. Accountability still flows one direction — down from the owner — instead of sideways, peer to peer, where it actually has to live for the model to work.
Here's what I've learned building and selling two companies, and now watching it play up close in EOS implementations: this isn't a knowledge problem. Leaders don't fail to build trust and productive conflict because they don't understand the concept. They fail because nobody taught them the skill.
Will Without Skill Is Just Posture
Lencioni's pyramid describes an outcome. It doesn't teach a behavior. A leadership team can have total will — genuine desire to trust each other, to fight about ideas instead of dodging them, to hold each other accountable — and still not have the first idea how to run that conversation when it actually matters.
Will gets you to the offsite. Skill is what happens in the room on a random Tuesday when someone underperforms and the team has to say something about it, in real time, without the meeting turning into either a blowup or a polite non-event where nothing real gets said.
Will without skill is just posture.
This is where Fierce Conversations earns its place next to EOS on my whiteboard. Fierce doesn't compete with Lencioni's model. It's the missing instruction manual for it. Every layer of that pyramid maps to a specific, learnable conversational skill — and most leadership teams have never been taught a single one of them.
Trust: The Skill of Coming Out From Behind Yourself
Vulnerability-based trust is the foundation of the pyramid, and it's also the layer most leaders fake their way past. They mistake trust for comfort. They think if the team gets along, trust exists.
Real vulnerability-based trust requires a leader to say what they actually think, admit what they don't know, and own a mistake out loud in front of the people they lead. Fierce calls this coming out from behind yourself into the conversation. It's a specific skill: dropping the polished, careful version of what you're saying and replacing it with the true one.
Most executives have spent a career being trained out of this. Corporate life rewards the polished answer. So when a leader finally decides they want a high-trust team, they run straight into the fact that they've never practiced saying the true thing in a room where it might cost them something. That's not a will gap. That's an unrehearsed skill.
Conflict: The Skill of Making It Productive Instead of Personal
Every leadership team says it wants "healthy conflict." Almost none of them have the skill to produce it. What they have instead is silence in the meeting and full-volume opinions afterward — the classic sign that conflict is happening, just not where anyone can use it.
The skill here is what Fierce calls the confrontation conversation — not confrontation in the aggressive sense, but the disciplined practice of naming the real issue directly, attaching it to a specific behavior or decision, and staying in the conversation until it resolves instead of retreating to safety the moment it gets tense.
Most leaders default to one of two failure modes: they avoid the conflict entirely to protect the relationship, or they let it turn personal because they've never practiced separating the idea from the person holding it. Both are skill failures. Neither is fixed by wanting conflict to be healthier.
Commitment: The Skill of Deciding What Matters Most
Commitment breaks down in leadership teams for a boring, specific reason: the room agrees to something without ever getting specific enough to know if they actually agreed.
Fierce's "Decide What Matters Most" conversation forces the specificity that real commitment requires — not vague alignment, but a clear, named decision everyone can hold each other to later. In EOS terms, this is exactly why Rocks fail. Not because the team lacked will to execute. Because the Rock was set without the skill of getting precise enough about what "done" actually means.
Accountability: The Skill of the Clean Ask
Peer-to-peer accountability is the layer that separates functional leadership teams from the rest, and it's the one built entirely on a skill most people have never been taught: how to ask someone for something directly, without padding it in apology or burying it in vague language that lets both parties pretend it wasn't really a request.
This is what Fierce calls a clean ask, and it's the mechanical foundation of accountability. Without it, "holding each other accountable" stays a value on the wall instead of a behavior in the room. I watch this fail constantly in L10 meetings — the issue gets identified, the discussion happens, and the solve gets softened into something so vague nobody can be held to it a week later.
Results Are the Byproduct, Not the Starting Point
By the time a team has the skill to build real trust, run productive conflict, get specific about commitment, and make clean asks of each other, results stop being something you have to chase. They're what the system produces once the conversational skill underneath it is actually there.
This is the piece most leadership development gets backwards. It treats results as a matter of alignment and effort — pure will. But a team with high will and low skill just produces friction faster. It doesn't produce results faster.
The Question Worth Asking Your Team
Which layer of the pyramid is your team weakest in — and is it because they don't want it, or because nobody ever taught them how?
Answer that honestly. It's usually the second one. And it's fixable.
