The healthiest teams argue more than the unhealthy ones. They admit failure more readily. They say things in meetings that would be career-limiting elsewhere. They’re the first to say when they don’t know something, when they got something wrong, when they need help.
This sounds like dysfunction. It isn’t. It’s what functional actually looks like. And the reason it looks wrong to most organisations is that most organisations have the wrong idea about what trust is.
Two kinds of trust
The kind of trust most teams have is reliability trust. You trust your colleagues because they deliver what they say they will. You trust them because they’re competent, consistent, and professional. This is real and it matters — you can’t build anything without it.
But it’s not enough. And it’s not what Patrick Lencioni’s model of team dysfunction identifies as the foundational requirement.
The trust that sits at the base of Lencioni’s stack — the trust that everything else depends on — is what he calls vulnerability-based trust. It’s not confidence that your colleagues are reliable. It’s the willingness to be seen as imperfect. To say, in front of people whose opinion of you matters to your career and your standing: “I was wrong.” “I need help.” “I don’t know.”
Those three sentences are simple. In most workplaces, they’re almost unsayable.
What gets built on skipped foundations
Lencioni presents his model as a leadership fable — a story about a fictional executive team — rather than a research report, and the five-dysfunction pyramid is a diagnostic heuristic rather than a proven causal mechanism. But it describes something real, and the thing it describes most precisely is the dependency.
The five dysfunctions sit in a stack, and the stack has a specific order. At the base: absence of trust. The dysfunction that follows is fear of conflict — but not conflict in the aggressive, personal sense. The conflict the model refers to is the productive kind: honest debate about ideas, the willingness to disagree openly in the room rather than agreeing in the meeting and relitigating it in the corridor. Without vulnerability-based trust, that kind of conflict doesn’t happen, because people are still protecting themselves rather than the work.
Without real conflict, you get a third dysfunction: lack of commitment. Not because people are uncommitted in principle, but because a decision reached without genuine debate is a decision no one has truly bought into. Unaired objections don’t disappear; they resurface as passive resistance.
Without real commitment, you get avoidance of accountability — people won’t hold each other to standards they never truly agreed to. And without peer accountability, you get the dysfunction at the top: inattention to results, where individual ego, status, and departmental territory matter more than what the team is actually trying to achieve.
This is why skipping the foundation doesn’t just make the base weak. It makes the top floor unreachable. A team working on its results when trust is absent is treating a symptom that will keep recurring because the cause is two levels down.
The difference in practice
Reliability trust accumulates over time. You work with someone long enough, they deliver enough times, and trust builds. This is how most people think trust works, and it’s not wrong — it’s just insufficient.
Vulnerability-based trust doesn’t work this way. It isn’t a by-product of time. It’s a precondition created by the willingness to be seen. And that willingness has to be actively demonstrated, because the default in most professional settings is the opposite: protect yourself, project confidence, never let them see you uncertain.
The three sentences that mark the presence of vulnerability-based trust in a team are deceptively ordinary. “I was wrong about that.” “I need help with this — I’m out of my depth.” “I don’t know.” What makes them significant isn’t the content; it’s that they’re said in front of people who have professional power over the speaker’s standing — and nothing bad happens. Not just tolerated. Actually fine.
In teams where this trust exists, those sentences make the work better. The person who says “I don’t know” gets the people who do know into the conversation. The person who says “I was wrong” opens the space to course-correct. The person who asks for help gets it without the request being stored as a data point against them.
In teams where it doesn’t exist, people work around those admissions — solving problems privately rather than collectively, holding positions past the point where they believe in them, agreeing in the room and undermining in the corridor. The work is slower and worse, and no one quite knows why, because the meetings are extremely polite.
The leader’s first job
Lencioni is clear on this, and it matters: vulnerability-based trust has to come from the top first. The team reads the leader, and what they read determines what’s permitted. If the leader never says “I was wrong” or “I don’t know,” the message — however unintentionally — is that being seen that way is a risk. If the leader says those things, matter-of-factly, in front of the team, the message is that the room is safe for honesty.
This is not about performing vulnerability. It’s not about confession or manufactured openness. It’s about being willing to be accurate about your own uncertainty and error in a context where your colleagues need that accuracy in order to make good decisions. The leader who admits they don’t know something opens the space for the person who does to say so. The leader who insists they do know — when they don’t — produces a team that answers the question they think the leader wants answered rather than the question being asked.
The team will follow whatever example the leader sets. That’s not a management insight; it’s a direct description of what power does to information flow. The example the leader sets on vulnerability sets the temperature for the whole team.
The question to take away
Think about the last significant failure on your team. How long did it take before the person responsible said so out loud, to the group? Think about the last meeting where a decision was reached that most of the room had reservations about. Were those reservations aired in the meeting, or in the conversations after it? Think about the last time someone said, in the middle of a problem, that they didn’t know how to solve it.
That gap — between what the team actually knows and what it’s willing to say it knows — is where the model points. Not to the top of the stack. To the foundation.
Building the foundation isn’t fast, and it isn’t a team-building exercise. It’s a set of daily decisions about whether to be accurate about uncertainty, made by the person with the most to lose from the answer.
Lencioni’s model is drawn from The Five Dysfunctions of a Team (2002, Jossey-Bass), presented by the author as a leadership fable. The framework is used here as a diagnostic vocabulary, not as a validated causal mechanism.