Before You Hit Send: A 4-Question Test for Every Notification
A notification costs its sender almost nothing and its reader a moment of attention. When one side decides and the other pays, everything gets announced.

How many notifications should exist? Far fewer than arrive. Most of what happens at work should be available, not announced: recorded where anyone can find it, and pushed to a person only when it truly needs them. It is announced anyway because of an imbalance. A notification costs its sender almost nothing and its reader a moment of attention. When one side decides and the other side pays, the default drifts towards notifying about everything. Here is a test to run before you hit send.
Why everything gets notified
- Defaults decide. Many tools notify on every comment, status change and edit unless someone switches it off, and few people ever do.
- Sending is almost free. At Microsoft, one message to a list of about 13,000 people set off a reply-all storm estimated at 15 million messages (Email storm).
- Notifying feels safe. In a study of email in multinational companies, a financial controller explained why he copied so many people: he needed to cover his back, so everybody knew that everybody else knew (Machili, Angouri and Harwood).
- Systems never hesitate. A person might pause before interrupting a colleague; a tool never does.
The four-question test
A notification earns its place if the answer to at least one question is yes:
- Does it change what this person will do? If not, it is information to be found, not a call to act.
- Does it change when they must do it? If timing does not matter, it can wait for a digest.
- Would they be upset to learn it later? If not, let them find it when they look.
- Is this the right person? Copying ten people to reach one spends ten people's attention.
Should this be a notification?
Think of the message you are about to send. Four quick answers tell you which rung of the delivery ladder it belongs on.
This interactive part needs JavaScript.
The delivery ladder, from quietest to loudest
- Don't send; leave it at its source. A question about a task belongs on the task, not in a chat message about it. A link beats a copy.
- Show it at the edge. A status, a dot, a quiet line in a feed.
- Bundle it into a digest. A daily or hourly summary of everything that can wait.
- Notify normally. A visible notification that waits its turn.
- Interrupt. Break through focus, with sound and repetition. Microsoft Teams lets a sender mark a chat urgent so it notifies the recipient every two minutes for 20 minutes (Office 365 for IT Pros). Keep it for what truly cannot wait.
Most work events belong on the first three rungs. Only a small share deserve the fourth, and very few the fifth.
The other side
Notifying too little has costs too. People feel excluded when decisions happen without them, and missing a key update can be worse than reading many unimportant ones. The aim is not silence. It is judgement: the right message, to the right person, at the right moment and volume, with everything else moved from push to pull. If your team needs shared rules, start with our manager's guide to notification norms, and if you receive more than you send, see notification burial.
Frequently asked questions
How do I know if I should send a notification?
Ask whether it changes what the person will do, when they must do it, whether they would be upset to learn it later, and whether they are the right person. If all four are no, leave it at the source.
What is the delivery ladder?
Five ways to deliver information, from quietest to loudest: leave it at the source, show it at the edge, bundle it in a digest, notify normally, or interrupt.
Is it bad to cc lots of people?
Copying many people spends everyone's attention and can quietly shift responsibility from the sender to the list. Send to the person who must act.
Sources
- Email storm (including Microsoft's Bedlam DL3), Wikipedia
- Machili, Angouri and Harwood, "The snowball of emails we deal with": CCing in multinational companies (2019)
- Teams priority notifications and urgent messages, Office 365 for IT Pros
In a well-designed system, silence also communicates something: everything is on track.
Keep reading
More from the blog
Who Really Controls Your Notifications?
We have more notification settings than ever and still feel less in control. The four hands on every notification, and why control is really an agreement.One Task, Six Notifications: The 5 Types of Notification Fragmentation
Duplicates, silos, conflicting states, scattered settings and lost threads. The five types of notification fragmentation, and which fixes are within your reach.Stop, Drop and Scroll: Surviving Fake Urgency at Work
URGENT!! at 4:52 pm on a Friday, unopened by Tuesday. Why fake urgency works on your brain, what it costs, and how fire starters and fire receivers can both stop it.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