# The real cost of email overload (it's not the hours) > The average worker gets 117 emails a day, interrupted every two minutes. The real cost isn't the hours — it's what that's doing to your focus. Canonical: https://beemy.co/blog/the-real-cost-of-email-overload/ · Last updated: 2026-09-02 The Hive The Beemy team 11 June 2026 7 min read **On this page** Ask most people how much time email takes and they’ll guess an hour a day. Maybe two. Microsoft’s own 2025 telemetry puts the average worker at **117 emails a day**, most skimmed in under a minute, and interrupted by a meeting, email or notification roughly **every 2 minutes** during the workday ([Microsoft WorkLab, 2025, sourced on /the-numbers](https://beemy.co/the-numbers)). For years this post led with a different number: the widely-quoted 2012 estimate that email eats 28 percent of the working week. We could no longer re-verify that figure’s source at the time of this update, so we’ve retired it here too. See [/the-numbers](https://beemy.co/the-numbers) for the full story on why. That statistic tends to land as a punchline. “Ha, yes, email is a time sink, we all know.” But the hours are the smaller problem. The bigger one is what email does to everything around it. ## The real cost isn’t the minutes, it’s the switching Email doesn’t consume your day in one continuous 90-minute block you could simply schedule around. It arrives in a drip — a notification here, a Slack ping there, a “quick question” in between two other things you were actually trying to finish. Each one costs you the minute it takes to read, plus the far more expensive minutes it takes to find your way back to what you were doing before it interrupted you. Researchers who study this call it [attention residue](https://beemy.co/the-numbers#attention-residue-leroy-2009): part of your brain stays stuck on the thing you just context-switched away from, even after you’ve moved on. A [field study of 24 information workers](https://beemy.co/the-numbers#fragmented-work-mark-2005) found 57% of their task periods were interrupted before they were finished — do that many times a day, and you’re not losing minutes, you’re losing your ability to do sustained, high-quality work at all. The interruption count above is really a proxy for a much larger, much less measurable cost: a day that never lets you get more than a couple of minutes deep into anything. ## Most of it isn’t even decisions: it’s triage Here’s the part that makes it worse: the vast majority of that time isn’t spent making judgement calls. It’s spent doing the same three-step dance, over and over, for every single message: 1. **Is this something I need to deal with right now, later, or never?** 2. **If later: who am I, in this reply? Curt and fast with a vendor, warm and specific with a client, careful with your boss?** 3. **If never — archive, unsubscribe, or just let it rot at the bottom of the inbox until guilt makes you deal with it in six months?** None of those three steps require your unique judgement or expertise. They require *context* — who’s writing, what your relationship is, what’s actually urgent versus what merely looks urgent because it has “ASAP” in the subject line. That’s a pattern-matching problem, not a thinking problem. Which is exactly why it’s the kind of work that shouldn’t need a human doing it manually, message by message, forever. ## Inbox Zero was never really the goal A lot of productivity advice treats the inbox itself as the enemy: get to zero, feel virtuous, repeat tomorrow. But an empty inbox doesn’t mean you made better decisions — it usually just means you spent more hours doing manual triage than the message volume deserved. (We’ve got more to say about this: see [inbox zero is the wrong goal](https://beemy.co/blog/inbox-zero-is-the-wrong-goal/).) The actual goal isn’t a smaller number in a folder. It’s fewer *interruptions that didn’t need to be interruptions* — while nothing that genuinely needed your attention slips through. That’s a much harder problem than “reply faster,” and it’s not one you solve with keyboard shortcuts or a stricter filing system. ## What triage actually needs to know To triage well (to route the noise away and hand you only what matters), you need context that most inbox tools simply don’t have: - **Who is this person, really, to you?** A message from your manager and a message from a newsletter you forgot you subscribed to shouldn’t be weighed the same way just because they both landed at 9am. - **What’s the relationship history?** Is this the first time this vendor has emailed, or the fifth follow-up because the first four went unanswered? - **What tone do you use with this specific person?** The reply-in-your-voice problem isn’t “sound professional” — it’s sound like *you*, specifically, to *this* person, specifically. - **What’s actually urgent versus what’s dressed up to look urgent?** Subject lines lie. Sender history and relationship weight don’t. This is the gap between a filter and an assistant. A filter can move messages between folders based on keywords. An assistant needs to understand your working relationships well enough to make the same call you’d make — and hand you, with full context, the handful of messages each day that genuinely need a human’s judgement. ## Getting the week back The interruption count above isn’t a call to work faster through your inbox. It’s a sign that the *task itself* (read, classify, decide, draft, repeat, hundreds of times a week) is exactly the kind of repetitive, context-dependent, low-judgement work that a contextually-aware assistant should be doing instead of you. That’s the bet behind Beemy: triage that actually understands who’s writing and why, drafts that sound like you instead of an autoresponder, and a growing list of things escalated to you only when they genuinely need your judgement. Not a faster inbox: fewer of your minutes spent restarting after someone else’s message. Curious what that’s worth in your own numbers? → [See what your inbox costs you](https://beemy.co/inbox-cost/), with the maths shown. One item, shown Illustrative example, built with mock data. In Gmail · work What arrived Overnight inbox (forty new messages) Forty messages land overnight, each one a fresh interruption if you'd opened them one at a time this morning. What Beemy tells you One roundup sorts the forty into three that need you and thirty-seven that don't, so the morning starts with three decisions instead of forty separate interruptions. You read the three. The other thirty-seven never cost you a moment at all. - [Email & focus](https://beemy.co/blog/topics/email-and-focus/) On this page Keep reading ## More from the Hive. inbox zero · productivity ### Inbox zero is the wrong goal Chasing an empty inbox optimises for the wrong number. The real goal is the right interruptions, and escalation, done well, is a deliberate feature. comparison · AI assistant ### Beemy vs. a general-purpose AI assistant: the long version Any AI can draft you a reply if you ask nicely. The real question is what it does when you're not asking, and whether it knows enough about your life to do it well. Here's the long answer. dual-life productivity · context ### The other half of the workday Life admin: the anticipating, deciding and checking-it-landed that never appears on a work calendar. Here's what the research actually says, why we still won't publish an hours-saved number, and what Beemy already handles.