Guide

Blocking distractions: a productivity approach that survives a bad day

Every productivity system works on a good day. The interesting question is what happens on a bad one.

Short answer

Remove the distractions during your working hours rather than relying on resisting them, and put a short delay on unblocking so a moment of friction in the work cannot become forty minutes elsewhere.

The failure mode is always the same

You hit something difficult in the work. It is uncomfortable for about four seconds. Somewhere in those four seconds a hand moves to a tab, and the discomfort is gone along with the next half hour.

No amount of planning addresses this, because the decision happens below the level of planning. What addresses it is the tab not being there.

The real cost is not the minutes

People account for a distraction as the time spent on it: five minutes on a feed is five minutes lost. That undercounts it badly. The expensive part is rebuilding the state you were in, and for anything with structure held in your head, that is considerably longer than the interruption itself.

This is why a five-minute check can cost half an hour, and why the same person can put in a nine-hour day and produce almost nothing. The day was not short of hours. It was short of uninterrupted ones.

It also explains a result people find counterintuitive: blocking a small number of things completely tends to beat moderating everything. Moderation leaves the decision live, and every live decision is another chance to break the state.

Ranking what to block by what it actually costs

The instinct is to block the embarrassing things first. The better order is by how thoroughly each one destroys the state you were in.

  • Anything with an infinite feed.Worst by a distance. There is no natural end, so the exit has to be a decision, and you are already avoiding a decision.
  • Anything that arrives unprompted.Notifications and unread badges start the interruption for you. You never chose to be distracted, which makes it feel unfair rather than avoidable.
  • Anything work-adjacent.Industry news, documentation rabbit holes, the tab you opened to look up one thing. These are the hardest to justify blocking and among the most expensive.
  • Genuinely idle browsing.Last, oddly. It is easy to notice and easy to stop, which is exactly why it is not the problem.

Why this beats a pause button

Focus tools with an instant off switch are testing you every time you hit a hard problem, which is precisely when you will fail the test. A delay changes the question from "can I resist" to "is this worth waiting fifteen minutes for", and it almost never is.

The result is not more discipline. It is fewer opportunities to need any.

It also survives the thing that kills every productivity system eventually, which is a bad week. A system that requires you to be at your best is not a system, it is a description of your best days.

Kellet schedules blocks around your working hours and puts a timer on unblocking, so a hard moment in the work cannot become an easy exit.

Where blocking is the wrong tool

If you are avoiding the work rather than being distracted from it, blocking will not help and will make the day worse. Distraction is reaching for something else while you are trying to work. Avoidance is not starting, and it usually means the task is unclear, too large, or you do not have what you need to do it.

The tell is simple: if you block everything and then sit staring at the same file for forty minutes, the problem was never the tab. Break the task down instead.

Persistent inability to start, across weeks and across tasks you care about, is worth talking to someone about rather than solving with software.

Straight answers

Common questions

Will this make me less reachable?
Only in the way you configure. Block feeds and leave messaging open if people genuinely need you, or schedule communication windows rather than staying permanently available.
Is this just the Pomodoro technique?
It pairs well with it, but the difference is enforcement. A timer tells you to focus; a block removes what you would have focused on instead. Pomodoro assumes the willingness is there and supplies structure; blocking assumes it is not and supplies a constraint.
How long should the cool-down be for work?
Short. Fifteen minutes is usually enough, because you are interrupting a reflex rather than resisting a craving. Long delays during a working day mostly produce resentment and get removed.
What if I need a blocked site for work?
Then you wait fifteen minutes for it, which is annoying roughly twice before you start keeping the genuinely needed things off the list. That friction is doing useful work: it makes you decide what is actually required rather than what is merely convenient.
One decision left

Calmer water is one decision away.

Kellet blocks the distractions you choose and lets you stay accountable to yourself, or to someone you trust.