# The Five Dysfunctions of a Team by Patrick Lencioni Source: https://thegisthub.com/books/the-five-dysfunctions-of-a-team-by-patrick-lencioni Last updated: 2026-10-24 Published 2002 · 229 pages · ISBN 9780787960759 · Categories: Business and startups, Communication and persuasion Patrick Lencioni's leadership fable about a new CEO who rebuilds a failing executive team, followed by his five-level model of why teams fail. For managers and anyone who sits on a leadership team. ## The gist Teams fail in a predictable order. Lencioni tells the story of Kathryn Petersen, a new CEO who turns around the dysfunctional executive team at DecisionTech, then lays out the model behind it. The five dysfunctions stack like a pyramid: **absence of trust** (people hide weaknesses), **fear of conflict** (artificial harmony), **lack of commitment** (ambiguity), **avoidance of accountability** (low standards) and **inattention to results** (status and ego win). Each level rests on the one below, so the fix starts with trust, which means leaders go first in admitting mistakes. A team that argues openly, commits to clear decisions, calls out peers and measures itself on shared results beats a team of smarter individuals. ## Key ideas ### 1. Teamwork is the rarest competitive advantage Lencioni argues that companies rarely fail on strategy, finance or technology. They fail because the leadership team cannot work together. DecisionTech has more money, more experience and better technology than any rival, yet it loses because its executives protect their departments instead of the company. Teamwork is hard because it requires people to admit weakness and argue openly, so few teams achieve it. That rarity is what makes it an advantage. ### 2. The five dysfunctions form a pyramid The dysfunctions stack in order: absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results. Each one makes the next more likely. A team that hides weaknesses cannot debate, a team that cannot debate does not buy in, a team without buy-in will not hold peers accountable, and a team without accountability drifts toward personal goals. Because the levels depend on each other, the fix begins at the base, with trust, and works upward. ### 3. Trust means vulnerability, and the leader goes first Trust in Lencioni's sense is not predictability. It is the confidence that colleagues have good intentions, so you can admit mistakes, ask for help and say "I was wrong" without fear. Kathryn builds this with a personal histories exercise, where each executive describes their childhood and hardest challenge, and by naming her own weaknesses before asking anyone else to. The leader who demands openness while staying guarded gets neither. ### 4. Healthy teams fight about ideas Teams that lack trust settle for artificial harmony: polite meetings where no one disagrees and nothing is decided. Lencioni argues that passionate, unfiltered debate about issues is a sign of health, not a problem. Kathryn tells the team to "mine" for buried conflict and gives real-time permission when debate gets uncomfortable. She also ends meetings that drift into personal attacks. Conflict about ideas saves time. Avoiding it just moves the argument into hallways. ### 5. Commitment needs clarity, not consensus People do not buy in because they agree. They buy in because they were heard. Great teams decide after real debate, and everyone backs the decision even if they argued against it. Lencioni calls this disagree and commit. A clear decision now beats a perfect decision later, since a wrong call can be corrected but ambiguity cannot. DecisionTech picks one goal, 18 new customers in the year, and every department measures itself against it. ### 6. Peers are the best source of accountability On most teams, the leader is the only person who confronts poor performance, and colleagues stay quiet to avoid awkwardness. Lencioni argues that peer pressure is more efficient and more respectful. When goals and standards are public, team members can ask each other direct questions about missed commitments. The leader's job is to let that happen rather than becoming the sole disciplinarian. JR, the head of sales, leaves when peer accountability makes his vague promises impossible. ### 7. The leadership team is your first team Executives naturally feel loyal to the people they manage. Lencioni insists that an executive's first team is the leadership team, and the department comes second. When Martin opens his laptop in a meeting to prepare for a customer call, Kathryn stops the session and tells him the team comes first. Putting the department first leads to silos, turf battles and decisions that help one group and hurt the company. ### 8. One toxic performer can outweigh their output Mikey, the head of marketing, produces good work but refuses feedback, mocks colleagues and ignores the team's rules. Kathryn concludes that keeping her sends a message that the team's standards are optional. She fires her, and the team reacts with relief. Lencioni's point is that leaders often keep high performers who damage trust because their individual numbers look good. The hidden cost to the team's results is larger than the visible gain. ## Questions this book answers ### What is The Five Dysfunctions of a Team about? The Five Dysfunctions of a Team by Patrick Lencioni is a leadership fable followed by a model. The story follows Kathryn Petersen, a new CEO who rebuilds the executive team at DecisionTech, a struggling software startup. The model names five dysfunctions that stack in order: absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results. Lencioni argues that teams fix them from the base up, starting with trust. ### What are the five dysfunctions of a team? Lencioni's five dysfunctions are absence of trust (team members hide weaknesses and mistakes), fear of conflict (people avoid open debate and settle for artificial harmony), lack of commitment (decisions stay ambiguous and no one buys in), avoidance of accountability (peers do not call each other on poor performance) and inattention to results (people put ego, career or department ahead of the team's goals). Each dysfunction makes the next one more likely. ### Who is Kathryn Petersen in The Five Dysfunctions of a Team? Kathryn Petersen is the main character of the fable. She is a 57-year-old former manufacturing executive hired as CEO of DecisionTech, a Silicon Valley startup with a talented but dysfunctional leadership team. She spends two weeks observing, then runs a series of offsites in Napa Valley where she teaches the five dysfunctions model, forces open debate, fires one executive who refuses to change and leads the team to a shared goal. ### What does Lencioni mean by vulnerability-based trust? Vulnerability-based trust is the confidence that teammates have good intentions, so you can admit mistakes, weaknesses and gaps in knowledge without fear of being used against you. Lencioni contrasts it with predictive trust, which is just knowing how someone will behave. He argues that the leader must go first by admitting their own weaknesses, and he offers tools such as the personal histories exercise and 360-degree feedback to build it. ### Is The Five Dysfunctions of a Team based on research? No. The model comes from Lencioni's consulting work, and the fable is a composite story rather than a case study. The book includes a short team assessment survey but no research that shows the five dysfunctions predict team performance. Critics see this as a weakness. Supporters say the model's value is as a shared vocabulary that teams find easy to remember and apply. ## Quotes > Not finance. Not strategy. Not technology. It is teamwork that remains the ultimate competitive advantage, both because it is so powerful and so rare. (Introduction) > If you could get all the people in an organization rowing in the same direction, you could dominate any industry, in any market, against any competition, at any time. (Opening line of the introduction) ## Full summary ### A company with every advantage Patrick Lencioni, founder of the consulting firm The Table Group, opens with a claim: teamwork is the one competitive advantage that remains both powerful and rare. Most companies do not fail because of bad strategy or weak technology. They fail because the people at the top cannot work together. The book is in two parts. The first part is a fable, a short business novel. The second part explains the model the story illustrates. The fable is set at **DecisionTech**, a software startup in Half Moon Bay, California. The company has 150 employees, more funding than its rivals and an executive team with more experience than any competitor. Two years in, it is behind on revenue, losing engineers and losing morale. The board moves the founding CEO, **Jeff Shanley**, into a business development role and hires **Kathryn Petersen** to replace him. Kathryn is 57, a former manufacturing executive with no software background. The staff doubt her from the first day. Her husband, Ken, coaches high school basketball, and the book uses that lens throughout: a team is a team, whether it plays ball or ships software. Kathryn spends her first two weeks doing almost nothing but observing. She sits in meetings, walks the halls and interviews each executive. Then she announces a series of two-day offsites in Napa Valley. The executives see the offsites as a waste of time. Kathryn sees them as the only way to save the company. ### The team Kathryn inherits The executive team is a set of smart people who do not trust each other. - **Jeff Shanley**, the former CEO, is well liked and avoids conflict. He let meetings become status reports where nothing gets decided. - **Mikey** (Michelle Bebe), the head of marketing, is brilliant on paper and rolls her eyes at colleagues. She ignores feedback and makes everyone tense. - **Martin Gilmore**, the chief technologist and co-founder, treats meetings as interruptions. He opens his laptop and checks out when discussion bores him. - **JR Rawlins**, the head of sales, agrees to everything and delivers little. - **Carlos Amador**, head of customer support, is the quiet one everyone trusts but who rarely pushes. - **Jan Mersino**, the CFO, guards the budget and keeps her head down. - **Nick Farrell**, the COO, was hired to run operations in a company that grew less than planned. He has no real job and resents it. Meetings are polite, dull and empty. No one argues. No one commits. Each executive works to protect a department. The company has no shared goal that everyone can name. ### The first offsite At the first offsite, Kathryn draws a triangle on a whiteboard and introduces the five dysfunctions, one level at a time. She starts at the base: **absence of trust**. Trust, in her definition, is not the ability to predict a colleague's behavior. It is the confidence that peers' intentions are good, so there is no reason to be guarded. That requires vulnerability: admitting mistakes, weaknesses and the need for help. She runs a **personal histories exercise**. Each person shares where they grew up, how many siblings they had and the hardest challenge of their childhood. The answers are small, but the room changes. Martin talks about growing up in a working-class family in England. Carlos describes being one of nine children. Mikey gives a short, guarded answer and the others notice. Kathryn then has the team review their **Myers-Briggs** profiles and discuss what each person brings to the team and what each person needs to work on. She goes first and names her own weaknesses. When Martin opens his laptop mid-session, Kathryn stops the meeting and tells him to put it away. The group is shocked. She explains that the team comes first, even above the customer call he says he needs to prepare for. This is a central idea in the book: every executive's **first team** is the leadership team, not the department they run. When department loyalty wins, the company loses. The second dysfunction, **fear of conflict**, follows from the first. Teams without trust avoid open disagreement and settle for **artificial harmony**. Kathryn argues that good teams fight. They have passionate, unfiltered debate about ideas, not about people. She calls on the team to "mine" for conflict: when someone sees a buried disagreement, they dig it out. Kathryn gives real-time permission in the room: when a debate gets uncomfortable, she reminds the team that the discomfort is the work. The third dysfunction is **lack of commitment**. Without conflict, people do not buy in. They nod in the meeting and ignore the decision afterwards. Kathryn distinguishes commitment from consensus. Great teams do not need everyone to agree. They need everyone to be heard, then they decide, and everyone backs the decision. She also argues for **disagree and commit** and for clarity over certainty: a clear decision made now beats a perfect decision made never. ### Conflict in the open Between offsites, the old habits return. Kathryn ends staff meetings when debate turns into personal attacks, and she ends them when there is no debate at all. She forces the group to pick **one overarching goal** for the year. After an argument about whether the goal should be revenue, product quality or market share, they settle on winning 18 new customers by year end. Every department's work is then measured against that one number. The fourth dysfunction, **avoidance of accountability**, surfaces next. Executives see a peer missing a commitment and say nothing, because it feels rude. Kathryn argues that peer pressure is the most efficient form of accountability. On a healthy team, members call each other out directly, so the leader does not have to be the only source of discipline. The team publishes its goals and standards so that everyone knows what the others are supposed to deliver. Two people leave. JR, the head of sales, quits after the pressure of real commitments becomes uncomfortable. Nick, who has been considering an outside acquisition deal that does not fit the strategy, nearly leaves too. Kathryn tells him no on the deal, then offers him the sales job. He takes it and becomes one of the team's strongest voices. Mikey is the harder case. She is talented and her marketing work is good. But she will not accept feedback, she undermines colleagues in meetings and she treats the team process with contempt. Kathryn concludes that one person who refuses to play by the team's rules can poison the whole group, however skilled. She fires Mikey. The team's reaction is relief, and Kathryn notes that they had known for months what needed to happen. The fifth dysfunction, **inattention to results**, caps the model. Team members put their own status, career or department ahead of the shared outcome. The fix is to make results public and tie rewards to them. Kathryn asks each executive to say out loud what success for the whole company looks like, then holds them to it. The fable ends about a year later. DecisionTech leads its market in sales, staff turnover has fallen and the executive team argues openly, decides quickly and backs each other. Martin, the most skeptical member at the start, becomes the model's strongest advocate. ### The model The second part of the book lays out the five dysfunctions as a pyramid. Each dysfunction makes the next one more likely, so you fix them in order. 1. **Absence of trust** comes from an unwillingness to be vulnerable within the group. Team members who hide mistakes and weaknesses cannot build a foundation. 2. **Fear of conflict** follows. Without trust, people cannot engage in open debate about ideas. They fall back on guarded comments and veiled discussion. 3. **Lack of commitment** follows. When people do not air their opinions in open debate, they rarely buy in to decisions, even if they fake agreement in the meeting. 4. **Avoidance of accountability** follows. Without a clear commitment, people hesitate to call their peers on behavior that hurts the team. 5. **Inattention to results** follows. When no one holds anyone accountable, individuals put personal goals, ego or department above the collective result. Lencioni offers a short diagnostic survey of 15 statements, which teams rate on a three-point scale, to see which dysfunction is their weakest point. ### Tools for each level For each dysfunction Lencioni names practical tools, most of which Kathryn uses in the story. - **Trust**: the personal histories exercise, the team effectiveness exercise (each member names one thing each peer should keep doing and one thing they should improve), personality profiles such as Myers-Briggs, 360-degree feedback and shared experiential activities. The leader must go first in showing vulnerability. - **Conflict**: mining for buried disagreements, real-time permission to continue when debate feels tense, and instruments such as the Thomas-Kilmann conflict mode model to understand each person's style. The leader must resist the urge to protect people from discomfort. - **Commitment**: cascading messaging (the team agrees at the end of each meeting on what to tell their departments), clear deadlines, contingency and worst-case analysis to reduce fear of a wrong decision, and low-risk exposure therapy (practice making decisive calls on small matters). The leader must be comfortable with making a decision that turns out wrong. - **Accountability**: public goals and standards, simple and regular progress reviews, and rewards for team rather than individual performance. The leader must let the team be the primary source of accountability instead of becoming the only one. - **Results**: public declaration of results and results-based rewards. The leader must set the tone by valuing the collective outcome above personal recognition. Lencioni also argues that the executive team should be small, that meetings should be frequent and that time spent in good meetings is not wasted but is the actual work of a leadership team. ### What the critics say The model is simple by design, and reviewers note that the fable is a composite rather than evidence. There is no research in the book that shows the five dysfunctions predict team outcomes, and the pyramid order rests on Lencioni's consulting experience. Some readers find the characters flat and the ending too neat, and some managers note that firing a strong performer such as Mikey is not always realistic. Supporters answer that the model is a shared vocabulary, not a theory, and that it works because it is easy to remember. ### Who should read it Read it if you lead a team or sit on one that is polite but gets little done. It is short enough to read in an evening, and the model gives a team a common language for talking about trust, conflict and commitment. Managers who want evidence-based team science should look elsewhere and use this as a starting point. ## Do this week - Run the personal histories exercise at your next team meeting: each person shares where they grew up, their siblings and a hard childhood challenge. - Admit one mistake or weakness to your team this week before you ask anyone else to open up. - Pick the one shared goal your team will measure itself against this quarter, and write it where everyone can see it. - In your next meeting, name a disagreement that people are avoiding and ask the group to debate it in the open. - End each meeting by agreeing on the exact message every member will carry back to their own department. Summary by The Gist Hub (https://thegisthub.com). In our own words, not the book's text.