Focus block? How is it different from a Pomodoro?

A focus block is a single-task work session of 60 to 120 minutes, set up before the work begins and ended on purpose rather than by interruption. It differs from a Pomodoro in three specific ways: length, intent of the break, and what counts as "the work." The distinction is small on paper and substantial in practice.

If your job involves loaded context — code, prose, complex spreadsheets, careful reasoning — focus blocks are usually a closer fit than Pomodoros. Here is why, and how to actually run one.

Why 25 minutes is the wrong unit for most knowledge work

The Pomodoro Technique sets a 25-minute timer, takes a 5-minute break, then repeats. It was designed in the late 1980s by Francesco Cirillo as a study aid — a way to make starting easier and procrastination harder. That problem is real and the technique is genuinely useful for it.

But studies of skilled knowledge work consistently find that the first 10 to 15 minutes of any session are warm-up: scanning the open files, recalling where you left off, re-loading mental state. Sophie Leroy's 2009 work on "attention residue" showed that switching tasks leaves cognitive traces that interfere with the next task — and that the residue takes time to dissipate. Twenty-five minutes barely covers the warm-up, which means a Pomodoro session for a complex coding task often ends just as the useful work begins.

A focus block is sized for the work. Sixty minutes for moderate problems, ninety for genuine depth, two hours for the rare deep-write or design session. The break afterwards is longer too — typically 15 to 30 minutes, with movement and no screens.

Anatomy of a focus block

A useful block has four moments most people skip:

1. A pre-block decision about what done looks like. One sentence on a sticky note. Not "work on the report" but "draft the executive summary".
2. A pre-block environment setup — close the inbox, silence the phone, put a glass of water within reach. The block has begun before the timer starts.
3. A protected middle where interruptions are batched and answered after, not during. This is the part most people break.
4. A deliberate end — even if the work isn't finished. End with a one-sentence note about what you would do first if the block resumed. Re-entry next time becomes much faster.

Pomodoro vs focus block at a glance

[Table — please re-add in Studio]

Neither is universally better. The right tool depends on the texture of the work.

For specific situations

For people with ADHD

Focus blocks are not always the right fit, despite their reputation. If your bottleneck is starting, Pomodoro often wins. If your bottleneck is staying in flow once started, blocks are kinder — but cap them at 60 minutes and use a movement break, not a sit-down break, before the next one.

For shift workers and parents

Two-hour blocks are rarely realistic. Aim for one well-protected 45-minute block at the most cognitively favourable time of day (often the first hour after waking, before anyone needs you). One protected block beats four fragmented ones.

For meeting-heavy roles

Negotiate one full morning per week as a "no meetings" block. Then book yourself into the calendar for that morning. Visible blocks on a shared calendar are honoured more often than personal intentions.

A small but useful test

For one week, keep a one-line log at the end of each block: what got done, how loaded the context felt at the start versus the end, and what interrupted you. The pattern usually surprises people. The output per protected hour tends to be 2–4× the output per fragmented hour, even though both feel busy.

The point of a block is not the timer. It is the protection.