The Pomodoro Technique: The 25-Minute Method, Honestly Assessed

Work on a single task for 25 minutes without stopping. When the timer rings, stop and take a five-minute break. Repeat that four times, then take a longer break of 15 to 30 minutes before starting the next set.

That is the entire Pomodoro Technique. One 25-minute block is called a pomodoro, and the method is really a set of rules about what you are allowed to do inside one — which is the part most people never learn, because the timer is easy to copy and the discipline around it is not.

This article covers where the technique came from, the full protocol as its inventor describes it, what attention research actually supports, where the method breaks down, and how to adapt it for learning rather than work.

Where it came from

Francesco Cirillo devised the technique in the late 1980s as a university student in Rome. He was struggling to revise — losing whole evenings to distraction and finishing with nothing to show — and challenged himself to study properly for just ten minutes. To hold himself to it he grabbed a wind-up kitchen timer shaped like a tomato. Pomodoro is Italian for tomato, and the unit of work took the name of the object that measured it.

The ten minutes became a repeatable block, and over the following years Cirillo settled on 25 minutes as the default and built a set of rules around it. He taught it as a time-management method through the 1990s and 2000s, self-published a short book describing the system, and later released an expanded commercial edition. The technique spread largely through software teams before reaching a general audience.

Two things are worth noting. The 25 minutes was arrived at by trial and error, not derived from anything. And the method was never only a timer — Cirillo's book spends most of its length on estimating, recording and protecting work, and comparatively little on the countdown.

How the technique actually works

The full protocol, as Cirillo sets it out:

1. Write the task down first. Cirillo keeps two lists: an activity inventory of everything outstanding, and a "To Do Today" sheet pulled from it each morning. Nothing gets a pomodoro until it has been written down and chosen deliberately.
2. Estimate the task in pomodoros. Anything you think will take more than five to seven pomodoros should be broken into smaller tasks. Anything smaller than one pomodoro should be bundled with other small tasks until the block is full.
3. Set the timer to 25 minutes and work on that task only. No email, no second tab, no "quick check".
4. Record interruptions rather than acting on them. This is the rule people skip most often. When an internal interruption arrives — the urge to look something up, message someone, check a score — you mark it on the sheet and carry on. Cirillo uses an apostrophe for internal interruptions and a dash for external ones. External interruptions get a four-step response: inform the person you are mid-task, negotiate a time, schedule it, and call back when the pomodoro ends.
5. Do not pause or extend a running pomodoro. A pomodoro is indivisible: there is no such thing as half a one. If an interruption genuinely cannot wait and you act on it, the pomodoro is void. It does not count, you do not get partial credit, and you start a fresh one afterwards.
6. If you finish early, keep going until the bell. Review what you did, tidy the work, reread it. Cirillo's phrasing is that you protect the pomodoro — the block is the unit, not the task.
7. Mark an X when the timer rings and stop, even mid-sentence. Take three to five minutes away from the work.
8. After four pomodoros, take 15 to 30 minutes. Then start the next set.
9. Record the day at the end of it — pomodoros completed, estimates against actuals, interruptions logged — and use that record to estimate better next week.

Strip out steps 1, 2, 4 and 9 and you have a kitchen timer, which is what most people are using when they say the technique did not work for them. The recording steps are what turn it from a focus trick into a planning system: after a fortnight you know roughly how many pomodoros a day you actually get, which is almost always fewer than you assumed.

Why it works, in terms of what we know about attention

The technique itself has little direct experimental evidence behind it — there is no substantial body of controlled trials comparing 25/5 against other schedules on real work. What does have evidence behind it is the set of problems the technique is designed around.

Switching between tasks is expensive. Laboratory work on task switching consistently finds that alternating between two tasks is slower and more error-prone than doing each in a block, even when the switch is trivial and expected. Sophie Leroy's work on what she called attention residue describes a related effect in real jobs: when you move from one task to another, part of your attention stays behind on the unfinished first task, and performance on the second suffers. A rule that forbids switching for 25 minutes attacks exactly this cost.

Getting back to interrupted work takes a long time. The figure quoted everywhere is "23 minutes to refocus", and it is usually quoted wrongly. It comes from Gloria Mark's observational research on information workers, which found that after being interrupted, people did not simply return to the original task — they typically worked on two other intervening tasks first, and it took on average around 23 minutes before they resumed the task they had been pulled away from. That is a measure of how long work stays abandoned, not of how long your brain takes to warm up. It is still a good argument for logging interruptions instead of chasing them, but repeat it accurately. Mark's related experimental work found that people compensate for interruption by working faster, and pay for it in stress and perceived time pressure.

A short deadline creates urgency on work that has none. Most knowledge work and most studying is open-ended, and open-ended tasks are the ones people put off. A 25-minute commitment is small enough that the cost of starting is low, and specific enough to remove the "where do I even begin" problem — you decided that in step 1. This is the same mechanism behind if-then planning, where deciding in advance exactly when and where you will do something reliably increases the odds you do it. The related folk claim, Parkinson's law — that work expands to fill the time available — is an adage from a 1955 magazine essay, not a research finding, so treat it as a useful metaphor rather than evidence.

A scheduled break removes the guilt that stops people starting. If a study session has no defined end, every break is a small failure, so people either avoid starting or work through until they are useless. Fixing the break in advance makes it part of the plan. Meta-analyses of short work breaks are reasonably consistent that they help with fatigue and vigour; the evidence that they directly improve task performance is weaker and more variable, so the honest claim is that breaks make the work sustainable, not that they make you faster.

Where it fails

Work that needs long uninterrupted stretches. Some tasks have a long ramp-up: reading a large unfamiliar codebase, working through a proof, drafting something structurally difficult. If it takes you fifteen minutes to load the problem into your head, a 25-minute block gives you ten minutes of useful work and then throws the state away.

Flow states. Flow takes time to enter and a bell is an interruption like any other. Cirillo's rule is to stop anyway, which is sound for repetitive or aversive work. When you are genuinely absorbed and producing, stopping on a timer is counterproductive.

Collaborative and reactive work. The technique assumes you control your own calendar. If your job is meetings, code review, support tickets or anything where other people's interruptions are the work rather than a distraction from it, "inform, negotiate, call back" is not available to you for most of the day.

The 25 minutes is arbitrary. It began as ten minutes and a kitchen timer. There is nothing special about 25, and plenty of people do better on 50/10 or on roughly 90-minute cycles with a longer break. The 90-minute figure is usually justified by reference to Kleitman's basic rest-activity cycle, which was observed in sleep research; the evidence that it governs desk work is thin. The popular "52 minutes on, 17 minutes off" ratio comes from a time-tracking company's analysis of its own users, not from a study. Both are fine as starting points and neither is a law.

Short admin tasks. Batching ten two-minute jobs into one pomodoro works; giving each of them a 25-minute container does not.

How to adapt it

Treat 25/5 as the default setting, not the method. Run it as written for two weeks, keep the record, and then change one variable at a time.

Common variants. 50/10 suits work with a long ramp-up. 90/20 suits a single deep session in the morning. A ten-minute starter pomodoro is the right tool for a task you have been avoiding for days — the point is only to get past the activation barrier. Flowtime inverts the whole thing: you start a timer, work until you naturally flag, record how long you lasted, then break proportionally. It gives up the deadline pressure in exchange for never cutting off a good run.

Breaks are not a reward, they are the other half of the mechanism. The break exists to let directed attention recover and to stop the session running until you are exhausted. A phone break defeats the purpose on every count: same screen, same posture, same demand on attention, plus the novelty and unpredictability that make phones absorbing in the first place. It also reliably overruns, and it hands you a new task to leave residue behind. Stand up, get water, look out of a window, walk. Dull is the point.

Using pomodoros for learning rather than work. A work pomodoro produces output; a study pomodoro has to produce memory, which is a different target. Three adjustments help. Spend the last five minutes of each study pomodoro closed-book, writing down what you can recall — that turns the block into retrieval practice rather than rereading, which is the single highest-return change you can make. Use the long break to revisit material from a previous day rather than the one you just covered, which starts building a spaced schedule for free. And keep study blocks shorter than work blocks when the material is new and dense, because the constraint is working memory rather than stamina; our cognitive load theory explained piece covers why heavy new material overloads quickly regardless of how motivated you are.

Pomodoro and microlearning

A five-minute learning session and a 25-minute work block are solving different problems, which is why both exist.

The pomodoro is a container for effort. It protects a stretch of concentrated production against interruption, and its length is set by how long you can sustain focus. Microlearning is a container for encoding. Its length is set by how much new material working memory can take before it stops going in — and the mechanism that makes it work is not the length of any single session but the gap between sessions. One 25-minute block on a new topic is worse for retention than five short sessions spread across a week, even though the total time is similar. That is the spaced repetition effect, and no amount of focus inside a single block substitutes for it.

In practice they layer. Use pomodoros to defend the hours where you do the hard work — the problem sets, the writing, the deliberate practice. Use short daily sessions, like the five-minute stories in Chunks, for the steady accumulation of material that only sticks if it comes back repeatedly. One is about protecting attention today; the other is about spacing exposure across weeks.

Frequently Asked Questions

What is the Pomodoro Technique?

The Pomodoro Technique is a time-management method in which you work on one task for 25 minutes, take a five-minute break, and take a longer 15 to 30 minute break after every four rounds. It was created by Francesco Cirillo in the late 1980s and named after the tomato-shaped kitchen timer he used. The full method also requires writing the task down beforehand, logging interruptions instead of acting on them, and never pausing or extending a running block.

Why is it 25 minutes?

There is no scientific basis for 25 minutes specifically. Cirillo started with ten minutes and a kitchen timer and settled on 25 through trial and error as a length most people can sustain without a break. Plenty of people work better on 50/10 or 90-minute cycles, and the sensible approach is to treat 25 as a default you test rather than a rule.

Does the Pomodoro Technique actually work?

For many people it works, but the evidence is indirect — there is no substantial body of controlled trials testing 25/5 against other schedules. What is well supported is the set of problems it addresses: task switching is costly, interrupted work often stays abandoned for a long time, and scheduled breaks make long sessions sustainable. It tends to help most with procrastination and distraction, and least with work that requires long uninterrupted stretches.

What is the best Pomodoro schedule?

The best schedule is whichever length you can hold your attention for without strain, tested over a fortnight rather than guessed. 25/5 with a longer break every four rounds is the standard starting point; 50/10 suits work with a slow ramp-up, and shorter 10 or 15-minute blocks are better for tasks you are avoiding or for dense new study material. Change one variable at a time and keep a record of what you actually completed.

Where to take it next

The Pomodoro Technique solves the problem of getting focused work started and keeping it uninterrupted. It does not solve the problem of making what you learn stick, which is governed by how often material comes back rather than how hard you concentrated the first time. If you are using pomodoros to study, the two pieces worth reading alongside this one are the science of spaced repetition, on why the gaps between sessions matter more than the length of any one of them, and cognitive load theory explained, on why dense new material overloads working memory long before you run out of willpower.

Chunks publishes a free five-minute narrated story every day, on iOS and Android — a short, spaced habit that sits alongside whatever focus method you use for the heavy work.