The Five Dysfunctions of a Team
A Leadership Fable
By Patrick M. Lencioni
Category: Corporate Culture | Reading Duration: 34 min | Rating: 4.5/5 (1065 ratings)
About the Book
The Five Dysfunctions of a Team (2002) presents the notion that teams are inherently dysfunctional, so deliberate steps must be taken to facilitate great teamwork. A knowledgeable team leader can do a great deal to make his or her team effective, and the book outlines practical tools for achieving this.
Who Should Read This?
- Anyone interested in the prerequisites of great teamwork
- Anyone interested in the kind of leadership and management that facilitates great teamwork
- Anyone interested in the interpersonal dynamics of the workplace
What is in it for me: learn how to build and maintain a winning team
There's a realization that hits almost everyone at some point in their career – working with brilliant people doesn't automatically guarantee brilliant results. Rooms full of the smartest, most accomplished individuals often stumble, stall, and struggle. Often, the most talented people don’t work well together; egos clash, politics take over, and energy gets wasted on internal maneuvering instead of actual work. Put bluntly, great people do not automatically make great teams. What makes this particularly frustrating is that teamwork isn't some mysterious, intangible quality. It's actually quite predictable. Teams that fail, do so in a particular pattern. It starts with a lack of trust. When trust is absent, people don't speak openly. Without honest dialogue, there's no real debate, just polite nodding and behind-the-scenes grumbling. Then, without healthy conflict to surface the best ideas, there's no genuine commitment to decisions. Without commitment, accountability becomes impossible; no one calls out behaviors that undermine the team. And without accountability, the focus on shared results evaporates. Everyone just optimizes for their own success while the team flounders. Each of these stages builds on top of each other like a pyramid. This is the pyramid of five dysfunctions: no trust, no conflict, no commitment, no accountability, bad results. Over the next eight chapters, we'll walk through exactly how great teams are built — not by accident, but through deliberate, concrete actions that address each level of the pyramid.
Chapter 1: Teamwork is the ultimate competitive advantage; make it your top priority.
Picture a basketball court. On one side, five star players—household names, massive egos, incredible individual stats. On the other side? Five relatively unknown players who've learned to move as one unit, anticipating each other's positions, creating opportunities through coordination rather than solo heroics. Who wins? The cohesive team beats the collection of stars almost every single time. And yet, in the business world, organizations constantly fail to understand this; they assemble teams of brilliant individuals and assume excellence will naturally follow. Consider DecisionTech, a Silicon Valley technology start-up that had everything going for it. Top-tier venture capital investors. An engineering team stacked with talent. An executive team that was experienced, accomplished, and expensive. On paper, this company was poised to dominate. Instead, they ended up hemorrhaging money and struggled to find customers. The situation deteriorated so rapidly that within two years, what had been seen as the next big thing was falling behind the competition and struggling to stay in the game. What went wrong? The technology was solid, the market opportunity was real, and individual capabilities were unquestionable. The problem lived in the space between people. The leadership team, a group of ambitious, successful individuals, had turned their workplace into a minefield of politics. Instead of collaborating, they competed. Instead of building something together, they maneuvered against each other. This is what happens when you don’t build a team. Ego takes over and every meeting becomes a performance, every decision becomes a chess match. Energy that should flow toward customers or toward building something valuable, gets redirected inward. People spend their days trying to outmaneuver their colleagues instead of outperforming competitors. As a result, morale craters. When trust disappears from a team, every interaction feels like a potential threat and work becomes exhausting. Your best people start looking for the exits. DecisionTech was at this stage when Kathryn Petersen entered the scene. The board chairman decided to bring her in as the new CEO. His choice surprised many. But Kathryn Petersen understood something fundamental: teamwork is the ultimate competitive advantage precisely because it's so rare. When you get it right, you create something competitors can't easily copy. They can hire talented people, buy better technology, match your prices, or imitate your products. But a truly cohesive team that operates as more than the sum of its parts is genuinely hard to replicate. So Kathryn made teamwork her focus. She prioritized it even above hitting immediate financial targets, believing that if she could get these people working together properly, everything else would follow. But where do you start when you're trying to transform a dysfunctional team? You can't just announce "we're going to be a great team now" and expect anything to change. You need a systematic approach—and that's where the pyramid comes in.
Chapter 2: All teamwork is based on trust, and trust is built when team members are open about their weaknesses and mistakes.
Here's a scene that might feel familiar. A senior leader needs to be replaced. Someone on the team volunteers for the role. But everyone in the room knows, knows, that this person isn't the right fit. What happens next? In most organizations, silence. People shift in their seats. No one wants to be the person who says what everyone's thinking. So the conversation gets awkward, then political. At DecisionTech, after Kathryn Petersen began building trust, something different happened. When the head of sales departed, Carlos Amador, the head of customer support, suggested he should take the position. The rest of the team had concerns, however. They felt that other team members had more relevant experience and that the chief operations officer seemed like a stronger candidate. But unlike in other companies, they shared their feelings – directly. They explained their thinking and made the case for why someone else would be better positioned to succeed. How do you think Carlos responded? Did he throw his toys out the pram and refuse to work? No, he listened. He considered the team’s perspective. And he agreed. He wasn't offended. He recognized they were right. What had to be in place for that interaction to work? In short, trust. The team needed enough trust that people felt comfortable delivering difficult feedback. Carlos needed enough trust in his colleagues' intentions that he could hear their concerns without interpreting them as a personal attack. Without trust, that situation would end up in chaos. Carlos would feel blindsided and rejected. Resentment would build. The decision, whatever it ended up being, would leave damage in its wake. This is why trust sits at the foundation of the pyramid. Without it, everything else crumbles. But what kind of trust are we talking about here? One thing we need to be clear on is that we’re not talking about professional reliability. It's not "I trust you to send that report on time" or "I trust you to handle that client call professionally. " Those are basic workplace expectations. Real team trust, the kind that enables high performance, is vulnerability-based trust. It means believing that when you expose a weakness, acknowledge a mistake, or admit you don't know something, your teammates won't use that against you. They won't exploit it for political gain or quietly update their assessment of your competence. When people can't be vulnerable with each other, every meeting becomes a performance. Real problems get discussed in hallways after the official meeting ends, never in the room where decisions are made. This means that issues that should take minutes to resolve stretch into weeks because no one will say what's actually wrong. So how do you build vulnerability-based trust? Put simply, you go first. Especially if you're the leader. You acknowledge what you don't know. You admit when you're struggling. You ask for help without disguising it as a rhetorical question. When the person with the most authority makes themselves vulnerable, it gives everyone else permission. It signals that this team operates by different rules. And gradually, as more people take the risk and find that their vulnerability isn't weaponized, trust builds. Let’s find out more about this in the next chapter.
Chapter 3: If people trust each other, they engage in constructive conflicts and make better decisions.
When Kathryn Petersen first arrived at DecisionTech, she noticed something odd about the leadership team meetings. They were remarkably. . . polite. People presented ideas. Others nodded. There were questions—but carefully worded ones, the kind that don't really challenge anything. Discussions moved smoothly from topic to topic. Everyone stayed professional. On the surface, it looked efficient. In reality the team were avoiding discussing and debating the topics that actually mattered. This is the paradox most teams face, we think conflict is a problem. We see teams arguing and assume that if we could just get everyone to be more civil, more collaborative, more aligned, then we'd perform better. But this is the wrong way around. It’s the absence of conflict that is often the real problem. It’s important that we’re clear about what kind of conflict we're talking about. We’re not talking about destructive conflict— the kind driven by ego, politics, and personal agendas. That's genuinely harmful and should be eliminated. We’re talking about constructive conflict. Constructive conflict is passionate, emotional debate about ideas, strategies, and decisions. It's what happens when smart people who care deeply about outcomes challenge each other's thinking to find the best solution. Above a lack of ‘trust,’ no willingness to engage in conflicts is the next level of the dysfunctions pyramid. When a team lacks trust, people avoid this kind of debate. They hold back their real opinions. They don't challenge ideas that seem flawed because they're worried about how it will be interpreted. Is this about the work, or is this personal? Will speaking up damage my standing with this person? In short, it’s better to stay quiet and let the idea move forward, even if you think it's wrong. The result of all this is, of course, bad decisions. Often, in fact, no real decision at all; just vague agreement to "explore options" or "circle back later. " You can think about all of this from a practical standpoint. If you're trying to solve a complex business problem, you need varied perspectives clashing against each other. You need someone to poke holes in the proposal. You need the person who sees the implementation challenges to speak up before you commit resources. You need honest debate about each idea’s merits and faults. Open, free debate leads to better outcomes. But such constructive conflict requires trust as its foundation. This is because when you trust someone's intentions, you can interpret their challenge to your idea differently. Instead of hearing "you're wrong and I'm right," you hear "I want to help make this better. " The disagreement becomes productive instead of threatening. At DecisionTech, Kathryn worked deliberately to encourage this kind of healthy debate. She pushed the team to engage with controversial topics they'd been avoiding. Over time, the team developed such a strong rapport that they started having passionate, even heated discussions about important issues; those debates made them healthier and more effective at finding the right answers. Trust enabled conflict. And conflict led to something else the team had been struggling with: actual decisions.
Chapter 4: Everybody has to be committed to a decision, even if there is no consensus or certainty about its correctness.
Listen to the following example and think about how many times you've sat in this type of meeting before. The discussion goes on for an hour. People share perspectives. Someone suggests a direction. Others nod. A few people offer mild feedback. Eventually, time runs out, and someone says, "Okay, so we're aligned on this approach? " Cue more nodding. Before, finally, the meeting ends. Two weeks later, nothing has happened. Worse still, sometimes people are actually pursuing completely different interpretations of what was decided. When you ask about progress, you get responses like "Well, I'm not sure that's really the right call" or "I thought we were still evaluating options. " All in all, the meeting produced the illusion of a decision without anyone actually committing to it. This is one of the most common dysfunctions in business: teams that can't make decisions and stand by them. And it stems directly from the absence of healthy conflict we mentioned in the previous chapter. Think about what happens when you skip real debate. People leave the meeting with unresolved concerns. They haven't voiced their objections, maybe because trust is low, maybe because the team culture discourages conflict. So they smile, they nod, but internally they're thinking "this won't work. " And when it's time to execute? They don't. Not really. They hedge, they slow-roll implementation, they keep second-guessing the decision, but nothing actually gets done. Great teams operate differently. They understand something counterintuitive; that any decision is better than no decision at all, especially when it comes to important matters. A lack of commitment creates ambiguity. In a leadership team, this ambiguity cascades down through the organization, resulting in misaligned goals and priorities that become more extreme at every level. No commitment is therefore the next level of the dysfunctions pyramid: above no trust and no conflict Before we move on, it’s important to remember one thing: commitment doesn't require consensus. Most teams get this wrong. They think everyone needs to agree before moving forward, so they keep discussing, keep negotiating, keep trying to find a solution that makes everyone happy. This is rarely productive. Instead, great teams understand that commitment means everyone has been heard and understands the greater goal, even if the final decision isn't the one they personally advocated for. At DecisionTech, Kathryn worked to ensure everyone had a genuine chance to express their opinion before decisions were finalized. Not performative input, but real engagement with their perspective. When team members knew their concerns had been considered and addressed, something shifted. They were willing to rally around team decisions, even ones they'd argued against. You'll often find this in great teams: people committing fully to group decisions they'd passionately opposed just hours earlier. The debate happened. They lost the argument. And now they're all-in on making it work.
Chapter 5: Great teams have peer-to-peer accountability, meaning everyone's performance is transparent.
Once, at DecisionTech, one employee missed his deadline for a competitor analysis. The team knew it was coming. Everyone could see the work wasn't getting done, but no one said a word. When Kathryn raised it at the next meeting, she didn't reprimand the individual. Instead, she turned to the rest of the team: "You should have addressed this earlier. It was obvious the analysis wouldn't be ready, and you should have challenged him to act. " The room went silent. Kathryn had just named the fourth dysfunction: avoidance of accountability. Peer-to-peer accountability is one of the most uncomfortable dynamics in any team. Calling out a colleague feels intrusive, even arrogant. It can feel like you're elevating yourself above a peer or meddling in their business. So most people simply stay quiet. But this silence has a cost. When team members don't hold each other to standards, everyone feels less accountable. Deadlines slip, performance drops, and the burden of discipline falls entirely on the leader . Ironically, its teams with strong rapport often struggle most with accountability. Team members fear that confronting a peer will damage the relationship, so they let issues slide. But the opposite happens, resentment builds, respect erodes, and performance standards drop. Great teams don’t fall into this trap. They hold one another accountable, and team rapport and results increase. The mechanics are pretty straightforward. Leaders must make performance transparent; if results, commitments, and progress are visible to everyone, accountability becomes natural. Leaders must also shift the culture of feedback. Teams need support and training to see calling out a peer as a mark of respect, not criticism. Finally, as with everything, leaders should model the ideal behavior first; when they welcome being held accountable by the team, they give everyone permission to do the same. Accountability is the bridge between commitment and results. You've debated openly, decided clearly, and committed fully. Now the question is: will you deliver? In high-performing teams, that question doesn't rest with the leader alone, it lives with every member of the team. And when everyone owns the answer, performance stops being a hope and becomes a habit. But even with strong accountability, there's one more trap that derails teams: losing sight of what truly matters. Next, we'll explore what happens when individuals stay accountable to their own goals, but the team forgets to focus on collective results.
Chapter 6: Effective teams focus on collective results rather than individual goals.
To start this chapter, let’s go back to basketball. Kathryn's husband coached basketball. One season, he had a talented player on his roster, someone who could score at will. But the player didn't care whether the team won or lost. He cared about one thing: how many points he scored. So Kathryn's husband dropped him from the team. His individual goals mattered more to him than the team's success, and that made him a liability, not an asset. Every team has goals it strives for, it might be designing a new product line, growing sales or winning a championship. Most individuals have goals too. In great teams, shared goals take precedence over individual ones. When people like that selfish basketball player remain on a team, the important collective goals fade and performance takes a nose-dive. So what kind of common goals keep a team focused? Clearly defined ones that are easy to measure. If the intended results are clear and leave no room for interpretation, it's not possible for any individual to slip away from the team goal to work on their own agenda instead. At DecisionTech, for example, the goal was specific: 18 customers by the end of the year. Everyone united behind it. There was no chance for ambiguity or wiggle room. When common goals are embraced, something remarkable happens. Individual team members become more willing to support and help each other, even across lines of responsibility. At DecisionTech, this meant the engineering department mobilized its resources to help the sales team with product demonstrations. It wasn't their job description, but it was the best way they could contribute to getting more customers and meeting the common goal. This is the fifth and final layer of the pyramid. Trust enables conflict. Conflict enables commitment. Commitment enables accountability. And accountability, when it's strong, channels every ounce of team energy toward collective results. Without it, you have a group of skilled individuals chasing personal wins. With it, you have a team capable of extraordinary performance. The lesson is simple but hard to live: your team's success must matter more than your individual scorecard. Set goals that are clear and measurable. Make sure everyone knows what winning looks like. And create a culture where people instinctively ask, "How does this help us win? " rather than, "How does this help me advance? " When that shift happens, the team stops competing internally and starts competing externally. And that's when results follow. But building a high-performing team isn't just about frameworks and principles. It requires something more fundamental: time. Next, we'll explore why great teams spend a lot of time together, and how that investment pays dividends in trust, alignment, and speed.
Chapter 7: Great teams spend a lot of time together, which results in them saving a lot of time.
A rowing boat goes nowhere if every oarsman rows in a different direction. The same is true for teams. If they don't agree on where they're going, they'll spin in circles, wasting energy and time. So how to ensure this doesn’t happen? The answer is surprisingly simple, you meet regularly . At first glance, this might sound counterintuitive. Meetings are often seen as the enemy of productivity. But for high-performing teams the opposite is true. Regular time together creates many benefits that compound over time. Firstly, it helps members develop good rapport and trust, which helps them resolve any issues quickly and effectively. Secondly, conflicts are easier to resolve face to face. It's far easier to gather arguments and counterarguments from all team members in real time when they're all situated in the same space. Thirdly, in face to face meetings, team members have better insight into what each of them is doing and how their skills might be leveraged in other areas as well, so there's less risk of redundant work . At DecisionTech, many of the team's inefficiencies were resolved by Kathryn forcing team members to spend considerable time together. Around eight days per fiscal quarter was spent in meetings like the annual meeting, the quarterly off site meetings, the weekly staff meetings and ad hoc topical meetings. That might sound excessive, but it paid off. At first this focus on more meetings might feel too much. But investing time upfront saves time later. Over the long run, the team moves faster, wastes less effort, and operates with far greater clarity than teams that try to "save time" by avoiding meetings. This all brings us to the top of the pyramid. We've climbed through trust, conflict, commitment, accountability, and collective results. But none of those behaviors can flourish without the bond that time together provides. It's the enabler of everything else. Time together builds trust. Trust enables conflict. Conflict sharpens commitment. Commitment fuels accountability. And accountability drives collective results. Each layer depends on the one below it, and all of them depend on teams spending real, deliberate time together. This isn't about meeting for the sake of meeting. It's about creating the conditions for all five behaviors to thrive. So how do you bring it all together and make these five behaviors stick in the real world? That's what we'll explore in the final chapter.
Chapter 8: Making It Stick: From Framework to Practice.
The pyramid looks elegant on paper. Trust at the base, then conflict, commitment, accountability, and collective results at the top. But knowing the model and living it are two different things. DecisionTech didn't transform because Kathryn drew a diagram. It transformed because she created the conditions for new behaviors to take root, one uncomfortable conversation and one deliberate practice at a time. Most teams already know what good teamwork looks like. They know trust matters, conflict avoidance is costly, and accountability can't rest with the leader alone. But knowledge doesn't change behavior. What changes behavior is deliberate, repeated practice in an environment where it's safe to try, fail, and improve. Trust is the foundation. It can't be mandated, but it can be cultivated through personal histories exercises, leader vulnerability, and shared experiences that reveal the human being behind the job title. Without trust, conflict stays personal, commitment stays shallow, and accountability stays absent. Conflict comes next. Productive teams distinguish between healthy tension and destructive politics. They normalize challenging ideas without making it personal, reward people who speak up even when it's uncomfortable, and make decisions when consensus isn't possible. Commitment to a clear decision beats endless debate over the perfect one. Accountability must be peer driven. Performance should be visible. Peers should challenge each other, framing it as respect rather than criticism. When someone holds a teammate accountable, that behavior should be celebrated, not discouraged. Collective results require relentless focus. Goals must be clear, measurable, and impossible to ignore. Everyone should know what winning looks like. The culture should push people to ask, "How does this help us win? " not "How does this help me? " Time together is the enabler. Regular meetings, real hours spent face to face, and shared context build the rapport and trust that make everything else faster and easier. It feels expensive at first, but over time it eliminates wasted effort, misalignment, and slow decisions. The five dysfunctions are daily realities in every team, but they're solvable. With the right leadership, the right practices, and the willingness to do uncomfortable work, any team can climb the pyramid. The question isn't whether it's possible. The question is whether you're ready to start.
Final summary
The key message in this summary is: Great teamwork doesn't happen by accident. It requires trust built on vulnerability, conflict focused on ideas rather than egos, commitment even without consensus, peer-to-peer accountability that doesn't rest with the leader alone, and a relentless focus on collective results over individual wins. The five dysfunctions are present in every team, but with deliberate practice and the right leadership, they can be overcome. The pyramid isn't just a model. It's a roadmap for building teams that outperform the competition.
About the Author
Patrick Lencioni is president of The Table Group, a management consultancy. His previous bestselling books include Overcoming the Five Dysfunctions of a Team, Death by Meeting and Silos, Politics and Turf Wars. In 2008, CNN Money listed him as one of "ten new gurus you should know." Patrick M. Lencioni: The Five Dysfunctions of a Team copyright 2002, John Wiley & Sons Inc. Used by permission of John Wiley & Sons Inc. and shall not be made available to any unauthorized third parties.