Research question

What does published research suggest about the capacity lost when recurring administrative work is fragmented by interruptions?

Evidence

Gloria Mark and colleagues observed information workers and found that interrupted work was often completed faster, but with higher reported stress, frustration, effort, and time pressure. A later controlled study by Borst, Taatgen, and van Rijn found that interruption effects depend on the mental state that must be reconstructed: resumptions were slower when people had to rebuild more task context. These studies do not establish one universal “minutes lost” figure, but they do show that switching costs are real and context-dependent.

The evidence matters for operations because coordination work contains many small stateful tasks: reconciling an owner’s update with a tracker, checking whether evidence satisfies a requirement, or preparing a handoff from several source records. Each may look short when measured in isolation. Fragmentation adds reconstruction work that a task count misses.

Operations-specific analysis

The practical unit of capacity is therefore not simply available clock time. It is uninterrupted time with the relevant context accessible. A coordinator who alternates continuously among inboxes, project boards, and chat may close many messages while leaving verification-heavy records unfinished. Conversely, batching every interaction can make urgent exceptions wait too long.

A useful local test separates work into two classes. Time-sensitive intake and escalation should be checked at defined service intervals. Context-heavy reconciliation, documentation, and reporting should receive protected blocks. For four weeks, record planned block length, interruption count, completion rate, and correction rate. Compare like tasks rather than attributing every delay to interruption.

This design preserves authority boundaries. A support professional can maintain the log, schedule agreed focus blocks, and route exceptions. The accountable leader still decides service levels, priorities, and which events justify interruption.

Conclusion

Research supports treating interruption as an operating condition, not a personal failing. Small teams should avoid applying a universal recovery-time claim. They can instead measure which recurring coordination tasks lose accuracy or completion when fragmented, then design response windows and protected blocks around their own evidence.

Sources and limits

The studies use different tasks and settings. They support the existence and mechanisms of switching costs, not a fixed productivity conversion for every workplace.