Read Time:

12 August 2026

Team Development

Leadership and Management Development

Summary:

Patrick Lencioni's five dysfunctions of a team are the absence of trust, a fear of conflict, a lack of commitment, the avoidance of accountability and inattention to results. He set them out in his 2002 book 'The Five Dysfunctions of a Team: A Leadership Fable', which The Table Group reports has since sold more than three million copies worldwide.

They stack in a useful, and memorable way. Each one sits on top and is reliant on the one below it, which is why teams that try to fix the top of the pile without touching the bottom tend to get nowhere and set themselves up for failure.

We have spent a lot of years in rooms with teams who were convinced their problem was accountability, or not meeting results. It almost never was, it was something much deeper that this model helps teams explore in a productive and safe way.

Why it's timeless

Plenty of team models have come and gone since 2002. This one stuck, and we think there are two reasons for that.

The first is the format. Lencioni wrote it as a fable rather than a textbook, following a fictional Silicon Valley company and a new chief executive walking into a leadership team that quietly loathes each other. People remember stories about the snidey backstabbing leader who becomes a snake in the grass. Nobody remembers a framework or diagram from a slide deck they saw in 2019.

The second is that it is uncomfortably recognisable. Most people read the section on fear of conflict and think of a specific meeting they sat in last week.

Whether the UK needs it is not really in question. Gallup's most recent data puts employee engagement in the United Kingdom at 10%, against a European average of 12% and a global average of 20%. That figure has been falling steadily since 2012, when it stood at 17%. In the same dataset, 83% of UK employees are classed as not engaged. Meanwhile 46% told Gallup they experienced a lot of stress the previous day, up five points and well above the European figure of 39%.

Those numbers describe a lot of teams that are technically functioning and quietly miserable.

The model is a pyramid, and the order matters.

The five dysfunctions are usually drawn as a pyramid, with absence of trust at the base and inattention to results at the top. The order is the whole point.

You cannot get honest conflict out of a team that does not trust each other. Without honest conflict, people will not genuinely commit, because they never really said what they thought. Without commitment, nobody will hold anyone to account, because it was never clear what was agreed. Without accountability, results drift, because there is nothing keeping anyone honest.

Start at the top and you get a team that talks about KPIs while the actual problem sits in the basement, fuelling a fire that smoulders away.

1. Absence of trust

Lencioni is talking about a specific kind of trust here, and it is worth being precise, because this is where most people misread the model.

He does not mean predictive trust, the sort where you know a colleague will deliver the report on Thursday because they always do. He means vulnerability-based trust. Being willing to say "I got that wrong", "I do not understand this" or "I need help" without calculating what it will cost you.

What it looks like in practice

People come to meetings with their positions already worked out. Mistakes get quietly absorbed rather than raised. There is a lot of careful language. You will hear "just to be clear, I did flag this in April" more often than you should.

What actually shifts it

Trust is built in small, repeated, fairly boring moments, not in a single away day with a raft-building exercise. Coffee before the meeting starts. Someone senior saying "I have no idea, what do you think" and meaning it. Consistency over time, so people learn you are the same person on a bad Tuesday as you are on a good Friday.

The single fastest accelerator we have seen is giving a team a shared language for how they differ. When people can say "I process this internally before I speak, so give me a minute" and everyone understands what that means, a whole layer of misreading each other disappears. That is a large part of why we use Insights Discovery in teamwork. It is not the model itself that does the work, it is that the model gives people permission to explain themselves and how they feel in this team
 

2. Fear of conflict

Conflict has a public relations problem. Most of us were raised to treat it as failure, so we have built workplaces where the absence of visible disagreement gets read as health.

It usually isn't health. It is politeness doing an impression of alignment.

What it looks like in practice

Meetings that finish early and achieve nothing. Everyone nodding. The real conversation happening afterwards in a group chat that does not include the person it concerns. Decisions that get quietly unpicked over the following fortnight because nobody actually agreed to them in the room.

What actually shifts it

Name it out loud. Tell the team you would rather have the argument in the meeting than in the corridor, then prove you mean it by responding well the first time someone takes you up on it. That first time is the whole test. Respond badly once, and you will not get another opportunity.

It helps to separate the two kinds of conflict. Task conflict, disagreeing about the work, makes decisions better. Relationship conflict, disagreeing about each other, makes everything worse. Teams that avoid all conflict are usually trying to avoid the second kind and losing the first as collateral damage. You can read more about How To Have Challenging Conversations here

3. Lack of commitment

Commitment is not enthusiasm. A team can commit to a decision that half of them think is second best, as long as they were genuinely heard on the way to it.

Lencioni's point is that people do not need to get their own way, they need to know their view was properly considered and that they felt heard. Buy-in follows being listened to, not being agreed with, like a nodding dog

What it looks like in practice

Decisions get revisited endlessly. Nobody can quite say what was agreed. Actions leave the room without owners or dates. Six weeks later two people are working to different versions of the same plan and neither of them is wrong.

What actually shifts it

End every meeting by stating the decision, the owner and the date, out loud, and watching faces while you do it. Ten seconds of visible discomfort at that moment saves six weeks of drift. If you spot someone go quiet, ask them there and then.

Ambiguity is more dangerous than disagreement. Disagreement you can work with, and what's even worse is silence, which tends to go unnoticed.

4. Avoidance of accountability

This is peer accountability, not management accountability, and that distinction is what makes it hard.

Most teams can cope with a manager raising a performance issue. Far fewer are willing to have a colleague say "you said you would do that and you did not". The reluctance is almost always about not wanting to damage a relationship. The irony is that letting it slide damages the relationship anyway, just more slowly and with more resentment.

What it looks like in practice

Standards drift, and the drift is invisible until something breaks. The same two or three people quietly absorb the slack. Everyone knows who is not pulling their weight and nobody says it. Eventually the reliable ones start to disengage, because carrying other people is exhausting and nobody has noticed.

What actually shifts it

Make commitments public within the team, so accountability has something concrete to attach to. Build in a regular, low-drama checkpoint, so raising a slipped commitment becomes routine rather than an escalation. Above all, the leader has to go first and be held to account visibly, because a team will not do this if it only ever flows downwards.
 

5. Inattention to results

The top of the pyramid, and the one that gets all the management attention despite being a symptom rather than a cause.

When the team is not functioning underneath, people retreat to what they can control. Their own objectives. Their own department's numbers. Their own reputation. Not out of malice, but because collective results feel unreachable when the team beneath them is not working.

What it looks like in practice

Departments hitting targets while the organisation misses them. People defending their function in meetings rather than solving the problem in front of them. A quiet pride in individual performance that nobody quite wants to examine.

What actually shifts it

Define what the team wins on together, and make it small enough to be real. Then talk about it more often than feels necessary. Celebrate the collective outcome more loudly than the individual one, because whatever a leader celebrates is the actual strategy, regardless of what the strategy document says.

Taking the "dys" out of dysfunction.

Here is where we part company slightly with how the model usually gets taught.

The five dysfunctions are typically presented as a diagnosis, which is useful, but it leaves teams staring at a list of everything wrong with them. Flip each one over and you get a far more workable set of goals. Trust. Healthy conflict. Clear commitment. Mutual accountability. Collective results.

Same model, better conversation. In our experience teams move faster when they are building towards something than when they are defending against a list of accusations, even accurate ones.

The other thing worth saying plainly is that this is not a one-off exercise. Trust decays. People join and leave. A team that did the work two years ago is not the same team now, and a reorganisation or a difficult quarter will strip a layer off the bottom of that pyramid without anyone noticing.

Frequently asked questions

What are the five dysfunctions of a team?

Absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results. They are cumulative, so each one is caused in part by the one below it.

Who wrote The Five Dysfunctions of a Team?

Patrick Lencioni, an American author and founder of The Table Group, published it in 2002. It is written as a business fable rather than a conventional management book.

Which dysfunction should we tackle first?

Absence of trust, almost always. It sits at the base of the pyramid and the other four are difficult to shift while it is unresolved. If a team tells us their problem is accountability, our first question is usually about trust.

Is the model still relevant?

The mechanics hold up well, though it predates most of what we now know about psychological safety and it was written for co-located teams. It works best combined with more recent thinking rather than used on its own.

What is the difference between this and psychological safety?

They overlap heavily at the base of the pyramid. Amy Edmondson's psychological safety research gives you the evidence base and the mechanism and becomes an environment where trust can thrive. Lencioni gives you a memorable structure and a shared language that teams can actually use to build trust. Google's Project Aristotle, which studied 180 of its own teams across 250 attributes, found psychological safety to be the strongest single predictor of team effectiveness.

How long does it take to fix a dysfunctional team?

Honestly, longer than most people want to hear. You can shift the conversation in a day. You can shift the behaviour in a quarter, if the leader is genuinely committed and goes first. Anyone promising faster than that is selling something

Where we come in.

Most teams do not need the theory explained to them. They need a safe room, someone independent in it, and a shared language that they will still be using six months later.

That is the work we do. If any of the above sounded uncomfortably familiar, let's talk.

Let's talk team.

Complete the form below and we'll be in touch within one business day or call us on 03456 185796

Sources

1. Gallup, *State of the Global Workplace: United Kingdom Country-Level Data*, from the 2026 report published April 2026, data collected January to December 2025. UK engagement 10%, not engaged 83%, actively disengaged 7%. Europe 12%, global 20%. UK daily stress 46%.
   https://www.gallup.com/workplace/707546/state-global-workplace-united-kingdom-country-level-data.aspx

2. Google re:Work, *Understand team effectiveness*, Project Aristotle. 180 teams, 250 attributes, psychological safety identified as the strongest predictor.
  https://rework.withgoogle.com/intl/en/guides/understand-team-effectiveness

3. The Table Group, *The Five Dysfunctions of a Team*. Publication year 2002 and the three million copies figure are the publisher's own claim.
  https://www.tablegroup.com/product/dysfunctions/
 

James Hampton (He/Him)

James Hampton (He/Him)

Director

Our areas of specialism.


Coaching.

  • Self-awareness

  • Resilience

  • Personal Development

  • Change

  • Decision making

  • Growth mindset

Team development.

  • Hybrid team working

  • Communication

  • Meetings

  • Feedback

  • Collaboration

  • Trust

Leadership development.

  • Leadership styles

  • Psychological safety

  • Leading change

  • Mission, vision, values

  • Culture

  • Mentoring