Skip to content
back to the episode
Episode summary2024CTO

The Five Dysfunctions of a Team: No Trust, No Real Debate

The sixteenth Code of Leadership episode: Alexander discusses Patrick Lencioni's The Five Dysfunctions of a Team with Andrey Sokolov, a business trainer who trained as an actor and has taught communication for twenty years. The talk climbs the pyramid of dysfunctions and keeps stepping outside the book — into Google's research, a Korolev story and Tuckman's stages.

Code of Leadership · episode #169 min read

This summary is shorter than the full episode; examples and assessments reflect the participants’ experience and views.

The main thread of the material
01

The business parable and its shape

Alexander opens the episode by explaining the gap: work kept him away from recording for almost three months, and he hopes this session restores the rhythm. To discuss Patrick Lencioni's The Five Dysfunctions of a Team he invited Andrey Sokolov, a business trainer whose course he once took himself. Andrey trained as an actor, director and screenwriter, has spent some twenty years teaching effective interaction built on storytelling and acting technique, and stages plays in his own studio. Alexander mentions that after that course his eighteen-year-old son took up theatre at a studio near home, reciting verse and working through emotions, and argues it is better learnt early than discovered when a senior manager is suddenly told to give a talk. Andrey adds a story about a leader who as a child acted in a drama club: once you have walked onto a stage in a children's role, stage fright stops looking serious.

The book, by the participants' reckoning, is over twenty years old: it came out in English in the early 2000s — "in 2002, I think" — and is still being reprinted in Russian. Andrey describes its shape: a business novel of short chapters, none longer than ten pages and usually two or three, with fast-moving events and recognisable characters, plus a closing practical chapter of team exercises and a questionnaire. A common reaction is "I wrote down five clever thoughts, the rest is padding"; Andrey argues that the padding is exactly what creates involvement, because the reader assembles the pyramid himself, while wisdom served ready-made is absorbed poorly. Alexander adds that in business novels the idea grows out of the narrative instead of arriving as dogma, and recalls The Goal, The Phoenix Project, which the club has already covered, and its sequel The Unicorn Project. Andrey replies that humanity has long passed knowledge on through tales and myths: the brain is tuned to events and empathy — hence the book being called a business parable.

02

Team, trust and Project Aristotle

Before climbing the pyramid the two settle what counts as a team. A group of professionals covering their positions is not yet a team; a team works together towards a shared result, and the familiar "my department is doing fine, it is those people who keep messing up" is a reliable sign that there is none. Alexander sees the same logic as in systems thinking: elements become a system when the sum exceeds the parts, hence the example "1 + 1 = 3". The base of Lencioni's pyramid is trust, and Andrey immediately strips away the everyday reading: it is not about letting colleagues into your private life. One side of it is the confidence that a colleague who comes to tell you off wants the result rather than your humiliation. The other is your own mistakes: with trust you share them, without it you hide them, which works against effectiveness. Asking for help and offering it grows from the same ground.

The remedy the book offers is showing vulnerability, and it is addressed to leaders: it is the leader who, by personal example, creates the ground on which vulnerability is possible, and it cannot be imitated: it takes genuine interest in what triggers the person. Without trust people close into a cocoon: they stay out of other people's work and let nobody into their own. Alexander lays Google's research alongside: Project Aristotle, as he recalls closer to the end of the 2000s, separated a work group — autonomous performers who at best share information — from a team with high interdependence, and from surveys and metrics derived five factors: psychological safety, dependability of colleagues, clarity of roles, plans and goals, meaning in the work, and the ability to make an impact. Psychological safety turned out to be the prerequisite for everything else — the same base as in Lencioni. Andrey describes life without it: fights for resources turn into a tug of war, and in a meeting it is easier to raise your hand so the meeting ends, since that commits you to nothing.

03

Conflict, Korolev and Tuckman's stages

The second dysfunction follows from the first: without trust people hide their own interests and refuse to hear anyone else's. As an actor, Andrey reminds everyone that conflict is the source of any action: a film in which the hero plans everything and everything works out stirs no emotion. An argument on the merits, with the visor up, ends either with you being persuaded or with a colleague seeing the problem from a new side. Alexander adds that where there are no conflicts there is usually no shared goal either, only people drifting towards local ones, which is why large companies write documents setting out the situation, the problem and how to compare the options — so the argument has a common reference point. False agreement, adopted so as not to offend anyone, turns into non-commitment: a decision I did not like I accept formally but neither defend nor demand of others, the conflict goes under the carpet, and the team lives in parallel realities where a year later it turns out who did what.

Against paralysis in uncertainty Andrey tells the Korolev story: scientists split over whether the surface of the Moon was solid or the craft would sink into dust, and Korolev wrote on a sheet of paper that the surface is solid, signed it and put the date. Taking a decision and quickly seeing it was wrong beats waiting for information that does not depend on you; Alexander translates this into Bezos's rule about irreversible and reversible decisions, and into pushing responsibility down to where there is enough information. Otherwise the fourth step grows — lowered standards, where a person commits only to a guaranteed result and the pace drops — and at the top of the pyramid sits indifference to the shared result, as in Raikin's sketch about the man who only sewed on the buttons. Alexander separately walks through Tuckman's model so that problems are not taken for a verdict: forming, storming, norming, performing — while Andrey warns that jumping over storming with a managerial "I am the boss, we do it this way" merely sweeps the conflict under the carpet. At the end Alexander says he has already ordered Lencioni's later book about six kinds of team genius.

Takeaways

What to take away

  1. 01Trust in Lencioni is not closeness but the right to admit a mistake out loud and take criticism on the merits; the leader creates that ground by personal example and cannot fake it.
  2. 02Project Aristotle's five factors map onto the same pyramid: psychological safety is the prerequisite without which dependability, clarity of roles and meaning do not function.
  3. 03An absence of conflict is not agreement but a drift towards local goals; a written problem statement with compared options gives the argument a shared reference point.
  4. 04Korolev's signed note about the lunar surface and Bezos's rule on reversible decisions: waiting for full certainty lowers standards and kills a team's pace.

Sources