What the Pomodoro Technique actually is (and why most people get it wrong)
Almost everyone knows the 25-minute part. Almost nobody knows the two rules that the 25 minutes exist to serve, and once you know them, most timer apps look like they are measuring the wrong thing.
Francesco Cirillo published the technique as a paper, not a product. The version quoted here is v1.3, dated 15 June 2007, first published 19 October 2006, released under a Creative Commons licence. The body runs to about thirty pages before the appendices, and reading it is a mildly annoying experience, because it keeps describing rules that the apps built in its name quietly dropped.
It was never mainly a timer
The paper describes a process of five stages, and only the second one involves the timer at all: planning at the start of the day, tracking through it, then recording, processing and visualizing at the end. Four of the five are about what you learn from the day after it is over.
To run it you need three sheets of paper and a timer. A To Do Today Sheet with the day's tasks in priority order and a section headed Unplanned & Urgent. An Activity Inventory of everything that has come up. And a Records Sheet, which is where the day's numbers go so that they can be compared with the next day's.
The timing is the familiar part: “The traditional Pomodoro is 30 minutes long: 25 minutes of work plus a 5-minute break.” Every four pomodoros you stop for a longer break, “from 15 to 30 minutes”, and Cirillo is specific that the long break must not be spent on anything complex, or your mind cannot reorganise what it just took in.
Rule one: a pomodoro cannot be split
Here is the rule that most people have never heard. Cirillo states it flatly: “A Pomodoro can't be split up; there is no such thing as half of a Pomodoro or a quarter of a Pomodoro.” And then the consequence:
“If a Pomodoro is definitively interrupted by someone or something, that Pomodoro should be considered void, as if it had never been set; then you should make a fresh start with a new Pomodoro.”
Void. Not paused, not shortened, not credited pro rata. Twenty-three minutes of work followed by a two-minute phone call scores zero. This sounds harsh until you see what it is for: the number at the end of the day is meant to be a count of unbroken half-hours, because unbroken half-hours are the thing whose supply you are trying to grow. A total that includes interrupted sessions cannot tell you that.
Look at the timer you use now. If it lets you pause and resume, it is not implementing this rule. That is a defensible design choice, but it means the number it gives you is elapsed time, and elapsed time is exactly the measurement the technique was written to replace.
Rule two: every interruption gets a mark
The second forgotten rule is that interruptions are recorded, in two separate categories, on paper, as they happen.
- Internal interruptions, the ones you cause. The urge to check something, look something up, send a message. Cirillo: “Every time you feel a potential interruption coming on, put an apostrophe (') on the sheet where you record your Pomodoros.”
- External interruptions, someone else. “Every time someone or something tries to interrupt a Pomodoro, put a dash (-) on the sheet.”
Then, crucially, you keep working. The mark is not permission to stop; it is a way of deferring the thing without letting it evaporate. You write the new task under Unplanned & Urgent, or into the Activity Inventory marked “U”, and you finish the pomodoro you are in.
Two categories of tally mark sounds like bureaucracy for its own sake. It is not. After a week you have a count of how often you interrupt yourself versus how often other people interrupt you, and those two numbers have completely different remedies. Cirillo notes that people who start doing this often discover they can absorb ten or fifteen external interruptions inside a single 25-minute pomodoro, a number nobody guesses correctly before they start counting.
Inform, negotiate, call back
For the external ones there is a named procedure, and it is three steps: “inform effectively, negotiate quickly to reschedule the interruption, and call back the person who interrupted you as agreed.”
The third step is the one that makes the first two work. You are not refusing people; you are moving them, and then actually turning up. Cirillo's framing is that this inverts the dependency: instead of your day being shaped by interruptions, the interruptions get allocated into pomodoros that you choose. If you skip the calling back, you have not protected your attention, you have just become unreliable.
The estimate is the point
The paper's stated first objective is not focus. It is: “Find Out How Much Effort an Activity Requires.” You estimate each task in whole pomodoros before starting, then compare with what it actually took, and the gap is the thing you work on.
Two rules fall out of this, and both are useful on their own:
- More than 5 to 7 pomodoros? Break it down. An activity you estimate at more than about three hours is not one activity, and your estimate of it is not worth much.
- Less than one pomodoro? Add it up. Small similar tasks get combined until they fill one. Half pomodoros are not allowed in the count either: an estimate of five and a half rounds to six.
This is why the technique produces a number at all. It is not a score. It is an input to tomorrow's plan.
Why Cirillo preferred a kitchen timer
Asked directly whether a mechanical timer or software is better, he does not hedge: “Speaking from experience, the most effective Pomodoro is always the kitchen timer.” His reasons are worth reading even if you ignore the conclusion.
- You have to physically wind it, and that act is a declaration that you are starting.
- It shows the time left and ticks, so you can feel time passing rather than check it.
- Ending a pomodoro and crossing off a finished task should be explicit gestures, and “for this reason it's better if these aren't automated.”
We sell a piece of software, so take this as an admission rather than a pitch: the man who invented this thing thinks the app is the inferior version, and he gives specific reasons that most apps do not answer. The ticking is easy to reproduce. The winding is not.
When he says not to use it
There is a short section titled When Not To Use the Pomodoro, and it says: not in your free time. “If you decide to read a book simply for leisure, you shouldn't use the Pomodoro Technique; doing so would be taking those Pomodoros away from unscheduled free time.”
He also concedes a limit, in his own words: the technique depends on “being helped by a little mechanical object”, and stopping using it removes most of the benefit. It is a scaffold, not a skill you graduate from. Anyone selling you the opposite is selling you something.
What this changes about the app you pick
Once you have read the two rules, the question to ask a timer is no longer “does it do 25 minutes?” Every one of them does. The questions are: does it distinguish a finished pomodoro from a broken one, and does it give you anywhere to put an interruption?
Most do neither, ours included in part. To be exact about our own: Focus Valley has no interruption log and no To Do Today sheet, so on the recording half of the technique it does nothing for you at all. What it does address is the measurement problem. A timer that counts the clock will happily credit you twenty-five minutes for a session you spent in another window, which is the same failure as counting a void pomodoro arriving by a different route. The desktop app reads how long it has been since your last keypress and stops counting when you stop working, so what it records is closer to the unbroken half-hour Cirillo was after. The free web timer cannot do that, because a browser tab is not allowed to know. That line is drawn plainly in how it works.
If you want the full method, the paper is short, free, and better than any summary of it, this one included. If you want the version that survives a working day at a computer, the developer setup starts from the same rules and bends the timings. And if you are shopping, the comparisons say which apps do what, including where they beat us.