Interruption Cost Estimator
Calculate productivity loss from workplace interruptions and context-switching. Enter values for instant results with step-by-step formulas.
Formula
Daily Lost Hours = Interruptions × (Interruption Minutes + Recovery Minutes) / 60; Daily Cost = Lost Hours × Hourly Rate; Annual Team Cost = Daily Cost × Work Days × Team Size × 12
The formula calculates total productivity loss by combining direct interruption time with recovery time. Each interruption triggers a recovery period—the brain needs time to reload context. Multiplying by hourly rate converts time loss to dollars. Scaling by team size reveals organizational impact. This works because it captures the hidden cost: the 5-minute question doesn't cost 5 minutes, it costs 5 minutes plus 15-20 minutes of regaining focus. Most people drastically underestimate this cost until they see the math.
Worked Examples
Example 1: Software Development Team
Problem:10 developers, $100/hour, 18 interruptions/day, 5 min each, 20 min recovery. Slack-heavy culture.
Solution:Lost time: 7.5 hours/person/day (94%). Only 0.5 productive hours remain. Team cost: $750/person/day × 10 = $7,500/day $7,500 × 22 workdays × 12 months = $1.98M/year.
Result:$1.98M annual cost | About 6% productive time left | Async communication urgently needed
Example 2: Product Management
Problem:5 PMs, $85/hour, 25 interruptions/day (meetings + Slack), 3 min avg, 10 min recovery.
Solution:Lost: 5.4 hours/person/day (68%). Team cost: $460/person/day × 5 = about $2,302/day $2,302 × 22 workdays × 12 months = about $608K/year. Meeting culture is the main driver.
Result:$608K annual cost | Meeting overload | Batch meetings to specific days
Example 3: Engineering Leadership
Problem:3 senior engineers, $125/hour, 12 interruptions (code reviews, questions), 8 min, 25 min recovery.
Solution:Lost: 6.6 hours/person/day (83%). These high-value employees have only about 1.4 focused hours left. Team cost: $825/person/day × 3 = $2,475/day $2,475 × 22 workdays × 12 months = $653K/year.
Result:$653K annual cost | Senior talent underutilized | Office hours for questions
Frequently Asked Questions
How much do interruptions really cost?
Research suggests interruptions cost 23 minutes of recovery time on average. For a $75/hour worker interrupted 15 times daily, that's ~$300/day in lost productivity—over $70K annually per person.
What types of interruptions are most costly?
Context-switching between different types of work is most costly. Slack/email notifications, unscheduled meetings, and 'quick questions' are common culprits. The cost increases with task complexity.
How do I reduce interruptions?
Implement focus time blocks (2-4 hours of uninterrupted work), use async communication, batch meetings, set Slack/email check times, and create team norms around interruptions.
What about necessary interruptions?
Some interruptions are valuable (urgent issues, important decisions). The goal isn't zero interruptions but reducing unnecessary ones. Create escalation paths that protect focus time for non-urgent items.
How do open offices affect interruptions?
Open offices can increase interruptions 60-70% compared to private offices. Mitigations: quiet zones, visual 'do not disturb' signals, and scheduled office hours for questions.
Does remote work reduce interruptions?
Remote work can reduce in-person interruptions but may increase digital ones (more Slack, more video calls). Intentional async culture is needed to realize productivity benefits.
How do I measure interruptions?
Track for one week: log each interruption (source, duration, whether necessary). Time-tracking tools like RescueTime can help. Most people underestimate interruptions by 2-3x.
What's a reasonable interruption level?
5-10 significant interruptions per day is manageable for most knowledge work. Above 15 significantly impacts deep work. Some roles (support, management) naturally have more but should still have focus time.
How do I convince management this matters?
Calculate the cost: team size × interruptions × (interruption + recovery time) × hourly rate. The annual figure is usually surprising. Propose a pilot: one week of focus time blocks with productivity measurement.