Notifications: a budget, not a ban

The advice to "turn off all notifications" has been given roughly a billion times and kept roughly never. Not because people are weak — because some pings genuinely are the job, the kid's school, the delivery you paid for. The fix that survives real life is not a ban. It is a budget.

What a ping actually costs

The visible cost of a notification is two seconds of glancing. The real cost is the switch: attention leaves the task, processes the interruption, and returns carrying residue from it — we unpacked that mechanism in attention residue. Research on interrupted work keeps finding recovery times measured in minutes, not seconds, and the interruptions arrive dozens of times a day. Run the multiplication and "two seconds" becomes the most expensive line item in the workday. This one sits comfortably in the well established column.

Worse, the cost lands unevenly. A ping during email triage costs almost nothing — you were switching anyway. The same ping during your one genuinely clear hour costs the hour. Which is the whole argument for budgeting instead of banning: the problem is not notifications existing, it is notifications spending your best attention on your worst tasks.

Building the budget: three lists

Take ten minutes and sort everything that pings you into three lists. Now: things where minutes matter — a short list if you are honest; for most people it is calls from family, a boss channel, maybe a delivery. These keep sound. Batched: things that matter today but not this minute — team chat, email, most messengers. These lose sound and badges, and you visit them at hours you choose, like mail in an actual mailbox. Never: everything whose ping serves the app, not you — social feeds, games, shops, news. These lose notification rights entirely; you were going to open them anyway.

The sorting is the easy half. The load-bearing decision is when the batched list gets opened — two or three fixed visits a day beats "whenever I feel a vibration in my soul". Put the first visit after your clear hour, not before it: the inbox opened at 8:55 spends the 9 a.m. head you needed at 9:05. Protecting that hour is the entire premise of the Clear Hour system, and the Focus Planner has a log built for exactly this experiment.

The two settings that do most of the work

You do not need seventeen toggles. Scheduled do-not-disturb with an allow-list — the "Now" list — covers the deep-work window and, separately, the evening. And badge removal on the batched apps matters more than people expect: the red dot is a notification that never stops firing. A phone that shows nothing until you ask it a question is a different object from the one you own now.

Expect the first two days to feel itchy — checking urges outlive the pings that trained them. By day four the batched visits start feeling like a schedule instead of a loss. Run it as a two-week experiment with notes, not a personality change.

FAQ

What if my job genuinely requires instant replies?

Then your "Now" list is bigger — it is still a list. Even jobs built on responsiveness have one or two channels that matter and a dozen that borrowed the urgency. Budget the dozen.

Is this just "check email twice a day" again?

That advice fails because it picks the number first. Budgeting picks the categories first; the visiting schedule falls out of what your actual work tolerates. Twice a day is one possible answer, not the doctrine.

Does the evening need its own budget?

Yes, and it is stricter — a work ping at 10 p.m. is a stress dose on a system trying to power down. We covered that half in screens before bed.

These statements have not been evaluated by the Food and Drug Administration. This product is not intended to diagnose, treat, cure, or prevent any disease. Educational content, not medical advice.