Focus blog

Pomodoro is half right: what calm blocks fix

The half it gets right

The Pomodoro technique is right about the hardest part of focus: starting. Twenty-five minutes is small enough that your resistance has nothing to grab. You are not committing to the whole essay, the whole refactor, the whole afternoon; you are committing to one tomato, and anyone can do one tomato. That trick, shrinking the first step until starting is easier than avoiding, is genuinely valuable, and it is why the technique has outlived every app that tried to improve it.

It is also right about breaks. Attention degrades over time on task, and short deliberate resets restore it. The cycle of work, then a real pause, then work again, is the part of Pomodoro worth protecting. Most failed focus sessions fail because someone skipped the pause, not because the timer was wrong.

The classic Pomodoro cycle: four 25-minute work blocks with short breaks and one long break.

The half it gets wrong

Where the technique overreaches is the fixed ceiling. Twenty-five minutes is a fine floor and a poor roof. It is exactly enough time to load a problem into your head, watch the water start to warm, and then get pulled out of it by the ring. For shallow work, batch processing, and dreaded chores, 25 minutes is plenty. For writing, design, and any task with a long ramp, the timer ends the session at the moment it was finally getting somewhere.

There is a research floor under any session length, and there is no research ceiling at 25 minutes: the number came from one student's kitchen timer in the 1980s, not from a study. Treating it as a law means your attention gets chopped at a fixed interval that has nothing to do with your task, your energy, or the state you are in. The session length should match the work, and the work varies.

A shallow task finishing comfortably inside 25 minutes beside a deep task cut off mid-flight by the timer.

Keep the reset, drop the rigidity

The fix is not to abandon the cycle; it is to stop worshiping one of its numbers. Keep what works: a deliberate start, one task per block, real breaks, a longer recovery after a few cycles. Change what does not: the ceiling becomes adjustable, and the boundary gets softer. A block should end at a natural edge when there is one, and the timer should ask before it cuts you off mid-thought.

The break science agrees with the rhythm, not the stopwatch. A 2022 meta-analysis found short breaks reliably restore energy and reduce fatigue, with the clearest gains on work that demands sustained attention; what the evidence does not endorse is any single sacred interval. Cal Newport's refinement points the same way: scale the break to the session that earned it, so a long block gets a long pause. People who keep this technique for years already work this way quietly. They start the 25 and keep going when the work is moving; they treat the timer as a floor, not a judge. The technique works best exactly when it is disobeyed thoughtfully, which is a strong hint about which parts were load-bearing.

An attention curve rising into flow, sliced by a rigid 25-minute ceiling versus eased down by a soft boundary at a natural end.

What calm blocks look like

This is the design behind focus blocks in Focus. The cycle is still there: work, short break, and a longer break after a few rounds, with lengths you can size to the task instead of to a tomato. Sessions survive being interrupted by real life; if the app closes or the phone dies, the block is recovered, not lost. And the break is a real break, not a notification asking you to come back.

The deeper change is what the timer is for. In a rigid system, the timer ends the block because time is up. In a calm one, the timer holds the space so you do not have to watch the clock, and the ending is a choice you make at a natural edge. The one intention per day practice pairs well with this: the intention decides what the block is for, and the block decides when it ends.

The anatomy of a calm block: a work stretch you can size, a real break, a longer recovery after a few rounds, and sessions that survive interruptions.

Try this week

Run one honest experiment. For shallow work, use the classic 25 and notice how well it fits; that is the technique's real home. Then pick one task with a long ramp, a draft, a hard bug, a design, and give it a 60-minute block with the phone in another room. When the timer arrives, ask one question before ending anything: am I done thinking, or was I just interrupted?

If the honest answer is the second one, you have discovered the half of Pomodoro worth changing. Keep the tomato for starting. Let the work decide when to stop.

Key takeaways
  • Pomodoro's real insight is a start small enough to defeat procrastination, plus deliberate breaks.
  • 25 minutes is a fine floor for shallow tasks and a poor ceiling for work with a long ramp.
  • The number itself is a convention from a kitchen timer, not a finding.
  • Keep the cycle: work, real break, longer recovery. Make the ceiling adjustable and the boundary soft.
  • When the timer rings mid-thought, ask whether you are done or just interrupted.

References