The Five Dysfunctions of a Team

Teams break down in a predictable order

When a team is not working, the visible problem is almost never the actual problem. Patrick Lencioni's contribution in The Five Dysfunctions of a Team was to stack the five failures as a pyramid, because each one rests on the one beneath it. That ordering is the useful part, and it is what makes the model a diagnostic rather than a list of complaints.

The practical consequence is that you fix a team from the bottom up. A results problem is usually solved several layers below results.

Absence of trust

At the base, people will not be vulnerable with each other, so they hide mistakes, weaknesses and the things they do not know.

The trust that matters here is narrower than the everyday sense of the word. It is not confidence that a colleague will deliver what they promised, which is reliability and is a different thing. It is the willingness to say "I was wrong" or "I need help" in front of people whose opinion of you matters professionally. The leader has to go first, because nobody below them will risk it otherwise.

Fear of conflict

Without that trust, teams avoid honest disagreement and settle for a surface politeness that feels like harmony and functions as avoidance. The debates that should happen in the room happen afterwards in ones and twos, or not at all.

Healthy teams argue, and they argue about ideas rather than people. If your meetings are consistently comfortable, the disagreement has not gone away, it has just relocated somewhere you cannot see it.

Lack of commitment

Without open conflict, people do not actually buy in, even when they nod. Agreement given in a meeting where dissent was never available is worth very little on Monday.

Commitment comes from having genuinely weighed in. People will get behind a decision they argued against, provided they were able to argue against it, which is why the fix for a commitment problem is usually more conflict rather than more communication.

Avoidance of accountability

Without commitment to a plan people can name, nobody will challenge a peer whose work or behavior is hurting the team. The hesitation is reasonable, because holding someone to a standard nobody clearly agreed to is an unpleasant conversation with no ground to stand on.

This layer is where teams most often ask the leader to do the work for them, escalating rather than addressing it peer to peer.

Inattention to results

At the top, people attend to their own status, their own function, or their own department ahead of what the team is collectively supposed to deliver. This is the layer everyone notices and the one least likely to be fixed where it appears.

The base layer, built deliberately

At a company I led, the executive team built a team charter, specifically to establish that people could say what was actually on their mind and challenge each other, including me.

What came of it was uncomfortable in the moment and exactly the point. In a planning meeting, one of the executives who reported to me told me directly that I was not close enough to the technical detail of a project to defend it in budget meetings. He was right. I had been carrying it on general confidence rather than on the specifics, and I would have been found out in the room where it counted.

We agreed he would come to the budget meeting as the technical resource. The project was approved.

That sequence is the pyramid working. The charter made the vulnerability survivable, which made the conflict possible, which produced a better decision than my own judgement would have. Without the base layer he would have watched me walk into that meeting underprepared, and he would have been entirely rational to keep quiet.

One thing to try this week

Take your own team and locate the cracked layer, working from the bottom rather than from the symptom. Ask whether anyone on the team said "I was wrong" or "I do not know" in the last month, and whether a real disagreement was voiced in the last meeting.

Whichever layer is the lowest one that fails is where the work goes, even if the pain you actually feel is at the top. Work that one layer rather than the whole pyramid, and give it longer than feels necessary before checking whether the layer above has improved on its own.