The 25-minute Pomodoro isn't a law of nature — it's just the interval Francesco Cirillo happened to use with a kitchen timer in the late 1980s. If it's not working for you, the fix isn't more willpower. It's finding the work-rest ratio that actually matches your brain and your task.
Millions of people use 25/5 because it's the default, not because it's optimal for them. Some tasks need longer runways to get into. Some brains fatigue faster than others. Treating Pomodoro as gospel instead of a starting template is why so many people try it for a week and quietly give up.
Why 25/5 isn't universal
Cirillo's original method was designed for a specific kind of work: discrete, well-defined tasks with an urgency component. It's less suited to work that requires deep ramp-up time — writing, coding, strategic thinking — where 25 minutes is barely enough to get warmed up before the timer interrupts you.
Research on ultradian rhythms (the roughly 90-minute cycles your brain and body naturally move through across a day) suggests attention and energy naturally ebb and flow in longer waves than 25 minutes. A 2014 internal study by the Draugiem Group, which tracked productivity app usage, found that the most productive employees worked in bursts averaging 52 minutes followed by 17-minute breaks — not 25/5. That's one data point, not a universal law, but it makes the same case this article is making: the "right" cycle is a variable, not a constant.
Three cycles worth testing
Instead of guessing, run a two-week experiment with three candidate cycles and see which one holds up against real work:
30/10 — for moderate-focus tasks. Slightly longer than classic Pomodoro, with a break long enough to actually leave your desk. Good for admin work, email triage, and meetings-adjacent tasks where 25 minutes felt rushed but 90 would be overkill.
45/15 — for standard deep work. Enough runway to get past the initial friction of a task (writing a section, debugging a function) without losing the day to a single block. The 15-minute break is long enough for a short walk or a real conversation, not just a sip of coffee.
90/20 — for flow-dependent work. Matches the ultradian rhythm research above. Best for work where the first 20 minutes are just you finding the thread — complex writing, architecture decisions, dense reading. The 20-minute break needs to be a real reset: food, movement, daylight, not scrolling your phone.
How to actually track it
Don't just try each cycle once and go with a gut feeling — a single bad night's sleep or a distracting Slack thread will skew the result. Run each cycle for 3-4 sessions across different days, and log two things after every work block on a scale of 1-5:
Focus quality — did you stay on task, or did your mind wander before the timer went off?
Energy after the break — did you come back ready to work, or still depleted?
After two weeks you'll have a rough table: cycle, task type, average focus score, average energy score. Patterns show up fast. You might find 45/15 wins for coding but 90/20 wins for writing, and 30/10 is your go-to for anything administrative. That's the actual goal here — not one universal number, but a small menu of cycles matched to task types.
This is where having a tool that can switch between named timer profiles matters more than it sounds. Manually resetting a phone timer four times a day, and remembering which ratio you used yesterday, adds friction that kills the experiment before it produces data. Download TimerForge — $17.95 and you can set up 30/10, 45/15, and 90/20 as separate saved timers, run them side by side across a week, and let custom sounds mark the transitions so you're not watching a clock.
When to break the rule entirely
Even your personal optimal cycle isn't fixed forever. Task complexity, sleep quality, and time of day all shift what your brain can sustain. Treat your chosen cycle as a default, not a cage — if you're 35 minutes into a 45-minute block and genuinely in flow, let it run. The point of self-tracking isn't to build a new rigid rule to replace the old rigid rule; it's to build enough self-awareness that you know when to override the timer on purpose, instead of by accident.
The inverse matters too: if you notice your focus score consistently tanks around minute 20 regardless of which cycle you're testing, that's a signal to shorten your blocks rather than push through on discipline alone.
Start today
Pick one task you're doing today that would normally get a standard 25-minute Pomodoro, and instead run it as 45/15. Log your focus and energy score right after. That single data point is the start of the experiment — and probably the first evidence you've had that 25/5 was never actually a rule.