Task Batching
Every switch between unrelated tasks costs you a little focus and a little time. Task batching cuts down the number of switches by keeping you in one mental mode for an extended period.
Email Overload at Work: Take Back Your Inbox
If email eats your day, the fix is fewer, deliberate sessions: check the inbox at a handful of set times, turn off the notifications that pull you back between them, and tell people when to expect a reply. This page collects practical ways to cut email overload at work without letting anything important slip. It covers what email overload is, how to check email less often without going silent, and how to keep the inbox from setting your day's agenda.
What is email overload?
Email overload is the point where the inbox stops being a way of receiving work and becomes the place your day gets decided. Volume is what people complain about, but volume is rarely the real problem. A hundred messages you read at a time of your choosing are a chore; thirty that interrupt you as they arrive are a workday nobody planned. What makes the difference is who initiates the contact: an inbox you visit on your own schedule is a tool, and one that calls you over whenever it likes sets your agenda for you.
The pull works through three small mechanisms. The first is the notification: every new message announces itself, and each announcement is a question, is this more important than what you are doing now? Answering that question costs attention even when the answer is no. The second is the unread count, which turns the inbox into a score that only ever gets worse between visits. The third is the expectation of speed. Reply within minutes for a few weeks and quick replies become what people order from you; the standard you set by being constantly reachable is the standard you are then held to.
The cost lands on the work that needs continuity. A message takes a minute to read, but the reading is not where the time goes. It goes into the walk back to what you were doing, working out where you were, and rebuilding the context the interruption dropped. Checking email between tasks is cheap; checking it during a task charges the task, and the charge repeats at every glance. A morning can hold thirty such glances and still show only twenty minutes of email in any honest log, which is why the loss is so hard to see from the outside.
None of this is anyone's plan. Each individual check feels reasonable: something might have arrived, and looking only takes a second. The trouble is arithmetic, the same shape as any interruption problem: a small, defensible act, repeated often enough to shape the whole day. By the time the pattern is visible it looks like a personality trait, which is one more reason to treat it as a design problem rather than a discipline problem.
The inbox is also where other people's priorities arrive looking like yours. Every message is a task proposal, and an inbox read newest-first sorts your day by recency rather than importance.
None of this is an argument against email, which remains the least interruptive way to move most work between people. The argument is against the defaults, yours and the sender's: alerts on, inbox open, reply now. The rest of this page takes the problem in order: checking less often without going silent, then keeping the sessions themselves short and decisive. Holding attention inside the recovered stretches is a focus question, and the hub holds the full method index.
How do you check email less often?
Checking less often means moving email from an interruption to an appointment. The mechanics are plain: pick a small number of set times a day, do email at those times, and keep the inbox closed in between. Most desk jobs tolerate two to four sessions, morning, midday and late afternoon being the common shape; some roles need more. The exact number matters less than the fact that you chose it, because a chosen number can be adjusted on evidence, and an unchosen one just grows.
Grouping the messages into sessions is Task Batching applied to correspondence, and its method page names email as the natural place to start. The reasoning carries over whole: same kind of work, same tools, same mental gear, done in one run instead of twelve restarts.
Turn the notifications off before you try any of it. A batching schedule with the pings still on is not a schedule: each alert re-asks a question you already answered when you set the times. Silence the banner, the badge and the sound, and let the inbox become somewhere you go rather than something that comes to you. If your workplace runs urgent traffic through email, deal with the worry directly instead of abandoning the plan: most mail clients can let one named sender or one flagged keyword through, which protects the genuine emergency without readmitting everything else.
The schedule holds only if expectations move with it. People are rarely upset by a reply that takes four hours; they are upset by not knowing when a reply will come. So say what you do: a line to your team, an answer when someone asks, a sentence in your signature if your role warrants it. And if a colleague needs you inside the hour, they also need a channel that is not email. Agreeing what that channel is, a call or a message marked urgent, is exactly what lets everything else wait calmly until the next session.
Batching does not fit every job, and pretending otherwise would oversell it. In practice it pays off most for people who get a lot of mail and owe nobody an instant reply, and least for roles where the inbox is the actual work: support queues, dispatch, anything with a response promise measured in minutes. If that is your job, the checking rhythm is not yours to change alone, and the useful boundary runs elsewhere, between messages that are your work and messages that merely arrive while you work.
Start smaller than feels impressive. Two protected hours with the inbox closed teach more than a heroic regime abandoned on Thursday.
What you do with the closed-inbox stretches decides whether any of this was worth doing. Give the first one to the task you keep not starting, and see the Deep Work page for how to spend long uninterrupted stretches once you have them.
How do you keep the inbox from running your day?
A session needs a shape, or it swells. The known failure of batching is the batch that eats the afternoon: you sit down to clear email and surface ninety minutes later, having read everything and finished nothing. Give each session a fixed length and a hard edge, which is Timeboxing at the scale of half an hour: when the box ends, the session ends, and whatever remains waits for the next one without renegotiation.
Inside the session, handle each message once. Read it and decide on the spot what it is: something to answer now, something to turn into a task, or something to archive. The Two-Minute Rule (for tasks) supplies the sorting line. A reply that takes under two minutes is cheapest done immediately; anything longer goes onto the task list to be scheduled with the rest of your work, not answered on the spot because it happens to be open in front of you. Rereading a message and putting it back is the quiet cost most inboxes carry, and deciding once is most of the discipline.
The two-minute line has a failure mode of its own. A session spent entirely on quick replies feels productive and leaves the one message that mattered untouched, because that one needs thought. Open each session with a scan for the message you least want to answer, and give it the front of the box while you are fresh. The quick ones will survive being second.
Inbox zero is worth reaching and not worth chasing. As the state a session ends in, an empty inbox is useful: whatever is visible still needs a decision, and nothing important is buried below the fold. As a permanent condition, it cannot be won, because the inbox refills at other people's pace, and a goal you can hold only through constant vigilance is just another notification system. Empty the inbox when a session closes, let it fill between sessions, and judge the arrangement by whether real work shipped, not by what the counter said at any given moment. A message that needs a week of thought does not need a week in the inbox either: move it to the task list, where slow decisions belong, and keep the mailbox for whatever has arrived since the last session and not yet been decided.
One more exit is worth naming: when a thread has gone three replies without converging, stop typing. The question has outgrown the medium, and a ten-minute call settles what another day of correspondence will not.
The pattern under all of this is one decision made once, in place of many small surrenders made hourly. Choose the session times, and choose what is allowed to interrupt them. If planning the recovered hours is your next problem, the planning pillar covers it, and your own working style points at the methods most likely to hold.
Methods that shrink the inbox
This site has no dedicated email methods yet; articles will land in this cluster as it grows. Until then, three existing methods do the most for a crowded inbox: Task Batching groups the checking into sessions, the Two-Minute Rule (for tasks) sorts what each message costs, and Timeboxing keeps a session from becoming an afternoon.
Two-Minute Rule (for tasks)
This rule from 'Getting Things Done' prevents small tasks from piling up. The overhead of tracking and deferring a tiny task is often more effort than just doing it right away.
Timeboxing
Based on Parkinson's Law ('work expands to fill the time available'), timeboxing forces efficiency by creating a tight, artificial deadline. It's a powerful tool to defeat perfectionism and procrastination.
Frequently asked questions
How often should you check email at work?
Check email at a small number of set times you chose in advance, for most desk jobs two to four sessions a day, rather than whenever a message arrives. The exact number matters less than its being a decision: a role with genuine urgency may need an hourly look, and busy weeks need more than quiet ones. What you are removing is the between-times checking, which costs a context switch at every glance and rarely surfaces anything that could not have waited an hour.
Does batching email actually save time?
Batching saves time mainly by cutting context switches: the same messages, handled in a few sessions, cost less attention than the same messages handled one interruption at a time. In practice the gain is largest for people with high volume and no instant-reply obligation, and smallest for roles where answering mail is the job itself. The honest test is a one-week trial with notifications off: if nothing broke and the afternoons got longer, it is working.
Should you turn off email notifications?
Yes, for most people and most of the day: every notification asks whether the new message beats your current task, and that question costs attention even when the answer is no. Turning them off is what makes a checking schedule real rather than aspirational. Keep one narrow exception, a named sender or an agreed urgent channel, so that silencing the noise does not mean becoming unreachable in a genuine emergency.
How do you get to inbox zero without spending all day on it?
Empty the inbox in short, fixed-length sessions by deciding each message once: answer it if that takes under two minutes, turn it into a scheduled task if longer, archive it if neither. Zero is the state a session ends in, not a state you hold all day. Between sessions the inbox refills, and that is fine. What matters is that nothing sits in it undecided for days, not that the counter reads zero at any given hour.
What is a reasonable email response time at work?
For most internal email, the same working day is a reasonable response time, and a few hours is generous; replies within minutes are a service level, not a norm. What counts as reasonable is set less by the clock than by expectations, so say what you do: a team that knows you answer at midday and at five stops wondering in between. Anything that cannot wait needs its own agreed channel rather than a faster inbox.