A few years ago I started doing a small audit on myself. For one ordinary Tuesday I counted every notification that pulled my eyes away from whatever I was supposed to be doing. The number was 312. Slack, email, calendar reminders, two project tools, a CRM that liked to congratulate me, and a phone that buzzed for things I had forgotten I subscribed to. None of them were urgent. All of them spent something. By the end of the day I had been interrupted more times than I had sent original thoughts into the world, and I run product for a living.
That is the moment I stopped thinking of notifications as messages and started thinking of them as withdrawals. Attention is the one resource on a team you cannot buy more of. You can hire more people, raise more money, and add more compute, but each individual still has roughly the same number of usable focus hours in a day. Treat that as a budget, and notifications become line items. Some are worth the spend. Most are not. The job is to manage the balance on purpose instead of letting a hundred apps overdraw the account for you.
What an interruption actually costs
The naive math says a notification costs you the two seconds it takes to glance and dismiss. The real cost is the recovery. Research on knowledge work has put the time to fully reload a complex task at somewhere between ten and twenty minutes, and that matches what I see in practice. A developer deep in a tricky piece of logic does not bounce back instantly after reading a one-line ping. They lose the thread, reread the last thing they wrote, and rebuild the mental model they were holding.
So price it honestly. If a single interruption costs fifteen minutes of recovery, and a person gets pulled out of focus six times in an afternoon, you have not lost six minutes of reading. You have lost an hour and a half of capacity, and you have it scattered into useless slivers. Attention management is not about willpower. It is about not handing the budget to software that has every incentive to spend it.
Every notification is a default someone chose
Here is the uncomfortable part. Almost none of the interruptions on your team are decisions you made. They are defaults. A tool ships with everything switched on because engagement looks good in their metrics, and a real person becomes the cost center. When we redesigned how alerts work in Atlas, the principle we kept coming back to was that the product should never spend a user's attention without a reason it could defend. A direct mention from a teammate who needs you, yes. A notice that someone reacted to a message with a thumbs up, no.
The fix at the individual level is to flip the question. Instead of asking which notifications you want to turn off, assume they are all off and ask which few you would deliberately turn on. For most people the honest answer is short: someone is blocked on me, something I own broke, or a human is waiting on a direct reply right now. Everything else can wait for a moment you choose.
Spend the budget in batches
The cheapest way to protect focus is to convert a stream of interruptions into a few scheduled withdrawals. Pull, do not be pushed. I check messages at set times rather than whenever the badge appears, and I tell my team that a non-urgent message will get a thoughtful answer in a couple of hours, not a distracted one in ninety seconds. That trade is almost always worth it.
Batching only works if the team agrees on what genuinely cannot wait. We settled on a simple norm: if it is truly time-sensitive, it gets a phone call or a clearly flagged urgent channel, and we use that escape hatch rarely enough that it still means something. Once people trust that real emergencies will reach them, they stop monitoring everything else out of fear they will miss something. That trust is the whole game.
- Off by default. Start from silence and add back only the alerts that pass the blocked-broken-waiting test.
- Batch the rest. Set two or three windows a day for messages and email instead of a continuous trickle.
- One urgent channel. Give people a real way to reach you fast, and protect it from noise so it stays credible.
Make the budget visible to the team
Individual discipline helps, but interruption budgets are really a team property. If one person guards their focus while the rest of the group fires off pings at all hours, you have moved the problem, not solved it. So make the norms explicit and write them down. State the response-time expectations. Name the channels and what each is for. Decide, as a group, that a status update belongs in a document someone reads on their own schedule, not in a meeting or a thread that demands ten people's attention at once.
When we made these expectations explicit internally, the most common reaction was relief. People had assumed that constant availability was the unspoken price of being a good colleague. Telling them plainly that focus is the priority, and that a few hours of delay on a non-urgent reply is not just tolerated but expected, gave them permission to do the deep work they were hired for.
The point of treating notifications as a budget is not to become unreachable. It is to be reachable for the things that matter and protected from the things that do not. Attention spent well shows up as finished work, fewer dropped balls, and people who are not fried by five o'clock. Spent badly, it shows up as a team that is always online and never quite making progress. You are spending the budget either way. The only choice is whether you do it on purpose.