LLM Book Knowledgebase

CPR Framework: Communication, Planning, Resources

7 min read

CPR Framework: Communication, Planning, Resources

Nick Sonnenberg’s Come Up for Air diagnoses a specific organizational disease: teams drowning in work not because they lack effort, but because they are using yesterday’s methods in today’s environment. The solution is not better individual productivity — it is structural alignment on how teams communicate, plan work, and store knowledge.

The book’s central metaphor is a broken sink: the response to an overflowing sink is not to mop faster. It is to fix the sink. Most productivity advice teaches faster mopping. Sonnenberg teaches plumbing.

“Looking back, Leverage was like a broken sink with water overflowing. I had two options: I could mop faster, or I could fix the sink. I decided to fix the sink.” — Come Up for Air

The Scavenger Hunt Problem

Before presenting the solution, Sonnenberg names the problem: the Scavenger Hunt. This occurs when team members cannot find the information they need without interrupting colleagues, searching multiple tools, or starting from scratch.

The Scavenger Hunt is not a symptom of laziness or disorganization — it is the structural outcome of optimizing for the wrong thing:

“Most organizations are set up as what I call ‘push’ communication environments, where information is pushed at you nonstop. This is what happens when you optimize solely for the speed of transfer of information.” — Come Up for Air

The critical insight: speed of transfer and speed of retrieval are different optimization targets that often trade off against each other. Sending a quick Slack message is optimized for transfer. Writing up notes in the knowledge base is optimized for retrieval. The former feels faster in the moment; the latter saves more time in aggregate.

“A business can grow only as fast as knowledge can be retrieved.” — Come Up for Air

“So in order to work effectively as a team, everyone needs to optimize for the speed of retrieval by putting information where it belongs—even if it’s painful, and even if it’s longer in the short term.” — Come Up for Air

The CPR Framework

Sonnenberg organizes the solution into three categories, each corresponding to a class of tools:

C — Communication

Communication is “the oxygen of a business.” The framework prescribes a strict channel hierarchy:

  • Email: External communication only (clients, vendors, partners)
  • Internal communication tools (Slack, Teams): Internal conversations, brainstorming, announcements
  • Work management tools: Task-specific communication, actionable items
  • Meetings: Complex discussions, sensitive conversations, brainstorming requiring real-time interaction

The key principle: every communication channel has a specific purpose. Using the wrong channel creates friction — information ends up where it cannot be found or triggers responses in the wrong context.

“Email should only be used for communicating with people outside your organization.” — Come Up for Air

“Email is just an external to-do list that others can add to.” — Come Up for Air

The boomerang effect: every email you send comes back to you. Reducing outbound email volume reduces inbound volume. Most teams can recover two to three hours per day simply by tightening email discipline.

P — Planning

The Planning category covers work management tools (Asana, ClickUp, Monday.com, Jira) — collaborative systems for tracking tasks, projects, and portfolios.

The distinction Sonnenberg draws is between a project management tool (for projects with defined endpoints) and a work management tool (for all work, including ongoing processes and individual tasks). Work management tools provide:

  • Visibility into who is doing what and when
  • Assignment and accountability tracking
  • Status updates that reduce the need for status meetings
  • Cross-functional coordination without constant interruption

“If you want to know something’s going to get done, it should go in a work management tool.” — Come Up for Air

A good task, properly specified, should include: a clear title with a verb, an actionable description, one owner, a due date, all relevant context, and a definition of done. The definition of done is often omitted — its absence creates enormous rework when interpretations of “complete” differ.

Bandwidth calculation is a practical planning tool Sonnenberg introduces: most people assume they have 40 hours of productive work capacity per week when accounting only for their role. They do not account for meetings, administrative work, and context switching. Calculating true bandwidth prevents chronic overcommitment.

R — Resources

Resources are the least “sexy” but often most impactful category. Resources cover knowledge bases (Notion, Confluence, Coda) and process management tools (process documentation, SOPs, checklists).

The purpose: anything someone needs to know to do their job should be findable without asking another person. This serves multiple functions:

  • Reduces interruptions (everyone stops asking the same questions)
  • De-risks the organization against personnel changes
  • Enables faster onboarding
  • Creates operational consistency

Knowledge bases answer: Who, What, Where, When, Why. Process tools answer: How.

“Critical company information should always be stored and organized in a knowledge base that all employees have access to, so they can quickly find the information they need without distracting coworkers or managers.” — Come Up for Air

Nine Principles of Efficiency

Sonnenberg distills the framework into nine operating principles:

  1. Optimize for the speed of retrieval of information, not transfer
  2. “Your brain is for having ideas, not holding them”
  3. Individual productivity is necessary but not sufficient for team productivity
  4. Focus on work that utilizes your Unique Ability
  5. It’s not the tool; it’s when and how you use it
  6. Fix the sink, don’t mop faster
  7. If something needs to be done more than once, find a way to not do it
  8. True productivity is the sum of many small wins — seconds matter
  9. Time isn’t linear; not all hours are created equal

Async First

A significant tactical theme is asynchronous communication as the default, with synchronous communication (calls, meetings) reserved for situations that genuinely require it:

“One obvious productivity hack is to communicate asynchronously as much as possible.” — Come Up for Air

Situations where synchronous communication is genuinely better: lengthy feedback, brainstorming with many back-and-forth questions, sensitive conversations (promotions, terminations), situations requiring real-time alignment.

Everything else — status updates, questions with known answers, information that needs to be on record — can and should be asynchronous. The result is what Sonnenberg calls a pull environment: team members access information when they need it rather than having it pushed at them continuously.

The Hiring Trap

Sonnenberg is explicit about a common mistake: hiring to solve operational problems before fixing the underlying systems:

“Hiring more people is a knee-jerk solution to many business problems. But it can be self-defeating, because the more people you hire, the more complicated things get.” — Come Up for Air

“Would you rather bring more people into a broken system and fix it later, or fix the system first and bring more people into an efficient system? The answer is obvious. Fix the overflowing sink, don’t mop faster!” — Come Up for Air

This connects directly to Who Not How: Sullivan and Hardy’s framework assumes you are adding Whos to an efficient system. Adding Whos to a broken system amplifies the dysfunction rather than resolving it.

Alignment Is Not Optional

The CPR Framework cannot be implemented by one person or one team in isolation. The value of the system depends entirely on everyone using the right tool for the right purpose, consistently. One person storing critical project information in a direct message rather than the work management tool — just once — can cascade into a Scavenger Hunt for their entire team. This is why Sonnenberg emphasizes team-level agreement and alignment as the prerequisite for tool adoption, not the tool selection itself.

Backlinks