| Method | Work | Break | Best for |
|---|---|---|---|
| Pomodoro | 25 min | 5 min, 15–30 after four | Starting when you do not want to |
| 52:17 | 52 min | 17 min | Sustained routine work |
| Ultradian block | 90 min | 20 min | Deep, complex problems |
| Flowtime | Until you stop | Proportional | Work that reaches flow |
Pomodoro was devised by Francesco Cirillo as a student in the late 1980s, using a kitchen timer shaped like a tomato. The 25 minutes was what the timer and his attention span happened to suggest. It is not a research finding, and there is nothing biologically special about 25.
52:17 circulates widely as though it were a study. It came from a productivity-tracking company analysing its own users and identifying the pattern among their most productive cohort. That is observational data from a self-selected sample of people who installed time-tracking software, published on a company blog. It is a plausible ratio and not an established one.
The 90-minute block rests on firmer ground — ultradian rhythms are real physiological cycles of roughly 90 to 120 minutes, well documented during sleep and with reasonable evidence for waking analogues in alertness. Whether they map neatly onto ideal work blocks is a further inference.
So the correct conclusion is not that one interval is right. It is that the interval should match the task, and any tool insisting on 25 minutes is applying a 1980s kitchen timer to your work.
Two findings are solid and both concern interruption rather than interval length.
Attention residue. After switching tasks, part of your attention remains on the previous one, measurably degrading performance on the new task. This is why a two-minute interruption does not cost two minutes.
Recovery time is long. Observational research on office workers found that after an interruption, returning to the original task took on the order of 23 minutes. That figure is often quoted as though it applies to every ping; it came from field studies of task-switching in real workplaces and describes an average across many interruption types. Treat the order of magnitude as reliable and the precise number as approximate.
Together these say something important about what a focus timer is actually for. Its value is far less about the countdown than about the commitment not to check anything during it. A 25-minute interval with three notification glances is worse than 25 unstructured minutes with the phone in another room.
This is the honest limitation and it is significant. Reaching flow on a hard problem — holding a complex model in working memory — can take 15 to 20 minutes. A bell at 25 minutes arrives exactly when you have finally got there, and the break dismantles what you built. Some programmers and writers report that strict Pomodoro makes deep work harder rather than easier, and the mechanism is straightforward.
The distinction worth drawing: Pomodoro is excellent for task initiation, where the problem is starting a thing you are avoiding, and a 25-minute commitment is small enough to accept. It is poor for flow protection, where the problem is staying immersed. Use short intervals to begin; switch to long blocks once you are moving. Flowtime — working until you naturally stop, then taking a proportional break — exists specifically to handle this case.
A timer cannot make work meaningful, cannot choose the right task, and cannot substitute for sleep. Fatigue reduces available focus far more than technique increases it, and no interval structure rescues a badly under-slept day. Timers also do not fit collaborative or reactive roles — a support engineer cannot ignore a queue for 25 minutes, and forcing the method there just produces guilt.
Move, look at something distant, get water. Scrolling is not a break for the attention system you are trying to rest — it is the same activity with different content.
Note them rather than discarding them. The count of interruptions is more useful information than the count of clean intervals, because it points at the fixable thing.
Most people sustain around three to four hours of genuinely deep work a day, and accounts from writers and researchers converge on that range. If you are planning eight, the plan is the problem.
No. Timings stay in your browser and nothing is transmitted or saved.
Every tool comes with a written guide, and every category is one click away.