The Five Dysfunctions of a Team

The story begins inside DecisionTech, a fictional tech company in California, near Napa Valley, which has an executive team full of brilliant people: award-winning engineers, sharp salespeople, a competent finance lead. On paper, it's the dream team. In practice, the company keeps losing market share to a slower competitor that, by any individual measure, is less talented.

That contrast is the question the whole book tries to answer: how can a group of smart, experienced, well-paid people produce worse results than an average team? Lencioni's answer is direct, almost uncomfortable: individual intelligence doesn't guarantee teamwork, and most companies spend a fortune hiring talent and almost nothing on making that talent work together.

DecisionTech's meetings are polite, punctual, and completely empty. Nobody disagrees out loud, decisions drag along, and the same topic comes back on the agenda week after week because, truth be told, nobody really committed to the previous decision. This is the team the new chief executive inherits.

Kathryn Petersen takes the top job at DecisionTech with no tech background: her history is in operations and in leading people in environments far rougher than a startup conference room. The team receives the news with polite suspicion, the kind of welcome that tells her nobody is going to make her life easy.

The company's former president, Jeff, accepts the new role of head of operations and becomes Kathryn's main quiet supporter, even though he knows colleagues like Mikey, from marketing, and Martin, the chief engineer, treat her arrival as a temporary nuisance.

Kathryn doesn't waste time trying to prove she understands technology. Instead, she bets everything on a simple hypothesis: that team's problem isn't technical, it's collective behavior. And collective behavior, unlike product strategy, can be taught and practiced.

A good part of the turnaround happens far from the office, in two-day retreats Kathryn organizes in the Napa Valley area. Taking the team out of its routine is deliberate: away from the day-to-day rush, there's room for the conversation nobody dares start in a Tuesday nine a.m. meeting.

In these gatherings, Kathryn forces uncomfortable situations, always with a simple question behind them: what does this group avoid saying to one another? And she doesn't let the silence slide. She insists, repeats the question, and waits for the discomfort to turn into a real conversation.

The retreat format isn't corporate fluff, it's a tool: every exercise there, personal stories, forced debate, behavior assessment, has a specific purpose within the model the book lays out in its second part, outside the fable.