The workday no longer begins when you sit down or ends when you leave. It leaks through an early message, a midday meeting grid, a late reply, and the quiet expectation that every open channel deserves attention.
Microsoft calls this pattern the “infinite workday.” Its 2025 analysis reported 117 emails and 153 Teams messages received by the average Microsoft 365 worker in its dataset each weekday. In a separate analysis of the most heavily pinged 20% of users, interruptions arrived about every two minutes during core hours. These telemetry findings excluded the European Union and education sector, so they are signals from a particular platform and population, not a universal description of every workplace.
The practical lesson is still useful: focus problems are often communication-design problems. A better timer cannot compensate for a team that treats every channel as urgent.
Find the demand surface
For three working days, record interruptions without trying to fix them. Label each one:
- direct request from another person;
- notification generated by a tool;
- self-initiated check;
- meeting or call;
- unresolved thought from another task.
Also record whether the interruption truly required an immediate response. This separates urgent coordination from ambient availability. Most people discover that the number of channels matters less than the absence of rules for those channels.
Attention residue research offers one reason switching feels expensive: thoughts about an unfinished task can impair performance after the switch. The study does not give a magic recovery time, and it does not mean all switching is harmful. It does suggest that frequent, unplanned transitions can carry a cognitive cost beyond the seconds spent opening a message.
Create a response ladder
Give each communication route a distinct promise.
- Emergency: one agreed route, reserved for events that truly cannot wait.
- Same day: a channel checked at two or three visible windows.
- Routine: asynchronous work answered within a stated service level.
- Reference: information that requires no response.
The ladder works only if other people know it. Put the rules in a team page, status message, client agreement, or project kickoff. A private focus plan cannot resolve a public expectation of instant access.
For individual work, the equivalent is simple: keep one route available for genuinely urgent contact and silence the rest during a defined block. Then use an attention warm-up to close the previous context and state the next output.
Replace status traffic with visible work
Many interruptions are attempts to answer three questions: What is happening? Who owns it? When will it be done? A current project board, concise decision log, or end-of-day update can answer those questions without a meeting.
Do not add documentation indiscriminately. A status page that no one trusts becomes another channel to monitor. Choose one location, name an owner, and include the next decision or delivery date. Remove a recurring meeting only after the replacement makes the needed information easier to find.
Protect an edge, not an ideal day
In reactive roles, four uninterrupted hours may be unrealistic. Protect the most valuable edge you can defend: the first 30 minutes, the hour before a deadline, or two 45-minute blocks between service windows.
Write a precise target before the block: “compare three supplier proposals and record a recommendation,” not “work on procurement.” Leave a restart note when the block ends. This reduces the cost of a necessary interruption and makes a shorter block useful.
Put an end on the day
Microsoft’s same report found after-hours meetings and messages were common in its dataset. The fix is not an elaborate evening ritual. It is a credible stopping condition.
Before finishing, capture unfinished work, identify the first action for tomorrow, communicate any genuine risk, and close work channels. If after-hours monitoring is part of the job, make the rota and escalation threshold explicit so the whole team is not permanently on call.
Test the system for two weeks with the Infinite Workday Reset guide. Track completed focus blocks, truly urgent interruptions, after-hours checks, and one output-quality measure. A quieter day is valuable only if essential coordination still works.
Sources
- Breaking down the infinite workday — Microsoft WorkLab, including methodology and limits for survey and product-use data
- Why is it so hard to do my work? Attention residue when switching tasks — experimental research on task switching and unfinished work