How to Find Out What Breaks Your Focus

You close the chat client, put the phone in a drawer, and book two hours in the calendar. At the end of it you have done forty minutes of work and cannot account for the rest.

Nobody interrupted you. The interruptions were all yours, and none of the measures you took address that.

Two kinds of interruption, two different fixes

External — a colleague, a message, a phone call, a delivery. Something arrived from outside.

Self-initiated — you switched. Opened a browser tab, checked something unrelated, went to make coffee mid-sentence.

They feel similar in the moment and they have nothing in common causally.

External interruptions are solved socially and environmentally: agreed focus hours, a closed door, notifications off, an expectation that non-urgent things wait.

Self-initiated switches are almost never solved by removing tools. Closing the chat client does not help when the urge was to escape the task rather than to read a message. If you close everything and switch anyway — to a different work task, to tidying your desk, to a thought — the tools were not the cause.

That distinction is why a week of logging is worth more than a month of blocking apps.

What self-initiated switching usually means

If most of your interruptions are your own, the pattern in when they happen is the finding.

At the start of a session — the task is not defined clearly enough to begin. “Work on the migration” is not a task; “write the rollback script” is.

When something gets difficult — the switch is avoidance, and the honest response is to name the difficulty rather than the distraction.

When blocked — waiting on information, a decision or another person. That is a legitimate stop, and it should end the session rather than becoming forty minutes of drift.

Consistently around the same elapsed time — the session is longer than your current attention supports. Shorter sessions with real breaks work better than long ones with drift.

Each of those has a different response, and none of them is a website blocker.

Log lightly or it becomes the distraction

The logging has to cost seconds. A single tap with a category is enough; writing a sentence about each interruption is a new way to avoid the task.

Some people find that noticing the urge is enough to override it, which makes the logging itself an intervention. Others find the opposite. Both are worth knowing about yourself.

A week of data is enough to see the pattern. After that, the log has done its job and can stop.

Match the session to the task

Different work needs different session shapes, and one default fits none of them well.

Deep problem-solving — holding a complex model in your head — needs long uninterrupted blocks, because the reload cost after any break is high. Ninety minutes or more.

Production work — writing, coding something understood, processing a queue — works in shorter blocks and tolerates interruption better.

Administrative work — email, forms, scheduling — is best batched into a block precisely because it is the thing that fragments other work.

Applying a twenty-five minute timer to deep work means stopping every time you get somewhere. Applying ninety-minute blocks to email means most of it spent avoiding email. The log tells you which kind of work you were actually doing when the interruptions clustered.

Common mistakes to avoid

• Treating all interruptions as external and solving them with tools.
• Logging in enough detail that the log becomes the distraction.
• Booking sessions longer than your attention currently supports.
• Starting a session without a specific task.
• Continuing a session while blocked, which produces the drift that looks like a focus problem.

How to do it with Single-Tasking Session Logger

The Single-Tasking Session Logger records sessions and interruptions locally.

1. Name one specific task, not a category of work.
2. Log each interruption with whether it came from outside or from you.
3. After a week, look at the split and at when the self-initiated ones cluster.
4. Fix the task definition before fixing your environment.

Other productivity tools are in the tools directory.

Frequently asked questions

Why distinguish self-initiated interruptions?

Because they have a different cause and a different fix. External ones need boundaries with other people; self-initiated ones usually mean the task is unclear, unpleasant or blocked, and closing an app will not help.

How long should a session be?

Long enough to reach depth and short enough to sustain. Twenty-five minutes suits fragmented work; ninety suits anything requiring a complex model in your head. If interruptions cluster at the same elapsed time, the session is too long.

Does logging make it worse?

Recording takes seconds, and noticing an urge is often enough to override it. If the logging becomes the distraction, count interruptions rather than describing them.

Final thought

Count who caused each interruption for one week. If most of them are yours, the problem is the task, and no amount of blocking software addresses it.

Try the free Single-Tasking Session Logger