How to Batch Your Work and Stop Context Switching
You touched 14 different tasks before lunch and finished none of them. You've been busy all day but can't point to a single completed deliverable. Your to-do list is longer at 5 PM than it was at 8 AM. The problem isn't that you have too much to do. It's that you're doing everything at once, and the constant switching is eating your productivity alive. Here's how to stop.
What a Day Without Batching Actually Looks Like
Here's an actual Tuesday for Maya, a marketing consultant. She's not lazy; she's just doing everything at once. Watch the switch counter climb.
| Time | Task | Category | Switch # |
|---|---|---|---|
| 8:00 AM | Check email (12 messages) | Communication | |
| 8:18 AM | Reply to client about scope change | Communication | #1 |
| 8:24 AM | Start writing blog post draft | Creative | #2 |
| 8:31 AM | Slack notification: answer team question | Communication | #3 |
| 8:36 AM | Back to blog post. Re-read what you wrote. | Creative | #4 |
| 8:42 AM | Email from Rachel: review contract redlines | Admin | #5 |
| 8:55 AM | Back to blog post. Where were you? | Creative | #6 |
| 9:00 AM | Calendar reminder: prep for 9:30 call | Meetings | #7 |
| 9:08 AM | Searching for the brief you need for the call | Admin | #8 |
| 9:15 AM | Quick email check while waiting | Communication | #9 |
| 9:30 AM | Client call | Meetings | #10 |
| 10:15 AM | Post-call notes + follow-up emails | Communication | #11 |
| 10:30 AM | Back to blog post. Again. | Creative | #12 |
Why Context Switching Hurts More Than You Think
A morning like Maya's survives on a few comforting beliefs. Each one sounds reasonable, and each one carries a measurable cost.
Myth: "It only takes a second to check email"
Reality: Each switch costs 23 minutes of cognitive recovery. You don't feel it because you never reach full focus.
Myth: "I'm good at multitasking"
Reality: No one is. What you call multitasking is rapid switching with degraded performance on every task. Studies show a 40% productivity loss.
Myth: "I need to be responsive"
Reality: Most messages don't need a response within 2 hours, let alone 2 minutes. You're optimizing for perceived responsiveness at the cost of actual output.
Myth: "Small tasks are quick to knock out"
Reality: The task takes 3 minutes. The context switch costs 23. You spent 26 minutes on a "quick" task and your deep work is gone.
The 4-Category Batching System
Every task you do falls into one of four categories. Batch them together and you eliminate 80% of context switches.
Communication
- Tasks: Email replies, Slack messages, text follow-ups, quick updates
- When: 10-10:30 AM, 2-2:30 PM, 4:30-5 PM
- Frequency: 3x per day
Creative / Deep Work
- Tasks: Writing, strategy, proposals, design, code
- When: 8-11 AM (before first comm batch)
- Frequency: 1 unbroken block
Admin / Operations
- Tasks: Invoices, contracts, scheduling, file organization
- When: 1-2 PM (post-lunch, low energy)
- Frequency: 1x per day
Meetings
- Tasks: Client calls, team syncs, 1:1s
- When: 11 AM-12:30 PM or 3-5 PM
- Frequency: Batched into 1-2 blocks
Same Tasks, Batched: Maya's Tuesday Reimagined
Same meetings, same emails, same deliverables. But grouped by type instead of scattered by arrival.
| Time | Block | What happens | Energy |
|---|---|---|---|
| 8:00–10:30 AM | Deep Work | Blog post draft completed. Email closed. Phone in drawer. One task, one block. | Peak |
| 10:30–11:00 AM | Communication | Process all email. Reply to Slack. Send 3 follow-ups. Done in 25 minutes. | Medium |
| 11:00–12:00 PM | Meetings | Client call + team sync. Back to back. No gaps. | Medium |
| 12:00–1:00 PM | Lunch | Actual lunch. Not "lunch + email." | Recharge |
| 1:00–2:00 PM | Admin | Invoices, contract review, scheduling. Low-cognitive tasks during low-energy time. | Low |
| 2:00–2:30 PM | Communication | Second email batch. Clear the queue. | Medium |
| 2:30–4:00 PM | Deep Work | Second focus block. Client proposal section 2. | Recovery peak |
| 4:00–5:00 PM | Meetings + Wrap | Final call. Last email batch. Plan tomorrow. Clean close. | Winding down |
Stop switching. Start batching.
alfred_ handles the email and task batches automatically, so you can focus your batching system on the work that actually requires your brain.
Try nowFrequently Asked Questions
What if I get an urgent email during a deep work block?
Truly urgent things are rare, and they usually come as phone calls, not emails. If something is genuinely urgent, people will find you. For the 99% that isn't urgent, it can wait 90 minutes. Set expectations with your team: "I check email at 10:30 and 2:30."
How do I start batching if my whole day is reactive?
Start with one batch. Just email. Pick 3 times per day and commit for one week. That alone will free up 1-2 hours of cognitive recovery time. Once that feels natural, add a deep work block. Build gradually.
Does batching work for client-facing roles?
Especially for client-facing roles. Clients don't need instant replies. They need good replies. A thoughtful response at 2:30 PM is worth more than a rushed one at 8:31 AM. Batching actually improves response quality.
How long should each batch be?
Communication batches: 20-30 minutes. Deep work blocks: 90-180 minutes. Admin: 30-60 minutes. The key is that batches have a hard start and stop. When the timer ends, you move to the next batch.
What about Slack and real-time communication?
Batch it with email. Check Slack 3x per day, not 30x. Set your status to "Deep work, back at 10:30." Most Slack messages are informational, not urgent. The ones that are will still reach you.
About the editorial team
Connor is the founder and CEO of alfred_, focused on making personal assistants accessible to business operators and individuals so they can focus on what matters and what’s important.