Part · Building & Leading Teams

So far the book has been about you and the people you manage one at a time — the manager’s job, the individuals, the conversations. This part zooms out to the thing all of that is really for: the team. Because a manager’s output isn’t a stack of great individuals; it’s a group that, together, produces reliable results.

This part answers one question: what turns a group of individuals into a team that produces reliable outcomes — without chaos, burnout, or politics? That “without” matters. Plenty of groups hit their numbers for a quarter by running everyone ragged, or by letting the loudest person win. That’s not what we’re after. We want a team that performs and stays healthy enough to keep performing. This overview lays out the whole arc, in the order you’d actually build it.

A note before we start: the word “team” gets used so loosely that it’s almost lost its meaning — every group of people who share a Slack channel gets called one. This part treats it precisely, because the difference between a group and a team is not a nicety. It changes what you build, in what order, and how you spend your energy as a manager. So we begin there.

A group is not a team

Start with a distinction most people blur. A group is a set of people who happen to share something — a manager, a room, a goal on a slide. A team is a set of people who are interdependent: they win or lose together, and the output of one depends on the work of another.

GROUP                                TEAM
five people, one manager             five people whose work interlocks
each has their own goal              one shared outcome they own together
success is individual                success is collective
"I did my part"                      "we shipped it / we saved the patient"

Six analysts who each write their own report and never touch each other’s work are a group, even if they share a boss and a floor. A surgical team — surgeon, anaesthetist, scrub nurse — is a team: no one succeeds alone, and a failure by any one of them is a failure for all. Most workplaces sit somewhere in between, and part of your job as a manager is to decide, honestly, how interdependent the work really is — and then build for that.

The consequence of that distinction is bigger than it looks. In a real team, a person’s individual brilliance is worth less than how well their work meshes with everyone else’s. The most talented analyst who won’t share findings, the fastest coder who breaks the build, the star surgeon who won’t listen to the nurse’s warning — each is a net loss to a team, however impressive alone. This is the first place management stops feeling like “hire the best people” and starts feeling like “build the best combination.” Everything downstream in this part is about that shift.

This matters because the moves in this part only pay off to the degree people actually depend on each other. If your “team” is really five independent contributors, forcing team-building rituals on them wastes everyone’s time. If they’re genuinely interdependent and you manage them like independent contributors, the work falls through the cracks between them — which is exactly where teams fail.

In practice — the handoff that no one owned

A hospital ward runs three shifts a day. Each nurse is excellent individually. But patients kept slipping between shifts — a medication change noted by the day nurse never reached the night nurse. No individual was failing; the seam between them was. That seam is a team problem, and no amount of hiring better individuals fixes it. It’s fixed by clarity, safety, and shared ownership — the things this part builds.

Why “without chaos, burnout, or politics” is the whole game

It’s easy to get a group to produce a result once. The hard part — the part that separates managing from just hustling — is producing results reliably, over months and years, without the three failure modes hiding in the book’s central question:

• Chaos is what you get when nobody knows who owns what, so work is done twice, or not at all, and every decision has to route through you. Chaos is a clarity failure.
• Burnout is what you get when reliability is bought by grinding people down — heroics on the weekend, the same two people carrying everyone, no slack in the system. Burnout is a sustainability failure.
• Politics is what you get when it’s safer to look good than to tell the truth, so people compete instead of cooperate and information gets distorted on its way to you. Politics is a safety-and-culture failure.

Each of the three maps onto something this part builds. Clarity (role clarity, RACI) attacks chaos. Healthy composition and culture attack burnout. Psychological safety and good conflict handling attack politics. That’s not a coincidence — it’s why these six topics, and not some other six, make up the part.

In practice — the warehouse that ran on heroes

A distribution warehouse always hit its shipping targets, so from the outside it looked like a great team. Underneath, it ran on two long-serving supervisors who quietly fixed everything — covering gaps, re-planning routes, staying late. Then both took holiday the same week and the operation seized up: nobody else knew how the pieces fit. The results had been real, but the reliability was an illusion resting on burnout. That’s the difference this part is after. A team that performs only because a couple of people are grinding themselves down isn’t a strong team; it’s a fragile one with a good-looking dashboard.

Why this order

You build a team the way you’d build anything reliable: you choose the parts, get them working, make the connections between them unambiguous, then create the conditions that let the whole thing run without you standing over it. That logic sets the sequence for this part.

1. First you decide who is on the team — because the cheapest fix for most team problems is not hiring the wrong person in the first place.
2. Then you get new people productive fast — a great hire who flounders for three months is a team problem you created.
3. Then you make who-does-what unambiguous — most day-to-day team friction is not personality, it’s unclear ownership.
4. Then you make it safe to speak up — because a team that can’t surface problems can’t fix them.
5. Then you make the culture — the actual repeated behaviours — deliberate rather than accidental.
6. And finally you learn to handle the conflict that every real team produces — because the goal is not zero conflict, it’s conflict that makes the work better instead of poisoning it.

Notice the shape: the early chapters are about composition and clarity (who’s here, what do they own), and the later ones are about conditions (is it safe, is it healthy, can we disagree well). You need the first before the second is even worth attempting — there’s no point building psychological safety around the wrong people doing unclear work.

Why not a different order? Because each step makes the next one cheaper. Skip hiring care and you spend onboarding energy on someone who won’t work out. Skip role clarity and your safety conversations get eaten by turf disputes that clear rules would have prevented. Skip safety and your culture work becomes a poster on a wall that nobody believes. The order isn’t arbitrary preference — it’s dependency. Later steps assume the earlier ones are in place, and quietly fail when they aren’t.

The same logic works in any setting. A café owner hires baristas (composition), trains them on the machines and the opening routine (productivity), decides who runs the till versus the bar during a rush (clarity), makes it normal for a new hire to say “I don’t know how to do this” without getting snapped at (safety), and sets the small repeated habits that define the place — how you greet a regular, whether you wipe the tables unasked (culture) — while sorting out the inevitable friction over who closes on Fridays (conflict). Swap the café for a software team, a warehouse crew, or an IT help desk and the six steps are identical; only the details change. That’s what makes them first principles rather than tips: they hold across industries because they follow from what a team fundamentally is.

The common trap — jumping straight to “culture” and “team-building”

When managers decide to “invest in the team,” they often reach first for the visible, feel-good stuff: an offsite, a values workshop, a set of team norms on the wall. Those aren’t wrong, but done first they’re building the roof before the walls. A team-building day cannot compensate for a bad hire, an unclear owner, or a fear of speaking up — and worse, it can paper over those problems just enough to delay fixing them. If your team feels off, resist the urge to schedule a retreat. Walk the sequence from the top: is it the right people? Are their roles clear? Is it safe to be honest? The retreat lands far better once those are true — and is often unnecessary once they are.

A quick map of the two halves

If the six steps feel like a lot to hold at once, collapse them into two halves and one bridge:

HALF 1 — COMPOSITION & CLARITY        (the parts, assembled)
  hiring        → who is on the team
  onboarding    → how fast they contribute
  role clarity  → who owns what

        ── bridge: now that the right people
           own clear work, can they be honest? ──

HALF 2 — CONDITIONS                   (the parts, running well)
  psychological safety → is it safe to speak up
  culture              → what habits repeat
  conflict             → can we disagree and improve

Most managers over-invest in one half and neglect the other. The manager who loves hiring and process but never builds safety ends up with a well-organised team that quietly hides its problems. The manager who is warm and safe but never clarifies roles or hires carefully ends up with a lovely group that misses its outcomes. The whole point of the sequence is that you need both halves, in this order.

The roadmap for this part

Read these in order. Each page answers one question and sets up the next.

#	Page	The question it answers	Why it comes here
2	From a Group to a Team	What actually makes a team more than a group?	Defines the target. You can’t build a team until you know what one is and why interdependence changes everything.
3	Hiring: Defining the Role and Structured Interviewing	How do you choose who’s on the team?	Composition first — the highest-leverage decision you make, and the one hardest to undo.
4	Onboarding: Getting People Productive Fast	How do you turn a new hire into a contributor quickly?	A good hire is wasted if they flounder for months. Onboarding is where hiring pays off.
5	Role Clarity: Who Does What (RACI)	How do you make ownership unambiguous?	Most team friction is unclear who-does-what, not bad people. Clarity removes it before it starts.
6	Psychological Safety: Why It Predicts Performance	Why can some teams surface problems and others can’t?	With the right people in clear roles, the next lever is whether they’ll speak up. It predicts performance more than talent does.
7	Team Culture as a Set of Behaviours	What is culture, concretely, and how do you shape it?	Culture isn’t posters or values on a wall — it’s repeated behaviour. Once the team is safe, you make its habits deliberate.
8	Handling Conflict Within a Team	What do you do when a healthy team disagrees hard?	Every real team has conflict. The skill is making it productive, not eliminating it. This is where the part lands.
—	Revision · Building & Leading Teams	Did it hold together?	A prose recap of the whole arc before you move on.

The thread

If you forget everything else in this part, keep this thread:

CHOOSE who's on the team        (hiring)
   →  get them PRODUCTIVE       (onboarding)
      →  make ownership CLEAR   (role clarity / RACI)
         →  make it SAFE        (psychological safety)
            →  make habits DELIBERATE   (culture)
               →  disagree WELL         (conflict)

Composition and clarity first; conditions second. Get the wrong people or unclear roles and no amount of safety or culture work will save you. Get them right and the later moves compound.

One more thing about that thread: it is not a one-time build. You don’t hire once, clarify once, and coast. People join and leave, roles drift, safety erodes under pressure, culture decays if you stop tending it, and new conflicts arrive with every deadline. Think of the six steps less as a checklist you complete and more as the dials you keep adjusting for as long as the team exists. This part gives you the vocabulary and the moves for each dial; the ongoing work of turning them is the job.

Case study — Toyota’s andon cord

On Toyota’s assembly lines, from the 1970s onward, any worker who spotted a defect could pull a cord (the andon) that could stop the entire production line. On paper this is terrifying — you’re letting a junior worker halt a multi-million-dollar operation. In practice it made Toyota’s quality legendary. The reason is exactly this part in miniature: the cord only works if it’s genuinely safe to pull it (psychological safety), if everyone knows it’s their job to (role clarity), and if stopping the line to fix a problem is celebrated rather than punished (culture-as-behaviour). Treat the specifics loosely, but the lesson is durable: a team’s ability to surface and fix problems early beats a team that hides them to look good. The technology was a cord; the real machinery was trust and clarity.

Hold onto that framing as you read the rest of the part. Every technique ahead — a structured interview scorecard, a RACI grid, a rule for how you respond to a mistake, a way to run a disagreement — is a cord of its own: a small, concrete mechanism whose real purpose is to make trust, clarity, and reliable outcomes the default rather than something that depends on you being in the room. That is what it means to lead a team rather than just supervise a group.

The evidence — what predicts a team that performs

When researchers go looking for what separates high-performing teams from struggling ones, the answer is rarely raw talent or IQ. Google’s multi-year study of its own teams (widely reported around 2015 under the name Project Aristotle) concluded that who was on a team mattered less than how the team worked together — and that the single strongest factor was psychological safety: whether members felt safe to take risks and admit mistakes. Treat the exact ranking loosely, but the direction is robust across decades of team research: conditions beat rosters. That’s why this part spends as much time on safety and culture as on hiring.

The common trap — thinking leadership is charisma you either have or don’t

People assume some managers are just “naturals” — born with the charm that makes teams gel — and the rest are out of luck. That belief is both false and paralysing. Everything in this part is a learnable move: how to define a role before you interview, how to run a structured interview, how to write a RACI, how to respond when someone admits a mistake, how to name a norm out loud. None of it requires charisma. Charismatic managers with no method build teams that look great and quietly fall apart. Methodical managers with no charisma build teams that perform for years. Bet on method.

How it connects

This part depends on the ones before it. The team you build is the vehicle for the manager’s real output — results produced through others. The individuals you hire and grow are managed with the skills from Managing People, and the trust you build here is deepened in One-on-Ones. Later, Ways of Working turns a healthy team into a repeatable operating rhythm, and Culture and Ethics widens the culture idea from one team to a whole organisation.

How to read this part

Whichever of the book’s three readers you are, this part has a use:

• If you’re a new or aspiring manager, read all eight pages in order and do each Try this. This is the part where “leading a team” stops being a vague ambition and becomes a set of specific things you can practise this week.
• If you already lead a team, use the roadmap table as a diagnostic. Read the row whose question you can’t confidently answer about your own team, and start there — you don’t have to go strictly in order once you know the shape.
• If you report to a manager and want to understand them, this part explains the moves a good one is making behind the scenes — and gives you language to ask for what a struggling team is missing (clearer ownership, a safer way to raise problems).

A word on pace: these ideas reward being tried, not just read. A page you apply to your actual team this week will teach you ten times what a page you merely nod along to does. The exercises are short on purpose — the aim is that you close each page and change one small thing, then come back for the next.

And don’t wait to feel “ready” or “senior enough.” You do not need a title or years of experience to run a structured interview, write down who owns what, or thank someone for admitting a mistake. These are moves, not credentials. You can start making them with whatever team you have, at whatever level you are, this week.

Try this

Before reading on, write a one-line honest answer to two questions about the group you lead or belong to. First: are we actually interdependent — do we win or lose together — or are we really a set of individuals who share a manager? Second: of the six things this part builds (hiring, onboarding, role clarity, safety, culture, conflict), which one is our weakest link right now? Keep the note. At the end of the part, you’ll have language for both answers — and a place to start.

Reflect

1. Is the group you spend most of your work time in genuinely a team (interdependent, shared outcome) or a group (individuals with a common manager)? What’s the honest evidence?
2. Think of a team failure you’ve witnessed. Was it a failure of an individual, or of the seam between people — a handoff, an unclear owner, a problem no one felt safe raising?
3. Looking at the six-step sequence, which step do you think your current team is weakest on? Is it a composition problem (who’s here) or a conditions problem (is it safe/healthy)?
4. Have you ever believed a manager was a “natural” who just had it? Looking closer, what specific, learnable moves were they actually making?
5. Which page in the roadmap answers a question you least know the answer to right now? That’s probably the one you need most.

Show reflections

1. The test is interdependence: if any one person’s work quietly depends on another’s, you’re a team, and seams matter. Many “teams” are really groups — and realising that saves you from forcing team rituals on people who don’t need them, or missing the seams if you do.
2. Most memorable failures live in the seams, not the people — the dropped handoff, the task two people each assumed the other owned, the risk everyone saw and no one voiced. Naming it as a team problem points you at clarity and safety rather than at blaming a person.
3. There’s no wrong answer, but the composition-vs-conditions split tells you where to spend effort. If it’s composition, the early pages (hiring, onboarding) matter most; if conditions, the later ones (safety, culture, conflict) are your leverage.
4. This is the “charisma trap” made personal. Look closely and the “natural” was usually doing concrete things — asking a quiet person for their view, admitting their own mistakes, making ownership clear. Those are exactly the learnable moves this part teaches.
5. The question whose answer feels least obvious usually hides an assumption you haven’t examined. If “why can some teams surface problems and others can’t?” or “what even is culture?” feels genuinely open, read those pages slowest.