Our Take
The piece correctly identifies the cost of fragmentation but offers no evidence that these tactics actually recover the 23-minute loss or improve output quality.
Why it matters
Organizations are adding AI tools and communication layers faster than employees can absorb them, extending the refocus penalty. HR teams need hard data on which interventions actually work before redesigning workflows around them.
Do this week
HR leader: audit your recurring meetings this week and cancel those without explicit decision criteria so you can baseline where interruptions actually originate.
The refocus tax is real and growing
Research by Gloria Mark at the University of California, Irvine shows that workers need an average of 23 minutes and 15 seconds to refocus after an interruption. The problem is not new, but the number of interruption vectors has exploded. Employees now contend with notifications from multiple apps, scheduled meetings (online and offline), various communication tools, message boards, and newly-deployed AI assistants that demand attention within minutes of each other.
The cost of this fragmentation extends beyond lost time. Mark's research also found that employees interrupted during tasks work faster to compensate, but at a measurable price: higher workload perception, elevated stress, greater frustration, increased time pressure, and more effort expended. Organizations treating this as a scheduling problem rather than a structural one are leaving productivity and retention gains on the table.
The tactics are sound; the evidence is incomplete
The article proposes concrete interventions: no-interruption work blocks (1-2 hours at the start or end of the week), routine analysis to map where interruptions originate, meeting audits to eliminate unnecessary recurring calls, protected focus hours, and consolidation of tools and apps. These are reasonable. But the piece does not establish whether implementing any of these tactics actually recovers the 23-minute refocus penalty or moves the quality/quantity needle on actual output.
The missing layer is measurement. Which interruption sources matter most? Does protecting two hours of deep work per week materially change error rates, cycle time, or employee burnout scores? The article treats focus as an operational hygiene issue when it may actually be a strategic capacity constraint. Organizations pursuing AI adoption simultaneously often neglect to ask: are we adding tools faster than employees can absorb them, and is that the real blocker?
Start with the interruption map, not the calendar block
Before blocking focus time, audit where interruptions actually come from in your organization. Are they meeting-driven, tool-driven, or people-driven? Which teams report the highest refocus cost? A week of data from your communication logs, calendar system, and a brief survey will tell you whether the problem is meeting density, tool sprawl, or something else entirely.
Only after you have that baseline should you pilot a no-interruption block. Measure the outcome: does it move quality metrics, cycle time, or engagement scores? If not, the problem may not be time scarcity but task clarity, role ambiguity, or tool friction. The article is right that focus is a priority; it's just incomplete on how to prove which levers actually work.