The number most people have not done the math on
Assume you check email 15 times a day. That is a conservative estimate — research from RescueTime and similar tools consistently finds knowledge workers check more often. But start there.
Each check takes 3–5 minutes on average. That is 45–75 minutes of direct email time per day, before you factor in actually writing responses.
Now add context switching. The research on context switch recovery is consistent: after an interruption, it takes an average of 23 minutes to fully return to deep work. You do not pay that 23 minutes every time — many email checks happen during shallow work, and the cost is lower. But for anyone doing work that requires sustained focus (writing, coding, analysis, strategy), the math becomes serious quickly.
A knowledge worker who checks email 15 times during a focused workday and loses even 5 minutes of recovery time per check — conservative, not the full 23 — loses 75 minutes of recovery time daily, on top of the 45–75 minutes of direct email time.
That is 2–2.5 hours of the workday consumed by email and its immediate aftermath. Over a five-day week, 10–12.5 hours. Over a year, 500–625 hours. Somewhere between 12 and 15 forty-hour workweeks, every year, in email.
What you are actually spending that time on
Not all email time is equal. A rough breakdown of what fills those hours:
Triage (30–40%): Scanning subject lines and senders to decide what needs attention now versus later. This is pure overhead — you are not producing anything, just sorting. And because most people triage reactively (check every time a notification arrives), this work is distributed throughout the day in tiny, high-interruption fragments.
Reading (25–35%): Actually reading the messages that pass triage. This is the part most people count as "email time" — but it is often the smallest portion of total email cost.
Writing responses (15–25%): Composing replies. This is the genuinely productive portion of email work: communicating with people, making decisions, moving things forward. The tragic thing is it represents a minority of total email time.
Re-reading and re-triaging (10–20%): Going back to messages you read but did not act on, reopening threads to remember context, searching for something you know arrived but cannot locate. This is waste, almost entirely — a tax paid for not having a reliable system.
The hidden multiplier: task residue
Cognitive science has a term for what happens when you switch from deep work to email and back: task residue. When you stop focused work to check a message, part of your attention remains on the original task. When you return to it, you are not starting fresh — you are carrying the residue of both the deep task and whatever you saw in email.
This is why "just five minutes to check email" does not cost five minutes. The interruption is cheap. The recovery is expensive.
For anyone doing creative, analytical, or strategic work, task residue means that even a brief mid-morning inbox check can degrade the quality of work for the hour that follows — not just the 3 minutes it took to look.
The Stackora bet
The claim behind Stackora — and behind digest-based email management generally — is not that you should spend less time on email. It is that you should consolidate email time into fewer, longer blocks rather than distributing it across the entire day in small fragments.
If 2.5 hours of daily email time is inevitable, spending that 2.5 hours in one or two deliberate review sessions produces different work than spending it in 15 fragmented interruptions. The total time is the same. The cognitive cost is not.
Batch email review preserves the deep work windows. The email gets processed — completely, attentively, without interruption — during the designated block. Everything else is protected time.
The 28 hours a week is not going to zero. But it stops leaking into every other hour of the day.