Notification overload: rules for internal communication
Notification overload means that so many alerts arrive that people stop reading them. A notification is the small message a program sends to say that something happened: a beep on the phone, a red dot, an email. The noise is annoying, but the real harm is the one message that mattered and was swiped away with forty that did not. A few simple rules for internal communication fix this.
Where it comes from
Think of a car alarm in the street. If it goes off every night, nobody looks out of the window any more. Alerts at work wear out in the same way.
It rarely comes from one bad decision. Each program tells everyone about every change. Each person is added to the list "to be safe". The same news arrives as an email, in the program and on the phone. Each step seemed sensible. Together they bury the day.
First, agree on three levels
Most arguments about alerts are really about how fast someone is expected to answer. Settle that first.
| Level | What it means | How it should arrive |
|---|---|---|
| Now | Something is broken, or a customer is waiting. Answer within the hour. | A phone call or a direct message |
| Today | Someone needs your decision or your work by the end of the day. | One alert in one place |
| Good to know | Nothing to do. | A daily or weekly summary |
Five rules
- Tell only the person who has to do something. You were given a task, asked to approve something or addressed by name: that deserves an alert. A small change to something you only follow does not.
- One piece of news, one place. The same task as an email, a chat message and a beep on the phone is three interruptions for one fact. Choose one and switch the others off.
- Say enough to judge it unopened. "Maria asks you to approve the quote for Hartmann" can be judged in two seconds. "New request" cannot.
- Collect what is only information. Finished tasks and weekly figures belong in one summary, not in twenty single messages.
- Give announcements an end date. "The office is closed on Friday" should disappear on Saturday by itself.
A thirty-minute check
Ask three people with different jobs to count their alerts for one working day. They sort them into three piles.
- I had to do something.
- I was glad to know.
- I did not need this.
Then take the third pile and switch off where it comes from, one kind at a time. Do it once for everyone, not in each person's own settings. Repeat the count after a month.
Quiet time belongs to the rules
Rules for sending need a partner rule for receiving. Agree on hours when nobody has to answer messages that are not urgent. Allow people to close their inbox for an hour of focused work.
This only works when everyone trusts the "now" level. People can ignore the rest calmly because they know a real emergency will reach them by phone.
How Worknano handles this
In Worknano the bell at the top of the screen is your personal inbox for notifications. Nobody can fill it by hand. Every entry is created by an automatic rule, from a template you can edit. The template says who is told, for example the owner of the record, and which page opens when the entry is clicked. Email or chat can be added per template. Announcements are separate: you choose the audience, a start date and an end date, and whether a message pops up only once. Each person sets their own desktop notices for chat. With tasks, approvals and messages in one workspace, there is one bell to check.
- How to read the bell and edit notification templates
- How to post an announcement
- Chat settings: your own notification switches
Create a free workspace and decide, template by template, who hears about what.