Batch Processing Life
Some things require internet. The strategy is not to avoid them—it is to batch them.
The Continuous vs. Batch Spectrum
Continuous processing: Checking email constantly. Responding immediately. Browsing throughout the day.
Batch processing: Checking email twice daily. Responding in blocks. Browsing in designated windows.
Continuous processing is the default because it feels productive. You are always doing something.
Batch processing is more effective because it protects attention. You do fewer things, but each thing is done with full focus.
What to Batch
Nearly all online tasks can be batched:
Communication: Email, messages, social media. 2-3 times per day, specific times.
Research: Questions accumulated offline. One research session per day.
Updates: News, feeds, content. Once per day, time-limited.
Downloads: As discussed—batched into specific windows.
Admin: Banking, forms, logistics. Weekly or as-needed blocks.
Social: Posting, engaging, connecting. Specific scheduled times.
The key is moving from reactive to scheduled.
The Batching Framework
Structure your batches:
Define the tasks: What exactly will you do in this batch? List before starting.
Set a time limit: 30 minutes for email. 20 minutes for research. Timers help.
Do the batch: Work through the tasks. Focus on completion, not perfection.
Exit cleanly: When the time ends or tasks are done, disconnect. No lingering.
Return to offline work: Back to creation, deep work, or rest.
Email Batching
Email deserves special attention because it is the biggest time sink:
Morning batch (15-30 minutes): Process everything from overnight. Respond to urgent items. Flag items for later. Archive the rest.
Afternoon batch (15-30 minutes): Same process. Clear the day's accumulation.
What this means: You check email twice. That is it. Everything else happens in batches tomorrow or in the next batch today.
But what about urgent things? Very few emails are truly urgent. The feeling of urgency is usually manufactured.
The Accumulation Method
While offline, accumulate tasks for batches:
The question list: Things you need to research. Write them down. Research in batch.
The response queue: Messages you need to send. Draft them offline. Send in batch.
The read-later pile: Articles you want to read. Save URLs or titles. Read in batch.
The admin list: Things requiring online action. Note them. Do them in weekly admin batch.
This accumulation means offline time is not interrupted by "I need to quickly..."
Setting Expectations
Batching requires setting expectations:
With others: "I check email at 9am and 4pm. Response within 24 hours for non-urgent items."
With yourself: "I do not check randomly. I wait for batch time."
Most people adapt to this quickly. Most "urgent" things are not actually urgent once you remove the always-available expectation.
The Benefits of Batching
When you batch online tasks:
Offline time is protected: No interruptions during deep work.
Transitions are minimized: Context switching costs are reduced.
Tasks are completed faster: Focused batch time is more efficient than scattered checking.
Anxiety decreases: You know when you will handle things. No need to constantly check.
Attention is preserved: The primary benefit. Your focus stays intact.
Sample Daily Schedule
Here is a batched day:
7:00 - 8:00: Morning routine (offline) 8:00 - 8:30: Morning email batch 8:30 - 12:00: Deep work block (offline) 12:00 - 12:30: Midday batch (research, messages) 12:30 - 1:30: Lunch (offline) 1:30 - 4:30: Creation block (offline) 4:30 - 5:00: Afternoon email batch 5:00 - 6:00: Wrap up, planning (offline) Evening: Personal time, possible evening batch if needed
Total online time: ~1.5 hours Total offline time: ~9 hours
Compare to the average always-connected worker: ~9 hours online, constant interruptions.
Implementing Batching
Start with one change:
Week 1: Batch email to twice per day.
If that works:
Week 2: Add batched research/browsing.
Then:
Week 3: Add batched communication (messages, social).
Build gradually. Perfect is not the goal. Better is the goal.
Batching transforms how you relate to the internet. From an always-running stream to a scheduled resource. From master to tool.
Next: The unexpected benefits of living with constraints.