Defaults Decide: Why Your Tools Are as Noisy as on Day One
For many people, the noise of a working day is simply whatever their tools were set to on the first day.

Every tool you use arrived with a set of notification settings someone else chose. Most of us never changed them. That means the noise of a working day is, for most people, simply whatever their tools were set to on day one. Notification defaults are the quietest, most powerful decision in your working life, and you probably did not make it.
The power of the default
Defaults are powerful far beyond software. In a landmark 2003 study of organ donation, Eric Johnson and Daniel Goldstein found that in countries where people had to opt in, consent was dramatically lower than in countries where they had to opt out. Religion, income and education did not explain the gap; the default did (Johnson and Goldstein).
Software is no different. When the usability researcher Jared Spool asked several hundred people to send him their Microsoft Word settings files, he found fewer than 5% had changed any setting at all (UIE). Notification settings sit in the same kind of menus and ask for the same effort.
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 →Defaults are not always chosen with care
In the same Word story, autosave was off by default, and nobody had decided it should be. A programmer had set every option to zero, which meant "off". Users assumed Microsoft had chosen it on purpose and left it off. Notification defaults work the same way: whatever a tool switches on at the start, by design or by accident, is what most users live with.
And the lists are long. Asana's help pages name 17 kinds of activity that can send you an email, including four kinds of likes (Asana). Jira attaches a default notification scheme to every new project. Each item on those lists was a decision, made once, on behalf of everyone who never opens the settings.
Even good settings go stale
Researchers at the University of British Columbia found that which notifications are welcome differs from person to person and changes with context, yet people rarely revisit their settings. When they showed 21 people two weeks of their own notifications, most had underestimated how many they received, and all of them accepted the changes suggested to them. One was still getting alerts from a game they no longer played (Janzen and McGrenere).
What do your untouched defaults cost?
Estimate the notifications you get only because nobody changed the settings, and the time they take.
This interactive part needs JavaScript.
A 20-minute notification reset
- List your top five noisy tools (your phone's notification history helps).
- In each, turn off likes, reactions and "someone viewed" alerts.
- Switch email copies of in-app activity to a daily digest, or off.
- Keep breakthrough rights for mentions, direct messages and assignments only.
- Put a recurring 15-minute "settings spring clean" in your calendar every quarter.
If you lead a team or choose tools, set calmer defaults before a new tool rolls out, and you will change everyone's days at once. Our manager's guide to notification norms helps.
Frequently asked questions
Why are my notifications so noisy?
Most tools ship with notifications switched on for many kinds of activity, and very few people ever change the defaults.
Do people change their notification settings?
Rarely. In Jared Spool's study of Microsoft Word settings, fewer than 5% of people had changed any setting at all.
How do I reduce notifications quickly?
Spend 20 minutes on your five noisiest tools: turn off likes and reactions, switch email copies to a digest, and keep breakthrough only for mentions, direct messages and assignments.
Sources
- Johnson and Goldstein, Do defaults save lives?, Science (2003), Columbia Business School
- Jared Spool, Do users change their settings?, UIE (2011)
- How to manage notification settings, Asana Help
- Janzen and McGrenere, Reflective spring cleaning, University of British Columbia (2022)
Whoever sets the defaults for a new tool is deciding how noisy thousands of working days will be.
Keep reading
More from the blog
Why People Copy Slack and Asana Into Their Email (and Whether It Will Last)
The email echo is not a rejection of Slack or Asana. It is an insurance policy against their speed. Why people choose it, and what to do instead.Why "Hi" Is the Worst Notification You Can Send
A lone "Hi" is a knock at the door with nobody there. Why it is the emptiest notification at work, and the one habit that fixes it.Your Inbox Belongs to Machines: Only 13% of Email Is Written by Humans
Most of your inbox was written by software. Why tools send notification email by default, what the echoes cost, and why email is becoming the archive, not the alarm.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