One Task, Six Notifications: The 5 Types of Notification Fragmentation

One piece of work, six notifications in six places, each showing only part of the picture. None of the tools knows the other five exist.

Illustration: One task card with six notification cards scattered around it

Take an ordinary piece of work: onboarding a new client. Sales marks the deal as won in the CRM. The client emails the signed contract. A project template assigns you twelve onboarding tasks. Brand files arrive in Google Drive, a kickoff call lands in your calendar, and a colleague asks in Slack who is preparing the welcome pack. One piece of work, six notifications in six places, each showing only part of the picture. This is notification fragmentation, and it is how most work now reaches us.

1,200App toggles a day in a study of 137 workers
~9%Of work time lost to reorienting after switches
27%Of enterprise apps integrated with each other

The price of scattered work

It is tempting to shrug fragmentation off as the small price of good tools. But small prices paid hundreds of times a day stop being small. Asana's 2021 survey of 13,123 knowledge workers found people switch between 10 apps 25 times a day, and more than a quarter said switching makes them miss actions and messages (CIO). A study published in Harvard Business Review tracked 137 people across three Fortune 500 companies and found they toggled between apps nearly 1,200 times a day, losing just under four hours a week to reorienting themselves (HBR). And in Salesforce's 2026 survey of IT leaders, only 27% of enterprise applications were integrated with each other (Salesforce).

The onboarding also does not stay the same size. Like a snowball, it gathers more as it moves: more people, more tasks, more files, and every new layer throws off new notifications.

Free ebookThe Language of InterruptionThe research behind every notification you get at work: where they came from, what they cost and what to do about them. 131 pages, free PDF.Get it free →

The five types of fragmentation

  1. Duplicates. The same event announced in several places. The kickoff call arrives as a calendar invite, an email confirmation and a Slack reminder: three notifications for one meeting.
  2. Information silos. Each tool holds a separate part of the truth. The contract terms live in Gmail, the plan in Asana, the brand files in Drive and the deal in the CRM. No single place shows the whole onboarding.
  3. Conflicting states. Two tools disagree. The welcome pack is marked done in Asana while a Slack thread still asks who owns it.
  4. Scattered settings. Every tool has its own rules for what may interrupt you. You mute the client channel in Slack, but Asana still emails every comment.
  5. Lost threads. Three weeks later the client asks what was agreed about invoicing. The contract email, the kickoff call or a Slack thread? Nobody remembers which tool holds the answer.
None of these is dramatic on its own. A duplicate costs a second. But they compound.
Audit · 6 questions

How fragmented is your work?

Think of one real project you are working on right now. Answer for that project.

This interactive part needs JavaScript.

Making work whole again

Fragmentation cannot be switched off, but it can be reduced. The aim is not fewer tools at any cost, but making each piece of work feel whole again. Picture the same onboarding, put in order: the project tool becomes its single home, with the contract, files and CRM deal linked inside it. The kickoff invite lives only in the calendar. Slack is for discussion, and every decision made there is noted back on the task. Email copies of task comments are switched off and a daily summary replaces them. The client still produces dozens of notifications, but they now point back to one place.

The cheapest fixes are habits: switching off duplicate copies, linking instead of copying, agreeing what each tool is for. They work best in small teams. The hardest fixes, like grouping related notifications across tools, depend on the tools themselves, which is where the newest layer of software is heading. For the practical, personal side, see how to stop context switching between Slack, Gmail and Asana and the SaaS consolidation checklist.

Frequently asked questions

What is notification fragmentation?

It is when one piece of work is spread across several tools, each sending its own notifications, so no single place shows the whole task and people have to rebuild it as they switch between apps.

What are the types of fragmentation?

Duplicates, information silos, conflicting states, scattered settings and lost threads.

How do I reduce app switching at work?

Give each piece of work one home, link to it rather than copying, switch off duplicate notifications, and agree as a team what each tool is for.

Sources

  1. App switching is killing your team's productivity (Asana Anatomy of Work 2021), CIO
  2. Murty, Dadlani and Das, How much time and energy do we waste toggling between applications?, Harvard Business Review (2022)
  3. Salesforce 2026 Connectivity Report

Fragmentation is a real problem. It is simply spread so thinly across the day that it rarely looks like one.

MMWritten byMarina MaksimovicFounder of Noticue and author of The Language of Interruption. She writes about how work notifications shape our attention, and builds the app that digests them.
One inbox for Slack, Gmail, Outlook and Asana.Noticue reads every notification, tells you what is urgent and plans your day. Free for the first 200 members.Get early access
Free for the first 200 members

Your unified notification inbox for Slack, Gmail, Outlook and Asana.

Every alert understood, prioritised, and ready to act on. We don’t manage your work. We digest it for you.

No credit card needed