Dysfunction 1: Absence of Trust

Lesson 3: Dysfunction 1 — Absence of Trust

"Trust" is one of the most abused words in business. People use it to mean predictability: "I trust she'll get the report done on time." Lencioni means something deeper — vulnerability-based trust: the confidence that you can admit mistakes, reveal weaknesses, and ask for help without fear that it will be used against you. It is the belief that your teammates have your best interests at heart.

Root cause: the unwillingness to be vulnerable. The fear that exposing a weakness will be remembered, weaponized, or judged — so everyone hides, and the team becomes a collection of carefully managed impressions.

What it looks like in practice

  • People hide their mistakes and weaknesses instead of surfacing them early.
  • Nobody asks for help — asking feels like admitting incompetence.
  • Feedback is withheld; people talk about each other, not to each other.
  • Meetings are performances. People say what protects their image, not what they think.
  • Enormous energy is spent on politics and impression management instead of the work.
  • Collaboration is transactional: "what's in it for me" governs every exchange.

Notice the cost. It isn't just that people feel bad — the team loses information. Problems get discovered late, bad decisions get rubber-stamped, and the organization's collective intelligence is never actually pooled.

How it relates to the other dysfunctions

Absence of trust is the foundation of the whole pyramid — the reason the other four exist. Without the safety of vulnerability:

  • Conflict feels personal, so the team avoids it (dysfunction 2).
  • Decisions never get truly debated, so nobody buys in (dysfunction 3).
  • Nobody has the standing to call anyone out (dysfunction 4).
  • Egos fill the vacuum (dysfunction 5).

This is why Lencioni is emphatic: you cannot fix anything above trust until trust exists. A team-building budget spent on goal-setting while people still can't admit mistakes is spent on a house with no foundation.

How to combat it

Lencioni's tools, roughly in order of risk — start small and low-stakes, build up:

  1. Personal histories. In a safe setting, each person shares where they grew up, what their childhood was like, formative experiences. This is the exercise Kathryn runs at DecisionTech's offsite. Low risk, high payoff: teammates stop being roles and become people. Humans find it hard to mistreat someone whose childhood they know.
  2. Personality profiling. Myers-Briggs, DISC, or similar instruments. Profiling depersonalizes differences: instead of "she's annoying," it becomes "she's an introvert who processes internally." That reframe makes behavior discussable without blame.
  3. 360-degree feedback. Structured, anonymous, and safe: a formal channel for giving and receiving feedback that bypasses the awkwardness of doing it cold. It teaches the muscle of hearing criticism without collapsing.
  4. Experiential team exercises. Challenges designed so the team must rely on each other to succeed. Shared struggle is a fast trust-builder — but only if it's real, not a ropes-course metaphor.
  5. The leader goes first. The most important tool. The leader must be the most vulnerable person in the room — admitting mistakes, asking for help, acknowledging limitations — and must do it repeatedly, because one retreat won't do it. Trust builds in months, not meetings.
Fable tie-in: Kathryn tells the team about her own failures — including being fired — before asking anything of them. At the offsite, personal histories crack the team open. And when the sales role opens up, the team's new trust makes an honest, uncomfortable conversation possible: they tell Carlos he isn't the best fit, and he doesn't take it as an attack.

Further Reading

🧠 Knowledge Check

1. What kind of trust does Lencioni mean when he talks about team trust?

2. Why is absence of trust the most important dysfunction to fix first?

3. What is the single most important trust-building tool, according to Lencioni?