You cannot productivity-hack your way out of an interrupt-driven operating system

I have tried most of the standard advice for taking back the workday. Block focus time. Batch email. Shorten meetings. Turn off notifications. Protect the morning. Create a no-meeting day.

Some of it helps. None of it changes the underlying problem.

If you work in product, engineering, or leadership, your time is rarely yours alone. Your day is shaped by decisions that need input, teams that need context, customers who need attention, and people waiting for answers. You can reserve two hours for deep work on Monday, but by Monday morning that block is competing with an urgent Slack thread, a customer escalation, three meeting follow-ups, and a decision holding up engineering.

Eventually, the focus block moves. Then it disappears. The work moves with it—to early morning, late evening, or the weekend.

When the same capable people repeatedly fail to protect their time, the problem is probably not their calendars. It is the system acting on them.

This became increasingly clear to us while building Earmark. Across more than 100 discovery conversations, product managers and product leaders described days dominated by internal meetings, fragmented attention, and constant follow-through. They did not lack productivity techniques. Many were meticulous about their calendars and priorities. They simply worked inside organizations where communication arrived continuously and where turning that communication into execution remained a manual job.

The more we listened, the less the infinite workday looked like an individual failure. It looked like the predictable output of an interrupt-driven operating system.

The workday has lost its boundaries

Microsoft’s research on the infinite workday gives the pattern a scale that personal experience cannot. Based on trillions of anonymized Microsoft 365 signals and a survey of 31,000 knowledge workers, it describes work stretching across nearly every part of the day.

The average worker receives 117 emails and 153 Teams messages each weekday. Half of all meetings occur during the periods when many people naturally reach peak productivity. Meetings after 8 p.m. increased 16% year over year, and nearly a third of workers who are still active at 10 p.m. return to their inboxes. One in three employees said the pace of work over the previous five years had made it impossible to keep up.

Even the apparent gaps are deceptive. In Microsoft’s highest-volume cohort, workers are interrupted by a meeting, email, or chat notification every two minutes during core working hours. A calendar might show an open hour, but that does not mean the hour is available for sustained thought.

UC Irvine professor Gloria Mark has spent years studying what digital interruption does to attention. Her research found that people spend an average of only 47 seconds on one screen before shifting their attention. People also switch between projects roughly every ten and a half minutes, and each transition consumes limited cognitive resources.

This changes the meaning of “free time” at work. Sixty open minutes fractured into messages, approvals, follow-ups, and context switches are not equivalent to one uninterrupted hour.

The calendar measures available minutes. It does not measure usable attention.

Work has become responsive by default

Most knowledge-work systems make it nearly effortless to create a demand on someone else’s attention. Send the message. Add the meeting. Tag the channel. Assign the comment. Forward the thread. Each action is cheap for the sender, but its cost is distributed across everyone expected to receive, interpret, and respond to it.

Over time, responsiveness starts to masquerade as productivity. A fast answer looks like progress. A full calendar looks like importance. A busy Slack channel looks like collaboration. But the volume of communication says little about whether important work is moving forward.

Asana calls much of this “work about work”: communicating about tasks, searching for information, switching between tools, managing changing priorities, and chasing status. Its Anatomy of Work research, based on more than 10,000 knowledge workers, found that 60% of time was spent on this coordination layer rather than skilled work.

That finding matched what we were hearing at Earmark. Product managers were not simply attending meetings. They were carrying information between them. They translated an engineering conversation into an executive update, a customer discussion into requirements, a planning decision into tickets, and a design review into follow-ups.

The meeting interrupted the work. Then the meeting created another layer of work.

The infinite workday is what happens when communication is immediate but execution is deferred.

Personal productivity advice assumes personal control

There is nothing wrong with protecting focus time or declining unnecessary meetings. The problem is that most productivity advice assumes an individual has meaningful control over both the volume and timing of incoming work.

That assumption breaks down quickly in collaborative roles. A product manager cannot simply ignore the engineering team until Thursday. A leader cannot batch every decision when several teams are blocked. A customer escalation does not respect a carefully color-coded calendar. When the organization relies on people to manually connect conversations, decisions, and work systems, those people remain interruptible by design.

The advice also treats every interruption as an isolated event. In reality, interruptions create chains. A meeting produces a decision that needs to be documented, distributed, converted into tasks, and explained to someone who was absent. Each step creates another opportunity for clarification, another message, or another meeting.

The individual can optimize their behavior inside that chain, but they cannot remove the chain.

This is why the workday expands instead of merely becoming more efficient. Unfinished focus work has to go somewhere, and the quietest hours are usually outside the official workday. Flexibility can make that trade feel voluntary, but routinely relocating work into nights and weekends is not the same as removing it.

The consequences are not merely cultural. The World Health Organization and International Labour Organization have identified working 55 hours or more per week as a serious occupational health risk associated with increased rates of ischemic heart disease and stroke. The infinite workday should not be romanticized as commitment or dismissed as poor boundary setting.

When an organization depends on people finishing the day after the day is over, personal discipline is not the remedy. Organizational redesign is.

AI can increase the pace or change the system

There is an obvious temptation to apply AI to each visible symptom. Summarize the inbox. Recap the meeting. Draft the document. Condense the thread. These uses can save time, but they can also preserve the same operating model while increasing its speed and output.

More summaries do not necessarily produce fewer interruptions. Faster content creation can mean more content for everyone else to process. An AI assistant that helps each person generate more messages, documents, and requests may increase the total coordination burden even while making each individual action easier.

The more important opportunity is to redesign the handoff between communication and execution.

When a conversation produces a decision, that decision should not wait for someone to reconstruct it later. When requirements take shape, the product manager should not have to begin again from a blank page. When a team establishes owners and next steps, those commitments should be ready to review and move into the systems where work happens.

This is the distinction that changed how we thought about Earmark. We stopped asking only how AI could help people process the workday faster. We started asking which parts of the workday should no longer require a person at all.

The goal is not to automate judgment, relationships, or the conversation itself. It is to stop using human attention as the default integration layer between what people discuss and what their organization does next.

The workday will not shrink on its own

The infinite workday emerged gradually. Every new communication tool made some part of collaboration faster and easier. But each also made it easier for work to reach us everywhere, at any time, without removing the coordination labor already on our plates.

Reversing that pattern requires more than another round of calendar etiquette. It requires systems in which context accumulates, decisions remain connected to their rationale, and conversations produce usable work before everyone moves to the next interruption.

That is what compels us to build Earmark. We have lived the expanding workday ourselves. We have heard product teams describe it in remarkably consistent terms. And we believe the technology now exists to address the structure of the problem rather than asking individuals to become more disciplined participants in a broken workflow.

The future of work should not depend on people becoming faster at absorbing interruptions. It should depend on creating fewer reasons to interrupt them.

The infinite workday ends when work stops waiting until after the workday.

Sources

• Microsoft WorkLab, “Breaking down the infinite workday”, June 17, 2025.

• Asana, “How work about work gets in the way of real work”.

• University of California, “Can’t pay attention? You’re not alone”, May 11, 2023.

• World Health Organization and International Labour Organization, “Long working hours increasing deaths from heart disease and stroke”, May 17, 2021.