Free Calculator

What Interruptions Are Costing Your Team

A single interruption costs almost nothing. Fifteen a day, across a team, costs a fortune. The bill is the time it takes to refocus after each one, and it never shows up on a timesheet. Run yours.

$

Used for loaded hourly cost of focus time

1 6 people 30

Set to 1 and use your salary to run it for yourself

3 12 / day 40

Slack pings, "quick questions," meetings, email breaks

2 10 min 25

Research average is ~23 min (Gloria Mark, UC Irvine). Default is conservative.

Annual cost of fragmentation

$140,000

Significant. Fragmentation is eating real capacity.

The cost is the refocus tax: the time each person spends reloading their task after every interruption, multiplied across the team, every day. It never appears on a timesheet.

Lost focus / person

7 hrs/wk

of effective focus time

Focus FTEs lost

1.1

full-time equivalents

Running per month

$11,700

current burn rate

Refocus tax / day

90 min

per person

What Halving the Interruptions Would Save

You cannot get to zero interruptions, and you should not try. But protected focus blocks and async-by-default routinely cut the count in half, and the refocus tax falls with it.

Current annual cost

$140,000

at your current interruption count

After cutting interruptions in half

$70,000

recovered focus, zero spend

What This Number Means for You

The cost is the refocus, not the interruption.

A two-minute question does not cost two minutes. It costs the two minutes plus the time to rebuild the task you were holding in your head, which research puts far higher than people expect. That reload is the real bill, and it scales with how much deep work the role requires.

Protecting focus is management work, not a perk.

The team cannot defend its own focus from cross-team pings, meeting invites, and the culture of instant replies. You can. Protected focus blocks and async-by-default are among the highest-leverage things a manager does, and they cost nothing. The manager leverage calculator frames why this counts as real work, and the manager's time budget calculator shows where the hours actually go.

You are probably the biggest interrupter.

Managers tend to underestimate how often their own "quick questions" and instant-reply expectations fragment the team. Modeling async, batching your asks, and rewarding deep output over fast responsiveness changes the team's whole interruption budget. This is downstream of the leadership skills in the pillar guide, particularly developing others and leading by removing what is in their way.

About the numbers: Loaded labor cost = salary × 1.3 (benefits and overhead). Refocus tax = interruptions/day × minutes-to-refocus, treated as lost-equivalent productivity (degraded output during the reload window, not literal idle time). Daily loss is capped at 60% of an 8-hour workday so high interruption counts stay believable. Annualized over 240 workdays. Research basis for refocus time: Gloria Mark, UC Irvine (~23 min average; the calculator defaults lower). These are planning baselines, not a time-and-motion study. Adjust the inputs to your reality.

The Most Expensive Thing on Your Team Is Invisible

Ask a manager where their team's productivity goes and they will point to meetings, unclear priorities, or under-staffing. Almost nobody points to fragmentation, because fragmentation does not look like anything. There is no meeting on the calendar called "lost the thread after a Slack ping." There is no line item for "re-read the same paragraph four times because the afternoon kept getting interrupted." The cost is real, large, and completely invisible, which is exactly why it persists.

Gloria Mark's research at UC Irvine is the reference point most people have half-heard: after an interruption, it takes an average of about 23 minutes to fully return to the original task. Even if you do not believe the full number for your team, halve it and the math is still brutal, because the cost does not come from one interruption. It comes from multiplying a modest refocus cost by every interruption, every person, every day, for a year.

Why the Refocus Tax Compounds

The reason fragmentation is so costly is that knowledge work has a warm-up cost. Loading a complex task into working memory (the variables in the code, the structure of the document, the threads of the analysis) takes time, and an interruption dumps it. You do not resume where you left off. You resume several steps back, rebuilding context, and you make more errors on the way back up because the model in your head is incomplete.

This is why a day with five hours of "available time" broken into twelve fragments produces far less than a day with three uninterrupted hours. The fragmented day spends most of its capacity on reloading. The protected day spends it on the work. Same hours on the clock, wildly different output, and the difference is entirely in how the time was shaped.

The Three Moves That Actually Work

  1. Protected focus blocks. The team agrees on hours (a morning, two afternoons, whatever fits) with no internal meetings and no expectation of instant replies. The single most effective intervention, and it costs nothing but the discipline to hold the boundary.
  2. Async by default. Most questions are not urgent. Route them to a channel that gets answered in batches rather than letting each one interrupt in real time. Reserve real-time interruption for things that are genuinely time-critical, which is a much smaller set than current habits assume.
  3. Manager models it. If you send "quick questions" expecting instant answers, or visibly reward the person who replies in ten seconds over the person who shipped deep work, the team learns that responsiveness beats focus. The interruption budget is set by what you reward. Reward the output.

Pick one this week. Protected focus blocks have the best ratio of effort to return. Announce the hours, hold the boundary for two weeks, and re-run this calculator with a lower interruption count. The recovered capacity is the cheapest headcount you will ever add.

Frequently Asked Questions

What counts as a context switch or interruption?
Anything that pulls a person off the task they were doing and onto something else: a Slack ping they answer, a "quick question" at their desk or in a DM, a meeting that breaks their afternoon in half, an email they stop to read, a notification they check. The cost is not the interruption itself (most are short). The cost is the time it takes to fully reload the original task into working memory afterward, which research puts much higher than people expect.
Where does the "minutes to refocus" number come from?
The most cited figure is from Gloria Mark's research at UC Irvine, which found it takes an average of about 23 minutes to fully return to a task after an interruption. That is the headline number. The calculator defaults to a more conservative figure because not every interruption resets you to zero, and knowledge workers develop partial-recovery habits. Even at half the research number, the cumulative cost across a team is large, because it multiplies by every interruption, every person, every day.
Is the full refocus time really "lost"?
Not entirely, which is why the calculator is conservative and caps the daily loss. During the refocus window you are still working, just at degraded effectiveness: re-reading what you had, rebuilding the mental model, making more errors. The calculator treats the refocus time as lost-equivalent productivity rather than literal idle time, and caps total daily loss at 60 percent of the workday so the number stays believable even at high interruption counts.
Why does this cost so much more than it feels like?
Because it is invisible per instance and enormous in aggregate. A single interruption costing fifteen minutes of refocus does not feel like anything. The same person taking fifteen such hits a day is losing a large fraction of their deep-work capacity, every day, and nobody sees it on a timesheet. Multiply by a team and it is often the single largest hidden productivity cost a manager controls, and one of the few they can fix without spending money.
How is the "focus FTEs lost" number calculated?
It sums the lost focus hours across the whole team per week and divides by 40. If your team of six is each losing roughly seven hours of effective focus per week, that is 42 hours, or just over one full-time-equivalent of capacity evaporating into fragmentation every week. It is a useful way to translate scattered minutes into a number a manager can actually feel: you are effectively short one person, and you are still paying for them.
What actually reduces context-switching cost?
Three moves with the best ratio of effort to return: (1) protected focus blocks, where the team agrees on hours with no meetings and no expectation of instant Slack replies; (2) moving to async by default, so most questions go to a channel and get answered in batches rather than interrupting in real time; (3) the manager modeling it, by not sending "quick questions" that expect instant answers and not rewarding instant responsiveness over deep output. The manager leverage calculator shows how protecting the team's focus is itself high-leverage management work.
Does this apply to the manager too?
Yes, and often worse. Managers tend to have the most fragmented calendars on the team and the highest interruption load, which is why strategic work keeps sliding. You can run the calculator for yourself by setting team size to 1 and using your own salary. The decision fatigue cost calculator covers the related load of being the team's decision bottleneck, which usually rides alongside fragmentation.

The Cheapest Headcount You Will Ever Add Is the Focus You Stop Wasting.

Announce one protected focus block. Move questions async. Stop rewarding instant replies over deep output. Re-run this in two weeks with a lower count.

Pillar: Leadership Skills for New Managers → Calc: Manager's Time Budget →

Related: Decision Fatigue Cost → Related: Manager Leverage →

← All Calculators