25/5, 50/10, or 90 Minutes? Choosing the Right Pomodoro Interval for Your Work
The Pomodoro Technique's default 25-minute focus block was chosen by one person in the 1980s based on what worked for him. It works well for a lot of people and tasks — but not for all of them. Choosing the wrong interval doesn't just feel off; it actively undermines the technique's effectiveness. Here's what the research suggests, and how to find your interval.
Why the interval length matters
The goal of any focus interval is to match your work rhythm to your brain's natural attention curve. Too short, and you spend a disproportionate fraction of your time on ramp-up — the cognitive overhead of re-entering a problem each session. Too long, and you're working through the tail end of your attention arc, where quality degrades without you noticing.
The "right" interval length depends on two things: the type of work you're doing and how long your personal attention arc actually is for that work. Both vary more than people assume.
The three most common interval structures
The classic 25/5
Twenty-five minutes of work, five minutes of rest. This is where Cirillo landed, and it's the default for good reasons: it's short enough to start without procrastination, long enough to produce real output on most tasks, and the break is frequent enough to prevent exhaustion.
Works best for:
- Tasks with low ramp-up time — email triage, code review, answering messages, processing a to-do list
- Studying subjects where a natural chunk fits in 25 minutes (a problem set, a textbook section)
- When you're new to time-boxing and building the habit
- Days when you're tired or unmotivated — shorter commitments reduce the resistance to starting
Works less well for: Creative work that requires entering a deep problem space, or any task where getting started takes 10+ minutes.
The 50/10
Fifty minutes of work, ten minutes of rest. A natural doubling of the classic structure. This variant has become popular among developers, writers, and designers who find that 25 minutes isn't long enough to reach the kind of depth where interesting work happens.
The case for 50/10 is real: for tasks with high cognitive ramp-up costs — getting deep into a complex codebase, entering a writing flow, working through a difficult proof — spending 10 minutes of every 30-minute window on context-switching is expensive. A 50-minute block gives you room to actually land in the problem.
Works best for:
- Writing, design, and creative work
- Complex coding tasks — debugging, new feature architecture, refactoring
- Deep reading and research
- Any task where your first 10–15 minutes are typically unproductive "getting into it" time
Watch for: Fatigue accumulating across sessions. A 50-minute block demands more sustained effort. If your 3rd or 4th block of the day feels hollow, you may be running too long.
The 90-minute block
Ninety minutes is not a Pomodoro in the traditional sense — it's a different interval philosophy altogether, rooted in sleep research rather than attention research. Sleep researcher Nathaniel Kleitman and, later, Peretz Lavie identified a roughly 90-minute basic rest-activity cycle (BRAC) in human physiology. During the day, alertness and cognitive capacity oscillate in cycles roughly matching this length. Working with a 90-minute block and then taking a 20-minute break aligns your focused work with the peak of this cycle.
Writer and performance researcher Steven Kotler, drawing on this research, advocates for working in these longer cycles to optimize for the flow state — the psychological state where difficulty, skill, and engagement align and work feels almost effortless. Getting into flow typically takes 15–20 minutes. In a 25-minute block, you'd barely arrive before it's time to stop. In a 90-minute block, you have real room for it.
Works best for:
- High-stakes creative and intellectual work where quality matters more than quantity
- Tasks you do at your cognitive peak (usually morning)
- When you have the schedule flexibility for 20-minute genuine recovery breaks
Works less well for: Most people for most of their workday. 90-minute blocks are demanding and require good conditions — quiet, no interruptions, genuine mental energy. Using them throughout the day isn't sustainable for most people.
A practical comparison
| Interval | Ramp-up overhead | Best for | Risk |
|---|---|---|---|
| 25/5 | Low | Admin, studying, habit-building | Too short for deep creative work |
| 50/10 | Medium | Writing, coding, research | Fatigue if done too many times |
| 90/20 | High | Peak creative work, flow states | Only sustainable 1–2 times per day |
What flow state research actually says
Flow — the state described by psychologist Mihaly Csikszentmihalyi as complete absorption in a challenge that matches your skill level — is associated with substantially higher output quality and satisfaction. Getting there consistently requires three things: clear goals for the session, minimal interruptions, and a challenge that's slightly above your comfort level.
Shorter intervals aren't necessarily hostile to flow, but they do make it harder to sustain. If you regularly find yourself "just getting into it" as the timer rings, your interval is probably too short for your work type. On the other hand, if you're often counting the minutes in the last 10 of a 50-minute block, your interval may be too long.
How to find your actual interval: a two-week experiment
The most reliable way to find your interval isn't to read about it — it's to track your own experience. Here's a simple experiment:
- Week 1: Use 25-minute blocks for all focused work. At the end of each session, rate your focus quality on a 1–5 scale. Write one sentence about how you felt — "hit stride and got cut off," "was ready to stop," "felt scattered," etc.
- Week 2: Switch to 50-minute blocks. Same rating and note after each session.
- At the end: Look at the pattern. Which sessions got higher focus ratings? Which felt more productive? The data usually points clearly in one direction.
Most people end up mixing interval lengths by task type rather than picking one universally — 25-minute blocks for admin, 50-minute blocks for deep work. That's a reasonable outcome. Pomodoro Focus lets you customize session length per sitting, so you can dial in to whatever the day calls for.
The one thing that matters more than the interval
Whatever length you choose, the most important variable is whether you actually protect the session from interruptions. A 50-minute block with two interruptions is worse than a 25-minute block that's clean. Interval optimization is secondary to interruption prevention — get the latter right first, then tune the former.
"The question isn't 'what's the optimal interval?' It's 'what's the longest interval I can reliably protect?' Start there."
Frequently asked questions
Is 25 minutes too short for deep creative work?
It can be. Creative work often requires 10–15 minutes just to re-enter the problem space. For that reason, many writers and designers prefer 50-minute blocks. The 25-minute default is better suited to tasks with lower cognitive ramp-up time — email, administrative work, problem sets with clear entry points.
Can you mix interval lengths in the same day?
Yes, and it often makes sense to. You might use 25-minute blocks for morning email and admin, then switch to 50-minute blocks for an afternoon coding or writing session. The key is deciding before you start, not adjusting mid-session because you're avoiding a task.
What's the minimum useful focus block length?
Below about 15 minutes, the overhead of context-switching in and out starts to dominate. A 10-minute block is better than nothing, but it's not really a Pomodoro — it's closer to a micro-sprint. For most tasks, 20 minutes is a practical floor.
Does the break length matter as much as the work length?
The break length matters, but less precisely than the work length. The important thing is that the break is genuinely restorative — away from the screen, mentally disengaged. A 5-minute break spent scrolling is worth less than a 3-minute break spent walking to the kitchen and back. Scale the break roughly in proportion to the work length: 25/5, 50/10, 90/20.