Team: Getting Things Done with Others

The problem it solves

Most teams are not short of talent or tools. They are short of agreements. Work arrives through email, chat, meetings and hallway requests, nobody has a full picture of what has been promised, and the leader says yes because the true workload is invisible. The book argues that this is a system problem rather than a personal failing, and that clever individual habits only go so far when the team around them is noisy.

What changes after reading it

You start looking at the mechanics. Does every meeting have a purpose, an end time and a named owner for each next step? Does the team have one list of its larger projects that it reviews each week? Do people know which channel to use and how fast a reply is expected? The authors give concrete answers, including a worked example of a channel contract with response times, and a simple rule for meetings that most teams could adopt tomorrow.

I also like the order of the book. It starts with the five working steps of capture, clarify, organise, reflect and engage, then moves up through purpose, vision, goals and roles. That means you can start with the dull, practical fixes and add the bigger conversations later.

When to read it, and when not

Read it when your team has grown past the point where everyone just knows what is going on, or when you have just taken over a team and want to set standards early. It is also useful when a team keeps missing deadlines and nobody can say why.

Do not expect help with personality clashes, hiring, motivation or conflict. The authors say plainly that they are covering team mechanics and not team building. If you have never used the personal method behind it, you can still use the book, but a short refresher is included in an appendix and the earlier books go deeper.

The chapter I would read twice

The chapter on saying no is the one I would keep nearby. Its argument is that a team cannot protect its focus until it can see all of its commitments, and that every new yes should be paired with the question of what the team will let go of. For a small company where the owner is the bottleneck, that single habit pays back quickly.

How it connects to decisions and repeatable work

Two ideas map well onto running a business that wants to hand work to other people, and eventually to software. The first is documenting the reasoning behind a standard, not only the rule, so that a decision still makes sense to someone who joins a year later. The second is the delegation conversation: agree the outcome, the deadline, the resources and how you will stay in touch. The authors note that the same clarity is needed when you hand work to an AI assistant, because without a clear brief it either idles or does too much. Work that has an owner, an outcome and a reason is work you can later turn into a playbook.

The book argues that team overwhelm is mostly a design problem. Give a team shared standards, one visible list of commitments and clear roles, and the people on it can do their work without constant noise.

Introduction

The authors start from the personal method set out in their earlier books and ask what happens when it is applied to a group. They cite a 2022 Gallup report finding that only 21 percent of employees are engaged, and argue that numbers like that point at teams and organisations, not at individuals. Their football comparison gives the frame: you can raise individual skills, improve how players work together, or shape the team's identity, and the book is about the second and third. They want "healthy high performance", meaning results that a team can sustain without burning people out. They are clear that this is team mechanics, not team building or conflict resolution, and that you can use the book in pieces.

Chapter 1: When "Teamwork" Doesn't Work for the Team

The opening chapter describes what unhealthy work looks like: too much incoming information, too many channels, constant interruption and rapid turnover in who counts as on the team. Leaders are caught in firefighting, so nobody does the strategic work on structure. The authors reject the idea that new tools will fix this. As they put it, "If you automate a mess, you only end up with an automated mess." They also point to organisations with more than a hundred key initiatives, which means none of them is a priority. The chapter ends with a picture of a better team: clear purpose, reliable turnaround on requests, mostly asynchronous work, few and effective meetings, and colleagues who feel free to say no.

Chapter 2: New World, New Work

This chapter sets the context. Work is moving away from fixed places and command-and-control hierarchies, and a family of methods has grown up around that shift. The authors give a short tour of Lean, Holacracy and Agile or Scrum, with a sales-approval process of six levels as an example of what those methods reacted against. Holacracy's move from job titles to roles with accountabilities is highlighted, and so is the difference between formal Agile and working in an agile way. Their point is that all of these methods rely on individuals who can keep their own commitments. If you want a self-organising team, they say, you need the selves to be organised.

Chapter 3: What Is a Team? Why Are They Important?

A team is defined by its purpose, and the authors name five principles that make one work: clarity, sufficient trust, open communication, learning and diversity. Trust here means a team member's willingness to commit to shared goals and keep their promises, not warmth. A longer list of nice-to-haves follows, including fluid leadership, an ownership culture, fun, proactivity and a common language. The chapter ends with a two-way contract. Individuals should bring self-mastery and the ability to make, track and renegotiate agreements. The team should offer clear structures, defined roles, guidance on priorities and protection of time to think.

Chapter 4: Maintaining Control and Focus

The five working steps are applied to a group. Capture means writing down commitments as they are made, because broken agreements wear down trust, and a team mind sweep asks what currently has the team's attention. Clarify means asking what the desired outcome is and what the next action is, who owns it and by when. Organise means keeping a shared list of the team's larger projects, a master calendar and a team reference store with someone looking after it. The authors suggest a small "p" for personal projects and a capital "P" for team ones. Reflect means reserving a few minutes in each meeting to review how the team worked, plus a weekly review. Engage means choosing priorities with the whole picture visible.

Chapter 5: Horizon Five, Purpose and Principles

Here the book moves from controlling today's work to the higher horizons that explain why the work exists. Ideally every new joiner hears on day one why the team exists, how it plays together, where it is going, the milestones on the way and what their own role is. To write a purpose, take the team somewhere away from the office and ask why it exists or what problem it solves. Do not get stuck on wording on the first pass, and expect someone to claim the purpose is to make money. The authors treat that as a side effect of serving the purpose well. Review it once or twice a year. Principles are how the team agrees to play together, and both authors include their own company's list as examples.

Chapter 6: Horizon Five, Principles Redux

This chapter is about working standards, which the authors treat as the practical form of principles. It opens with a sales visit where nobody arrived on time, and moves to three simple rules for meetings: everyone knows the purpose, everyone knows what done looks like and by when, and nobody leaves without next actions and owners. It lists five reasons to meet: to give information, get information, develop options, make decisions and build human connection. A channel contract from a client sets out which medium to use for which purpose and the expected reply time for each. The authors insist on writing down the logic behind each standard, because a rule without a reason reads as arbitrary to the next person who joins.

Chapter 7: Horizon Four, Vision

A vision answers what wild success would look like in three to five years. The authors say the hard part is allowing yourself to want what you really want, rather than only what you expect to get. They suggest each person writes a future article about the team's success, and show a case in which an infrastructure advisory team set a goal of building a global business earning a billion dollars. Vision is for dreaming without worrying about the plan. The chapter ends with advice on keeping it alive by revisiting it, so it keeps shaping choices.

Chapter 8: Horizon Three, Goals

Goals turn the vision into milestones with a plan. The authors describe how one of them set a vision of growing revenue tenfold in some European markets, then broke it into goals once it was clear that more travel could not achieve it. Where vision needs the dreamers, goals need the detail people. The recipe is to diverge on ideas, converge on a few high-impact targets, plan enough to start and follow up consistently. Goals fail when there are too few ideas, unclear owners, vague definitions, lists inflated by enthusiasm and politics, or loose follow-up.

Chapter 9: Horizon Two, Areas of Focus and Accountability

Roles link the lofty horizons to daily work. The chapter argues that unclear accountability is fine for a while and then causes chaos, because nobody is sure who tracks commitments, owns the calendar or reports upwards. One method builds an organisation chart from the bottom, starting with the final product and the outputs needed to produce it. A solo entrepreneur wears every hat, and a larger company splits them. Most people can name four to seven areas they are accountable for, and the same holds for a team. Written roles also make handovers fast, as a pair of successors who compared their lists showed.

Chapter 10: Planning (and Replanning) in a Complex, Fast-Moving World

The Natural Planning Model has six steps: purpose, principles, vision, brainstorm, organise and next actions. For teams its value is to surface differing views of why a project exists before anyone starts work. The authors give timings for a twelve-minute version and an hour-long group session, and the aim in both is a rough plan that tells you the next action rather than a perfect one. They also describe using it to set up a new team over two days, to hand over a large project in an hour, and to plan the book itself. Teams that arrive at a meeting with a rough first plan, they say, avoid starting from scratch on every initiative, and the same habit helped a broadcaster break an overwhelming change into next actions.

Chapter 11: The Structures of Leadership

The authors set aside charisma and focus on the mechanics of running a team. Their image is the leader as gardener, who cannot make plants grow but can tend the soil and keep weeds out. That means keeping yourself from becoming the bottleneck, clarifying who may decide what, and delegating quickly. The practical habits are concrete: capture commitments in front of the team, protect daily thinking time, keep a complete view of what the team has committed to, give a one-day response on email, and think about the signals sent by after-hours messages. They cite a large email study linking faster leader replies to higher team satisfaction.

Chapter 12: If You Don't Have a No, Your Yes Means Nothing

Saying yes too often hides opportunity costs, damages reputation and leaves no space to spot root causes. Using queuing theory, the authors explain why knowledge work does not slow down gradually under load but breaks down, and why running everyone near full utilisation makes a team slow to coordinate. Overwhelm is a systemic problem, so a team needs a collective no, built on one visible list of commitments and regular pruning. The test question is "If we are taking this on, what are we letting go of to give us space to get it done?" Three models are offered: the Eisenhower matrix, impact against effort, and a simple do, maybe later or drop split.

Chapter 13: Delegation That Works

Leaders often cling to work because control feels safer, and the chapter pushes them to only do what only they can do. The authors summarise Fernando Flores's four phases of a delegation conversation: preparation, negotiation, delivery and satisfaction. In negotiation the other person has more options than yes, namely asking for more information, committing to respond later or making a counteroffer, and both sides agree the conditions of satisfaction. They call skipping that agreement the biggest source of failed delegation, and note that the same clarity is needed when briefing AI assistants.

Chapter 14: So What? Now What?

The closing chapter treats the book as a menu rather than a course. The authors urge readers to pick the one or two problems most pressing for their team, try the matching practices and return for more. They warn that knowing about something is not the same as doing it, and that small changes practised over time beat radical ones. A committed core group makes everything easier, and if you lack one, forming it may be your first project.

Appendices

Appendix 1 is a condensed refresher on the five steps, the six horizons of focus and the planning model for readers new to the method. Appendix 2 gives questions for deciding how a team should use collaborative software, sample protocols for channels and threads, and three ways to run a shared inbox: rotation, grab it and dispatcher. Appendix 3 covers working well in a virtual or hybrid world, weighing the pros and cons and listing practices that make remote work function.

What to do with it

• Pick one recurring meeting this week and add the three rules: a stated purpose, a defined finish and named next actions before anyone leaves.
• Hold a team mind sweep, then build a single list of the team's larger projects and review it every week.
• Write a short channel contract that names each medium, what it is for and the expected response time, with a line on why.
• Run a prune session on the project list and ask of each new request what you will let go of to take it on.
• Choose one task you hold on to and delegate it with an agreed outcome, deadline and resources, using a short conversation rather than a message.