Building trust in a team: Lencioni’s five dysfunctions and the trust equation

Teams without trust are easy to spot. Meetings are polite and pointless, the real discussion happens in private messages afterwards, and decisions get quietly reopened. People spend energy protecting themselves instead of doing the work.

Two frameworks come up again and again when managers try to fix this. Patrick Lencioni’s five dysfunctions of a team describe what goes wrong when trust is missing. The trust equation from The Trusted Advisor breaks trust in a person down into parts you can work on. This guide explains both, what the evidence says about them and how to use them in practice.

Lencioni’s five dysfunctions

The Five Dysfunctions of a Team is a 2002 business book written mostly as a fable about a new chief executive and her struggling leadership team. Lencioni’s firm, The Table Group, describes the five dysfunctions like this:

1. Absence of trust: people fear being vulnerable with each other.
2. Fear of conflict: the wish for artificial harmony blocks productive debate.
3. Lack of commitment: without real debate, people do not fully buy into decisions.
4. Avoidance of accountability: people avoid the discomfort of calling out each other’s behaviour and performance.
5. Inattention to results: personal goals and status take priority over collective success.

Lencioni presents them in sequence, with each one feeding the next. If people cannot admit mistakes, they will not argue openly. If they do not argue, they nod along without committing. If they never committed, they will not hold each other to the decision, and attention drifts to individual targets.

What the evidence says about Lencioni

The model is popular because it is simple and matches what many people have lived through. It is also not based on research. Organisational psychologists Gordon Curphy and Robert Hogan praised several of its insights, including how much time teams waste avoiding conflict, but pointed out that the book is fiction and its recommendations lack empirical support. In particular, they doubted that personal disclosure exercises build trust, and argued that teams build trust and cohesion mainly by doing real work together.

That fits Katzenbach and Smith’s classic Harvard Business Review article “The Discipline of Teams”, which describes the best teams as spending time shaping a purpose they own, turning it into specific performance goals and holding themselves mutually accountable. Use Lencioni as a diagnostic map, then build trust through shared work and kept promises rather than icebreakers.

The trust equation

David Maister, Charles Green and Robert Galford introduced the trust equation in The Trusted Advisor in 2000. Trusted Advisor Associates states it as:

Trust = (Credibility + Reliability + Intimacy) / Self-orientation

The structure carries the main lesson. Self-orientation sits alone below the line, so a manager who is credible, reliable and approachable can still lose trust by appearing to put their own interests, image or career first. The equation started as a way to think about client advisers. It works as a thinking tool for managers too, but it is a model, not a measured formula.

How to build trust as a manager

1. Go first on vulnerability. Admit a mistake or a gap in your knowledge in a team meeting. People take their cue from the most senior person in the room.
2. Keep small promises. Reliability is built from many small commitments kept: replying when you said you would, following up on the action you took in a meeting.
3. Say what you know and what you do not. Credibility suffers more from false confidence than from honest uncertainty.
4. Make debate normal. Ask “What would make this plan fail?” and thank the person who answers. Fear of conflict is the second dysfunction on Lencioni’s list, and a team that never disagrees in the room usually disagrees outside it.
5. Close decisions clearly. End discussions by stating the decision, who owns what and by when, so commitment does not stay vague.
6. Lower your self-orientation. Give credit away, ask more questions than you answer, and avoid using team wins for your own visibility.
7. Work on real problems together. A shared, meaningful goal does more than a team-building day.

A worked example

An example (illustration only). Ravi takes over a product team of six after a reorganisation. In the first month he notices that meetings end in agreement, yet the same decisions come back a week later. Two engineers complain about each other privately but never in the room.

Using Lencioni as a map, he sees missing trust and avoided conflict. Using the trust equation on himself, he realises his reliability is low: he has cancelled three one-to-ones. He takes four steps. He stops cancelling meetings. He opens the next retrospective by describing a call he got wrong in his first week. He adds a standing agenda item called “risks and objections”. And he ends each decision with a written summary of owners and dates. After two months, the reopened decisions have mostly stopped and the two engineers raise their disagreement in a planning session, where it gets resolved.

Common mistakes

• Running trust exercises instead of changing behaviour. A personality workshop does little if the manager still breaks promises.
• Confusing harmony with trust. A quiet team may simply be an unsafe one.
• Demanding vulnerability without giving it. Asking others to open up while you stay guarded feels like a trap.
• Treating trust as a one-off project. It builds slowly through repeated experience and can drop quickly after one broken promise.

When to use each tool

Use Lencioni’s model when a team is stuck and you need a shared language for why: it helps a group name the pattern without blaming individuals. Use the trust equation for self-review, or to prepare for a relationship that matters, such as a new manager, a key client or a peer you need to win over. Neither replaces the work of keeping your word, and neither is a substitute for a team that has something worth achieving together.