Partly, and not for the reason it is usually sold. What holds up in the Pomodoro technique is the bounded commitment and the forced stop: a stretch of work with a defined end is easier to start and easier to finish well than an open-ended one. What does not hold up is the number 25. No study has shown that 25 minutes beats 30 or 50, and anyone quoting you a productivity percentage for the method is quoting something nobody measured.
What the research actually shows
Almost none of it is about the Pomodoro technique. Francesco Cirillo published a method in the late 1980s, not a trial, and the studies people cite in its defence are about breaks and attention in general.
The oldest is still the clearest. In 1948 Norman Mackworth sat people in front of a clock face whose pointer occasionally jumped a double step, and asked them to catch every jump across a two-hour watch. Detection fell off inside the first half hour and kept sliding. That decline, the vigilance decrement, has been reproduced for seventy years on radar screens and baggage scanners. Sustained attention has a shelf life, and it is shorter than a working morning.
The more directly useful result is from 2011. Atsunori Ariga and Alejandro Lleras, writing in Cognition, ran people through a 50-minute monitoring task and briefly pulled one group away from it twice. That group held its accuracy steady for the full 50 minutes; the group that worked straight through got steadily worse. Their reading is that a goal held continuously goes stale, and a short break resets it.
That is good evidence for stopping periodically. It is not evidence for stopping at 25 minutes, and nobody should pretend otherwise. The honest summary: the mechanism has support, the specific protocol has a plausible shape and no result of its own.
Why it works when it works
Three things, roughly in order of how much they matter.
Starting gets cheaper. "Write the report" has no edge to it, so the part of you looking for a reason to delay always finds one. "Twenty-five minutes on the report, then I stop" is too small a commitment to argue with. Most of the value people get out of the method is collected in the first sixty seconds of a session, before any work has happened.
Stopping becomes automatic. Left alone, you stop when something interrupts you or when you are too tired to go on, which is well past the point where the output was worth keeping. A scheduled stop is the cheapest fix for that, and the half of the technique people delete first.
Interruptions acquire a price. Cirillo's rule is that a session cannot be split: break off to answer a message and it is void, and you start it over from the beginning. Nobody enjoys this rule. It works because it converts a cost you previously ignored into one you can see, and seeing it is what makes you start defending the time.
The two rules almost everyone drops
The version of the technique that spread online is the interval and nothing else. The two rules left behind are the ones that make it a method rather than a countdown.
The first is the indivisible session above. In a real job a softer version survives: void it when the interruption came from you, note it and carry on when it came from someone else. Either way you write it down, which is the second rule.
Cirillo has you record what you planned for the day, how many sessions each item consumed, and what interrupted you. It is tedious and it is the only part of the method that produces new information. After a week you know whether "that is about an hour of work" means an hour, and after a month you can plan against your own numbers instead of your optimism. Any text file will do — a plain scratchpad that opens instantly is enough, as long as it is somewhere you will look again. If you would rather not create an account for a to-do list, keeping notes without signing up for anything runs through what that costs you in exchange.
Is 25 minutes the right length?
No, and it was never claimed to be. Cirillo was a student with a tomato-shaped kitchen timer, and 25 minutes is what he set it to. Treating that number as a finding is the most common way people bounce off the technique and conclude it does not work.
Work with a long ramp-up pays a reload cost every time you stop. If getting the problem back into your head takes ten minutes — debugging, a contract, anything where you are holding a lot of state at once — a 25 minute session spends close to half of itself on setup. Blocks of 45 to 90 minutes suit that work better. Shallow work is the opposite case: the difficulty is starting, not stopping, so make the session small enough that refusing it feels absurd. Fifteen minutes on the expense report is hard to talk yourself out of.
The timer on this site takes any length from 1 to 240 minutes for each phase, and lets you change how many focus sessions come before a long break, because the four-round cycle is as arbitrary as the 25. It works out the remaining time from your device clock instead of counting its own ticks, so switching tabs does not make it drift. The chime is the weak point: a browser that has throttled a hidden tab can deliver it up to a minute late, and a laptop that has gone to sleep will not play it at all.
Who it does not work for
The method has a shape, and plenty of jobs are the wrong shape for it.
- Work made of interruptions. Support, ops, on-call, anything with a shared inbox you are meant to be watching. Under the real rule almost every session is void, and the technique spends your whole day reporting a failure at something you were never allowed to do.
- A run that is already going well. Stopping a productive stretch for a mandated five minutes is a tax, not a break. The usual compromise is to finish the session, skip the break and start another, which is fine and is also no longer the technique.
- A calendar full of meetings. The method allocates uninterrupted time. If your day contains three free gaps of 25 minutes, a timer is not the thing standing between you and focus.
- Anything collaborative in real time. Pairing, reviews, a call. The boundary has to be negotiated with another person, and a countdown does not negotiate.
There is also the failure mode nobody warns you about: the technique can make you fast at the wrong work. Twelve tidy sessions of clearing a queue feel excellent and can be a whole day spent not touching the thing that mattered. The timer measures effort, never direction.
How to find out whether it works for you
Two weeks, and a count rather than a feeling. "I felt productive" is the least reliable measurement available to you, and it correlates mostly with how busy the day was.
What it looks like when it is working: you start sooner in the morning, you stop before the output goes bad, and your estimates start landing near reality. What it looks like when it is not: you skip the breaks, the breaks stretch to twenty minutes on a feed, or you sit out the last four minutes of a session with nothing left to do. That last one is not a discipline problem. It means your interval is longer than the task, and you should shorten it.
What a timer cannot fix
A phone on the desk. Notifications you have not turned off. A chat window with a green dot. A timer enforces a boundary you have already decided to keep; it has no opinion about the other things competing for the same 25 minutes.
The bigger one is not knowing what the session is for. If you press start without a specific next action — not "the proposal" but "the pricing section of the proposal" — you will spend the first ten minutes deciding, and then blame the method. Pick the action, put the phone somewhere else, then start the timer. In that order.
If you want to test any of this rather than read further about it, the Pomodoro timer here will run the classic 25/5 or whatever lengths you decide the work needs, and it counts the sessions you finish so the two-week experiment has something to show at the end.
The part that does the quiet work is seeing the number go down. Why a visible countdown changes what you do gets into why a timer you can see behaves so differently from one running silently in another window — which also explains why hiding the tab tends to undo the whole thing.
Frequently asked questions
Does the Pomodoro technique actually work?
For a lot of people, yes, but through a plainer mechanism than the branding suggests. A session with a defined end is easier to begin, and a scheduled stop keeps you from working past the point where the output is any good. The specific 25/5 split has never been shown to beat other intervals.
Is the Pomodoro technique backed by science?
The idea behind it is; the protocol is not. Research on the vigilance decrement going back to Mackworth in 1948 shows sustained attention degrades within about half an hour, and a 2011 experiment by Ariga and Lleras in Cognition found brief breaks prevented that decline over 50 minutes. Neither study tested 25-minute work blocks.
Why is a Pomodoro 25 minutes long?
Because that is where Francesco Cirillo set his kitchen timer as a university student in the late 1980s. The technique is named after the tomato-shaped timer he used. The number is a starting point, not a result, and changing it is not cheating.
What should I do if I get interrupted during a Pomodoro?
The strict rule is that the session is void and you start it again, which is deliberately harsh so that interruptions become visible instead of free. In a real job, a workable compromise is to void the session when the interruption came from you, and to note and continue when it came from someone else. Either way, write down what it was.
How many pomodoros should I do in a day?
There is no correct number, and the ones published online are guesses. Count what you actually complete in a normal week and use that as your baseline, because most people plan for far more focused hours than any day contains. Planning against your own tally is the point of keeping one.
Is it bad to pause a Pomodoro?
By the method, yes — a pomodoro is meant to be indivisible, and pausing removes the pressure that makes the rule useful. In practice most timers let you pause anyway, including this one. If the technique is not working for you, how often you reach for pause is the first thing worth checking.
Last updated September 19, 2026