From task switching to calendar design
Abstract
Interruption research is often summarized as a single claim that interruptions cost twenty-three minutes, but the underlying studies measure specific tasks, specific switches, and specific recovery periods. Executive calendars create a different pattern of interruptions across meetings, messages, and travel. This review separates what the research measured from what an office can reasonably apply, then sets a small calendar test with honest limits. [1][2][3] The local test is the only way to know whether the mechanism matters in this office.
Methodology
The review uses experimental and field evidence on task switching as context and treats calendar records as a local planning input. It does not convert a laboratory result into a guaranteed productivity figure. It defines an interruption as a switch away from a planned block and a resumption as the point at which the original work continues. The recommended test uses a two-week observation window and a small set of categories. [1][2][4]
What interruption research actually measured
The widely cited interruption studies observed office workers performing real tasks while being interrupted at controlled moments. They measured the time to return to the original task, the number of intermediate tasks, and the stress reported by participants. The findings showed that resumption is not instant and that people often take up several intervening tasks before returning. The studies describe a mechanism rather than a universal delay for every person and every role. [1]
The setting matters. A laboratory or short field study can control the type of interruption and the complexity of the primary task, while an executive's day includes meetings, travel, and messages from many sources. The research is useful because it shows that switching has a cost. It is not a stopwatch that can be applied to a calendar without observing how the work actually resumes. [1][2]
The difference between a break and a switch
Not every interruption is harmful. A planned break can restore attention, and a short check-in can prevent a larger problem later. The cost appears when the switch is unplanned, when the original task requires deep concentration, or when the person cannot control the timing. A calendar review should distinguish between a deliberate pause and an unexpected demand on attention. [1][2]
The distinction changes the design. If the problem is unexpected demand, the fix may be a clearer escalation path or a protected window. If the problem is too many planned meetings, the fix may be consolidation rather than protection. Treating every interruption as waste leads to a rigid calendar that ignores the legitimate need for responsiveness. [2][3]
Why executive calendars hide switching costs
A calendar shows the meeting, not the preparation before it or the mental residue after it. Two back-to-back meetings in different topics may look efficient because there is no gap, but the switch can leave the executive still processing the first conversation. The cost appears in the quality of the second meeting, not in the number of hours booked. Standard calendar reports cannot see that. [2][3]
Travel adds another layer because the switch includes a change of place, a security line, and a different set of people. A short flight can consume half a day of usable attention even if the flight itself is brief. A calendar review should mark travel as transition time rather than treating it as open space for calls. That single change often reveals why a day felt overloaded. [1][3]
Design blocks around recovery, not just focus
Most calendar advice focuses on protecting a block of focus time. Recovery matters too, because the period after a demanding meeting determines whether the next task starts cleanly. A short buffer can be more valuable than a longer block later in the day. The assistant should protect a realistic gap after meetings that involve conflict, decisions, or complex material. [1][2]
Recovery does not require an empty hour. Ten minutes to write down the open questions and the next action can prevent the conversation from leaking into the next meeting. The assistant can build a note-taking habit at the close of each high-stakes session. That record also improves the meeting notes and the decision log. [2][4]
Prepare for the interruption you cannot remove
Some interruptions are part of the job, especially in a leadership role with external stakeholders. The goal is not to eliminate them but to make resumption cheaper. A short written state note at the end of a work session lets the executive return without reconstructing the whole context. The note can be three lines: what was decided, what remains, and what to do next.
The support desk can also prepare a capture path for interruptions. When a call comes in, the assistant records the request and the deadline so the executive does not have to hold it in working memory. This is a simple operational habit, but it reduces the number of things competing for attention. The desk becomes a buffer rather than another source of interruption. [2][3]
Measure resumption time locally
Choose a small number of work sessions and record when the executive started, when an interruption occurred, and when the original work resumed. Do not attempt to measure every minute of the week. A two-week sample with five or six sessions is enough to reveal whether resumption is a recurring problem. The observation should be done with consent and without content monitoring.
Categorize the interruptions by source, such as a scheduled meeting, an unscheduled call, a message, or a travel change. Then look at which category is most associated with a long resumption. The result may show that the biggest cost comes from a source the assistant can control, such as a poorly timed internal check-in. That is a more actionable finding than a general complaint about interruptions. [1][3]
Avoid turning research into a rigid rule
A common mistake is to declare that every interruption costs a fixed number of minutes and then design a policy around that number. The research does not support a universal constant, and a rigid rule can damage responsiveness. A better use of the evidence is to justify a test, such as a buffer after high-stakes meetings or a single daily window for internal requests. A local test protects the office from both overreaction and complacency.
The test should have a clear measure and a review date. If the buffer reduces late starts and improves preparation, keep it. If it merely pushes work later without improving quality, revise it. The calendar should adapt to the executive's actual work rather than to a slogan about focus. [2][4]
What to test in a two-week window
Test one change at a time. A reasonable first test is a ten-minute buffer after any meeting with an external stakeholder or a decision. Another is a single internal-request window each afternoon. Record late starts, meeting overruns, and the executive's own rating of readiness before the next commitment. Keep the record short so it does not become another task.
At the end of the window, compare the test days with a similar period without the change. Look for a consistent pattern rather than a single good day. If the change is promising, extend it for another month before making it permanent. If the week is unusual because of travel or a board cycle, repeat the test later rather than forcing a conclusion. [1][4]
Limits and responsible use
This review cannot prove that a specific calendar design will improve decision quality or output. It describes a plausible mechanism and a local way to test it. Individual differences, the nature of the work, and the executive's control over the schedule all affect the result. The evidence should inform a conversation, not replace judgment.
The method should also avoid turning the assistant into a time auditor. The purpose is to protect attention and improve recovery, not to score the executive or the team. For related reading, see our guide to <a href="/blog/defend-meeting-free-blocks-when-the-calendar-keeps-filling">defending meeting-free blocks</a> and our <a href="/services">executive support services</a>. [2][3] That boundary keeps the exercise focused on calendar design rather than individual assessment.
Key findings
- Interruption studies show a real resumption cost, but they do not establish one universal delay for every role. [1][2]
- Distinguish a planned break from an unplanned switch before treating an interruption as waste. [1][3]
- Calendars hide switching costs because they show the meeting but not preparation, travel, or mental residue. [2][3]
- Protect short recovery gaps after high-stakes meetings and use written state notes to make resumption cheaper. [1][2]
- Test one calendar change in a two-week window and compare it with a similar period before making it permanent. [3][4]
Sources
- The Cost of Interrupted Work: More Speed and Stress, Gloria Mark, Daniela Gudith, and Ulrich Klocke, University of California, Irvine
- Work Trend Index, Microsoft
- American Time Use Survey, U.S. Bureau of Labor Statistics
- How CEOs Manage Time, Harvard Business Review