ARTICLE · 11 SEPTEMBER 2026

The Pomodoro Technique: why 25 minutes, and where it goes wrong

The rule fits in one line: work for 25 minutes, rest for 5. Yet very few people keep it up for more than a week. What the original rules actually say, where the number 25 came from, and the four places the method quietly falls apart.

A name borrowed from a kitchen timer

Pomodoro is Italian for tomato. In the late 1980s Francesco Cirillo, then a university student who could not make himself study, fetched the tomato-shaped kitchen timer and, by his own account, decided to try "just ten minutes". Timing it worked. The experience hardened into a method, the length settled at 25 minutes, and rules about breaks were added until it reached the form used today.

The detail that matters is that it began as a way of staying with one task, not a way of planning a day. The question was not how to divide the hours but how to remain at the desk on one thing. Keep that in mind and the rules below make sense.

The original rules take five lines

Choose one task and set the timer to 25 minutes
That block is one pomodoro. Do not mix tasks. If the task finishes early, the rest of the block goes to reviewing it.
Work on that task until the timer rings
A pomodoro is indivisible. Switch tasks or leave the desk halfway and it did not happen. Half a pomodoro does not count as half.
When it rings, rest for 5 minutes
Even if the work is going well. This is the rule most often ignored and the point where the whole method most often collapses.
After four, take a longer break of 15 to 30 minutes
The long break after the fourth pomodoro is recovery for the next four.
Log interruptions and defer them
When someone interrupts, say you are mid-pomodoro, negotiate a time a few minutes away, and go to them at that time. Cirillo called it inform, negotiate, call back.

Two more habits are attached. Before starting, estimate how many pomodoros the task will take; afterwards, record how many it did. The gap between estimate and reality shrinking over time is the second thing the method promises. The first is focus; the second is a feel for your own work.

25 minutes is a compromise, not a finding

There is no research showing 25 minutes is a limit of human attention. Cirillo himself says it was chosen after trying several lengths. The number survived for practical reasons.

Short enough to startFaced with a task you are avoiding, "just 25 minutes" is a negotiation you can win. "Just an hour" usually is not. Lowering the bar to starting is half the method.
Not too long to sustainMost people can sit through 25 minutes without drifting once. At 45, most drift at least once.
Easy arithmeticWith the break it is 30 minutes; two make an hour. Count the day's pomodoros and you have your real working time. Twelve is six hours, which is a lot of work.
Not a unit of workThe task is not expected to finish inside 25 minutes. What finishes is a block of attention. Misread that and you end up frustrated that "nothing got done in 25 minutes".

Four places it breaks

Skipping the breakCarrying on because it is going well is rational in the moment. The problem shows up around the third pomodoro, when the tank empties all at once. The break is not a reward; it is the condition for the next 25 minutes. It also tests whether the urge to continue is still there five minutes later.
Not looking at the timerYou start the timer, switch to another window, miss the ring, and find yourself 40 minutes in. That is not a pomodoro; that is just working. The remaining time has to be in your field of view, which is exactly why a small window floating above everything else exists.
Making the count the goalDoing easy tasks first to reach ten for the day, or counting meetings as pomodoros. The count is a record, not a score. Its purpose is to sharpen estimates, not to be large.
Believing interruptions can be eliminatedAn uninterrupted 25 minutes is a privilege of working alone. In a team the goal is not to remove interruptions but to handle them. Saying "not now, in ten minutes" is part of the method.

Variations: 50/10, 90/20, 52/17

Some work does not fit 25/5. Design, long-form writing and anything that takes ten minutes just to load into your head loses too much when cut off at 25. Hence the variations.

Split	Where it comes from	Suits
25 / 5	The original	Work that is hard to start, tasks made of many small units, repetition
50 / 10	The university lecture rhythm	Work that takes time to get into, remote-work mornings
90 / 20	Borrowed from the 90-minute cycle in sleep research	One block of deep work, exam-length rehearsal
52 / 17	A time-tracking company's analysis of its user data, published in 2014	Effectively the same as 50/10; the odd numbers made it memorable

Which is right depends on the work and the person, and the same person differs between morning and afternoon. One practical test covers it: when the session ends, are you disappointed or relieved? Disappointed every time means lengthen it; relieved every time means shorten it. The criteria for studying specifically are in how long should a study session be.

Setting it up in PipTim

The Pomodoro 25/5 page opens with 25 minutes of focus, a 5 minute break and a 15 minute long break after the fourth round already filled in. Press start and PiP and you are running. If you want to change something, these are the settings that matter.

Auto-start next sessionOn, and the next focus block begins the moment the break ends. That is closer to the original rules. Off on days when you want to stretch the breaks.
Rounds until the long breakFour by default. If you lengthen sessions to 50 minutes, three is the better fit.
Completion soundYou come back from a break because you hear it end. Leave it on and check the device volume.
The PiP windowDuring focus it shows time remaining; during a break, how much break is left. It is the guard against the second trap above.

Once configured, use Copy settings link to produce an address you can bookmark or send to a study group. Anyone who opens the link starts with the same configuration.