How to Stop Doomscrolling: Blocking It Is Not Enough

You did not decide to spend forty minutes on that. There was no moment of choosing. There was a gap — between two tasks, after a hard message, at the end of an unsatisfying meeting — and the gap filled itself.

That is the part worth understanding, because it explains why the obvious solution keeps not working.

Why blockers get uninstalled

App blockers are genuinely useful and there is a reason so many people cycle through several of them. The pattern is consistent: install, two good days, then a moment of friction met with a workaround, then a week of ignoring it, then removal.

Three reasons this happens.

The block arrives after the reach. By the time the blocker shows its screen, you have already picked up the phone, opened the app, and entered the loop. The blocker interrupts a behaviour that is already running, which is the hardest possible moment to intervene.

The gap is still there. You blocked one destination. The state that sent you looking — restlessness, avoidance, the specific discomfort of a task you do not want to start — is unchanged. Attention flows to the next available thing, and there is always a next available thing.

Circumvention teaches you something. The first time you disable the blocker to get past it, you learn that the barrier is optional. That lesson does not un-learn, and every subsequent barrier inherits it.

Blocking is a reasonable component. It is a poor foundation, because it is purely subtractive: it removes a destination without addressing the departure.

What is actually happening

Doomscrolling is rarely appetite. Almost nobody sits down genuinely wanting forty minutes of distressing news.

It is a gap-filler, and it appears reliably in the same four gaps:

• Before a task you are avoiding. The scroll is the avoidance, wearing entertainment's clothes.
• After something emotionally loaded. A difficult conversation, a piece of criticism. The scroll is regulation.
• In genuine dead time. Queues, transit, waiting. Mostly harmless.
• At the end of a day that felt unchosen. This one has its own name — revenge bedtime procrastination — and its own fix, which is in the daytime.

Only the third is really about the phone. The others are about the gap.

Fill the gap instead

Name the gap out loud. "I do not want to start this." Four seconds. Naming the state, rather than acting on it, is the entire skill, and it works far more often than it has any right to.

Have a default that is not the phone. The gap will get filled by something. Decide in advance what: stand up, refill water, two minutes outside. It does not need to be virtuous, only pre-decided — an undecided gap goes to the phone by default.

Make the next task obviously enterable. Most avoidance gaps open in front of an unclear next action. If the document is open on the right page and the next keystroke is obvious, the gap is much smaller. Stopping mid-sentence at the end of the previous session is the cheapest way to arrange this.

Put presence on the other side. The strongest version. Working with someone present — a silent call, a drop-in room, a companion that notices when you leave — means the gap is not private. Not punishment; just the small fact that drifting is visible, which is enough to make returning easier than continuing.

Where blocking does belong

Keep a blocker for the specific, narrow job it is good at: a hard boundary on the one app that accounts for most of your losses, during the hours you have decided are working hours.

Not all apps. Not all day. One app, one window, no exceptions to negotiate. A blocker with a small perimeter and no override survives; a blocker that is a general prohibition on being distracted gets uninstalled by Thursday.

The short version

You are not scrolling because you want to. You are scrolling because there was a gap and nothing else was assigned to it.

Assign something. The scrolling has less to do.