Francesco Cirillo devised the method as a university student in the late 1980s, using a tomato-shaped kitchen timer — pomodoro is Italian for tomato. The interval was the one his timer offered, and he has described starting with a much shorter period and settling on 25 minutes because it worked for him.
That is worth saying plainly, because the number is usually presented as though it were a research finding about attention span. It is not. It is a practical default that turned out to be a reasonable one, and the technique does not depend on it being optimal.
Most timer apps implement the clock and drop the method, which is why people try it, find it unremarkable and stop. The mechanism is not the countdown; it is the discipline around it.
A pomodoro is indivisible. There is no half pomodoro. Either you completed twenty-five minutes on one task, or you did not.
An interrupted pomodoro is void. If you break off and cannot resume immediately, it does not count and you start a fresh one. This sounds harsh and it is the entire point — it puts a real price on picking up your phone, which is the only reason the rule changes behaviour.
Interruptions get written down, not acted on. When something occurs to you mid-interval — an email to send, a thing to look up — you note it on a sheet and continue. For interruptions from other people, Cirillo prescribes a sequence: acknowledge, negotiate a time, call back, and honour it. The note-and-defer habit is what makes the interval defensible.
When the timer rings you stop. Even mid-sentence, even when it is going well. This is the most-broken rule and the one that protects the following four hours.
You record every completed pomodoro. The tally is the feedback loop. Without it the technique is just a timer.
The part almost everyone skips is where the improvement comes from. Before starting, estimate each task in whole pomodoros. Afterwards, record how many it took.
| Task | Estimated | Actual | Error |
|---|---|---|---|
| Draft the proposal | 3 | 5 | +67% |
| Fix the reporting bug | 2 | 4 | +100% |
| Clear the review queue | 4 | 3 | −25% |
The first weeks look like this for nearly everybody, and the systematic direction of the error is the finding. Underestimation of your own tasks is robust and well documented, and no amount of resolving to be realistic fixes it. Comparing estimates against a tally does, slowly, because a pomodoro is a fixed unit and the record is unambiguous. After a month or two most people can size familiar work within one unit.
Anything that exceeds five to seven pomodoros should be split; anything under one should be batched with other small items. That sizing rule is a planning discipline that survives even if you abandon the timer.
| Unit | Composition | Elapsed |
|---|---|---|
| One pomodoro | 25 work + 5 break | 30 min |
| One set | 4 pomodoros, last break extended to 20 | 135 min |
| Realistic day | 8 to 12 pomodoros | 3 h 20 to 5 h of timed work |
| Working week | 50 pomodoros | 20.8 h |
Two things fall out of that table. First, a full day does not contain sixteen pomodoros once meetings, email and lunch are counted — planning for more than about twelve is planning to fail. Second, twenty focused hours a week is a great deal more deliberate work than most weeks contain, so the low number is not a disappointment.
Being straight about this: there is no strong body of controlled research establishing that 25 and 5 is the optimal ratio, or that the Pomodoro Technique outperforms other structured break schedules. Claims to that effect are marketing.
What is better supported sits underneath the method rather than in its specific numbers. Performance on sustained attention tasks degrades over time, and breaks reduce that decline. Deciding in advance exactly when and on what you will work — an implementation intention — reliably improves follow-through compared with a general intention. Recovering from an interruption costs far more than the interruption itself. Each of those supports some timed-interval discipline. None of them singles out this one.
The most substantial criticism is internal. The stop-at-the-bell rule directly conflicts with sustained absorption: if you are twenty-three minutes into something difficult and finally holding the whole problem in your head, a bell is an interruption you have scheduled for yourself. Practitioners who work on long analytical or creative problems commonly abandon the fixed length for that reason, and keep only the record-keeping.
If you do change the length, keep it constant. The moment a pomodoro means 25 minutes on Monday and 50 on Tuesday, the tally stops being a unit of measurement and the estimation loop — the part that produces the gains — breaks.
The technique assumes work that decomposes into uniform blocks under your own control. It fits badly with roles where it cannot: on-call and support work where the interruption is the job, collaborative sessions, days built from meetings, and tasks with a long warm-up before anything useful happens.
It also assumes the timer helps. For some people a countdown adds pressure rather than structure, and watching it becomes its own distraction. Others find external time structure genuinely transformative — the experience varies enough that the only test is a week of trying it.
On that point, one careful note: people with attention difficulties report both extremes, some finding a fixed external interval the single most useful support they have, others finding the forced stop destroys focus that was hard to establish. There is no general answer here and this page is not medical advice; if attention is a persistent difficulty rather than an ordinary bad week, that is worth discussing with a clinician rather than solving with a timer.
Finally, no timer addresses the common underlying problem. Task avoidance is frequently about the feeling attached to a task rather than about time management, and a twenty-five minute block does not make an unpleasant task pleasant. What it does is lower the cost of starting to twenty-five minutes, which is often enough.
The orthodox answer is to stop, because the rule exists to keep you working sustainably rather than in bursts followed by collapse. The pragmatic answer is that finishing the thought and taking the break immediately after costs little. Doing it every time means you have chosen a different method, which is fine — just choose it deliberately.
No. A pomodoro is time you controlled and spent on one chosen task. Counting meetings inflates the tally and destroys its value for estimation.
By the rules it is void. In practice, note it as void and move on without ceremony — the purpose of the rule is to make interruptions visible, not to punish you.
No. The timer runs entirely in your browser, and nothing about your sessions is transmitted or saved. Closing the tab clears it.
Every tool comes with a written guide, and every category is one click away.