The Five Dysfunctions of a Team

Why even good teams fail — and what actually fixes them.

By Patrick Lencioni

Why This Book Matters

If you lead a team, manage people, or work alongside others in any capacity, this book will hold a mirror up to dynamics you've probably felt but never been able to name.

Patrick Lencioni's The Five Dysfunctions of a Team is one of the most widely referenced books on team performance for good reason. It's simple. It's honest. And it describes patterns that show up in almost every team I've ever worked with — military, corporate, sporting, or otherwise.

The book is written as a leadership fable — a fictional story about a new CEO called Kathryn Petersen who takes over a struggling tech company called DecisionTech. Her executive team is talented individually but dysfunctional collectively. They avoid hard conversations. They protect their own positions. They leave meetings without genuine commitment.

Through the story, Kathryn draws a pyramid on a whiteboard and walks her team through the five dysfunctions — layer by layer. It's uncomfortable. People resist. Some eventually leave. But the team that emerges is fundamentally different.

The model itself is deceptively simple. Five layers, each building on the one below. If the foundation is broken, everything above it fails.

The Pyramid

From the bottom up:

Absence of Trust

Fear of Conflict

Lack of Commitment

Avoidance of Accountability

Inattention to Results

Lencioni's argument is that these dysfunctions are sequential and compounding. You can't fix accountability if there's no commitment. You can't get commitment without honest conflict. And you can't have honest conflict without trust.

Every layer depends on the one beneath it. Miss the foundation and the whole structure is unstable — no matter how talented the people inside it.

Absence of Trust — The Foundation

This is where everything starts. And this isn't trust in the conventional sense — "I trust you'll do your job." Lencioni calls it vulnerability-based trust. The willingness to admit mistakes. To ask for help. To say "I don't know." To be open about weaknesses without fear of it being used against you.

In the book, Kathryn starts her first offsite by making the team share personal histories — simple things the group wouldn't have known about each other. It takes just 45 minutes, but it begins to shift the dynamic. She follows it with behavioural profiling to help them understand each other's styles and tendencies.

It's a small step. But it matters — because it signals that openness is expected, not optional.

Without vulnerability-based trust, Lencioni says, team members conceal problems, hesitate to ask for support, assume the worst about each other's intentions, and dread being in the same room.

I've experienced this at the sharpest end imaginable.

During a mobilised operation in Afghanistan, our vehicle section was operating in the desert for ten days at a time. It was kinetic. Regular contact with the Taliban. High-pressure, high-consequence work where trust wasn't a nice-to-have — it was survival.

We had an army attachment — a non-commando, not someone who'd been through our selection process or trained to our standards. The trust simply wasn't there. Not because he was a bad person, but because he hadn't been through what we'd been through together. He didn't share the same ethos, the same training, the same instincts.

During very close contact, I needed him watching my back while I engaged targets in the opposite direction. And I had zero confidence that he was doing it effectively.

When trust is absent at that level, it's visceral. You feel it in your body. And it changes how you operate — you compensate, you overcheck, you carry more than you need to because you can't rely on the person beside you.

That experience sits with me whenever I see trust missing in any team, in any environment. The consequences are different, but the dysfunction is the same.

Lencioni is clear: leaders must go first. They must be willing to be vulnerable, to show that it's safe to admit weakness, and to demonstrate that openness is strength, not exposure.

Fear of Conflict — Artificial Harmony

When trust is absent, teams avoid conflict. Meetings become surface-level. People nod along. The real conversations happen afterwards — in corridors, in private messages, in small groups.

Lencioni calls this artificial harmony — and he argues it's far more damaging than the conflict teams are trying to avoid. He flips the common assumption: avoiding conflict isn't professional. It's dangerous.

In the fable, Kathryn has to repeatedly push her team into uncomfortable territory. At one point, an executive called Martin sits typing on his laptop during a session. Kathryn tells him to put it away. He does — and the rest of the team is shocked. That single moment sets a new standard. It signals that disengagement will be challenged, not tolerated.

Lencioni makes an important distinction: productive conflict is passionate, unfiltered debate about ideas. Not personal attacks. Not shouting matches. Teams that can argue well and still leave the room aligned are stronger for it. The teams that can't are stuck in a cycle of politeness that prevents progress.

I've witnessed environments where toxic positivity has completely replaced honest challenge. Everybody's positive. Everything's great. No one calls anyone out. No one questions anything.

And then when things go wrong — and they always do — they go seriously wrong. Because nobody flagged the problems when they were small enough to fix.

A powerful example of this comes from Matthew Syed's book Rebel Ideas. He examines the intelligence failures leading up to 9/11 and makes the case that the agencies involved had technically brilliant people in the room — but they were all the same. Same backgrounds, same education, same institutions, same worldview. They missed the gaps because nobody was different enough to see them.

That's what happens when conflict is suppressed.

In the military, and in how special operations units function, people are expected to call each other out. Regardless of rank. The "check your six" mentality — always watching each other's blind spots — only works if people feel safe enough to speak up.

The same applies in business. The best teams I've worked with argue well. They challenge. They disagree. And then they align and commit.

Lack of Commitment

When people don't feel heard — because conflict was avoided — they don't genuinely commit. They go through the motions. They say the right things. But real buy-in isn't there.

Lencioni's insight here is critical: commitment doesn't require consensus. People don't need to agree with every decision. They need to feel that their voice was heard and that the decision was made with clarity and intent.

He writes that the two biggest causes of lack of commitment are the desire for consensus and the need for certainty. Teams that wait for everyone to agree never move. Teams that wait for perfect information never decide. Both create ambiguity — and ambiguity kills execution.

In the fable, Kathryn pushes the team to make decisions even when not everyone is fully aligned — because she understands that a clear decision, even an imperfect one, is better than no decision at all. People can commit to something they didn't fully agree with, as long as they were heard and the rationale was clear.

From my experience, commitment comes when people believe in the vision, the values, and the behaviours expected of them. When those are clear and genuinely shared, people commit because they understand what they're part of and why it matters.

When they're vague, or when leaders skip the hard conversations to get to a decision faster, commitment is hollow. And hollow commitment creates the conditions for the next dysfunction.

Avoidance of Accountability

Without genuine commitment, people won't hold each other accountable. They avoid the discomfort of calling out poor behaviour, missed standards, or lack of follow-through — in peers, in direct reports, and especially upward.

Lencioni is clear that this isn't about top-down accountability. It's peer-to-peer. The best teams hold each other to high standards directly. They don't rely on the leader to police everyone. They own the standard collectively.

He writes that when accountability is absent, low standards creep in unchallenged. People who aren't pulling their weight are tolerated. Deadlines slip. Quality drops. And resentment builds quietly among the people who are doing the work.

One of my core leadership values is accountability for success. Not accountability as punishment. Accountability as ownership.

This connects directly to the philosophy in Extreme Ownership by Jocko Willink and Leif Babin. Everyone is accountable for everything. Not in a blame sense — in an ownership sense. When something goes wrong, the question isn't "whose fault is it?" It's "how can we do this better?"

At Be Fearsome, when we run team events and leadership challenges, every activity ends with what we call a hot wash-up — a structured debrief taken from elite military units. We use two frameworks depending on the group.

The first is simple and fast: What went well? What can we do better next time?

The second is more detailed. It follows a structured mantra: I-HU-WU-MU.

Intent — spell out the original intent of the task. What were we trying to achieve?

HU — How useful was what we did? How effectively did our actions move us toward the intent?

WU — What was useful? What specifically worked well and contributed toward the intent?

MU — More useful. What would be more useful next time? What would we change, adapt, or do differently?

It's structured. It's honest. It's immediate. And it creates a habit of constructive accountability built into the rhythm of the work — rather than waiting for things to go wrong before anyone says anything.

Inattention to Results — Ego Over Outcome

When accountability is weak, people default to prioritising their own status, ego, or comfort over the team's collective results.

Lencioni uses a brilliant basketball analogy in the book. Kathryn tells the story of her husband, who coaches a school team. One player was far more talented than anyone else. But he was happy when the team lost — as long as he scored the most points. And disappointed when the team won — if he didn't.

Her husband benched him. The player eventually quit. And the team improved.

Kathryn's message to her own executive team is blunt: her job is to build a team, not to shepherd individual careers. If someone prioritises their own results over the team's, they don't belong.

Ben Hunt-Davis captures a similar philosophy in his book Will It Make the Boat Go Faster? — the story of how the GB men's rowing eight went from consistent underachievers to Olympic gold medallists in Sydney 2000. The crew's entire approach was governed by one question: does this decision, this behaviour, this action make the boat go faster?

If the answer was no, it didn't matter how good it felt individually. It didn't serve the team.

That's the standard. Results first. Ego second.

And it only works if the four layers beneath it — trust, conflict, commitment, and accountability — are already in place.

How Our Events & Leadership Development Programmes Expose These Dysfunctions

One of the reasons I believe so strongly in experiential team development is that you can't hide from these five dysfunctions when you're under pressure and working on a real problem together.

Our team events and leadership challenges are deliberately designed to surface these dynamics:

Trust — activities that require reliance on others, including blindfold exercises where you literally cannot see and must trust your team to guide you.

Conflict — time-pressured problems where decisions must be made quickly. Teams that avoid honest debate under pressure make poor decisions. It shows up fast.

Commitment — tasks that require a team to commit to a plan and execute it. Half-hearted commitment reveals itself immediately when the plan meets reality.

Accountability — hot wash-ups after every challenge. Teams are asked to reflect honestly on what happened, what went wrong, and who stepped up. Peer-to-peer accountability is encouraged, not avoided.

Results — every challenge has a measurable outcome. Teams either achieved it or they didn't. There's no hiding behind good intentions.

You can talk about team performance in a classroom for days. Or you can put people into an environment that reveals it in minutes.

Who This Book Is For

Anyone who leads a team. Anyone who is part of a team. Anyone who has ever sat in a meeting and felt that the real conversation was happening somewhere else.

Lencioni himself acknowledges that the root of all five dysfunctions is human nature. We're imperfect. We protect ourselves. We avoid discomfort. We prioritise self-interest. That means dysfunction isn't a failure — it's a default. The work is in overcoming it.

The model is simple — perhaps deceptively so. But simplicity is its strength. It gives leaders a common language for diagnosing what's actually going wrong, rather than treating symptoms.

And it's a reminder that team dysfunction is human, not organisational. It starts with people. And it's fixed by people — starting with the leader who is willing to be vulnerable first.

Final Thought

Lencioni opens the book with a line that has stayed with me:

"Not finance. Not strategy. Not technology. It is teamwork that remains the ultimate competitive advantage, both because it is so powerful and so rare."

If you get all the people in your organisation rowing in the same direction, you can achieve extraordinary things.

But that starts with trust. Real trust. The kind that requires vulnerability, honesty, and the courage to go first.