The Complexity Behind Work Interruptions and Attention
A work notification sparks a complex moral drama between software, colleagues, and organisations. While the alert is generated by software and the message originates from a colleague, the pressure to respond is imposed by the organisation. Yet, when an employee’s concentration is broken, the blame often falls on personal discipline rather than systemic factors.
Two key data points complicate this narrative. Gloria Mark’s workplace fieldwork famously found an average of 23 minutes and 15 seconds before workers returned to interrupted tasks. Separately, Microsoft’s telemetry from its own environment revealed that the busiest 20% of users might receive as many as 275 meeting invitations, emails, and chats in a single day.
It’s critical to remember these are independent studies—not a settled consensus. The Microsoft figure is a corporate telemetry snapshot unrelated to Mark’s participants. Neither statistic means quite what their most dramatic retellings imply, and understanding these nuances is essential.
Clarifying the 23 Minutes and 15 Seconds Metric
In a 2006 Gallup interview, Gloria Mark described research involving 36 knowledge workers—managers, financial analysts, software developers, engineers, and project leaders—observed over three working days. Trained observers timed interruptions to the second. Of the interrupted work resumed that day, 81.9% was eventually picked up again, with an average return time of 23 minutes and 15 seconds. Notably, workers typically engaged in about two other tasks before returning.
This figure does not represent 23 minutes of idle, distracted staring at a screen. Instead, it includes time spent managing the interruption and completing other work before returning to the original task. It is important to note that the research measured real workdays, not a controlled laboratory’s cognitive refocus period.
The study’s unit of analysis was a “working sphere”—a cluster of activity linked by a common goal, people, resources, and timeframe. Returning after interruption often meant re-engaging with the broader project rather than reopening the exact document or spreadsheet cell. Thus, the oft-cited “refocus time” oversimplifies what the research actually measured.
Published Findings Show Slightly Different Averages
A less frequently cited detail is found in the peer-reviewed CHI 2005 paper by Mark, Victor Gonzalez, and Justin Harris. It reports a slightly longer average return time of 25 minutes and 26 seconds.
This study observed 24 workers—managers, analysts, and developers—in an IT and accounting outsourcing company for roughly three and a half days, accumulating about 700 hours of observation. When interrupted work was resumed the same day, workers visited an average of 2.26 other working spheres beforehand. The resumption rate was 77.2% for eligible interruptions.
The data showed wide variation, with a standard deviation of 54 minutes and 48 seconds, indicating some interruptions were brief detours while others caused prolonged delays. The Gallup interview’s larger sample yielded the 23:15 figure, but no definitive reconciliation exists. Both studies agree that interrupted work often involves navigating through other tasks before returning to the original goal.
Given these findings stem from a small sample in a single organisation, they cannot be generalized to all contemporary workplaces in 2026.
Microsoft’s 275 Contacts Reflect Volume, Not Attention Shifts
Microsoft’s 2025 Work Trend Index analyses aggregated and anonymized Microsoft 365 data. The cited figure of 275 contacts is a rolling daily average over 28 days for the top 20% of users by incoming volume, including meeting invitations, emails, and chats.
This number does not represent the typical employee’s experience but rather Microsoft’s most heavily contacted segment. The data excludes educational and European Union tenants and covers activity up to February 15, 2025.
Crucially, Microsoft does not confirm that all counted messages were noticed, answered, or caused task switching. The impact of a quiet unread email differs vastly from an urgent chat demanding immediate action. The report also states the average worker receives 117 emails and 153 Teams messages per weekday.
The claim that employees are interrupted every two minutes derives from the average interval between alerts (pings) during an eight-hour day. However, a ping only signals a potential interruption, not a guaranteed task switch. This distinction is essential when interpreting such statistics.
Why Multiplying These Figures Is Misleading
It may seem tempting to multiply 275 by 23 minutes to conclude the workday is impossible to complete. However, this is incorrect. The figures come from different populations, timeframes, and definitions. Multiplying them assigns a recovery period to every message, ignoring that many messages arrive while already away from the original task.
Mark’s return interval includes productive work on other tasks. Many incoming items are ignored, batched, or deferred. Some interruptions are helpful or can be processed together. This complexity prevents the numbers from turning into an exaggerated narrative.
A controlled experiment by Mark and colleagues (2008 study) offers additional insight. Participants performing simulated office tasks completed them faster when interrupted and did not produce lower-quality work but reported higher stress, frustration, and time pressure. Although not the source of the 23-minute figure, this experiment highlights that costs of interruptions extend beyond lost minutes.
The meaningful connection between these datasets lies not in arithmetic but in illustrating that returning to interrupted work often involves detours through other activities, and modern systems generate immense volumes of potential interruptions.
Content Matters More Than the Alert
Mark’s fieldwork emphasizes a crucial distinction: interruptions within the same working sphere can be beneficial. A colleague’s message might clarify ambiguity, provide a necessary answer, or save time. The more disruptive interruptions occur when pulled into a different working sphere with distinct goals, groups, and deadlines.
Another complexity is that 44% of interruptions noted in the Gallup study were self-initiated. While sometimes reflecting a lapse in willpower, often workers check messages because of multiple live priorities, expectations of replies, blocked tasks, or organisational culture that treats unseen messages as potentially urgent.
Previously, I have written about the difference between appearing busy and producing meaningful work (read here). Fragmentation fits within the same conversation. A day filled with replies, status updates, and short meetings can still result in slow progress on tasks requiring sustained focus.
Therefore, framing every interruption as an adversary is counterproductive. Communication often advances work. The design challenge is when workers cannot distinguish which channels, senders, or notifications genuinely require immediate attention.
Focus Is Partly an Organisational Responsibility
Personal habits—muting alerts, batching emails, closing tabs—can help manage interruptions. Yet, these choices occur within organisational rules. If an unanswered message signals disengagement, muting alerts is not purely personal preference. When projects use multiple communication channels, monitoring them becomes part of the job.
Microsoft’s dual role as a telemetry source and software vendor—including AI tools it promotes as solutions—means its reports warrant scrutiny similar to any vendor’s problem framing.
Eliminating communication is neither feasible nor desirable. Coordination is essential work. The practical questions are less dramatic but more impactful: which messages require synchronous attention, which can wait, whether urgency labels are meaningful, who can protect time blocks, and whether teams share response expectations.
These two statistics persist because they capture a contradiction many workplaces have normalised: employees are expected to perform deep, focused work while simultaneously demonstrating responsiveness. Personal focus strategies may reduce noise but cannot resolve incompatible organisational expectations alone.
An organisation cannot reasonably demand deep concentration and continuous availability simultaneously, then blame individuals when conflicts arise. Attention’s architecture is partly personal, but permission to use it is granted organisationally.
Source: Here
