🪴 GoDeep Search
← Bookshelf

Habits & Productivity

Come Up for Air: How Teams Can Leverage Systems and Tools to Stop Drowning in Work

Nick Sonnenberg

Most teams are drowning not in work but in work about work — and the fix is which tool goes where.

2023 Read 2025/03/18 ★★★★★ 4 min read

Nick Sonnenberg runs an operational efficiency consultancy and came to it from high-frequency trading, where shaving milliseconds off a process was the entire business. This book applies that instinct to knowledge work. His diagnosis is that teams are not overwhelmed by the actual work; they are overwhelmed by the coordination surrounding it — the status chasing, the duplicated messages, the search for a decision someone made in a thread three weeks ago. He cites research putting well over half of the working day in this category, and argues that the accumulation of small, individually trivial inefficiencies is what makes competent teams feel permanently underwater.

The core argument

Sonnenberg’s central move is to insist the problem is structural rather than personal. Individual productivity advice fails at team scale because the friction lives in the seams between people. His summary of the mistake is memorable: “Fix the overflowing sink, don’t mop faster!” Working harder inside a badly designed system just produces a tired team inside a badly designed system.

The remedy is his CPR framework — Communication, Planning, Resources — which he presents as the three domains every team must consciously design. Communication covers where conversations happen. Planning covers where work is tracked. Resources covers where durable knowledge lives. The failure mode he attacks hardest is collapsing all three into email and chat, so that tasks, decisions and reference material all end up buried in an undifferentiated stream that nobody can search.

From there the argument is about tool discipline rather than tool choice. Sonnenberg is largely agnostic about which platforms you pick; his insistence is that each category of information has exactly one home, that everyone knows what that home is, and that the rules are enforced. He also makes a good point about scale: every person added to a team multiplies the number of communication channels, so hiring to solve an overload problem often deepens it. Fix the system before you fix the headcount.

Key ideas

  • CPR. Communication, Planning, Resources as three distinct domains, each needing its own designated tool and its own agreed conventions.
  • Retrieval over transfer. The expensive activity is not sending information but finding it later, so structure documentation around how it will be searched.
  • Email is for outside; chat is for inside. Internal discussion moves to a chat platform, email is reserved for external correspondence, and neither is a task list.
  • Unread zero is not inbox zero. Having read a message does not mean the work is done; Sonnenberg’s triage method routes every item to a reply, an archive, or a deferred task.
  • Asynchronous by default. Meetings are treated as an expensive last resort, with structured written updates replacing most standing syncs.
  • Protect high-value hours. Not all working time is equally productive; identify your team’s best hours and defend them from coordination overhead.
  • Complexity scales faster than headcount. Communication paths grow disproportionately with team size, which is a hidden cost of hiring.

Who it’s for

This is a book for whoever has the authority to change how a team works — a manager, an ops lead, a founder. Read individually it will mostly frustrate you, because almost every recommendation requires collective adoption to pay off. Read with a team you can actually reorganise, it is one of the more immediately actionable books in this area: the CPR structure gives you a checklist, the design is clear, and Sonnenberg alternates sensibly between principle and specific practice.

The fair criticisms are that it is longer than its content requires — the inbox material in particular circles back several times, which sits awkwardly in a book about eliminating waste — and that it functions in part as a shop window for the author’s consultancy, with case studies drawn from his own client roster and no serious engagement with implementations that failed. Some of the tool-specific advice will date quickly. And there is an unaddressed tension: a system this prescriptive requires meaningful ongoing enforcement, which is itself a form of work about work. Worth reading for the framework; skim the middle.

An original summary of this book's ideas — not an extract from the book itself.