Why the Pomodoro technique stops working
The 25/5 split was never a research finding. Francesco Cirillo picked it in the late 1980s using a tomato-shaped kitchen timer. That is the entire origin story. There was no trial, no control group, no measurement of anything. He tried a length, it worked, and the name stuck because the timer was a tomato.
That is not a criticism. Plenty of useful things start as one person’s habit. But it matters, because when the technique stops working for you, the instinctive reaction is to assume you are doing it wrong. You are probably not. You are following a number someone chose four decades ago for a different kind of work.
There are only about four peer-reviewed studies on the Pomodoro technique in existence. Here is what they found.
Someone finally ran the experiment
Smits et al. (2025), in Behavioral Sciences, put 94 students through a randomised two-hour work session and compared three approaches: Pomodoro at 25/5, Flowtime, and self-regulated breaks where people stopped whenever they felt like it.
There was no significant difference in productivity, task completion or flow between the three.
Worse for the tomato, the Pomodoro group got tired faster than the self-regulated group (p=0.025) and lost motivation faster too.
Read that carefully before you throw your timer away. It was a single two-hour session with students, not a month of professional work, and no method beat any other. Pomodoro simply did not do the thing it is famous for doing, and the enforced interruption appears to have cost something.
The earlier study pointed the same way
Biwer et al. (2023), in the British Journal of Educational Psychology, studied 87 students and compared systematic breaks against letting people manage their own. Systematic breaks produced real mood benefits, and the people who regulated their own breaks ended up more fatigued and more distracted.
But there was no significant difference in mental effort or task completion.
Put the two studies side by side and a consistent picture appears. Structured breaks change how the work feels. They do not reliably change how much of it gets done. That is a smaller claim than the internet makes, and it is the honest one.
Four ways the technique actually breaks
1. The interval does not fit the work
Twenty-five minutes is a fine unit for email, admin and anything you can pick up and put down. It is a poor unit for work with a long spin-up, which is most engineering, most writing and most analysis. If it takes you fifteen minutes to load the problem into your head, a 25-minute block gives you ten minutes of actual work and then takes the problem away from you.
The vigilance research often cited in defence of short intervals does not transfer cleanly either. Ariga and Lleras (2011), in Cognition, found that brief switches to an unrelated task roughly every ten minutes prevented the usual decline across a 40-minute vigilance task, while every control group declined. That is a genuine finding. It is also a finding about sustained monitoring. Mackworth’s original 1948 work, the ancestor of all this, involved watching a radar screen. Applying it to writing code is an analogy, not a result.
The technique gives one fixed answer to a question whose answer depends on the work.
2. The break gets contaminated
The second failure is the one almost nobody admits to. You finish the focus block, the chime goes, and you pick up your phone. Five minutes later the timer starts again and you have not rested. You have switched feeds.
A break that is another screen at the same desk is barely a break. The evidence for what breaks reliably do comes from breaks that change what you are doing, not from ones that change which rectangle you are staring at. Reed and Ones (2006), pooling 158 studies and 13,101 people, found acute aerobic exercise reliably raises positive activated affect, meaning energy and vigour, at d=0.47, with the effect lasting at least thirty minutes. Notably, low-intensity movement worked consistently. You do not have to sprint. You have to stop scrolling.
This is where the technique quietly rots. The focus half stays intact for months. The break half degrades in about a week.
3. It is rigid and your calendar is not
Pomodoro assumes you control 25 uninterrupted minutes at a time. Standups, pairing sessions, a Slack message that actually is urgent, a 40-minute meeting starting at ten past the hour. Half a working day in most companies cannot be divided into tomatoes.
People respond by abandoning the system rather than adapting it, because rigid intervals give you no graceful way to be interrupted. You are either doing it or you have broken the streak. Streak logic is fine for habits. It is terrible for calendars.
4. It treats attention as the only resource
This is the big one, and it is structural.
Every part of the Pomodoro technique is about your mind. Focus, distraction, mental effort, flow. Your body is not mentioned once, which means the default implementation has you sitting for the focus block and then sitting for the break.
That default has consequences. Schöne et al. (2025), in BMC Public Health, pooled 38 studies and 282,264 people and found working from home added roughly 31 minutes a day of sedentary time during work hours and cut about 2,564 steps, with the odds of sitting eight or more hours a day roughly doubling. Most of those underlying studies were also pandemic-era, so hold it loosely. In pooled data from 34 cohorts and 1.33 million people, Patterson et al. (2018) found sitting beyond about eight hours a day was associated with rising all-cause mortality risk.
Meanwhile the neck and lower back do not respond to the usual fix. Across 27 randomised trials, Chen et al. (2018) found strengthening exercise helped office-worker neck and shoulder pain, at moderate-quality evidence, while stretching was no better than doing nothing. Ergonomic changes alone and education alone did not work either.
So the technique optimises one resource and silently degrades another. That is not a flaw in Cirillo’s idea. It is a flaw in what the idea leaves out.
What the evidence does support
Strip out the marketing and a modest, well-supported set of claims remains.
Micro-breaks restore energy. Albulescu et al. (2022), a meta-analysis in PLOS ONE covering 22 samples and 2,335 people, found breaks of ten minutes or less significantly increased vigour (d=0.36) and reduced fatigue (d=0.35). Those are real, replicated effects.
Micro-breaks do not measurably improve performance. In the same analysis the performance effect was d=0.16 and not statistically significant (p=.116). For cognitively demanding tasks it was d=-0.09, which is nothing. Longer breaks helped performance more than shorter ones. So the correct claim is not that breaks make you more productive. It is that breaks give you energy back and do not cost you output.
Exercise snacks do not make you sharper. Garrett et al. (2024) reviewed 113 studies and found acute exercise has only a small effect on cognition (g=0.13), with strong evidence of publication bias. Separate trials of sitting breaks by Duran and by Wennberg found no improvement in cognition, executive function or memory. Anyone telling you a five-minute walk boosts your brain is selling something.
Short counts as something. The US Physical Activity Guidelines for Americans, 2nd edition (2018) removed the old rule that activity had to come in bouts of at least ten minutes to count. That single change is what makes an exercise snack inside a work break worth doing.
Hourly appears to be enough. Diaz et al. (2026), in the British Journal of Sports Medicine, ran 19,342 US adults through NPR’s Body Electric Challenge, with 11,484 completing five-minute movement breaks at self-chosen intervals for 14 days. Fatigue and low mood fell, positive mood rose, work engagement improved 4 to 7% and performance 1 to 3%. Hourly was nearly as effective as every 30 minutes and far more sustainable. It was uncontrolled and self-reported, so treat the numbers as a direction rather than a measurement.
The alternatives, described accurately
Flowtime. You work until you reach a natural stopping point, then take a break scaled to how long you worked. It removes the arbitrary cut-off, which is the main complaint about Pomodoro. It was tested head-to-head in Smits et al. (2025) and produced no significant difference in productivity, task completion or flow. It is not proven better. It is less rigid, and rigidity is the specific thing that was making you quit.
52/17. Widely repeated, frequently presented as research. It is not. The figure comes from an internal blog analysis of DeskTime’s own users. It is unpublished company data, not a peer-reviewed study, and there is no reason to treat 52 and 17 as special numbers. Use it as one person’s suggestion, at the same evidential level as Cirillo’s kitchen timer.
Self-regulated breaks. In Smits, the self-regulated group stayed less tired and more motivated than the Pomodoro group. In Biwer, self-regulated break-takers were more fatigued and distracted. The two disagree. Self-regulation works if your judgement is good and fails if it is not.
Choose the interval, then defend the break
The useful conclusion is not that Pomodoro is bad. The interval is a variable, not a rule. Set it from the shape of the work.
Email, admin, ticket triage, anything you can drop. A 25-minute focus block, then a 5-minute break.
Writing, design, code with a long spin-up. A 50 to 90 minute focus block, then a 10 to 15 minute break.
Debugging, on-call, meeting-heavy days. Do not fix an interval. Move once an hour regardless.
Starting something you have been avoiding. A 10 to 15 minute focus block, then a 5-minute break.
Three rules make it work.
Set the block by spin-up cost. If loading the problem takes ten minutes, never use a block shorter than forty.
Never let the break become another screen. The break is the part that decays, and it is also the part carrying most of the evidence.
Anchor to the hour, not the streak. If the interval collapses because of a meeting, stand up anyway. Hourly movement is the floor. Everything above it is a bonus.
If you want more on what to actually do in those five minutes, we wrote what to do during a Pomodoro break. For where the whole idea came from, there is from kitchen timers to cognitive science.
The honest sales paragraph
We built PomoFit because of failure mode two. It is a Pomodoro timer that puts a short guided bodyweight exercise into the break so the break cannot quietly turn into your phone. The interval is yours to set, because 25 minutes is not sacred. There are ready-made plans if you would rather not decide each time, including weekly brain fog killer and energy boost cardio. It will give you energy back and get you off your chair. It will not make you smarter, and the research above is why we do not claim it. If you want it lined up against what you already use, that is the Pomofocus alternative breakdown.
Frequently Asked Questions
Why does the Pomodoro technique stop working?
Usually because the interval does not match the work. Twenty-five minutes suits tasks you can drop and resume, but not work with a long spin-up, where the timer removes the problem just as you have loaded it. The other common cause is break decay, where the five minutes quietly becomes phone time and stops restoring anything.
Is 25 minutes scientifically optimal?
No. No study derived 25 minutes. Francesco Cirillo chose it in the late 1980s with a tomato-shaped kitchen timer, and the number stuck through repetition rather than evidence. When researchers finally compared Pomodoro against Flowtime and self-regulated breaks in 2025, they found no significant difference in productivity, task completion or flow.
Is 25 minutes too short for deep work?
Often, yes. If it takes you fifteen minutes to load a problem into working memory, a 25-minute block leaves about ten minutes of real work before the timer interrupts you. For writing, design and engineering, blocks of 50 to 90 minutes with a 10 to 15 minute break usually fit better. Match the block to the spin-up cost.
What does the research say about Pomodoro versus Flowtime?
Smits et al. (2025) randomised 94 students across Pomodoro, Flowtime and self-regulated breaks in a two-hour session and found no significant difference in productivity, task completion or flow. The Pomodoro group did get tired faster than the self-regulated group (p=0.025) and lost motivation faster. Neither method won on output.
Is the 52/17 rule real science?
No. The 52/17 figure comes from an internal blog analysis of DeskTime’s own user data. It was never published in a peer-reviewed journal and no trial has tested it. Treat it as one company’s observation about its own customers, not a finding. It sits at the same evidential level as Cirillo’s original kitchen timer.
Do breaks actually make you more productive?
The evidence does not support that claim. A 2022 meta-analysis of 22 samples found micro-breaks significantly increase vigour and reduce fatigue, but the performance effect was not statistically significant. The accurate version is that breaks restore energy and mood, and crucially do not cost you output. That is a real benefit, just not the one usually advertised.
What should I do instead of the Pomodoro technique?
Treat the interval as adjustable rather than switching systems. Set the focus block from the spin-up cost of the work, take a movement break roughly once an hour, and keep the break off screens. Hourly five-minute breaks performed nearly as well as every 30 minutes in a 2026 study of over 11,000 desk workers, and were far more sustainable.