The Five Dysfunctions of a Team: building trust from the ground up

Most teams don't fall apart because people lack talent. In his book The Five Dysfunctions of a Team, Patrick Lencioni argues that they fall apart because of five dysfunctions of a team that stack on top of each other, like a pyramid. And the whole structure starts to wobble at the very bottom, where trust should be. Get the base right and everything above it gets easier; ignore it and no strategy off-site will save you.

The five dysfunctions of a team, layer by layer

Lencioni's model is a pyramid, read from the bottom up. Each dysfunction feeds the one above it, so you can't skip a level or paper over the one below.

• Absence of trust — people hide their weaknesses and mistakes from each other.
• Fear of conflict — without trust, teams fake harmony instead of debating ideas openly.
• Lack of commitment — with no honest debate, people nod in the room and quietly opt out later.
• Avoidance of accountability — if no one truly committed, no one feels able to call out a peer who is slipping.
• Inattention to results — everyone protects their own status or department instead of the team's shared score.

It starts with vulnerability-based trust

The base isn't the 'I trust you'll do what you promised' kind of trust. Lencioni means vulnerability-based trust: being able to say 'I was wrong,' 'I need help,' or 'I don't know' without it being used against you later. You can't order it into existence. The leader has to go first, out loud, so it becomes safe for everyone else to follow. In practice that means normalizing phrases most workplaces quietly treat as weakness — a team where 'I don't know yet' is a perfectly normal thing to say moves faster, because problems surface while they are still small and cheap to fix.

Concrete moves for each level

• Trust: as the leader, admit a real mistake in the next team meeting before you ask anyone else to.
• Conflict: mine for it — ask the quietest person what they actually think, and keep the fight about ideas, never about people.
• Commitment: end every meeting by restating the decision in one sentence, so people can disagree and still commit.
• Accountability: make goals visible to the whole team, so peers hold peers instead of the boss chasing everyone.
• Results: pick two or three shared numbers as the team scoreboard, and celebrate the collective win over individual heroics.

Notice how tightly the layers connect. Teams that avoid conflict rarely reach real commitment, and teams that never truly commit can't hold each other accountable. That is why chasing the top of the pyramid — results — while the base is cracked almost never works. You end up with dashboards full of green and the real problems still unspoken in the hallway.

Measure your culture free →