This brief is designed for enterprise leaders, operations teams, and product organizations that need to increase output without silently increasing cognitive strain. The core question is not whether interruptions exist, but how interruption patterns change total cognitive load and long-horizon decision quality. Across controlled interruption conditions, Mark et al. (2008) reported faster completion time in interrupted work (baseline: 22.77 min; same-context interruption: 20.31; different-context interruption: 20.60), with no significant quality drop in email errors. At face value, this looks positive for throughput. However, workload-related indicators moved in the opposite direction: stress rose from 6.92 (baseline) to 9.46 (same-context) and 9.13 (different-context), while effort rose from 9.50 to 11.04 and 11.52 on a 1-20 scale. In practical terms, teams can appear faster while paying a hidden cognitive tax. This creates a known enterprise risk pattern: short-term performance appears stable, but system-level resilience weakens as mental effort stays elevated for longer periods. When this pattern persists, organizations often see delayed symptoms: reduced decision consistency, lower tolerance for ambiguity, shallow prioritization, and increased rework. Task-switching research supports this interpretation. Rubinstein et al. (2001) and later synthesis work show that switch costs are real, reproducible, and strongly sensitive to rule complexity. This means the same interruption policy can be manageable in low-complexity work but costly in high-complexity work. For enterprise implementation, this reinforces a portfolio approach: protect uninterrupted blocks for high-load tasks while using explicit interruption channels for time-critical events. Recommended practical model for rollout: 1) Measure baseline load and interruption frequency by team and task type. 2) Classify interruption classes (critical, urgent, deferrable). 3) Introduce response windows and protected focus blocks. 4) Track both throughput metrics and cognitive-load proxies over 4-8 weeks. 5) Recalibrate policies by role and complexity tier. The strategic objective is not zero interruption. The objective is sustainable high performance under high cognitive demand. Organizations that operationalize interruption governance typically gain better output stability, improved decision quality, and lower hidden fatigue cost over time.
Observed Interruption Effects (Mark et al., CHI 2008)
Time to task completion and perceived stress by interruption condition
Methodology
Structured evidence synthesis focused on controlled interruption experiments and task-switching studies relevant to enterprise knowledge work. Source selection prioritized peer-reviewed studies that reported measurable outcomes (time, error, workload, stress, effort) under interrupted and uninterrupted conditions. We extracted central tendencies and directional effects, then translated them into practical implications for high-complexity operating environments. The synthesis framework used four decision lenses: throughput impact, quality impact, cognitive cost, and implementation feasibility for teams with cross-functional dependencies.
Key Findings
- - Interrupted conditions showed faster task completion time than uninterrupted baseline in controlled email-work simulations.
- - Despite faster completion, interruption conditions reported higher stress, frustration, time pressure, and effort on NASA-TLX-derived scales.
- - Task-switching literature consistently reports a switch cost, with higher cost under greater rule complexity and reduced cost with cueing.
- - Observed enterprise implication: apparent productivity gains can hide rising cognitive load, creating latent risk in decision quality and fatigue accumulation.
- - Operationally, interruption governance (when/why to interrupt) is more effective than attempting to remove interruptions entirely.
Limitations
- - Primary interruption experiment was lab-based with n=48, so direct transfer to every enterprise workflow should be validated in pilot programs.
- - Outcome measures combine objective task timing and subjective workload; organizations should pair both with internal operational KPIs.
- - The source set includes mixed task domains; results are strongest for analytical and communication-heavy work, and may differ in highly procedural roles.
- - This brief is a synthesis, not a new randomized field trial; downstream implementation should include internal baseline measurement and review checkpoints.