Skip to main content

Focus

The Pomodoro Technique: A Practical Guide

The Pomodoro Technique is a way of working in short, timed blocks with enforced breaks. It was designed by Francesco Cirillo in the late 1980s using a tomato-shaped kitchen timer, and it has survived because it fixes two problems most productivity systems ignore: starting, and stopping.

By the Alarm Click team · · 6 min read

The basic loop

  1. Pick one task and write it down.
  2. Set a timer for 25 minutes and work on nothing else until it rings. That block is one "pomodoro".
  3. Take a 5-minute break: stand up, get water, look out of a window. Do not start another task.
  4. After four pomodoros, take a longer break of 15 to 30 minutes.

The rules that matter are the ones people tend to drop. A pomodoro is indivisible: if you stop halfway, it does not count, and you start a fresh one. Breaks are compulsory, not optional. And the timer is visible, so the decision "should I keep going?" is taken away from you.

The online timer has a Pomodoro Mode that runs this loop automatically, switching between work and break and counting rounds. If you prefer longer blocks, the focus timer offers 50 and 90-minute sessions with the same structure.

Why it works

It shrinks the first step. Most procrastination is about starting, not working. "Write the report" is open-ended and vaguely threatening; "work on the report for 25 minutes" is small, finite and easy to agree to. Once you have started, continuing is much easier than beginning.

It makes time visible. Without a timer, an hour of work can turn out to be fifteen minutes of work and forty-five minutes of email, tab-switching and drinks. A ticking pomodoro turns time into something you spend deliberately. After a few days you also get an honest measure of how long tasks take: a report that "takes an afternoon" turns out to be six pomodoros, which is useful information.

It forces recovery. Attention fatigues like a muscle. Studies of sustained attention show performance declining measurably after 20 to 30 minutes of continuous demanding work, and brief breaks restoring it. The five-minute break is not lost time; it is what lets the next block be as good as the first.

It creates urgency without stress. A visible countdown produces a mild deadline effect, but the stakes are trivial, so it sharpens rather than paralyses.

Planning a day in pomodoros

A realistic working day contains far fewer pomodoros than people expect. Eight hours at a desk yields perhaps 10 to 12 usable pomodoros once you subtract meetings, email, lunch and the long breaks. Plan for that number, not for 16.

  • Estimate in pomodoros. Next to each task write how many blocks you think it needs. Anything over five should be split into smaller tasks; anything under one can be batched with other small items into a single "admin" pomodoro.
  • Protect the first two. Put the hardest or most important task in the first pomodoros of the day, before email. Willpower and attention are highest early.
  • Record actuals. Tick each completed pomodoro next to its task. At the end of the week you will know your real capacity and your estimation error, which improves planning more than any app.
  • Batch communication. Check email and messages in one dedicated pomodoro mid-morning and one mid-afternoon rather than continuously. Each unplanned check costs the rest of the current block.

Interruptions, and the "inform, negotiate, call back" rule

Interruptions are the main reason people abandon the technique. Cirillo's own rule handles them in three steps. Inform the person you are in the middle of something. Negotiate a time to get back to them, usually at the next break. Call back when you said you would. Most interruptions survive a 15-minute delay perfectly well, and colleagues quickly learn the pattern.

Internal interruptions, the sudden urge to check a price or reply to a message, are handled by writing them on a list beside you and returning to the task. The list is emptied during breaks. After a week most people find the urges themselves become less frequent, because the brain learns that they will be dealt with later.

If an interruption is genuinely unavoidable, void the pomodoro, deal with it, and start a fresh 25 minutes. Do not "pause" and resume; a pomodoro that was paused for a phone call is not a pomodoro.

Adapting the numbers

Twenty-five minutes is a starting point, not a law. Programmers, writers and researchers often prefer 50 minutes of work and 10 of break once they are used to the rhythm, because getting into a complex problem takes longer than a few minutes. Students revising for exams frequently find the opposite: 25 minutes is long enough for a hard subject, and shorter blocks keep the material fresh. The study timer keeps daily totals per subject if you want to see where the hours go.

What should not change is the break. Whatever the block length, take the break away from the screen. Looking at something distant for a few seconds also rests the eye muscles that focus at reading distance, which is the basis of the 20-20-20 rule and the break reminder tool.

Finally, measure. Run a normal week with a stopwatch on how long focused work actually lasts before you switch tasks; then run a week of pomodoros and compare the totals. The technique is worth keeping if the number goes up, and for most people it does.