The Radicati Group has counted global email volume for two decades, and the line only goes one way: past 360 billion messages a day now, with the average professional receiving about 120. Over the same two decades, human reading speed, working memory, and hours in a day have improved by exactly nothing. Email overload isn't a personal failing. It's what a fixed-capacity system experiences under unbounded input.
Why it feels the way it feels
An unprocessed email is an open decision, and minds are bad at holding open decisions quietly. Psychology calls it the Zeigarnik effect: unfinished items keep intruding on attention until they're captured somewhere trusted. A hundred undecided messages is a hundred small intrusions, which is why a full inbox follows people into evenings and weekends even when nothing in it is individually important.
Add the checking habit (knowledge workers glance at communication tools dozens of times daily, paying roughly 23 minutes of refocus per interruption per UC Irvine's research) and overload becomes self-sustaining: the fuller the inbox, the more often you check it, the less continuous attention you have for clearing it.
The fix has a required order
Most overload advice fails because it's applied out of order. The order is arrivals, then processing, then tracking, and each step only works if the previous one happened.
- First, cut arrivals. Unsubscribe hard, filter everything automated past the inbox, push back on cc-culture. One hour of this typically removes 20 to 40 percent of daily volume, permanently. Skipping this step means the next two operate on double the necessary input.
- Second, batch processing. Two to four fixed windows, one-touch decisions inside them. The batching case in full.
- Third, move tracking out of your head. Tasks to a task list, things-you're-owed to a waiting-for list. This is the step that ends the Zeigarnik hum, because captured loops stop intruding.
When the math still doesn't close
At some volumes, disciplined manual processing still costs an hour a day, and that's the point where the sorting layer itself should stop being human work. Pidgy reads a Gmail or Outlook inbox continuously and delivers the processed result: the short needs-you list, the tasks extracted, the waiting-fors tracked and chased. Overload is an input problem meeting a capacity problem; automation is the only fix that scales with the input.
Start with the full system, and treat this as the diagnosis chapter: volume up, attention fixed, order matters.
