The Five Dysfunctions of a Team: A Tribute to a Culture-Building Classic

Some books explain why teams fail. The Five Dysfunctions of a Team made it impossible to unsee. Published in 2002 by Patrick Lencioni and told as a business fable, it took every messy reason teams underperform and stacked them into one clean pyramid, five dysfunctions, each resting on the one beneath it. I am a sucker for a framework this clean, and few have ever earned their keep like this one, which is part of why it has sold more than three million copies. Do yourself a favor and read it.

More than 3 million copies sold, translated into over 30 languages. Two decades on, it is still the book teams reach for when they want to understand why they are stuck, used by thousands of organizations and assessed across thousands of real teams through Lencioni’s firm. It did the rarest thing a management book can do: it gave people a shared language for a problem they could feel but could not name.

Watch it work. A meeting is sailing along, everyone nodding, nobody pushing back, and instead of relief you feel a flicker of worry, because a phrase has surfaced to name it: this is artificial harmony, not agreement. Then someone finally says the uncomfortable thing, the debate gets real, and another phrase reframes what would have felt like a fight: this is the healthy conflict we have been avoiding. That is the mechanism in miniature. A few shared words, surfacing the right thought at the moment it is needed, turning a vague unease into something the team can name and fix.

That small moment is the whole reason I wanted to write about this book. I spend my days helping leaders build culture, and I have come to believe culture is built exactly like that, not from values on a wall but from shared commitments: simple language a team holds in common and acts on, again and again, until it becomes who they are. That is what I call Culture by Commitment, and it is the lens I am reading this book through. Seen that way, the pyramid is not just a diagnosis. It is a shared vocabulary a team can use to catch itself and choose better, which is exactly why it has stuck for twenty years. It is also worth knowing how to hold it, because a model this clean is easy to misuse.

Why It Works: Language Drives Behavior

Here is the deeper reason this book lands, beyond the clever fable. It works because of how culture actually gets built, through a simple chain. Language shapes thinking, and thinking shapes behavior. And behavior, repeated across a team day after day, becomes culture.

How simple language builds culture: shared language shapes thinking, thinking drives behavior, and behavior repeated over time becomes culture, illustrated with the vulnerability-based trust at the base of the Five Dysfunctions pyramid and the honest, trusting team culture it creates.

Most leaders try to fix a struggling team at the wrong end of that chain. They reshuffle the org chart, or they put “teamwork” on a values poster, and the same quiet dysfunction continues underneath. But values are an output of culture, not an input to it, and a reorg does not teach a team to trust each other. The leverage is at the front of the chain, in the language people use to name what is actually happening between them.

That is exactly what Lencioni supplied. Most of the commitment systems I admire fire as cues in the moment you act. This one works a little differently, as a shared vocabulary for naming what is going wrong. “Artificial harmony,” “vulnerability-based trust,” “disagree and commit” are not abstractions you study once, they are words that flash the instant a team feels the thing they describe. And naming a dysfunction is the first step to choosing against it. The book is a master class in building culture through commitments, even though it never uses that phrase.

The System of Commitments, and Why Shared Language Is So Powerful

Here is what makes these words powerful, and it is not that they are clever. It is that they are shared. A good idea about teamwork in one leader’s head changes one leader. The same idea turned into language the whole team holds changes the team, because shared language does three things no private insight can. It lets people coordinate without re-negotiating the basics, because everyone already means the same thing by “healthy conflict.” It lets people hold each other to a standard, because a shared word is one anyone can point to. And it compresses culture into something teachable, so a new hire learns how this team works in a sentence instead of a year.

So how did Lencioni hand teams that language? He stacked it into a pyramid. Five dysfunctions, each one built on the failure beneath it, which means you have to build from the bottom up. Flip each into the behavior that cures it, and the pyramid becomes five commitments a team makes to each other.

Trust, the foundation. The commitment to be vulnerable with each other, to say “I was wrong,” “I do not know,” or “I need help” without fear it will be used against you. Everything above rests on this.

Healthy Conflict. The commitment to debate ideas openly instead of preserving a polite, artificial harmony. The fight is about ideas, never people, and trust is what makes it safe.

Commitment. The commitment to buy in for real and then disagree and commit, instead of nodding in the room and undermining the decision later.

Accountability. The commitment to call each other out, peer to peer, on anything hurting the team, rather than leaving every hard conversation to the boss.

Results. The commitment to put the team’s collective results ahead of personal status, ego, and turf. The whole point of the other four.

Notice the move. Lencioni’s real gift was not the pyramid, plenty of people have drawn teamwork as a diagram. It was the language he hung on it, words vivid enough that a team can say them out loud and catch itself in the act. That is the leap from a smart diagnosis to a living culture: language a whole team holds in common and uses on itself, at the moment it is needed. The diagram explains. The words change behavior.

Why Culture Is the Cumulative Effect

Notice what those five have in common. None is a value statement. Each is a behavior a team chooses, in a specific moment, over and over. On its own, any single choice changes a single meeting. That is not culture yet.

Culture is what happens when you repeat them. Take trust, the willingness to say “I was wrong” out loud. Said once, it is a brave moment. But a whole team that does it every week for a year becomes a team where the truth is simply safe, where people ask for help early and problems surface while they are still small. The commitment is the input. The culture is the cumulative effect.

Think about your own team. Which of the five is your foundation crack, and what would change if the whole team had a word for it?

This is the part most people miss, about this book and about culture in general. A cohesive team is not declared at an offsite. It is accumulated. It is the residue of the same five commitments lived over and over until trust, honest debate, real buy-in, and mutual accountability are simply how this team operates. Change the commitments and you change the culture, one named moment at a time, compounding.

And here is the bigger idea the book points straight at. Lencioni gave you the diagnosis, the five things a healthy team needs. The work he leaves to you is turning those five into the concrete shared commitments your team actually lives, in its meetings, its feedback, its decisions, its handoffs. Every activity a team does has its own version of trust, conflict, commitment, and accountability. That compounding, across a whole organization, is the whole of Culture by Commitment, and The Five Dysfunctions of a Team is one of the cleanest proofs that the engine works.

The Heart of It: Trust Is the Whole Foundation

The Core Idea

The trust that builds a team is not believing others will do their jobs. It is the safety to say I was wrong, I do not know, and I need help.

This is the most powerful idea in the book and the most misread. People hear “trust” and think reliability, the confidence that a colleague will deliver. That is not what holds a team together. What does is vulnerability-based trust: the safety to admit a mistake, ask for help, or say you are lost, without it being stored away and used against you later. It sits at the base of the pyramid for a reason. Without it, no one risks the honest debate, so no one truly commits, so no one holds anyone accountable, so the results never come. Every layer above is downstream of whether people feel safe being human with each other.

That is also why trust is the hardest one and the one you cannot fake. It is not built with an icebreaker. It is built when a leader goes first, admits their own mistake in the open, and nothing bad happens, and then does it again, until the team believes it is real. Get that right and the rest of the pyramid has a foundation to stand on.

Watch Out for These Things

A model this clean is strong medicine, and strong medicine has side effects. The most common one: someone reads the book, decides the team needs more conflict, and starts steamrolling meetings, waving Lencioni as a permit to be combative. But the book never asked for combat. It asked for honest debate about ideas, with enough trust underneath to keep it safe. That is the inversion to guard against, and there are a few more. Four cautions, so you get the benefit without the damage.

Hold it as a map, not a proven science. Lencioni wrote a fable, not a research study, and some of its trust-building exercises have real critics. The pyramid is a brilliant way to see your team. It is not a law of nature, so use it to start the conversation, not to end it.

Do not weaponize “healthy conflict.” As in that example, “we need more conflict” becomes cover for being difficult. The conflict that helps is about ideas, and it only works on a foundation of trust. Without the trust beneath it, conflict is just conflict.

Do not force vulnerability. You cannot mandate trust with a personal-disclosure exercise at an offsite. Vulnerability-based trust is built by leaders going first, for real, and by doing hard work together over time, not by a game.

Do not let “fix trust first” become an excuse to wait. The pyramid is a sequence, but real teams build all five in the actual work, not in tidy order. Attach each behavior to the real moments it shows up in, which is what activity commitments do.

Hold it right and it is simple: build real trust by going first, fight about ideas and not people, commit out loud, hold each other to it, and keep the team’s results above your own.

From a Great Book to a Culture You Can Build

So if you came here for The Five Dysfunctions of a Team, here is what to do with it. The mechanism that makes the book work is not unique to team cohesion. It is how every part of a culture gets built.

Read the book, take the spirit of it, and then do the part the book leaves to you: turn its five into a handful of commitments your team actually shares and lives. And if the idea grabs you, that culture is the cumulative effect of the right commitments lived day after day, that is the whole premise of Culture by Commitment. Start with the core commitments a team shares, and the activity commitments that make them real, one activity at a time, until the cumulative effect is a culture you chose on purpose.

Work with Joe

Want to turn great ideas like these into a culture your team lives?

Books like The Five Dysfunctions of a Team prove the mechanism: simple shared language, lived over time, becomes culture. The work is turning that into the specific commitments your team actually runs on, across the activities that matter most, meetings, feedback, decisions, accountability, and rolling them out so they stick.

If you want to build a culture through commitments that hold, let’s build it.

Work With Joe

Joe Newsum: McKinsey alum, former CEO, COO, CFO, and CMO, and creator of Culture by Commitment, working directly with Fortune 500 CEOs and executive committees to build cultures that hold.


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. Patrick Lencioni arranges them as a pyramid, each dysfunction resting on the one below it, so the problems compound from the bottom up.

What is the foundation of the pyramid?

The absence of trust, and specifically a lack of vulnerability-based trust, the willingness to say I was wrong, I do not know, or I need help without fear it will be used against you. Everything above it on the pyramid depends on it.

What does Lencioni mean by fear of conflict?

He means avoiding honest, productive debate about ideas in order to preserve a polite, artificial harmony. The conflict he wants more of is about ideas and never personal, and it is only possible once there is enough trust to make disagreement safe.

Is The Five Dysfunctions of a Team based on research?

No. It is a leadership fable, a story rather than an empirical study, and critics note that some of its trust-building exercises lack hard support. That does not make it wrong, but it is best held as a useful map for seeing your team, not as a proven law.

How do you fix the five dysfunctions?

Build vulnerability-based trust with leaders going first, make space for honest debate about ideas, get real buy-in and then disagree and commit, hold each other accountable peer to peer, and keep the team’s collective results ahead of personal status and ego.

How does it relate to building culture?

The book gives a team shared language for its own health. The five behaviors become commitments a team makes to each other and, repeated over time, compound into culture. Culture by Commitment turns that diagnosis into the specific commitments a team lives across every activity it does.