Build vulnerability-based trust
Teams that can’t admit weakness, mistakes, or ignorance to each other cannot genuinely collaborate.
Why it works
Lencioni distinguishes vulnerability-based trust — the comfort to show your real limitations — from predictability-based trust (knowing someone will do what they say). Teams can be predictable and still be guarded. Vulnerability-based trust accelerates because it shortcuts the slow process of inferring character from behavior: when someone says "I was wrong" or "I don’t know," others update their model of them rapidly and positively. That update makes self-disclosure reciprocal, which is the foundation of psychological safety.
How to do it
- Start with structured personal sharing in low-stakes settings — brief, genuine self-disclosure from leaders before anyone else.
- Leaders must go first and go real: performative vulnerability ("I’m not perfect either!") is detectable and counterproductive.
- Use personal history exercises: ask each person to share something about their background that the others wouldn’t know and that affected how they work.
- Make admitting mistakes and ignorance the norm in meetings — model it, reward it, never weaponize it.
Evidence
Vulnerability-based trust aligns with Edmondson’s psychological safety research, which shows that teams where interpersonal risk-taking is safe show higher learning and performance. Lencioni’s specific framing is practitioner-derived; the underlying construct is well studied. (observational)
Psychological safety research is observational (correlational); Lencioni’s "vulnerability-based trust" is his prescriptive label for a related but distinct construct. The causal direction is supported by field research but not established by controlled experiments.
Sources
- Edmondson (1999), Psychological safety and learning behavior in work teams, Administrative Science Quarterly
Common mistake
Asking team members to be vulnerable before the leader has modeled it — people take their cue from the top; asking for openness without demonstrating it first produces a performance of vulnerability, not the real thing.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Five Dysfunctions of a Team, Made Practical
- Engage in productive ideological conflict
Teams that avoid conflict don’t avoid disagreement — they bury it, where it grows into resentment and bad decisions.
- Get genuine commitment, not false consensus
Teams that avoid conflict often confuse silence for agreement — false consensus is catastrophic for execution.
- Create a culture of peer-to-peer accountability
Teams that only hold each other accountable through the manager haven’t built real accountability at all.
- Align around collective results, not individual status
Teams fail when members prioritize their own visibility or department’s success over the shared goal.
- Use regular team health checks to surface dysfunction early
Teams that check in on how they’re working together catch dysfunction before it compounds.
Related concepts
- Psychological Safety, Made Practical
The team climate that lets people speak up — and how leaders create it
- Radical Candor, Made Practical
The 2x2, the mechanisms behind real candor, and an honest read on the evidence
- Crucial Conversations, Made Practical
Safety, mutual purpose, STATE, and the stories that drive us