Lencioni's five dysfunctions – trust makes or breaks the team

Published 2026-07-02 · The research behind Project-simulator

Every meeting is polite. Nobody pushes back on decisions. Yet nothing happens between meetings, deadlines slip, and no one seems to genuinely care about the outcome. Sound like a team you know? What looks like harmony can be the first sign that something is fundamentally wrong.

In his 2002 book The Five Dysfunctions of a Team, the American leadership consultant Patrick Lencioni described a model for why teams fail. It is written as a fable – the story of a leadership team in crisis – and is based on Lencioni's consulting experience rather than controlled studies. But the model has become hugely influential because so many people recognize the pattern.

What does the research say?

Lencioni's model is a five-layer pyramid, where each layer makes the next one possible. At the base sits absence of trust: members don't dare to show vulnerability, admit mistakes, or ask for help. Without that trust, the next dysfunction emerges – fear of conflict. No one dares to disagree openly, so discussions become watered down and the real disagreements are settled in the corridor afterwards.

When opinions never clash, lack of commitment follows: people don't get behind decisions they were never allowed to challenge – they nod in the meeting and do as they please afterwards. That leads to avoidance of accountability – it feels unfair to hold a colleague accountable for something they never really said yes to. And at the top: inattention to results, where everyone prioritizes their own area, their career, or their department over the team's shared goals.

The model's most important point: the symptoms show up at the top, but the cause sits at the bottom. A team that misses its goals rarely has a goals problem – it usually has a trust problem. By trust, Lencioni doesn't mean confidence in each other's competence, but vulnerability-based trust: the safety to say "I was wrong", "I can't do this alone", or "I need help".

What does this mean for you as a project manager?

Read silence correctly. If nobody objects to your plan in the meeting, don't take it as agreement – test it: "What's the biggest risk with this approach? I want to hear at least one objection before we move on." Actively inviting conflict about the issues is the opposite of a bad atmosphere; it's what makes decisions stick.

Go first with vulnerability. Trust isn't built through team-building exercises but by someone taking the first step. When you as project manager say "that estimate was my mistake", you lower the cost for everyone else to be honest. If you wait for the team to open up first, you'll wait forever.

And when a delivery slips: hold people accountable to the commitment, not the person. "We said Friday, it's now Wednesday – what happened and what do we do?" is an act of trust, not an attack. Teams where no one dares to ask that question aren't protecting each other – they're abandoning the results together.

How to practice this

The conversations that build trust and demand accountability are exactly the conversations most people put off. In Project-simulator you can practice them in advance – against an AI counterpart that gets defensive, goes quiet, or deflects – and get feedback anchored in what you actually said. Try it free for a week at project-simulator.com.