Protect your focus from the noise
A blocked calendar is worthless if every ping can override it, so the block is only as real as your defence of it
You are at the Cover step of the Empty-Head Loop. The week is planned, but a plan lives or dies on whether the deep-work blocks survive a connected day. Knowing how to stop distractions while working is what turns a calendar from a suggestion into a boundary. The shift here is that a noise-filter agent triages your inbox so only real signal reaches you, while discipline handles the rest.
By the close you will have a focus protocol that defends your blocks and a configured noise-filter agent that empties the trivial out of your inbox before it can pull you.
Distraction is a tax on every block, and most of it is self-inflicted
A distraction is anything that pulls you off the current block: a notification, an email that "will only take a second", a Slack ping, the reflex to check something. The cost is not the interruption itself but the re-entry, because deep work has a warm-up, and every break forces you to pay it again. Research on context switching puts the recovery cost at many minutes per interruption, so a morning with eight pings is a morning with almost no deep work in it, regardless of what your calendar says.
The defence has two halves. One is discipline you apply to yourself: notification settings, batching, environment. The other is delegation: an agent that decides what is worth your attention before you ever see it. You need both, because willpower alone leaks and an agent alone cannot move your hands away from your phone.
The focus protocol: defend the block
- Kill notifications by default. Turn off all non-essential push notifications on every device. The exceptions you keep are a deliberate short list, never the default-on pile every app ships with.
- Batch client comms into windows. Decide that email and Slack get checked at two or three set times a day, not continuously. Tell clients your response window so the expectation is set and the silence between windows is guilt-free.
- Make the deep-work block physical. Phone in another room, one browser tab, full-screen, do-not-disturb on. The friction to break the block should be higher than the friction to stay in it.
- Single-task the block. One block, one piece of work. Multitasking is just fast switching, and switching is the tax you are trying to avoid.
Configure the noise-filter agent
Most of what reaches your inbox is not signal, and reading it to decide that is itself the distraction. SaneBox sits on your existing email and triages incoming mail by importance, moving the unimportant into a separate folder you scan once a day and leaving only what matters in the inbox. It learns from how you handle mail, so the filter sharpens over time.
The setup: connect it to your mail, let it sort for a few days while you correct the misfiles by dragging them, and define a digest you review once daily. The genuinely urgent stays in your main inbox and reaches you in a comms window; everything else waits in the holding folder for the daily scan. Your inbox stops being a slot machine and becomes a short list of real things.
SaneBox reclaiming focus: a worked example
Take a freelance UX designer running solo, the sort whose inbox ran to roughly 120 emails a day, most of them newsletters, cc threads and low-priority client notes. The challenge was that checking email "quickly" between tasks meant checking it constantly, and the constant checking shredded the deep-design blocks that were the whole value of the practice.
The approach paired the focus protocol with SaneBox. Notifications went off, email moved to two daily windows, and SaneBox triaged the 120-a-day flow so only the dozen or so important messages stayed in the main inbox while the rest dropped into a once-a-day digest.
The measurable result over the first month: the designer reclaimed roughly two hours of focused work a day, measured as deep-work blocks completed without interruption rising from about one a day to three, and email-triggered context switches fell from dozens a day to the two scheduled windows.
INTERVIEW EWOUD: What is the one notification you refused to turn off, and how did batching your comms into windows change what clients expected from you?
Pitfalls at the focus stage
Treating the agent as a reason to relax discipline. A noise filter cleans the inbox, but if your notifications are still on, the phone defeats it. Run both halves.
Checking the holding folder too often. A holding folder you peek at hourly is just the inbox with extra steps. Scan it once a day.
Setting no comms expectation with clients. Silence between windows reads as neglect unless you have told clients the windows. Set the expectation and the silence is fine.
Keeping a long notification exception list. Every exception is a door for distraction. Keep the list short and deliberate.
With your blocks defended and the noise filtered before it reaches you, the system now runs a full week without leaking back into your head. The last move is the one that makes it sustainable: closing the week cleanly, with a review agent drafting the recap.