Give every task its own clockwork.

Switching between tasks is not free. Each time your brain disengages from one activity and re-engages with another, there is a measurable lag where part of your focus is still caught up in the thing you just left. Psychologists call this "attention residue," and it is one of the better-documented reasons that constant task-switching tends to leave people feeling busy but unproductive.

The exact size of that cost varies a lot between people and tasks, and you should be wary of the precise minute figures that get quoted around this topic — they are often pulled from studies with narrow conditions and applied far too broadly. The direction of the effect, though, is consistent: more switching tends to mean more leftover attention on the previous task and less available for the current one.

Open-plan offices, notification-heavy phones, and multi-tab browsers have made switching easier than ever, which is precisely the problem. It has never been simpler to glance at a message mid-task, and each glance carries a small recovery cost.

Why a running timer reduces switching

A visible, running timer works against this in two ways. First, it gives you a concrete reason to say "not now" to an interruption — the timer is proof that this block belongs to one task, and it is easier to defend a commitment you can see than an abstract intention to "focus." Second, it creates a natural, scheduled stopping point. You do not need to fight the urge to check something else indefinitely; you only need to hold out until the timer ends, which is a much smaller ask of your willpower.

Batch, do not sprinkle

The most direct application is batching similar shallow tasks into a single timed block instead of sprinkling them throughout the day. Set one 15-minute timer for replying to messages, rather than answering each one as it lands. Set one block for admin tasks, one for calls, one for creative work. Every batch you create is a set of context switches you no longer have to pay for individually.

On the Task Timer page, you can label one timer "Inbox" and another "Admin" and run them back to back, so the batching is visible and the boundary between batches is enforced by the clock rather than by willpower alone.

Use overtime as a signal, not a failure

When a timer runs into overtime, it is tempting to feel like you failed the estimate. Reframe it: overtime is data. If a task labelled "10 minutes" consistently runs to 25, that is useful information about how you plan, not a character flaw. Over a few weeks of watching overtime patterns, your estimates for similar tasks will naturally get sharper, and sharper estimates mean fewer accidental context switches caused by misjudging how long something will take.

Protect the first and last five minutes

The beginning of a timed block is when your mind is most likely to wander toward whatever you were doing before, and the last few minutes are when it starts drifting toward whatever comes next. Treat both edges with a little extra discipline — close unrelated tabs before you start, and resist glancing ahead at your next task until the current timer actually ends.

None of this requires new software or a rebuilt calendar. It requires a timer you actually look at, and the discipline to let it, rather than your inbox, decide when a task is over. Try running your next few work sessions in Track mode so you can see exactly how long focused blocks last before something pulls you away — the numbers are often more revealing than they sound.