The Pomodoro technique: why 25 minutes still works

Francesco Cirillo named the technique after a tomato-shaped kitchen timer in the late 1980s. The promise is modest — work in fixed sprints with breaks — and it has outlasted a dozen productivity systems because it solves a problem the others ignore: the cost of context switching.

What the timer is really for

The 25-minute block is not magic. It is a contract with yourself that for the next 25 minutes you will not check anything else. The value is not in the number 25; it is in the boundary it draws.

Without a boundary, a hard task gets interrupted by an easy one. You open a ticket, think "let me check Slack first", and the ticket is still open an hour later. The timer reframes every interruption as a cost: is checking email worth breaking a block I am nine minutes into? Often the answer is no, and that is the whole mechanism.

Why 25 and not 50

A longer block sounds more productive, and for deep work it can be. But 25 minutes works for a specific reason: it is short enough that starting is cheap. "Just one pomodoro" is an easier commitment than "the next hour", and starting is the hardest part of any task that resists being started.

If you are already in flow when the bell rings, ignore it and finish the thought. The rule is a floor, not a ceiling. What the timer buys is the decision to begin.

The break matters as much as the block

The five-minute break is not a reward; it is a reset. Stare at something far away, stand up, drink water. Do not open another tab. The break is what lets you start the next block at full attention instead of running the fourth sprint on the fuel of the first.

After four blocks, take a longer break — 15 to 30 minutes. Skipping it is the most common way the technique fails: you keep the sprints but drop the recovery, and by the afternoon you are staring at the same line of code unable to decide anything.

Tuning the durations

The defaults are a starting point, not a law.

• 25 / 5 — the classic. Best for task switching, admin work, and days when motivation is low.
• 50 / 10 — better for deep, build-state work where the cost of re-entry is high. Two of these fit in a morning.
• 90 / 20 — matches the natural ultradian rhythm some people find in sustained creative work. Hard to start cold with; warm up with a shorter block first.

The Pomodoro Timer lets you set all three durations, auto-start the breaks, and shows the countdown in the browser tab title so you can work in another window and still feel the clock. It runs entirely in the browser — no account, no data leaving your machine.

When the technique does not help

Pomodoro is a focus aid, not a productivity metric. It does not write code or design a system; it just reduces the number of times you abandon the work mid-thought. If your day is meetings interrupted by meetings, the timer will not save you — guard the blocks of uninterrupted time you do have instead.

Used as intended — start the clock, do one thing, take the break — it is still the simplest reliable answer to "I sat down to work and two hours vanished."