How to Batch Tasks with the Pomodoro Technique
Stop mixing email with deep work. Here's how to group tasks so your focused hours stay focused.
Most people don't have a productivity problem. They have a context-switching problem. They sit down to write a report, check one email, draft a paragraph, reply to a message, write another paragraph, check Slack, and wonder why two hours passed with barely a page written. The problem isn't effort — it's mixing tasks that require fundamentally different cognitive modes.
Task batching solves this by separating your day into dedicated blocks: deep work blocks for complex, demanding tasks, and shallow work blocks for everything else. The Pomodoro Technique provides the structure. Batching provides the strategy. Together, they create a workday where every type of task gets the right amount of attention in the right context.
What Is Task Batching?
Batching means collecting similar tasks and handling them together in a single block, rather than sprinkling them throughout your day. Instead of checking email every time a notification pops up, you dedicate one or two Pomodoro sessions to processing your entire inbox. Instead of responding to messages throughout the day, you batch all replies into a 25-minute session.
The cognitive benefit is significant. Every time you switch from one type of task to another — from writing to email, from coding to Slack, from reading to messaging — your brain pays a "switching cost." Research from the American Psychological Association shows that this cost can consume up to 40% of your productive time over the course of a day. Batching eliminates most of these switches.
Think of it like laundry. You don't wash one shirt, then dry it, then wash another shirt. You batch: collect all the laundry, wash it together, dry it together, fold it together. Your workday should operate the same way.
Which Tasks to Batch vs. Protect for Deep Work
Not all tasks are equal, and the first step in effective batching is sorting your tasks into two categories: deep work and shallow work.
Deep work includes tasks that require sustained concentration and produce your most valuable output: writing, coding, designing, strategic planning, research, and creative problem-solving. These tasks need uninterrupted deep work sessions of 45–90 minutes to reach peak quality. They should never be batched with anything else. Protect these hours fiercely.
Shallow work includes tasks that are necessary but don't require deep thought: email, scheduling, expense reports, routine communications, file organisation, status updates, and administrative tasks. These are perfect for batching. They're individually quick, cognitively light, and benefit from momentum — once you're in "admin mode," clearing ten small tasks in a row feels efficient rather than tedious.
The key insight is that shallow work isn't unimportant — it just needs a different type of attention. By containing it to dedicated sessions, you stop it from contaminating your deep work hours. A focus timer with a clear intention ("process all email") makes these batched sessions surprisingly satisfying.
A Sample Batched Day
Here's what a typical batched workday looks like using the Pomodoro Technique. This isn't a rigid template — adapt it to your schedule, energy patterns, and role. The principle is consistent even if the specifics change.
Morning: Deep work block (3–4 Pomodoros). Start your day with your most demanding task. Use 50-minute or 45-minute sessions for work that requires sustained immersion. Don't check email. Don't open Slack. Your morning brain is your sharpest tool — don't waste it on inbox triage.
Late morning: Communication batch (1–2 Pomodoros). After your deep work block, switch modes. Open your inbox, process all email, respond to messages, and handle any scheduling tasks. Use standard 25-minute sessions — the shorter duration creates urgency that prevents you from lingering on any single message.
After lunch: Second deep work block (2–3 Pomodoros). Your energy may be slightly lower than the morning, so consider slightly shorter sessions (35–45 minutes). Focus on your second-priority deep work task. If your afternoon energy is consistently low, this is also a good time for creative work that benefits from a more relaxed, diffuse thinking style.
Late afternoon: Admin batch (1–2 Pomodoros). Handle everything that accumulated during the day: filing, updating project trackers, responding to non-urgent requests, planning tomorrow. This is also when to review what you accomplished and set intentions for the next day.
The ratio of deep work to shallow work Pomodoros tells you something important about your workday. If shallow work consistently outnumbers deep work, you're spending too much time on reactive tasks and not enough on the work that matters most.
Common Batching Mistakes
The most common batching mistake is creating too many categories. You don't need separate batches for email, Slack, scheduling, admin, and filing. Group them into one or two "shallow work" blocks. Over-categorising defeats the purpose of simplification.
Another mistake is scheduling batched shallow work during peak energy hours. Your morning is almost certainly your best time for deep focus — don't waste it on email just because "checking email first" feels productive. It's not productive; it's comfortable. The discomfort of diving into deep work first thing is the price of doing your best work during your best hours.
Finally, don't batch deep work tasks together unless they're closely related. "Write report, then design presentation, then debug code" isn't batching — it's a random task list. Each of these tasks requires a different mental mode. Treat each as its own dedicated block with its own intention.
Making Batching Sustainable
The hardest part of batching isn't the concept — it's the discipline of not checking email outside your batch. This gets easier with practice, but two tactics help immediately.
First, close the applications. If Gmail isn't open, you can't check it. If Slack is closed, you won't see the notification badge. This is obvious advice that almost nobody follows. Close the apps. Your deep work will thank you.
Second, communicate your schedule. Tell your team: "I check and respond to messages at 11 AM and 3 PM." This sets expectations so people aren't waiting anxiously for a reply. Most "urgent" messages turn out to not be urgent at all — and the ones that are genuinely urgent will find you through other channels.
The challenge of staying focused at home makes batching even more important for remote workers. Without the external structure of an office, batching provides the rhythm that keeps your day from dissolving into a continuous stream of reactive tasks.
Frequently Asked Questions
What does it mean to batch tasks in Pomodoro?
Which tasks should I batch together?
How many Pomodoros should I spend on batched tasks?
Should I batch tasks at a specific time of day?
Start Your Next Focus Session
Set up your first batched session and protect your deep work hours.
Open Focus Timer