Published October 12, 2026.
An interruption count alone cannot show whether an executive office is protecting attention. One urgent safety escalation and ten redundant status pings are not equivalent. This review proposes an observation method that separates interruption source, consequence, recovery, and preventability without treating every contact as a defect.
Evidence and scope
NIOSH resources describe work-schedule and human-factors concerns, while federal plain-language guidance supports clear, audience-centered communication. These sources do not establish a universal interruption limit for CEOs. The method below is an operational synthesis for baseline learning, not a productivity diagnosis.
Event definition
Record an interruption when unplanned input causes the executive or assistant to switch from the current intended task. Capture channel, requester class, stated urgency, action taken, duration band, recovery marker, and whether an existing route should have handled it. Do not copy sensitive content into the study extract.
Sampling design
Sample representative weeks, including travel, board preparation, and ordinary operations. Use short diary prompts plus calendar and channel metadata available under policy. Report observation coverage and missing intervals. A self-selected high-pressure day is not a baseline.
Interpretation
Group events into necessary escalation, avoidable clarification, missing-owner routing, repeated status request, and personal preference. Compare count, time, and recovery burden. A reduction in interruptions is not beneficial if important concerns are suppressed or moved into hidden channels.
Limitations
Observation changes behavior, duration estimates are imperfect, and context determines value. The method can identify routing and communication patterns; it cannot measure cognitive harm or prove that a specific interruption caused a decision outcome.