Skip to content
On this page

Measuring interruption recovery in executive support: a bounded protocol

A local, evidence-based protocol for measuring how long an executive office takes to return to planned work after an interruption, with definitions, record fields, and limits.

Remote Executive Support Editorial Desk · · 9 min read · Sources: 4 · Verified 2026-11-05

Measuring interruption recovery in executive support: a bounded protocol

Key statistics

  • The protocol measures elapsed time from the end of an interruption to the start of a sustained return to the planned task.
  • Each record should include the task, the interruption source, the channel, the start and end time, and the resume time.
  • A useful review separates self-interruptions from external interruptions and separates urgent from non-urgent contacts.
  • The cited studies examine interrupted work and meeting load; none establishes a universal recovery target for executives.

Key takeaways

  • Define recovery from the principal's planned work, not from the moment the assistant sends a message.
  • Record the interruption, the resumed task, and the first sustained work block after it so the measure is reproducible.
  • Report a distribution by interruption type and time of day; a single average hides the cases that matter.
  • Treat laboratory and survey evidence as context for the protocol, not as a benchmark for a private executive office.

Interruptions are easy to count and hard to price. An executive office can list every call, message, and walk-in, but the list does not show what the interruption cost. The more useful question is how long it took the principal to return to the work that was planned before the interruption arrived. That interval is what this protocol calls recovery. It is local, observable, and narrow enough to measure without turning the office into a surveillance system.

The evidence base is suggestive rather than definitive. Laboratory studies find that interrupted work is completed faster but with more stress and effort, and workplace surveys report heavy meeting and communication load. Those findings do not tell a particular executive how long recovery should take. This article therefore proposes a bounded method for producing a local baseline, not a universal target. The aim is to help an assistant and principal see where recovery is repeatedly lost and decide which change is worth testing.

The question and the unit of analysis

The question is: after an interruption ends, how long does it take the principal to resume the planned task in a sustained way, and how does that interval vary by interruption type, channel, and time of day? The unit of analysis is one interruption-resumption episode. An episode begins when the principal stops the planned activity and ends when the principal has returned to that activity, or to a deliberate replacement, for a defined minimum block. The protocol does not judge whether the interruption was worthwhile.

The definition of "sustained" must be set before measurement. Five minutes is a practical minimum for calendar work, document review, or preparation. A shorter return may be only a glance at the screen before another contact arrives. The office should choose one minimum and keep it constant across the sample. If the principal returns to a different task because priorities changed, record that as a deliberate redirection rather than a recovery failure.

The protocol should exclude periods that are not comparable. Travel days, live events, and scheduled all-day workshops produce interruptions by design. They can be recorded separately, but mixing them into the normal workday average makes the result uninterpretable. The same applies to a crisis week. Keep the sample window visible in the report so the reader knows what the number describes.

Define what counts as an interruption

An interruption is any event that causes the principal to stop the planned task before its planned stopping point. It can be external, such as a call from a client or a question from a colleague. It can be self-initiated, such as checking email or opening a news site. It can be a scheduled meeting that was added at the last minute. The common feature is the break in the intended sequence, not the source.

The definition should include micro-interruptions that are easy to dismiss. A notification glanced at for ten seconds can still break the thread of a document. If the principal reads the message and returns immediately, the episode is short but real. Excluding these events because they seem trivial will produce a flattering number that does not match the principal's experience.

The office should also distinguish an interruption from a deliberate pause. Standing up for water, walking to a meeting, or taking a planned break is not an interruption. The test is whether the principal intended to continue the task at that moment. If the answer is yes, the event is an interruption. If the answer is no, it belongs in a different category. That distinction keeps the record honest without requiring minute-by-minute observation.

Record the fields that make recovery visible

A minimal record has eight fields: date, planned task, interruption source, channel, interruption start, interruption end, resume time, and whether the return was sustained. Add a short note for context and a flag for whether the interruption was urgent. The record should live in the same system the assistant already uses for the principal's calendar and task list. A separate spreadsheet is acceptable only if it is reviewed on a fixed cadence.

The planned task field matters more than it appears. "Work" is not a task. "Review the acquisition memo" or "prepare questions for the board call" gives the reviewer something to compare across episodes. The task type can then be grouped into categories such as writing, reading, decision preparation, relationship work, and administration. Grouping after collection is safer than asking the assistant to classify in the moment.

Resume time is the hardest field to capture. The assistant may not be present when the principal returns to work, especially in a remote or hybrid office. One option is a lightweight check-in at the next natural contact: the assistant asks whether the principal got back to the memo and notes the time. Another is a calendar marker the principal sets when resuming. Neither method is perfect, but both are more reliable than reconstructing the day from memory at the end of the week.

Sample the episodes without inflating the result

Choose a sample window of two to four weeks and record every episode the office can observe, not only the dramatic ones. A sample built from the interruptions the assistant happened to notice will overrepresent contacts that arrived through the assistant and underrepresent direct messages, walk-ins, and self-interruptions. State the observation method in the report so the reader can judge the coverage. Keep that method identical across samples.

Record the time of day and the day of week. Interruptions cluster around predictable boundaries: the start of the day, the hour before a board meeting, and the end of the week. A single average can hide a pattern in which recovery is fine on Tuesday morning and poor on Thursday afternoon. The review should show enough slices to make those patterns visible without pretending that a small sample supports fine-grained conclusions.

Keep a separate count of interruptions that the principal initiated. Self-interruption is often the largest category in knowledge work, and it responds to different changes than external contact. If the principal checks email every few minutes, a stricter assistant routing rule will not fix the problem. The office may need a different intervention, such as a scheduled communication window or a device boundary. Measuring the source is what makes the intervention choice possible.

Interpret recovery without inventing a benchmark

The first review should describe the distribution, not grade it. Report the median and the range, the share of episodes that recovered within the chosen minimum block, and the share that did not recover before the next scheduled event. Report the count by source, channel, and time of day. A median without a range can make a volatile week look stable, and a range without counts can make one unusual episode look like a trend.

The cited research offers context, not a target. Mark and colleagues found that interrupted workers completed tasks faster but reported higher stress and effort, which suggests that speed alone is a poor measure of recovery. Microsoft's work trend reports describe meeting and communication load across many organizations, but they do not measure a specific executive's return to a specific task. The Bureau of Labor Statistics time-use data can help the office describe how time is allocated, but it does not identify interruption recovery. None of these sources supports a claim that recovery should take a fixed number of minutes.

Use the local baseline to choose one change. If most lost recovery follows direct messages, the office might test a routing rule for the first hour of the day. If it follows late meetings, the office might protect the following morning. If it follows self-interruption, the principal may need a visible cue or a scheduled check. Choose one change, define the check date, and compare the next sample with the baseline. A change that cannot be described in one sentence is unlikely to survive a busy quarter.

State the limits plainly

This protocol measures observed episodes, not cognitive recovery. A principal may sit back down at the desk while still thinking about the interruption. The record cannot see that residual load. It also cannot prove that an interruption caused a later delay, because the day contains many other causes. The method is a way to find patterns worth investigating, not a way to assign blame.

Observation can change behavior. If the principal knows the office is recording interruptions, they may batch contacts or hide self-interruptions. The review should acknowledge that possibility and treat the first sample as a baseline with unknown bias. A second sample collected after the novelty fades is more useful than a single perfect-looking week.

Privacy and access also matter. The record may reveal client names, health issues, or personnel matters. Keep it in an approved system, limit access to the people who need it, and avoid copying sensitive content into the notes. The measurement should be small enough to protect and specific enough to act on. For a related method of tracking delegated work, see the open-loop audit. For the handoff that often precedes an interruption, see how to hand off decision context.

Run a two-week trial before expanding

Start with one principal, one assistant, and one planned-task category. Record for two weeks, review the distribution, and choose one change. Do not add dashboards, sensors, or new software in the first trial. The goal is to learn whether the office can capture the fields consistently, not to build a permanent measurement program. If the record is incomplete after two weeks, fix the recording routine before drawing conclusions.

At the review, ask three questions. Which interruption type accounts for the most lost recovery? Which time of day is most exposed? Which change is small enough to test in the next two weeks? The answers should fit on one page. If they do not, the sample is too broad or the definitions are too loose. A narrow protocol that the office actually maintains is more credible than a comprehensive one that collapses after a month.

The final test is whether the measurement changes a decision. If the office collects two weeks of records and changes nothing, the exercise was observation without management. If the office changes one routing rule, protects one morning, or moves one recurring meeting, the protocol has done its job. The number is not the point. The point is a better local conversation about what attention costs and which interruptions are worth it.

Sources

Frequently Asked Questions

What does Measuring interruption recovery in executive support: a bounded protocol examine?

A local, evidence-based protocol for measuring how long an executive office takes to return to planned work after an interruption, with definitions, record fields, and limits.

What key statistics does Measuring interruption recovery in executive support: a bounded protocol report?

The protocol measures elapsed time from the end of an interruption to the start of a sustained return to the planned task. Each record should include the task, the interruption source, the channel, the start and end time, and the resume time. A useful review separates self-interruptions from external interruptions and separates urgent from non-urgent contacts. The cited studies examine interrupted work and meeting load; none establishes a universal recovery target for executives.

What are the key takeaways from Measuring interruption recovery in executive support: a bounded protocol?

Define recovery from the principal's planned work, not from the moment the assistant sends a message. Record the interruption, the resumed task, and the first sustained work block after it so the measure is reproducible. Report a distribution by interruption type and time of day; a single average hides the cases that matter. Treat laboratory and survey evidence as context for the protocol, not as a benchmark for a private executive office.

Book a Free Consultation Call