CPR Method
Organize communication, planning, and resources to reclaim productive time.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 99%
The CPR Method divides operational efficiency into three connected systems: Communication, Planning, and Resources. Communication defines where conversations belong and reduces inbox or messaging overload. Planning creates a visible work-management layer where people can identify responsibilities, priorities, and project status without requesting updates. Resources capture SOPs, processes, and reusable knowledge so recurring work does not depend on memory. The mechanism is cumulative: weak planning produces more questions, weak resources create repeated explanations, and both increase communication volume. By auditing all three buckets and assigning each type of information a dependable home, a team reduces scavenger hunts, interruptions, and administrative work. The resulting capacity can be redirected toward process improvement, higher-value work, and growth.
Origin
Nick Sonnenberg developed the method while rescuing Leverage after rapid growth left its 150-person remote team overloaded and financially unstable.
Core principles
- 01Treat operational overload as a systems problem.
- 02Make information accessible without interrupting another person.
- 03Use dedicated systems for communication, planning, and resources.
- 04Improve connected workflows together rather than optimizing tools in isolation.
How to run it
- 1
Audit Lost Time
Identify recurring activities that consume time without creating proportional value. Group the findings according to communication, planning, or resources.
Pro tip Start with the work that repeatedly delays senior decision-makers.
Watch out Do not treat visible busyness as evidence that the underlying workflow is necessary.
- 2
Clean Up Communication
Define which channels should carry which kinds of messages, then reduce unnecessary responses and interruptions. Make urgent, asynchronous, and reference information distinguishable.
Pro tip Begin with email because individuals can improve it without requiring immediate team-wide adoption.
Watch out Adding another communication tool without usage rules can make the scavenger hunt worse.
- 3
Make Work Visible
Use a planning or work-management system to expose owners, next actions, deadlines, and project status. Design it so common questions can be answered without waiting for another person.
Pro tip Test whether a leader can find the answer to a routine status question within two clicks.
Watch out A project tool that is not consistently updated will generate more follow-up communication.
- 4
Centralize Resources
Document how recurring work is performed, including SOPs, standards, and decision guidance. Give each resource a clear and searchable home.
Pro tip Document the processes whose failure would create the greatest disruption.
Watch out Documentation distributed across multiple competing repositories recreates the original search problem.
- 5
Improve the Whole System
Review how each bucket affects the others and repair connected failure points together. Repeat the audit as the team, tools, and work change.
Pro tip Track interruptions, search time, and repeated questions as leading indicators.
Watch out Optimizing one tool in isolation may simply shift work into another bucket.
In the wild
After Leverage grew to 150 people, Nick was consumed by email, Slack messages, status questions, and process problems. He separated the operational burden into communication, planning, and resources, then improved each system so he could recover time for deeper repairs.
→ The business began turning around and the method became the basis of his consulting work.
A growing marketing team routes conversations through Slack, manages deliverables in Asana, and stores institutional knowledge in Notion. It audits overlaps, defines what belongs in each system, and links tasks to the relevant procedures.
→ Team members can find decisions, work status, and instructions without repeatedly interrupting colleagues.
Common mistakes
Treating Tools as Independent
Planning failures increase communication, while missing resources create repeated questions. Repair the connected workflow rather than declaring one application the entire problem.
Creating Multiple Sources of Truth
A tool stack becomes a scavenger hunt when the same information may live in several places. Assign each information type a clear home.
Waiting Until There Is Spare Time
Operational repair requires an initial time investment, even when the team already feels overloaded. Start with the highest-leverage source of wasted time to create capacity for later improvements.
Is it for you?
Best for
It is best for growing teams whose members waste time searching, asking for updates, or reconstructing recurring procedures.
Not ideal for
It is not ideal for solo operators whose main constraint is demand generation rather than operational coordination.
From the transcript
“So I call that communication. So that's the C of CPR right?”
“So I knew this planning was another thing. Like I wanted to be able to click a button and just be able to answer any…”
“And then the last part was resources. So how does everything work? What are the SOPs? The processes?”
From the episode
How to Reclaim Your Time and Boost Business Productivity with Nick Sonnenberg
Nick Sonnenberg