There’s something weird about the way an email client makes you feel when you open it.

You sit down with the quiet intention of clearing your inbox, maybe reading a few things and filing the rest, and within thirty seconds you have scrolled past seven unread messages that look urgent out of context and three from people you haven’t heard from in six months. You start reading one and switch to another because the subject line of the second one made you realize you needed to reply to something immediately. Before lunch is over you have a stack of partially read emails with subjects like “Quick question” and “Following up on this” that each feel simultaneously urgent and meaningless.

This is not unique to any person I know. It is built into what email actually is as a protocol.

Email was designed in 1982 as a tool for sending letters over an academic network. The designers were scientists who needed to share drafts of papers with colleagues who might be anywhere on the nascent internet. They thought about routing (how does this message reach its destination?), format (what’s in the body versus the header), and addressing (who exactly should receive it?). What they did not think about was what every professional and eventually every student would do by the late 1990s: treat their personal inbox as a task queue.

The letter-writing protocol became humanity’s first distributed to-do list without its creators intending that at all. A physical letter you received sits on your desk until you decide what to do about it. You file it in a drawer or put it in the trash after responding. The sender has no record of whether you read it unless they call you. An email changes this fundamentally: it disappears from view when you archive or mark it, but the sender never knows exactly what happened to it. They don’t know if you read it, scanned it, forwarded it, or ignored it entirely. The sender’s perception is binary: sent or delivered. They do not have access to the same information about disposition that you see in your own inbox. And this asymmetry creates almost everything stressful about modern email culture.

When I think about why this mismatch is so hard to solve, what comes to mind first is how every productivity app tries to fix inbox fatigue by adding more layers on top of it. Things like labels and filters and priority flags that organize messages into increasingly granular categories. But the apps do not address the underlying problem: you are treating letters as tasks because the tool was never designed for either one specifically. They create the illusion of control while maintaining the fundamental tension between being a reader, being an actor, and being someone who receives correspondence. The better label system in the world will still have a message from three days ago sitting at the top that you opened once without replying, which means something different to the sender than it does to you.

The real question is whether this was inevitable or accidental. Email’s early adopters were academics and government researchers: people who already treated information exchange as their primary work activity. They did not have a preexisting task management system outside of physical filing cabinets or paper notebooks. When electronic correspondence arrived, there was no competing paradigm for where tasks lived. A personal to-do list was something you carried in your pocket on paper, not something that appeared on screen. The digital equivalent simply did not exist at scale until task management software like Things and Trello arrived years later by completely independent paths.

Once email became the dominant communication channel in any organization, it absorbed everything that needed to be communicated between people. Meeting scheduling became an exchange of confirmations rather than a calendar event you accepted with one click. Project updates moved from standup meetings into threaded message chains. Decisions happened as replies rather than formal documentation stored in any shared drive. The protocol did the work of dozens of different systems because it was the only communication tool everyone already had access to and understood. It required zero onboarding, worked across organizational boundaries, survived address changes without a central authority updating records, and provided permanent written evidence that something happened when people needed proof. You can argue about whether these are good trade-offs from any perspective other than the one where you need something to work immediately with no setup overhead.

The result is what happens in every single inbox regardless of industry or geography: a persistent low-grade sense of unfinished business. Not the satisfying incomplete feeling of standing over a half-built piece of furniture that represents real progress, but the draining accumulation of micro-tasks that demand attention without ever being fully present. Each message pulls at you just enough to make ignoring it feel irresponsible but not enough to justify doing it immediately. The subject lines created under time pressure by overwhelmed people who are trying to get something out before noon create urgency through ambiguity rather than genuine necessity. You open an email about a project deadline and realize within three seconds that you are not actually the person responsible for delivering anything.

The solution is not obvious even though everyone agrees that every inbox feels broken by design. Building email as a task management system from scratch would mean abandoning backward compatibility with decades of existing protocols, addresses, and expectations. Nobody wants to wait through another migration period where something like Gmail or Outlook replaces their workflow overnight and nobody understands their old organizational structure. But the alternative is accepting that a letter-writing protocol designed for academic collaboration in 1982 will never be optimized for modern professional life, regardless of how many layers of productivity features get stacked on top of it.

Maybe the most honest answer is also the simplest: every inbox will always feel unfinished when it contains letters you have received but not yet replied to plus messages you need to act on plus carbon copies that landed there by accident rather than deliberate choice. A physical inbox would overflow and stop accepting mail if you never cleared it out. Digital inboxes have no such natural limit, which means the only thing stopping complete overload is conscious behavior rather than any mechanical constraint built into the system itself.

The people who seem most capable with email tend not to be ones using the most sophisticated filters or subscribing to productivity courses. They are the ones who check less frequently and batch-process responses when they do open it, the same way you might clear a physical desk at the end of a workday rather than organizing papers continuously throughout it. The people in the opposite camp who answer every email within five minutes and maintain elaborate label hierarchies with color-coded priorities look exactly as overwhelmed as their inboxes suggest they should be.

I have spent more time thinking about this than is productive but the pattern keeps showing up wherever I observe working professionals across any context. We can acknowledge that our primary communication tool is an academic letter-writing protocol from 1982 that was accidentally upgraded into a global task management system, or we can keep trying to hack around its fundamental design mismatch with tools built for problems it was never meant to solve. The tension does not go away just by adding features. It goes away only when someone decides they want the behavior to be different enough to justify breaking compatibility with decades of expectations. That has not happened yet, but the conversation about whether email should even remain relevant has started in places that were not part of its original design at all.