Deciding what is allowed to interrupt you
Every module ships with notifications turned up, because the people who built it think their part is the important one. All thirty are wrong at once.
Thirty modules with sensible defaults produce an unreasonable amount of noise together. Nobody designed that; it is just what happens when every part is individually reasonable.
One test for every notification
Ask what you would do differently if it arrived now rather than at the end of the day. If the honest answer is nothing, it does not deserve to interrupt — it deserves to be in a list you read when you choose to.
Almost everything fails this test. A task assigned to you for next week, a comment on a document, a file uploaded, someone joining a channel: all useful, none urgent. The small set that passes is usually a person waiting on you right now, or something breaking.
Turn things off after the second time, not the first
You cannot predict which notifications will be noise, and switching everything off on day one means missing the two that mattered. But the second time something interrupts you and you do nothing about it, you have your evidence.
Make that the rule: the second useless interruption from a source, turn that source down. It takes a month and you end up with settings that fit how you actually work rather than how you imagined you would.
Different channels for different urgencies
Push on a phone, a desktop badge and an email are not the same promise, and treating them as one is why people end up ignoring all three.
A reasonable division: phone push only for things a person is actively waiting on, desktop for the work you are in right now, email for everything that can be read in a batch. The moment email starts arriving for things that also push, you have taught yourself to ignore email, and that is expensive because email is where the things that actually need reading live.
Keep one thing deliberately loud
The risk of a good notification diet is that you also silence the one alert that should wake somebody — a failed payment, a production error, a client escalation.
Pick that small set deliberately and give it a channel nothing else uses. A sound or a route that only ever means something real keeps its meaning; the moment two harmless things start using the same route, the real one stops being noticed within a week.
Questions people actually ask
How do I decide what should notify me?
Ask what you would do differently if it arrived now rather than at the end of the day. If the answer is nothing, it belongs in a list you read by choice, not an interruption.
Should I just turn most notifications off?
Not on day one — you cannot predict which two mattered. Use the second-time rule: the second time a source interrupts you and you do nothing about it, turn that source down.
How should phone, desktop and email differ?
Phone push only for someone actively waiting on you, desktop for the work you are in right now, email for anything readable in a batch. When email duplicates pushes, you train yourself to ignore email.
