The Five Dysfunctions of a Team: A Leadership Fable

The summary

DecisionTech had everything a Silicon Valley start-up is supposed to need: the most experienced and expensive executive team imaginable, more cash than its rivals, better technology, top-tier investors. Two years in, it trailed two competitors on revenue and customers and had a reputation as one of the most political places to work in the Valley. Patrick Lencioni’s fable drops a former car-plant executive, Kathryn Petersen, into the CEO chair, and her diagnosis never changes: the problem isn’t strategy, technology, or money. The eight people at the top aren’t a team. At an off-site in Napa she draws a pyramid on the whiteboard, filled in from the bottom:

• Absence of trust
• Fear of conflict
• Lack of commitment
• Avoidance of accountability
• Inattention to results

The order is the argument: each one produces the next, so a single broken link takes down the chain.

Trust means vulnerability, not predictability

The everyday sense of trust is prediction: she always hits her deadlines, so you trust her to. That isn’t enough. A team needs people willing to be exposed — to admit a weakness, a mistake, a need for help — and confident that none of it comes back at them later. Careers reward the opposite instinct, teaching successful people to compete with their peers and guard their reputations.

Kathryn starts absurdly small: five harmless questions about hometown, siblings, childhood hobbies, first job. Forty-five minutes later the team is looser than it had been in a year. Then she raises the stakes and goes first, naming her own weakness — she’s a poor public spokesperson who dismisses PR. A leader who won’t risk losing face sets the ceiling for everyone else, and staged vulnerability is worse than none.

Artificial harmony is the expensive kind

Nick objects that the team has plenty of conflict. Kathryn corrects him: they have tension. Nobody argues, so frustration leaks out as eye-rolls and sarcasm. The kind that matters is ideological — about ideas, not personalities — and from outside it can look like a brawl while leaving no wreckage behind.

The efficiency case for avoiding it runs backwards. Outsourcing IT, Jan points out, comes up at every meeting, half the room for and half against, and never moves because nobody wants to annoy anyone. “And ironically,” Carlos says, “that is exactly what pisses us off.” Ducking the argument means revisiting it forever, and rerouting the disagreement into back-channel attacks nastier than any clash over a decision. So Kathryn promises that every staff meeting will be loaded with conflict, and that if there’s nothing worth debating, there’s no meeting.

People weigh in before they buy in

Commitment rests on clarity and buy-in, and two appetites block it: consensus and certainty. Reasonable people don’t need to win an argument; they need to know their view was heard. Consensus chased for its own sake becomes an attempt to please everyone, which, as Jeff puts it, usually turns into displeasing everyone equally. Waiting for certainty just breeds paralysis.

The team fights over market share, revenue, cost containment, and new customers as the single goal for the year. “If everything is important, then nothing is,” Kathryn says, refusing to let them keep two. Once everyone has argued, she sets the number herself: eighteen new customers by December 31, at least ten willing to be active references. Nobody voted; everyone had spoken. Carlos names the rule: people need to weigh in before they can buy in. Skip it and small gaps between executives become open contradictions by the time they reach the employees below.

Peer pressure beats a boss with a whip

Accountability here means one narrow thing: telling a peer their performance or behavior is hurting the team. Interpersonal discomfort stops it, and people are hard to confront for opposite reasons — Carlos is so helpful that nobody challenges him when he admits he never started the competitive analysis; others get defensive, or are intimidating. When the leader is the only source of discipline, the team quietly outsources the job.

Kathryn’s own story lands hardest. Early in her career she inherited an analyst, Fred, who out-produced everyone and made sure they knew it. Complaints came; she ignored them rather than come down on her best performer. Output slid, so she promoted him. Three of her seven analysts quit and her boss fired her. “They fired the right person,” she tells the group. What cost the department half its output wasn’t Fred’s behavior. It was her tolerance of it.

Make the score too clear for ego to hide behind

The top of the pyramid isn’t about killing ego; the key, Kathryn says, is to make the collective ego greater than the individual ones. Teams drift toward two substitutes: team status, where belonging to something prestigious is satisfying enough, and individual status, where a career quietly outranks the group’s goals. Her husband Ken, a high-school basketball coach, benched his most talented player — a kid content after a loss as long as his own points were up — and won more without him.

It’s also why she insists the executive staff be everyone’s first team, ahead of the departments they built and love — not dismantled, but made secondary, which to most of her reports feels like abandonment. Mikey, the gifted marketing VP who rolls her eyes through meetings and rates her own department a success while the company fails, never makes that shift, and Kathryn moves her out.

The bottom line

Building a team is simple and brutally hard, and the difficulty is behavioral, not intellectual: obvious practices sustained with unusual discipline. Because the pyramid is sequential, there’s no jumping to accountability or results. You start at the bottom, and as the leader that means being first to say something unflattering about yourself. Read it if your meetings are polite and your hallways are not, or if you’ve ever shielded a high performer whose behavior was draining everyone around them.