Why the classic 25-minute Pomodoro might be wrong for you

The Pomodoro Technique has a problem nobody talks about: the 25 minutes was made up.

Francesco Cirillo invented it in the late 1980s using a tomato-shaped kitchen timer. He found that breaking work into intervals helped him concentrate. The specific number — 25 — came from his own experience as a university student, not from any study of human cognition.

That’s fine. A lot of useful productivity tools start with intuition. The problem is that 25 minutes became dogma.

What neuroscience actually says

Your brain doesn’t operate on a fixed clock. It follows ultradian rhythms — natural cycles of roughly 90–120 minutes in which your alertness, focus capacity, and cognitive performance rise and fall.

Researchers like Peretz Lavie and Nathaniel Kleitman (who first described REM sleep cycles) documented these rhythms in the 1970s and 80s. The same ~90-minute oscillation that governs sleep stages also governs waking alertness. This is sometimes called the Basic Rest-Activity Cycle (BRAC).

What this means practically: you don’t have uniform focus capacity across the day. You have natural peaks and valleys. A timer that treats every 25 minutes the same ignores all of this.

The chronotype problem

Even if 25 minutes made sense on average (it doesn’t), it would still fail because people have radically different chronotypes — the timing of their natural alertness peaks.

An early chronotype (colloquially, a “morning person”) has peak cognitive performance between roughly 9–11 AM. A late chronotype might not hit peak alertness until early afternoon. Research by Carolyn Anderson and others shows that forcing people to work at mismatched times reduces performance by a measurable margin.

A fixed 25-minute timer has no opinion about when you’re using it. It’s equally “helpful” at 8 AM on a Monday when you’re fresh, and at 3 PM on a Friday when your cortisol has been declining for hours.

The interruption cost

Here’s the part that makes the fixed-interval problem even worse: interruptions are expensive.

Gloria Mark at UC Irvine found that it takes an average of 23 minutes and 15 seconds to fully return to a task after an interruption. A mandatory 5-minute break after a 25-minute session isn’t just neutral — if it cuts through a flow state, it can nuke 20+ minutes of productive recovery time.

The classic Pomodoro response to this is: “just skip the break if you’re in flow.” But that defeats the purpose of having a system in the first place. You’re back to manual judgment calls.

What actually works

The honest answer is: it depends on you.

Some people genuinely thrive on 25-minute intervals. Their cognitive style, work type, and chronotype happen to align with it. For others, 45, 52, or even 90-minute sessions produce better outcomes.

What the research does agree on:

Short breaks are essential — even 5-minute micro-rests restore alertness measurably
The optimal session length varies by individual and should be discovered, not assumed
Fatigue compounds — your ideal session at 10 AM is longer than your ideal session at 4 PM
Flow state should be protected — breaking flow for a scheduled interval is almost always counterproductive

The most honest thing a timer can do is adapt. That means watching how you actually work, not prescribing how you should.

A different approach

Instead of starting with 25 minutes, start with your actual focus signals: how fast you type, when you slow down, how your performance evolves across a session. Use that data to estimate where you are in your natural focus cycle.

This is what Pomodoro tAImer does. It doesn’t replace your judgment — it informs it. The AI watches your keystroke patterns, models your cumulative fatigue, and adjusts session lengths based on what’s actually happening in your brain — not what a 1980s kitchen timer decided was universal.

The goal isn’t to make you a better Pomodoro user. It’s to make you a better thinker.