Somewhere along the way, email became the operating system for work.

Nobody planned this. No committee convened to decide that a message-delivery tool should also manage tasks, track approvals, archive decisions, coordinate projects, and serve as institutional memory. It happened by accretion—one forwarded thread at a time—until here I am, running my work through a system that was never designed for the job.

Once you see the pattern, you can’t unsee it. And that’s the first step toward something better.

Here’s what you might have noticed: Email looks like productivity. You open it, process things, respond, file, move on. There’s a satisfying rhythm to all that activity. But what actually gets produced? What decisions get made and stay made? What moves forward? Honestly assessed, the answer is often: not much. The inbox got slightly lighter. The work stayed where it was.

The promise that never quite delivers

Email promises to be everything:

• A communication channel (it mostly is—credit where due)
• A task management system (it fails reliably, sometimes spectacularly)
• An approval workflow (chaos dressed up in business casual)
• A record-keeping system (unsearchable, unstructured, unreliable)
• A decision archive (where decisions go to die)

We’ve loaded an impossible burden onto a tool that was never architected to carry it. And because everyone else does the same thing, ubiquity becomes validation. Everyone uses email this way, so it must work.

The more interesting question: What if everyone is simply stuck in the same trap, mistaking universal adoption for effectiveness?

What the research shows

Researchers have been documenting email’s dysfunction for over two decades. This isn’t productivity-guru speculation—it’s measured, replicated, and remarkably consistent.

Studies using biosensors and heart rate monitors confirm that more time in email correlates with higher stress and lower perceived productivity.[1][2] Not subjective impressions—actual physiological markers registering the toll.

When researchers cut off email access entirely for a group of workers, the results were striking: people multitasked less, maintained longer focus, and showed measurably lower stress. Participants described working “at a pace not dictated by electrons.”[2]

And here’s a paradox worth sitting with: interrupted workers complete tasks faster than uninterrupted workers—but at the cost of significantly higher stress, frustration, and effort.[3] The speed is compensatory behavior, the body running harder to overcome fragmentation. Not genuine efficiency.

You can sprint through a burning building. That doesn’t make the fire acceptable.

The anatomy of the illusion

The productivity illusion. Processing email feels like accomplishment. Motion exists, activity exists, the satisfying act of clearing things out exists. But activity isn’t output. The feeling of productivity can be completely decoupled from reality—which is both humbling and oddly liberating once noticed.

The self-interruption trap. The uncomfortable part is that much of this dysfunction is self-inflicted. Research distinguishes between being interrupted by others and interrupting yourself to check email.[1] I’m complicit in my own fragmentation—that compulsive urge to check, just in case something urgent arrived, fracturing my attention dozens of times daily. The flip side? If I’m doing it to myself, I can also stop.

The autonomy paradox. I put email on my phone to gain freedom—work from anywhere, stay connected on my terms. Instead, the freedom became a leash. Harvard researcher Ashley Whillans calls the result “time confetti”—hours shredded into pieces too small to use for anything meaningful.[4] Maybe the goal isn’t better confetti management, but fewer scissors.

The false urgency machine. Everything arrives with equal weight. A critical deadline notification sits next to the newsletter we forgot to unsubscribe from. Nothing signals actual priority, so everything feels urgent, which means nothing actually is. The noise drowns out the signal—but signals can be separated once we decide to.

The decision burial ground. Important choices get made in email threads, then vanish. Six months later, someone asks “didn’t we decide this already?” and everyone vaguely remembers that yes, there was a thread—but nobody can locate it. The decision existed briefly before disappearing into the archive.

Accountability theater. CC culture creates the appearance of communication. Everyone’s “in the loop.” But being copied on an email is not understanding, not agreeing, not aligning. The illusion of shared knowledge masks the absence of actual coordination.

The spillover that doesn’t stay at work

Email doesn’t observe boundaries. Research confirms what most of us sense: email demands contribute to job tension that bleeds into home life.[5] The expectation of responsiveness has become 24/7 reality, erasing the boundaries that once provided recovery time.

But here’s what interests me: boundaries erased by default can be rebuilt by design. If the creep happened without anyone deciding it should, then deciding it shouldn’t is also possible.

Why nothing has changed (yet)

If the dysfunction is so well-documented, why hasn’t anything changed?

Researchers have explicitly called email overload “intractable to manage” despite decades of awareness.[6] Solutions don’t stick. The problem exists, organizations try various interventions, and somehow end up right back where they started.

A few structural patterns help explain the persistence:

The switching cost feels prohibitive. Moving away from email requires coordinated change across an entire organization. Individual action isn’t enough—if I stop using email but everyone else keeps sending messages, I’ve created a new problem without solving the original one.

No single alternative exists. Email pretends to do many things. Replacing it means adopting multiple purpose-built tools—one for tasks, one for decisions, one for communication, one for records. That’s a harder sell than “just use email for everything,” even when “everything” doesn’t actually work.

Familiar dysfunction beats unfamiliar solutions. I know email is broken. I also know how to navigate it. New systems require learning, adjustment, the discomfort of temporary incompetence. The devil I know often wins.

But “intractable so far” isn’t the same as “intractable forever.” The patterns that created this mess weren’t inevitable, and neither is their continuation.

What email actually is

Stripped of pretense, email is a notification delivery system that we’ve overloaded with incompatible purposes. An anxiety generator masquerading as a productivity tool. A CYA archive that creates the illusion of documentation while making actual retrieval nearly impossible.

It’s the place where work goes to become invisible.

Recognizing this doesn’t solve the problem. But it shifts the frame—and shifted frames open new possibilities. When we see email for what it actually is rather than what it claims to be, different questions become available.

What might actually help

The “intractable” label exists for a reason. Simple solutions to coordination problems rarely work, and anyone claiming to have cracked the code deserves skepticism. But a few observations seem worth holding:

Someone has to go first. Email dysfunction is fundamentally a coordination problem. Individual inbox tactics cannot fix systemic issues. Leaders who want different outcomes have to declare what email is and isn’t for, model the behavior themselves, and refuse to let critical decisions live in threads. Going first creates permission for others to follow.

Moving one category of work out of email—deliberately—is a reasonable start. Pick decisions, or tasks, or records. Move that one thing to a purpose-built system. Use email only for what remains. See what happens before trying to solve everything at once.

The physiological reality matters. This isn’t just about efficiency. The stress is real and measurable.[1][2] Treating email overload as a health issue rather than merely a productivity issue might change how organizations approach it—and health arguments tend to carry weight that productivity arguments don’t.

Honesty about what email is actually good for might be the most useful intervention. It’s genuinely decent for asynchronous, low-stakes communication that doesn’t require action or tracking. That’s a much narrower use case than how most of us deploy it—and acknowledging the mismatch is the first step toward designing something that actually fits the work.

Worth questioning

If email dysfunction is structural rather than personal, what shifts when we stop treating it as an individual discipline problem and start treating it as a design problem?

The research has been clear for twenty years. The dysfunction is well-documented. And yet—nothing has fundamentally changed. That persistence is itself worth examining.

Watch for early signals that the pattern might finally be breaking. Generational expectations are shifting. Remote work has made the dysfunction more visible, not less. The conversation about burnout and boundaries has moved from fringe concern to mainstream discussion.

If this is the decade when organizations finally get serious about work design—and there are reasons to think it might be, not the least of which is Artificial Intelligence—email’s role as the default operating system is one of the first things that will have to give.

The question isn’t whether better alternatives exist. They do. The question is what it takes to choose them—and whether that choice happens by design or only after the current approach becomes genuinely unsustainable.

Here’s where the organizational reality becomes unavoidable: while individual workers experience email dysfunction personally—the stress, the fragmentation, the overwhelm—the dysfunction itself is structurally organizational. It emerges from coordination systems, cultural expectations, and communication architectures that individuals didn’t design and can’t unilaterally change.

The person checking email at 11 PM isn’t making an individual productivity mistake. They’re responding to organizational systems that route decisions, tasks, and coordination through email, then measure professional competence partly by responsiveness. The overwhelmed manager with 200 unread messages isn’t personally disorganized—they’re experiencing the downstream effects of coordination infrastructure that was never designed to handle the load it currently carries.

The research shows what changes when organizations—not just individuals—address email dysfunction.[7] When leadership establishes explicit norms around response expectations, designates certain communication types for non-email channels, and creates collective agreements about availability, measurable outcomes shift: email volume decreases, stress markers decline, attention fragmentation reduces.

This doesn’t happen through inbox zero techniques or individual discipline. It happens through coordination—the same capability that email is ostensibly providing. Organizations experiencing email dysfunction are, in effect, trying to coordinate their work through a system that has itself become a coordination problem.

The gap between research clarity and organizational change isn’t about individuals failing to implement better email practices. It’s about organizations continuing to route coordination through a system that research has documented as inadequate for that purpose, while the authority to change that routing sits with leadership rather than individual contributors.

Can we think different?

What would your work look like if decisions, tasks, and records actually lived in systems designed for them? What would you do with the attention you’d get back? And who has the authority to make that change where you work?

Those aren’t rhetorical questions. They’re worth genuinely sitting with.

---