What the Pomodoro technique actually is, and why 25 minutes
It was invented by a student with a tomato-shaped kitchen timer, and the number on it matters less than almost everyone thinks.
Where it came from
In the late 1980s an Italian university student called Francesco Cirillo was struggling to get through his reading. He made a bet with himself: could he concentrate, properly, for ten minutes? He grabbed the kitchen timer to hand, which was shaped like a tomato, pomodoro in Italian, wound it up, and worked until it rang. That is the entire origin. He refined it into a method, the twenty-five-minute block stuck, and the tomato gave it a name.
The actual rules
The technique is more specific than “work for a bit, then stop”. As Cirillo set it out:
- Pick one task. Not a list. One.
- Set the timer for 25 minutes and work only on that.
- If something interrupts you, write it down and carry on. This is the rule people skip, and it is doing more work than the timer is. A thought like I should check whether the deadline moved loses its pull once it is on paper.
- When the timer rings, stop. Even mid-sentence. Take five minutes away from the work.
- After four rounds, take a longer break of fifteen to thirty minutes.
A pomodoro is indivisible. If you break off halfway to answer a message, it does not count as half a pomodoro; it counts as nothing. That sounds punitive but it is the point. It makes the twenty-five minutes worth protecting.
Why a fixed block helps
Two things make starting hard: the task is large and vague, and stopping is undefined. “Revise chemistry” has no end, so beginning it feels like agreeing to an indefinite sentence. Twenty-five minutes on one topic has a visible finish line, which makes the cost of starting small enough to pay.
The timer also takes the decision to stop away from you. Left to ourselves we either stop the moment work gets uncomfortable, which is often exactly when it is working, or push on long past the point of usefulness because stopping feels like giving up. A timer has no opinion about either.
The useful part is not the twenty-five minutes. It is that you decided in advance when you would start and when you would stop, and then handed both decisions to something that is not you at your most tired.
Is 25 minutes special?
No. There is nothing magic about it, and you should be sceptical of anyone who tells you otherwise. It is short enough that almost anyone can commit to it and long enough to get properly into something. That is the whole justification.
It is also worth being straight about the evidence. The Pomodoro technique itself has very little direct experimental support. It is a popular practice, not a laboratory finding. What it does is enforce two things that are well supported, namely that you begin and that you take breaks, and it packages them in a way people actually stick to.
Adapting it
- Longer blocks for deep work. Essays, long maths problems and coding often suit 50 minutes on, 10 off. Anything that takes fifteen minutes to get into is badly served by a twenty-five-minute cap.
- Shorter blocks when you are avoiding something. If you cannot start, ten minutes is not a failure, it is the correct size. Cirillo’s own first attempt was ten.
- Do not stack them all day. Four to eight good rounds is a real day’s work. Twelve is usually a story you are telling yourself.
Using it for revision specifically
One pomodoro, one topic. Spend the last three or four minutes of the block with the book shut, writing down what you can remember. That is not a summary of the round, it is the most valuable part of it. It is called retrieval practice, and it is the single best-supported revision technique there is.