You've assembled a team of A-players. Each member has a stellar resume, deep expertise, and proven results. So why does the team underdeliver? Why do meetings drag on without decisions? Why does the same problem keep coming back, quarter after quarter?
The answer rarely lies in skill. It lies in how the team relates to itself.
Patrick Lencioni's The Five Dysfunctions of a Team — and the model now widely known as The Five Behaviors of a Cohesive Team — is one of the clearest frameworks ever written about why smart groups fail. After running this assessment with hundreds of leadership teams across 37+ countries, one pattern is unmistakable: teams that perform together share one thing first.
Trust.
The Pyramid That Built Modern Team Coaching
The model is built as a pyramid. You can't skip a level — each layer literally rests on the one below it. From bottom to top:
- Trust — Members feel safe to be vulnerable with one another. They admit weaknesses, ask for help, and own mistakes without performing.
- Healthy Conflict — Because trust exists, the team can engage in passionate, unfiltered debate around ideas. Disagreement becomes productive, not personal.
- Commitment — Once everyone has been heard, the team can fully commit to decisions — even those they didn't initially agree with.
- Accountability — Members hold each other to those commitments. Peer-to-peer accountability replaces the bottleneck of "the boss has to do it."
- Results — The team focuses on collective outcomes, not individual recognition. The scoreboard becomes shared.
Not finance. Not strategy. Not technology. It is teamwork that remains the ultimate competitive advantage, both because it is so powerful and so rare. Patrick Lencioni, The Five Dysfunctions of a Team
Why Trust Is Different From What You Think
When most leaders say "trust," they mean what Lencioni calls predictive trust — the basic confidence that a colleague will deliver what they said they'd deliver. That's important, but it's not what builds cohesive teams.
The trust that powers the pyramid is vulnerability-based trust. It's the willingness to say, in front of your peers and your leader, things like:
- "I don't know how to solve this."
- "I made the wrong call on that one."
- "You're better at this than I am — what would you do?"
- "I need help."
Most leadership teams operate without this. People hold back. They pre-rehearse their points before meetings. They protect their territory. They smile through disagreement and grumble in the parking lot afterward. The team isn't bad — it's just guarded. And guarded teams cannot have the conflict they need to make great decisions.
How to Build It (Without a "Trust Fall")
Vulnerability-based trust isn't built in a single offsite or a ropes course. It's built through repeated, low-stakes moments where the team sees that it's safe to be human. Four practices that consistently work:
1. Leaders go first
The leader sets the ceiling for vulnerability on the team. If you, as the leader, never admit a mistake, never say "I don't know," and never ask for help, your team won't either. Going first is uncomfortable. It's also the single most leveraged behavior in this entire model.
2. Personal histories exercise
A simple but powerful intervention: each team member shares three things — where they grew up, how many siblings they had, and the most interesting or difficult challenge of their childhood. In 30 minutes, people learn things about each other they didn't know in three years. The point isn't oversharing; it's seeing each other as full human beings.
3. Working styles assessments
Tools like DiSC, MBTI, or the Five Behaviors assessment itself give the team a shared language for difference. When a team understands that one member processes externally and another internally — that one optimizes for relationship and another for task — disagreement stops being a personality flaw. It becomes a design feature.
4. Regular feedback rituals
Small, repeated rituals beat big quarterly reviews every time. A simple round at the end of each leadership meeting — "What's one thing each of us could do differently next week to help the team?" — normalizes feedback and removes the awkwardness from harder conversations later.
The Cost of Skipping the Foundation
Here's what happens to teams that try to skip trust and start higher up the pyramid:
Skip trust → Get artificial harmony. The team avoids conflict entirely. Decisions are made in side conversations. Real issues never reach the table.
Skip conflict → Get false commitment. Without debate, people leave the room without buy-in. They nod, then revert.
Skip commitment → Get blame culture. Without clarity on what was decided, accountability becomes finger-pointing.
Skip accountability → Get mediocre results. The team optimizes for individual visibility rather than the collective scoreboard.
It's all interconnected. And it all starts at the base.
Where to Go From Here
If any of this resonates — if you can name the gap on your own team between where you are and where the pyramid says you could be — that's good news. The framework is teachable. The behaviors are practiceable. And the change tends to compound: a team that builds genuine trust this quarter will be having different, better conversations by next quarter.
The hardest part is rarely the model. It's the willingness to start by going first.