The classic Pomodoro is 25 minutes of work + a 5-minute break, and it's the right default for beginners. But the best session length depends on the task: 15 minutes to beat procrastination, 25 for email-grade work, 45–52 for substantial tasks, and 90 minutes for deep work like writing or coding, where context-loading alone eats your first 15 minutes.
Why 25 minutes became the default
Francesco Cirillo picked 25 minutes in the late 1980s because it was the length of his kitchen tomato timer — and because it's psychologically tiny. The genius of 25 minutes is that it lowers the cost of starting, and starting is the hardest part of focus. Nobody negotiates with themselves over 25 minutes the way they do over "the whole afternoon."
But the tomato timer was an anti-procrastination tool, not an optimal-performance finding. Once starting is no longer your bottleneck, 25-minute blocks start working against you on hard tasks: you spend 10–15 minutes loading the problem into your head, hit stride, and the timer kills the session at its most productive moment.
Match the length to the work
| Length | Best for | Break | Watch out for |
|---|---|---|---|
| 15 min | Beating procrastination, ADHD-friendly starts, awful tasks | 3–5 min | Too short for anything requiring deep context |
| 25 min | Email, admin, studying with active recall, getting started | 5 min | Interrupts hard tasks right as you hit stride |
| 45–52 min | Reports, problem sets, design work — most real tasks | 10–17 min | Requires phone out of the room to survive |
| 90 min | Writing, coding, deep study — one full ultradian cycle | 20–30 min | Hard cap: 2–3 of these per day is elite |
What this looks like in practice
Resolve's focus timer ships with exactly these four presets — 15, 25, 45, and 90 — because they cover the full range from "can't start" to "deep work morning." You name the task before the timer starts (a detail that matters more than the length: a session with a stated intent survives distraction far better), and every second is added to your daily, weekly, and all-time focus totals:
The 90-minute block: focus as a physiological rhythm
Your brain cycles through roughly 90-minute waves of alertness (ultradian rhythms) all day — the same cycles that structure your sleep. A 90-minute focus block rides one full wave: ramp-up, peak, and natural descent into fatigue. That descent is real; pushing through it with caffeine instead of a break is how a great morning becomes a useless afternoon.
For these long sessions, Resolve has a Zen mode — a fullscreen flip clock with nothing else on the screen. No progress bar to glance at, no stats, nothing to fiddle with. The point of deep work is to forget the timer exists:
A simple protocol to find your length
- Week 1: run 25s. Count how many you complete without touching your phone. That completion rate is your baseline.
- Week 2: try 45s on your hardest task. If you finish them, your bottleneck was never attention span — it was session design.
- Week 3: protect one 90 first thing in the morning. Before email, before messages. One real 90-minute block typically outproduces an afternoon of fragmented half-hours.
- Keep 15s in your pocket for days when you can't focus for more than 10 minutes — a tiny completed session restarts the engine.
Whatever lengths you land on, the non-negotiable is tracking them. Focus time you can see compounds; focus time you can't see evaporates into "I was busy all day." That's the same self-monitoring effect that makes habit tracking work — measurement changes behavior.
Frequently asked questions
Is 25 minutes really the best Pomodoro length?
25 minutes is the best starting length, not the best length. Francesco Cirillo chose it because it's short enough that starting feels easy. Once you can reliably finish 25-minute blocks, most people get more done graduating to 45–50 minute sessions, because heavy cognitive work needs 10–15 minutes just to load context.
Why do I still get distracted during a 25-minute Pomodoro?
Usually because the phone is within reach or the task wasn't defined before the timer started. Decide the exact task first ('draft the intro section', not 'work on essay'), put the phone in another room, and use a timer with a visible countdown. If 25 minutes still fails, drop to 15 — a completed 15 beats an abandoned 25.
How many Pomodoros should I do per day?
Most people sustain 6–10 focused 25-minute Pomodoros (about 3–4 hours of true focus) per day, and elite performers rarely exceed 4–5 hours of genuinely deep work. If you're logging 12+ Pomodoros daily, some of them are probably shallow work that doesn't need the ritual.
What's the 52/17 rule?
A study of top-performing employees (via time-tracking app DeskTime) found their average rhythm was 52 minutes of work followed by a 17-minute genuine break. It's evidence that longer-than-25-minute blocks work well — provided the breaks are real breaks, away from the screen.
Should breaks be 5 minutes or longer?
Match the break to the block: ~5 minutes after a 25-minute session, 10–15 after 45–50, and 20–30 after a 90-minute deep work block. The break's job is to let your attention recover — walking, water, stretching. Scrolling your phone isn't a break; it's a different kind of focus drain.
Related questions
The dopamine baseline problem and how to rebuild attention span.
52/17, 90-minute blocks, and other rhythms worth stealing.
Evening screen habits are daytime focus killers.
What has to be true before a 90-minute block turns into flow.
Start Your Transformation Today
Stop relying on motivation. Build the discipline you need to achieve your goals with Resolve.
Download on iOSNo Credit Card Required • Free Plan Available