Come Up For Air

The central claim is that the time a company loses is structural, not personal. It disappears into the seams between people: the ping that arrives mid-thought, the status meeting that exists only because nobody trusts the tracker, the four tools that each hold a third of the answer so every question becomes a small search party. None of that is anyone's fault, and none of it is fixed by trying harder. It is the cost of a team that never explicitly agreed on how it would work together.

The book calls that cost the coordination tax, and its first job is to make it visible. Most leaders have a strong intuition that their week is being eaten and no vocabulary for saying by what. Teams can rarely name the specific mechanisms: where work is tracked versus where it is discussed, which channel carries a decision and which carries noise, what happens to a question when the one person who knows the answer is on holiday. Naming them is what makes the argument concrete enough to act on.

The second job is the fix, and it is deliberately unglamorous. Decide where work lives. Decide where conversation lives. Decide where a decision gets written down so it survives the meeting. Then defend those boundaries hard enough that the team stops re-litigating them every week. The system is not clever. It is agreed, which is the part organisations reliably skip.

It runs diagnosis first, installation second. The early material is about seeing clearly, auditing where the week actually goes rather than where you assume it goes, because a team that installs a new system on top of an unexamined one simply adds a seventh tool to six. The later material is sequenced: the changes are ordered so each one makes the next cheaper, rather than asking a company to change everything on a Monday.

The method has a name and three parts: the CPR® Business Efficiency Framework — Communication, Planning, Resources. Communication covers where conversation happens and what each channel is allowed to carry. Planning covers where work is tracked, so status is something you look at rather than something you ask for. Resources covers where knowledge lives, so an answer outlives the person who happens to hold it. Nearly every specific fix in the book lands under one of the three, which is what stops it reading as a list of tips.

It is short on anecdote for its genre and long on procedure. If you want a narrative about a founder's turnaround, this is the wrong shelf. If you want something a chief of staff can open on page one and run against a real team, it is written for that.

Team leads, operations leaders, chiefs of staff, and founders somewhere past the size where everyone still knows everything by default. That is roughly the point at which people start asking each other for status instead of seeing it. It suits anyone who has already bought the tools and is now quietly wondering why the week did not get shorter.

It is a poor fit for someone looking for a personal morning routine, and a poor fit for a team that cannot change how it works. The method needs enough authority behind it to make an agreement stick. One motivated individual reading it in isolation will get sharper personally and will not move the organisation.

The book's own site carries the current editions and retailers, including Amazon, Barnes & Noble, Books-a-Million, Bookshop.org, IndieBound and Audible.

It is worth reading as a group rather than alone. The argument is about how a team works together, so one person applying it privately gets sharper while the organisation stays exactly where it was — which is the failure the book spends its first chapters describing.