Communication Batching
Let similar requests accumulate and process them at fixed, infrequent times
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 99%
Communication Batching lets similar requests accumulate and processes them during a small number of fixed windows. Ferriss compares the approach to printing, where setup cost can make three shirts cost nearly as much as 20. Knowledge work carries a similar transition cost, so continuous email checking fragments attention and leaves tasks unfinished. The method combines a schedule with expectation management: an autoresponder tells colleagues when email will be checked, gives an alternative for questions that truly cannot wait, and explains that confirmations may not receive replies. Ferriss recommends avoiding email first thing in the morning and completing the most important 80/20 task before lunch. The mechanism protects uninterrupted work while ensuring accumulated communication still receives predictable attention.
Origin
Ferriss presented batching as the main elimination tactic for knowledge workers and demonstrated it with an email autoresponder he had used repeatedly.
Core principles
- 01Every task transition carries a setup cost
- 02Similar work should accumulate before processing
- 03Fixed response windows reduce task switching
- 04Clear expectations train others to respect communication boundaries
- 05Important work should happen before the inbox shapes the day
How to run it
- 1
Select the batch
Choose a repeated task with meaningful setup or switching cost, such as email. Confirm that it can safely wait between processing windows.
Pro tip Start with email because Ferriss identifies it as a major turning point for knowledge workers.
Watch out Do not batch a task whose delay creates real danger or irreversible loss.
- 2
Set fixed windows
Choose limited, predictable times to process the accumulated work. Keep the windows infrequent enough for a useful batch to form.
Pro tip Ferriss recommends twice daily as a starting point rather than continuous checking.
Watch out A schedule that keeps changing will not reset other people's expectations.
- 3
Publish the boundary
Use an autoresponder to state the schedule, the reason, the urgent alternative, and which messages will not receive a response. Keep the language friendly.
Pro tip Frame the change as a move toward efficiency and effectiveness.
Watch out Silently becoming unavailable can create confusion rather than a workable norm.
- 4
Protect the morning
Do not open the inbox first thing. Complete the single most important task before lunch so incoming messages do not determine the day's priorities.
Pro tip Choose the task through the 80/20 audit.
Watch out Early email checking introduces unrelated ideas before focused work begins.
- 5
Process together
Handle the accumulated messages during the announced windows, using the urgent route only for genuine exceptions. Repeat consistently so others learn the pattern.
Watch out Breaking the rule repeatedly trains people to ignore it.
In the wild
Ferriss proposes an autoresponder telling colleagues that email will be checked at 11:00 a.m. and 4:00 p.m. The message directs questions needing an earlier response to a cell phone and says confirmations or statements will not receive replies.
→ Colleagues receive predictable response expectations while the worker protects uninterrupted blocks of time.
Common mistakes
Checking before the batch forms
Frequent checking preserves the switching cost and prevents enough similar work from accumulating for efficient processing.
Starting the day in the inbox
Ferriss says early email checking scrambles attention with disorganized and unrelated ideas.
Setting a boundary without an escalation path
The proposed autoresponder gives immediate questions a cell-phone route instead of pretending urgent needs never exist.
Is it for you?
Best for
Knowledge workers who spend substantial time in email and can define an escalation route for urgent issues.
Not ideal for
Roles requiring continuous real-time monitoring where delayed responses would create genuine harm.
From the transcript
“So, batching involves letting similar tasks accumulate and then performing them at very limited times, as infrequently as possible to accomplish what it is you…”
“one of the major keys to achieving a 4-hour work week, which is it's not a misnomer, it's not a typo, it this is possible,…”
“Focus on getting the one most important task that you've identified through 80/20 done before lunch so you can't postpone it and use that as…”
From the episode
#548: The Lost Presentation That Launched The 4-Hour Workweek — “Secrets of Doing More with Less in a Digital World” from SXSW 2007