How teams can stop drowning in work using the CPR framework

Executive overview

Most teams waste half their working hours on communication chaos, document scavenger hunts, and unfocused meetings — not on actual work. Nick Sonnenberg built the CPR framework (Communication, Planning, Resources) after nearly losing his company and discovering that individual productivity tools alone cannot fix team-level dysfunction.

Individual productivity is necessary but not sufficient. Teams need shared systems, agreed channels, and disciplined planning to compound individual output into collective results.

The core insight: if your team doesn't share a single system for where information lives and how work is tracked, every person is solving the same coordination problem independently — and losing hours every day doing it.

The CPR framework

• Communication — where information flows
• Planning — what people are working on and when
• Resources — documented knowledge, processes, and intellectual property
• All three must be addressed at the team level; fixing only one leaves the others as bottlenecks

Why individual productivity isn't enough

• The 2004 US Olympic basketball team had elite individual players but trained together for only a month — they lost to Puerto Rico and won bronze
• Knowing your own productivity tricks doesn't help when your teammates operate differently
• Sometimes individual sacrifice is required for collective output
• Research shows only ~50% of people's time is spent on their core skill or work that gives them joy

Communication: eliminating the scavenger hunt

• Use a clear channel hierarchy: text for personal, email for external, Slack/Teams for internal
• Without a hierarchy, finding any piece of information requires checking every channel
• Agendas are the most underused communication tool — park non-urgent items there instead of pinging someone
• Interrupting a colleague's flow state costs ~15 minutes to recover (Cal Newport, Deep Work)
• Turn off all notifications; set intentional check-in windows instead of reacting to every ping
• Don't ping someone for something that can wait until next week's meeting — it may resolve itself

Email: the RAD system

• RAD = Reply, Archive, Defer — the only three actions any email needs
• No need for elaborate folder systems
• Use snooze to make emails disappear and reappear when relevant
• Inbox zero is achievable with the right settings and mindset
• Leaders must not expect five-minute email responses — that expectation forces everyone to stay in reactive mode

Meetings: reduce cost, shift time

• Every meeting has a calculable cost: annual salary ÷ 2,000 = hourly rate; multiply by attendees and duration
• US businesses waste over $30 billion annually on inefficient meetings
• Levers to pull: fewer attendees, lower frequency, shorter duration, or eliminate entirely
• Async tools like Loom let one person record a screen share or update — freeing live meeting time for decisions only
• Pre-watch or pre-read materials in low-focus windows (commutes, between tasks) rather than consuming them in prime calendar time
• Not every hour is worth the same — protect high-horsepower morning blocks for deep work
• Tools like Fireflies.ai record, transcribe, and summarise meetings; attendees can skip and catch up later at 1.5x speed

Effective meeting hygiene

• Always have a written agenda — it forces focus and reduces intraday pings
• Log key decisions in the company wiki (the R in CPR)
• Capture action items into your planning tool (the P in CPR) immediately, not in chat or memory
• Rate meetings 1–5 at close; if below 3, ask why — create a feedback loop
• Consider structured formats (e.g., Traction's Level 10 meeting) with wins, challenges, and agenda items

Planning: visibility across the team

• Leaders need to answer at a glance: what is each person working on, what is overdue, what should I prioritise?
• Without a shared planning tool, these basics require interrupting people to find out
• All action items from meetings should land in the planning system, not in Slack or email threads

Resources: the knowledge base

• Document how recurring tasks are done — onboarding, payroll, core values, processes
• A well-organised company wiki is not a replacement for Google Drive/Dropbox; it links to them
• Key decisions made in meetings should be logged so context is never lost
• This layer compounds over time — new hires onboard faster, fewer questions get asked repeatedly