The 25 minutes of work are the easy part. The 5-minute break is where the technique falls apart, and here is what the research actually says about it.
If the Pomodoro Technique stopped working for you, it is probably not the 25 minutes that broke. Most people can hold a work block. What they cannot do is end a break. The bell rings, the phone comes out, and the five minutes that were supposed to reset your attention turn into twenty-five that reset your whole afternoon. The technique has a rule for this, everybody ignores it, and the fix is not more discipline at minute four. It is making the break physically incapable of containing your phone.
The break is a rule, not a reward
Read the actual technique and the break is specified as carefully as the work block. Emory’s library guide to the method lays out the standard version: 3 to 5 minutes after each pomodoro, 15 to 30 after four of them, and the instruction to disconnect from your work and do something that does not take mental effort. Stand up. Walk. Water. Coffee. The same guide states the other rule that everybody quotes and nobody applies to the break: a pomodoro is indivisible and cannot be interrupted.
The break was never meant to be entertainment. It was meant to be empty. The point of an empty five minutes is that your attention has somewhere to go and nothing to grip.
A phone is the opposite of empty. It is the densest thing in the room.
So when people say the technique does not work for them, what they usually mean is that they implemented half of it. They kept the timer, which is the easy half, and replaced the break with a feed.
What the research actually says, including the part I don’t like
Here is where I have to be careful, because the evidence is not one-sided and the internet’s version of it is.
A survey of more than 400 working adults, summarised by the Association for Psychological Science, compared roughly 200 people who used their phones during lunch breaks with roughly 220 who did something screen-free: walking, reading, talking. The phone group reported significantly higher emotional exhaustion later in the day. The screen-free group’s negative emotions went down after the break. The phone group got no mood bump at all. The researchers’ reading was that phone use is not restful because it is not passive: hyperlinks, ads, notifications, all of it asks for the same focused attention that work does.
That is the study everyone cites, including me until recently. But there is a more recent one that cuts the other way.
A 2026 experiment by Burak Yildirim and Jan Rummel had participants take breaks either on their phone or sitting quietly, then measured performance and mind wandering on a demanding memory task. Their finding: no significant difference in subsequent task performance, and no significant difference in mind wandering. What did differ was mood. People felt more positive after the phone break than after sitting quietly, and the effect was strongest in people who reach for their phones most in daily life.
Take both seriously and you get something more useful than “phones ruin breaks”. A short phone break does not appear to damage the next work block, and it genuinely feels better than staring at a wall. The problem is the word short.
The timer has no rule for coming back
In a lab, the break ends when the experimenter says so. In your kitchen, nothing says so.
That is the whole failure, and it is a design failure rather than a character one. Gloria Mark’s research, summarised by the University of California, tracked how long people hold their attention on a single screen before switching: about 2.5 minutes in 2003, 75 seconds in 2012, 47 seconds in recent years, with a median of 40. Your five-minute break is roughly seven switches long. Each switch is a fresh chance for one of them to be interesting.
And the return is not free. Mark’s data puts the time to get back to an interrupted project at around 25 and a half minutes. That is longer than the pomodoro you were about to start.
The timer tells you when the break should end. Nothing tells your thumb.
This is the same shape as the problem I wrote about in why willpower isn’t a feature. Every soft limit asks you to make the right call at the exact moment you are least able to. A pomodoro app that rings at you is a suggestion. You have already learned to hear it and keep scrolling.
What I changed
I do not run a strict pomodoro. My work does not divide into 25-minute units, and I will say more about that in a second. But I stole the good part: the block is protected, and the break is physical.
When I start a block, I tap my phone on an NFC tag. Lock blocks the apps I chose and there is no on-screen button to undo it. The tag lives at the coffee machine. So the break is: stand up, walk to the coffee machine, and if I actually want Instagram, it is right there waiting for me. That is the honest version. I am not locked out. I have moved the decision from my chair to my feet, and most of the time my feet do not bother.
The side effect I did not expect is that the tag’s location became the break itself. Walking to the kitchen is a proper Cirillo break: no screen, some movement, mild boredom. I did not have to design a break ritual. I put the key somewhere annoying and the ritual appeared.
Three honest limits, because this article is worthless if I oversell it:
- It does not make you work. Nothing here helps with a task you are avoiding. A locked phone just means you avoid it while looking at your editor.
- Whitelist first. If your team lives in Slack or you are on call, block the feeds and leave the work apps open. A block that makes you miss something important gets uninstalled by Thursday. The support page covers emergency unlocks and the session timeout, which exist for exactly this.
- The laptop is still right there. A phone lock does nothing about a browser tab. It removes the second screen, not every screen. That is a smaller claim, and it is the one I can make.
When pomodoro is the wrong tool
Being fair to the technique means admitting where it does not fit.
If your work has long ramp-up costs, a bell at minute 25 is an interruption you are paying for, not a break you are taking. Debugging is the obvious case. So is writing anything long. Cirillo’s own rule that a pomodoro is indivisible was written to protect the block from the outside world, but the timer cuts from the inside just as hard.
It also fits badly with agent-driven work, where the waits are imposed on you rather than scheduled by you. That is a different problem with a different shape, and I wrote about it separately in the 90-second gap.
The part of pomodoro that generalises is not the number 25. It is the pairing: a bounded block, and a break that is genuinely different from both the block and your feed.
What to try this week
One change, five days.
- Time your next break honestly. Not the timer’s five minutes. The wall clock, from bell to actually restarting. Most people find a number between 12 and 30. Knowing yours is the whole diagnosis.
- Give the break a location. Not a rule, a place. Kitchen, window, front step. The walk does more than the intention.
- Move the exit off the phone. Any tool works if the undo is not a button. If you want the version I built, the setup guide takes about ten minutes and a €0.50 sticker.
- Put the key where the break is. Tag at the coffee machine, not on the desk. Then the walk to unlock and the walk to rest are the same walk.
- Drop the timer if it is fighting you. Keep the protected block, keep the physical break, change the number. The technique is not the 25.
The bell was never the hard part. Getting up is not the hard part either. Sitting back down is.