Productivity10 min read
Customizing Focus Intervals: Find Your Perfect 25/5, 50/10, or 90/15 Pomodoro
Standard Pomodoro too short? Custom intervals in FlowQuest let you match your focus rhythm. Learn when to use 25/5, 50/10, or 90/15 sessions.
By FlowQuest Editorial · 2026-05-22 · Updated 2026-05-22
Why 25 minutes doesn't work for everyone
The classic Pomodoro interval is 25 minutes of focus followed by a 5-minute break. Cirillo invented it in the 1980s with a tomato-shaped kitchen timer (hence the name). The interval was based on his personal experience as a university student, not on any neurological research. For decades it was treated as gospel — 25/5 is just 'the' focus interval. Modern research on focus has revealed that 25 minutes works well for some brains and fails completely for others. ADHD brains with short attention spans need 25/5 or shorter. Deep-work professionals need 50/10 or longer. Creative workers benefit from 90/15 to match ultradian rhythms. Marathon mode (120/20) works for deadline sprints. The point isn't that 25/5 is wrong — it's that there is no universal interval. Your optimal interval depends on your brain, your task, and your current energy state. Treating 25/5 as the default for everyone is like saying everyone should wear size 9 shoes.
The 25/5 foundation: Pomodoro's core
The 25/5 Pomodoro interval works well for: ADHD brains in high-distraction states, frequent context-switchers, light tasks (email, admin), beginners building focus stamina. The 25-minute window is short enough that quitting feels less appealing — you can almost always push through 'just 25 minutes.' The 5-minute break is long enough to physically move, drink water, or check messages, but short enough that you don't lose context. Best use cases: clearing email backlogs, weekly admin work, quick research bursts, anything you'd consider a 'shallow' task. ADHD users in fatigued states benefit specifically — when willpower is depleted, the short interval is the only one that feels achievable. The risk with 25/5 is that you never enter deep flow. Knowledge workers doing complex problem-solving rarely reach productive depth in 25 minutes. Use 25/5 as a maintenance interval and longer intervals for deep work. Don't make it your default if your work demands real concentration.
The 50/10 sprint: Deep work for designers and developers
The 50/10 interval doubles the focus block and the break. 50 minutes is roughly the minimum time required to enter deep flow for most knowledge workers — Cal Newport's research on Deep Work confirms most cognitive flow states require 30-45 minutes of warm-up before peak engagement. 50 minutes gives you 20-30 minutes of real depth. The 10-minute break is long enough for a real reset — walk outside, eat something, decompress — but short enough that you return to the work before the context fully fades. Best use cases: software development sprints, design iteration cycles, writing drafts, complex problem-solving sessions, financial modeling. The 50/10 interval matches what teams in Silicon Valley unofficially adopted as the actual Pomodoro duration in the 2010s. Most professional knowledge workers prefer 50/10 to 25/5 after a 2-week trial. The longer focus block respects the actual time to reach flow, which is the entire point of structured focus.
The 90/15 flow: Ultradian rhythm matching
Your body operates on a 90-minute biological cycle called the ultradian rhythm. This rhythm governs sleep stages (REM + NREM in 90-min cycles) and also waking attention — you experience a natural peak of alertness for ~75-90 minutes, followed by a natural dip when attention degrades. Working with this rhythm is more efficient than fighting it. The 90/15 interval matches the ultradian cycle exactly. 90 minutes of focused work covers a full alertness wave. The 15-minute break covers the natural dip — your body wants to disengage at that point regardless of what you're doing. Trying to push through the dip with willpower works for 5-10 minutes and then collapses into low-quality work. Best use cases: creative work (writing, design, music), research analysis, anything where deep flow matters more than total clock time. Authors and scientists report peak output at this interval. The downside: 90 minutes is intimidating to start, so use it on tasks you're already engaged with, not for warm-up sessions.
The 120/20 marathon: Deadline and team modes
The 120/20 interval is for marathon focus — deadline crunches, sprint finishes, team flow sessions. Two hours of focus with a 20-minute break covers two ultradian cycles back-to-back, with a longer recovery. This isn't sustainable as a daily default, but it's powerful for specific contexts. Best use cases: deadline finishes (last 2 hours before a deliverable), team sprints (everyone in the same 2-hour block), code review marathons, research deep-dives, anything where stopping breaks more than the work. The 20-minute break is mandatory — skipping it leads to 4-hour exhaustion sessions that look productive but produce diminishing returns. FlowQuest's SLA mode pairs with 120/20 to provide 2x XP during deadline pressure, which adds extrinsic motivation when intrinsic drive is fading. Use 120/20 sparingly — once or twice a week max — for the work that actually needs 2-hour blocks. Daily marathon mode causes burnout within a month.
How to test intervals: Start, track, adjust weekly
Don't pick your interval from a blog post — test it. Run a structured experiment: pick one interval (start with 50/10, the most widely-applicable), use it for a full week, track completion rate, energy after sessions, and overall output. Week 2, try a different interval. Week 3, a third. By week 4, you have 60-80 data points and clear winners. The metrics matter: completion rate alone is misleading (you can complete easy 25/5 sessions and call yourself productive). Energy after sessions reveals whether the interval drained or sustained you. Output quality reveals whether the interval enabled deep work. Adjust weekly, not daily — your brain needs time to adapt to a new rhythm before you can judge it fairly. Avoid changing intervals after a bad single session — bad sessions happen at any interval and tell you nothing. Wait for 5+ session data points before drawing conclusions. The right interval is the one that maximizes completion + energy + output for the work you do most often.
Anti-patterns: Too long = overwhelm, too short = no flow
Two common interval mistakes destroy productivity systems. Too long: trying to default to 90/15 or 120/20 when your brain isn't conditioned for it. The result is abandoned sessions, shame, and a system that 'doesn't work for you.' If you abandon 90-minute sessions, drop to 50/10 and rebuild stamina. Long intervals are earned, not assumed. Too short: defaulting to 25/5 for complex work. You'll complete every session and feel productive, but produce shallow output. Your brain enters warm-up and gets pulled back to break before reaching depth. The signal that you're under-intervaled: you finish every session wanting more focus time, not less. Other warning signs: chronic fatigue at week 2 of any new interval (likely too long), restlessness within the first 10 minutes of every session (likely too long or wrong room), getting bored mid-session (interval might be fine but task isn't challenging enough). Listen to your fatigue patterns. They tell you more than your aspirations.
Customize your intervals free — custom intervals included
Custom intervals are FlowQuest's free-tier feature. Set any focus/break combination — 23/7, 45/9, 75/12, whatever your brain wants. No paywall, no Pro requirement. The full custom-interval design space (1-180 minutes focus, 1-60 minutes break) is available from session one. This matters because the right interval is personal. Forcing free users into 25/5 would make FlowQuest useless for the 50% of brains that need different rhythms. Open app.flowquest.io, configure your interval in the session settings, start. No signup, no card. Test 50/10 for a week, then 90/15. After two weeks of structured testing, your default interval will become obvious. The system bends to your brain. That's the entire design philosophy.