Notification Fatigue: What Slack, Email, and Teams Are Costing Knowledge Workers (2026)
The knowledge-worker side of alert fatigue. Updated April 2026. The old /slack, /email, /teams, and /scenarios pages are consolidated here.
Looking for DevOps alert fatigue? Use the Alert Fatigue Calculator or see What is Alert Fatigue.
Alert Fatigue vs Notification Fatigue
- Source: monitoring systems (PagerDuty, Opsgenie)
- Victims: on-call engineers, SREs
- Fix: SLO-based alerting, correlation
- Stakes: missed P1s, MTTR, retention
- Source: Slack, email, Teams, mobile push
- Victims: knowledge workers broadly
- Fix: async norms, batching, DND schedules
- Stakes: productivity, deep work loss
Notification Cost Calculator
# Slack Notification Overload
The Slack Workforce Index 2023 found workers receive an average of 32 @mentions per day in addition to all-channel messages. At a 3-minute check plus 23-minute refocus per mention, a worker receiving 32 Slack mentions per day spends 8.5 hours per day on notification handling alone. That is impossible in practice, which means engineers have adapted by skimming, ignoring, or not refocusing fully.
Average Slack @mentions per worker (Slack WI 2023)
Workers report being interrupted constantly by notifications (Microsoft WTI 2023)
Average refocus time after interruption (Gloria Mark, UC Irvine 2023)
Average annual cost per $80K knowledge worker at 120 notifications/day
@ Email Notification Overload
RescueTime (2019) found knowledge workers check email or messaging applications every 6 minutes on average, amounting to roughly 74 checks per 8-hour working day. Each check carries the 23-minute refocus penalty if it constitutes a true interruption. The HBR "No Meeting Wednesdays" studies found that eliminating a subset of interruptions improved productivity by 35% for the affected cohort. Email notification fatigue predates Slack and is additive to it, not a replacement.
Batch email processing to 3 fixed windows per day (08:30, 12:30, 17:00)
Turn off email push notifications on mobile during working hours
Unsubscribe from all newsletters and CC chains that do not require action
Use subject-line conventions: [FYI] = no reply needed, [ACTION] = response required
Set up filters: anything CC'd to you defaults to a lower-priority folder
T Microsoft Teams Notification Fatigue
The Microsoft Work Trend Index 2023 reports that Teams users in large organisations interact with 10+ channels and receive 50+ messages per day from channels they are nominally part of but do not actively manage. The compound effect of Teams + email + Slack (in mixed-tool organisations) creates a tripled notification burden. The same interventions apply: limit active channels, set notification hours, use @mention-only pings for genuinely urgent items, and establish team-wide response-time norms that do not penalise async work.
> Focus-Mode Scenarios
How different notification loads compare for a $100K knowledge worker working 5 days per week:
| Scenario | Notifications/day | Hours lost/day | Annual cost |
|---|---|---|---|
| Heavy Slack + email (no boundaries) | 200 | 4.2 hrs | $26,000 |
| Moderate (single tool, light async norms) | 60 | 1.9 hrs | $12,000 |
| Async-first (batched notifications, DND windows) | 20 | 0.7 hrs | $4,500 |
| Deep-work block (2hr focus, then check) | 15 | 0.5 hrs | $3,200 |