Francesco Cirillo developed the Pomodoro Technique in the late 1980s using an actual tomato-shaped kitchen timer, as a university student trying to get through his own reading list. It's now one of the most recommended study techniques online, usually summarized as "study 25 minutes, break 5." That summary is accurate and almost useless, because it skips the part that actually makes it work \u2014 and skipping it is the single most common reason people say the technique "doesn't work for them."
It's Not About the 25 Minutes
The specific number matters far less than the structure it creates: a fixed work interval followed by a genuine break, repeated in a cycle. It works because it solves two problems at once. First, a vague goal like "study biology tonight" has no natural entry point, which is exactly why it's easy to open the textbook and reach for your phone instead \u2014 a 25-minute commitment is small enough that starting doesn't feel like a big decision. Second, sustained attention isn't a battery that drains smoothly; working for hours without a real break produces a slow decline in comprehension that's easy to miss because you're still technically "studying." The scheduled break is the mechanism that keeps the next interval effective, not a reward for finishing it.
Four Mistakes That Quietly Cancel the Benefit
Treating the Break as Optional
Skipping it feels productive in the short term but leads to faster fatigue and worse focus in the next interval. The break isn’t a reward for finishing — it’s the mechanism that keeps the next interval effective.
Being Too Rigid About 25 Minutes
The specific number is a reasonable default, not a rule. Dense, formula-heavy work often benefits from longer blocks (35–50 minutes) because reloading a complex problem into working memory after an interruption has a real cost.
Using It for Tasks That Don’t Need It
Quick replies, routine admin, or work you’re already absorbed in don’t need the motivational structure a timer provides. Reserve it for the work you tend to procrastinate on.
Abandoning It After One Bad Day
Some days, interruptions make it impossible to finish a single clean interval. That’s a bad day, not proof the method doesn’t work — the technique is a framework to return to, not a streak to protect.
The Technical Reason Free Timers Drift
There's a wrinkle worth knowing if you've ever had a Pomodoro timer "lose time": most browsers throttle JavaScript timers running in inactive background tabs to save battery, which means a basic countdown that simply subtracts one second at a time can silently drift \u2014 sometimes by minutes \u2014 if you switch tabs mid-session. You come back expecting your break to start and find you've actually been "focusing" for 34 minutes instead of 25, with the extra nine minutes never really measured.
Adapting It for Exam Revision Specifically
The standard 25/5 split is a reasonable default, not the only valid ratio. Dense, formula-heavy subjects often benefit from slightly longer focus blocks (35\u201350 minutes) because context-switching cost is higher \u2014 it takes longer to reload a complex problem into working memory after an interruption. Lighter review work (flashcards, re-reading notes) tends to sit comfortably at the classic 25-minute interval. The discipline of a real break matters more than which exact numbers you use.
Frequently Asked Questions
Why does the Pomodoro technique stop working for some people?
Almost always because the break gets skipped or filled with something high-stimulation like short-form video, which doesn’t actually rest attention — it just swaps one kind of stimulation for another, making it harder to drop back into focused work afterward.
Is 25 minutes the right length for exam revision?
It’s a reasonable starting point, not a fixed rule. Lighter review work (flashcards, re-reading notes) tends to suit the classic 25-minute interval well; dense, formula-heavy subjects often work better with longer 35–50 minute blocks, since context-switching cost is higher for complex material.
Why does my Pomodoro timer lose time when I switch tabs?
Most browsers throttle JavaScript timers in inactive background tabs to save battery, so a countdown that simply subtracts one second at a time can silently drift by minutes. The fix is anchoring the timer to an absolute end timestamp and recalculating from the real clock whenever the tab becomes active again, rather than trusting an uninterrupted countdown.