Home

How Notification Fatigue Compounds in Team Chat Over a Quarter — What Workplace-Research Studies Show

 


  Last updated: September 06, 2026

Disclosure: This article currently contains no affiliate links, and no vendor mentioned here paid for or previewed it. If that changes, I will say so here and mark any affiliate links clearly. See my Affiliate Disclosure and Editorial Policy.

Key takeaways

  • Independently sourced research (a 2014 peer-reviewed logging study, Microsoft's 2025 telemetry, and RescueTime's activity data) converges on the same picture: knowledge workers face somewhere between roughly 60 and 275+ pings a day, depending on what's counted, and the trend is rising 6–15% year over year.
  • A single interruption's cost doesn't multiply cleanly across a whole day — a common error in this space — but the net, directly measured effect is stark: about 3 hours of real focus work out of every 8-hour day.
  • Modeling that gap across a business quarter (not a single study's finding — shown as explicit arithmetic below) works out to roughly 325 hours per employee.
  • The tier of Slack, Teams, or Google Workspace a company pays for rarely fixes this: the actual notification controls are free on every tier, and the pattern matches a broader, well-documented SaaS overpay problem.

I did not start this piece with a thesis. I started it because I kept seeing the same complaint buried in software reviews I was reading for other articles: people didn't say Slack or Microsoft Teams were bad tools. They said the notifications wore them down over time — not on day one, but by week eight, week ten, the end of the quarter. That's a different claim than "notifications are annoying," and it's the one I wanted to actually check against research rather than take on faith.

So this article does three things. First, it lays out what the workplace-research literature — not marketing blog posts citing each other in a circle — actually says about notification volume and interruption cost. Second, it does the math on what that compounds to across a business quarter, and it's honest about where that math is a modeled estimate rather than a single study's finding. Third, it looks at where teams overspend trying to solve a behavioral problem with a pricing-tier upgrade, using live, verified vendor pricing as of September 2026.

A note on methodology before you read further: every statistic below is attributed to its original source, with a link in the Sources section at the end. Where I had to combine numbers from different studies to build the quarterly estimate, I say so explicitly and show the arithmetic, rather than presenting it as something a single research team measured directly. I'd rather you distrust one paragraph than the whole article.

What the research actually measures (and what it doesn't)

Three separate research traditions feed into "notification fatigue," and they don't always agree on units, which is part of why blog posts about this topic get sloppy.

How many notifications people actually receive. The most-cited peer-reviewed number comes from Pielot, Church, and de Oliveira's 2014 MobileHCI logging study, which tracked real phone usage rather than relying on self-report and found a median of 63.5 notifications per day. That's a mobile-notification figure, not a workplace-chat-specific one, but it's a useful, methodologically solid floor.

Microsoft's Work Trend Index, published in April 2025, comes at it differently: it's not a survey, it's aggregated telemetry from Microsoft 365 accounts. It found that the average worker receives 153 Teams messages and 117 emails on a typical weekday, and that during core work hours, workers are interrupted roughly every two minutes — adding up to about 275 pings a day once meetings, email, and chat are all counted. It also found something that speaks directly to the "over a quarter" framing of this article: chats sent outside the traditional 9-to-5 workday are up 15% year-over-year, with roughly 58 messages now arriving before or after normal hours. That's not a snapshot problem. That's a trend line moving in one direction across the same measurement periods, quarter after quarter.

What a single interruption costs cognitively. This is Gloria Mark's territory. Mark, a professor of informatics at UC Irvine, ran the field study behind the frequently cited "23 minutes to refocus" figure — informants were tracked in real offices, and the paper found that after an interruption, people took roughly 23 minutes to fully return to the original task. It's worth flagging that this number gets misquoted constantly online (some outlets round it to 25 minutes, citing an earlier 2005 paper by the same author), and I'd treat "about 20–25 minutes" as the honest range rather than treating 23:15 as a precise constant. Mark has also pushed back on the popular narrative that blames software alone: in interviews about her research, she's noted that people turn out to be just about as likely to interrupt themselves as to be interrupted by an incoming notification — meaning the fix isn't purely a software setting.

What all of this adds up to across a working day. RescueTime, which has logged activity data from tens of thousands of knowledge workers over more than a decade, reports that the average knowledge worker gets three hours or less of what it calls "Focus Work" out of a typical eight-hour day. Microsoft's telemetry backs this from a different angle: across Microsoft 365 apps, communication work (meetings, email, chat) now consumes a majority of the measured workday, leaving well under half for the deep, synthesis-heavy work most knowledge jobs actually exist to produce.

Here's the thing many "productivity cost" articles get wrong, and I want to name it directly because it's a credibility marker for how you should read the rest of this piece: you cannot validly multiply "275 interruptions" by "23 minutes to recover" and get a number in the thousands of minutes — that exceeds the length of the workday itself, and it's a math error that shows up constantly in this space. What you can do is use the directly measured net effect — RescueTime's 3-hours-of-focus-work finding — as your anchor, because that number already accounts for the fact that recovery periods overlap, get interrupted again mid-recovery, and compress.

Doing the quarter-long math, explicitly

Here is the model, with every assumption stated:

  • A standard business quarter runs roughly 13 weeks, or about 64–65 working days after accounting for a couple of holidays.
  • RescueTime's data says knowledge workers get roughly 3 hours of Focus Work out of an 8-hour day — call it a 5-hour daily gap between scheduled work time and actual deep-focus time, some (not all) of which is attributable to chat and email interruptions specifically, alongside meetings and self-interruption.
  • Multiply 5 hours by 65 working days: that's roughly 325 hours per employee, per quarter, spent in a fragmented, non-deep-focus state rather than sustained concentration.

That 325-hour figure is not a number any single study reports — it's arithmetic built from a real, sourced daily measurement extended across a real, sourced calendar period. I'm showing you the math specifically so you can disagree with the assumption (maybe you think chat accounts for 40% of that gap, not 60%) and adjust it for your own team rather than take my word for it.

What compounds this across a quarter rather than a single bad week is the trend data, not just the level data. Microsoft's year-over-year figures — messages up, after-hours chat up 15%, ad hoc meetings at 60% of all meetings — mean the baseline itself is rising each quarter, not holding steady. Separately, longitudinal occupational-health research on burnout (distinct from the tech-industry telemetry above) consistently finds that exhaustion from sustained digital-communication load builds over a period of months rather than appearing after a single bad day, which is the academic basis for why "week one" and "week twelve" of the same chat habits don't feel the same to the person living through them, even though the daily notification count hasn't changed.

What that looks like in practice: real user reviews

Vendor pricing pages and press releases won't tell you this part. Verified user reviews on G2 and Capterra will.

On Slack, one G2 reviewer's dislikes section put it plainly, describing "frequent notifications that break my focus" as a recurring problem once someone is active in a lot of channels. Another reviewer on the same platform described a related pattern: constant pings from channels, threads, mentions, and connected apps that "start to feel overwhelming" in larger teams. G2's own aggregated pros-and-cons summary for the product backs this up, naming notification overload and a "culture of immediacy" that discourages deep work as recurring, commonly cited complaints.

Microsoft Teams draws a similar pattern from its own reviewer base. Capterra's aggregated review summary for Teams notes that most reviewers describe notifications as inconsistent, delayed, and excessive enough to cause missed messages. A G2 reviewer described the same tension from the other direction, noting the platform can feel resource-heavy at times and that its notifications are "overwhelming and hard to manage effectively."

What's notable across both tools' review bases is that the complaint is rarely about a missing feature. It's about volume and defaults — the tools work as designed; the design just wasn't built with a quarter-long time horizon in mind.

The overpay pattern: paying for a tier that doesn't fix the problem

This is where the research crosses into a buying decision, and it's the part most "which chat app is best" content skips entirely.

Here is live, first-party pricing as of September 2026:

Plan Vendor list price (annual billing) What it adds over the tier below
Slack Free $0/user/mo Core chat, 90-day message history
Slack Pro $7.25/user/mo Unlimited history, unlimited integrations, group calls
Slack Business+ $15/user/mo SAML SSO, compliance data exports, 99.99% uptime SLA, advanced Slack AI
Slack Enterprise+ Custom (real-world median ~$26/user/mo, per Vendr's analysis of 535 verified deals) Multi-workspace org controls, DLP, enterprise key management
Microsoft Teams Essentials $4/user/mo Meetings, chat, 10GB storage
Microsoft 365 Business Basic $7/user/mo Web/mobile Office apps, business email
Microsoft 365 Business Standard $14/user/mo Desktop Office apps
Microsoft 365 Business Premium $22/user/mo Advanced device security, cyberthreat protection
Google Workspace Business Starter $7/user/mo Gmail, Chat, Meet (100 participants), 30GB storage
Google Workspace Business Standard $14/user/mo 2TB storage, Meet recording, 150 participants

Now here's the overpay pattern specifically: the core notification controls that actually address fatigue — Do Not Disturb, custom notification schedules, muting channels, pausing alerts — are free features, available on Slack's free tier and every paid tier alike. Slack's own help documentation confirms notification schedules and DND are configurable by any user regardless of plan; the one exception is a "focus mode" VIP-override feature reserved for paid plans, which is a minor refinement, not the core fix.

What this means in practice: a team that upgrades from Slack Pro to Business+ specifically believing it will solve notification overload is paying an incremental $7.75 per user, per month — $93 per user, per year — for a problem that plan doesn't touch. For a 50-person team, that's $4,650 a year spent on SAML SSO and compliance exports (genuinely useful for other reasons) while the notification-fatigue complaint sitting in their internal feedback survey goes unaddressed, because the actual fix — channel hygiene, muting non-essential channels, setting an organization-wide default quiet-hours schedule, and changing the norm that @here means "read this in the next five minutes" — costs nothing and isn't a pricing-tier feature at all.

This isn't a hypothetical pattern. It matches what SaaS-spend researchers see across categories generally. Vertice's 2026 analysis of enterprise software portfolios found that roughly 15% of purchased applications sit entirely unused as pure "shelfware," and that another 51% are underutilized, with organizations paying for far more capacity than employees actually use. Zylo's SaaS Management Index, cited by multiple analyses this year, puts average license utilization at 54%. And License Logic's research is nearly a direct description of the notification-tier problem: businesses commonly buy a "premium" license for every user specifically to avoid feature limitations, even when most employees only ever needed the basic tier's functionality.

Translate that to team chat specifically, and the pattern is: pay for the tier that promises "better collaboration," when the thing actually degrading collaboration is a default notification setting nobody configured and a culture where every channel feels mandatory. The upgrade fixes procurement's compliance checklist. It does not fix the quarter-long fatigue curve described above.

What the research says actually helps

None of the studies above suggest team chat should be abandoned — Slack, Teams, and Google Chat all solve a real problem (email's slowness) that predates them. The research instead points to specific, low-cost interventions:

  • Set an organization-default quiet-hours schedule, not just an individually-opt-in one. Slack and Teams both support admin-level defaults; most teams never set them, leaving each employee to independently discover and configure the feature.
  • Audit channel membership quarterly. Muting isn't the fix if muted channels still contribute to visible unread counts and background anxiety; removal from channels that no longer apply is more effective than muting, per the pattern in reviewer complaints about "dozens or hundreds of channels."
  • Separate urgent from FYI at the point of sending, not receiving. Gloria Mark's research on self-interruption suggests that giving people a genuinely reliable "this can wait" channel (and trusting it) reduces the anxious over-checking that muting alone doesn't solve.
  • Measure focus-time trend, not notification count, quarter over quarter. Given that Microsoft's own telemetry shows the underlying volume climbing 6–15% year-over-year depending on region, a team that doesn't actively counter the drift will simply arrive at the same fatigue point sooner each quarter.

Quick answers

Is Slack or Microsoft Teams worse for notification fatigue? Neither is inherently worse — the review-based complaints above look nearly identical across both, and both give admins the same core levers (org-wide quiet hours, channel/team muting). The difference is less the software and more how a given organization has configured and normed around it.

Does upgrading to a higher-tier plan reduce notification overload? Not directly, based on what's actually gated behind each tier. Slack's Business+ and Microsoft's Business Premium add security, compliance, and admin-control features — genuinely useful for other reasons — but the notification-schedule and Do Not Disturb controls that address fatigue are already present on the entry-level and free tiers.

How would a team check if this is actually a problem for them, rather than assume it? Rather than trusting a gut sense that "Slack is exhausting," pull three things: the number of channels the average employee belongs to (most tools show this in admin analytics on paid plans), whether an org-wide quiet-hours default has ever been set, and a simple pulse survey asking employees to rate whether they feel able to disconnect after hours — then re-run that same survey next quarter and compare, rather than relying on a single point-in-time read.

Does this apply to Google Chat too? The pattern holds. Google Workspace's Business Starter ($7/user/month) through Business Plus ($22/user/month, annual) tiers gate storage, meeting size, and admin/security controls — not core notification muting, which is a per-user Chat setting available at every tier. The overpay dynamic described above for Slack and Teams applies just as directly to a team upgrading Workspace tiers in the hope of fixing chat fatigue.

Bottom line

The research supports the complaint I started with: notification fatigue in team chat is a compounding problem, not a first-week annoyance, and the compounding is now measurable in Microsoft's own telemetry as rising communication volume quarter over quarter. But the fix that actually matches the research is behavioral and configuration-level, not a pricing-tier upgrade — and teams paying for Business+ or Business Premium specifically to solve notification overload are, per the vendors' own documentation, paying for something that plan doesn't include.

Methodology & sources

This article combines: one peer-reviewed academic logging study (Pielot, Church & de Oliveira, MobileHCI 2014); one academic field-study author's body of work on interruption cost (Gloria Mark, UC Irvine, CHI 2008 and related publications); one large-scale telemetry report (Microsoft Work Trend Index, April 2025, based on Microsoft 365 usage data); one longitudinal industry activity-tracking dataset (RescueTime); verified user reviews from G2.com and Capterra.com, quoted under fifteen words per source per this publication's editorial quoting policy; and first-party vendor pricing pages, checked in September 2026. The 325-hour quarterly estimate in this piece is this publication's own calculation built from the RescueTime and calendar figures cited, clearly presented as a model rather than a directly measured statistic — readers should adjust the underlying assumptions for their own team's context rather than treat it as a universal constant.

Affiliate & editorial disclosure

SaaSSoftwareReviews.com is an independent, individually operated publication. Vendors do not review or approve this content before publication, this article currently contains no affiliate links and no vendor paid for or influenced the analysis, pricing comparisons, or conclusions above. Pricing is verified against official vendor sources at the time of writing and is subject to change; check the vendor's current pricing page before purchasing.

This publication updates the above as vendor program terms change, and would rather tell you a link isn't earning me anything than imply otherwise.

About the author

Sandra Robert is the founder and editor of SaaS Software Reviews, an independent site that compares the real cost of business software. She checks prices against vendor pages and linked sources where possible, dates the figures, and updates articles when I learn of pricing changes. Corrections? Contact Sandra.



 

Above: an original chart built from the three figures cited in this article — not a vendor screenshot. Sources noted in the chart caption.

 

Above: Sandra Robert's own Slack workspace, Preferences → Notifications. Every control shown here — how to notify you, mobile notification timing, and what to show in Activity — is available on Slack's free tier, with no plan-upgrade prompt anywhere in the panel.