The Pomodoro Technique: what if focus only took 25 minutes?

How do you run the Pomodoro Technique?

1. At the start of the day, choose and prioritize tasks from your full list, and write them on a 'To Do Today' sheet.
2. Set the timer for 25 minutes and start the first task.
3. Work until the timer rings, even if you finish early; spend leftover minutes reviewing what you just did.
4. When it rings, mark an X next to the task, then take a 3 to 5 minute break away from the work.
5. After every four pomodoros, take a longer break of 15 to 30 minutes.
6. When the task is done, cross it out. Break a task down if it looks bigger than 5 to 7 pomodoros; batch smaller-than-one tasks together.
7. At day's end, copy your Xs to a records sheet and look for one thing to improve tomorrow.

Most guides print only the loop; the earlier version of this page did too. In Cirillo's own paper, the process has five stages: planning at the start of the day, tracking while you work, then recording, processing and visualizing at the end of it. The timer loop covers only the first two. On what the Xs are for, Cirillo is explicit: the completed count is the real effort, and tracking it is 'the key to fully understanding the Pomodoro Technique.'

The end-of-day stages cost little: copy the day's Xs into a records sheet, then ask the data where the same output could take less effort tomorrow. Cirillo caps the whole review at one pomodoro. And the 'six steps of Pomodoro' list you will meet elsewhere is not Cirillo's; recording is exactly the step it drops.

Why do short sprints beat long intentions?

Starting is the expensive part of focus. A vague intention to work on the report all afternoon offers your brain a large, shapeless commitment, and shapeless commitments are what procrastination feeds on. Twenty-five minutes is a different proposition: short enough that refusing feels silly, long enough that real work happens inside it. The timer also gives distraction a price tag. An interruption no longer costs a moment; it costs the sprint.

The breaks are maintenance. Attention wears down quietly, and the 3 to 5 minute pause resets it before the wear shows. Skip the breaks and you have not made the method more serious, you have removed its suspension.

The record does the slower work. A week of Xs tells you what a report costs you in real effort, and next week's estimate stops being a guess. Cirillo built the method around that count, not the countdown.

The timer is a container, not a race.

When does the tomato timer work against you?

The method jars with work that needs long immersion. If you write or code your way into a state where the world disappears, a bell every 25 minutes interrupts exactly the state you were trying to reach, and a longer container like Deep Work will serve you better. It also strains in meeting-heavy jobs where you rarely own 25 unbroken minutes; there, the honest first move is clearing the space, not starting the timer.

And when a sprint ends mid-thought, write the next step down before you stand up. The break is mandatory; losing your thread is not.

The classic mistake: Treating the method as a countdown clock, with breaks skipped and finished sprints never recorded. The breaks keep your attention alive; the record is what you learn from.

What do you do when a pomodoro gets interrupted?

Two kinds, in Cirillo's telling. Internal interruptions are your own impulses: check a price, send that mail, get coffee. Mark an apostrophe on your sheet, write the intruding task on today's list under 'Unplanned and Urgent' if it cannot wait, otherwise on your master list, and finish the pomodoro. The noting has to take seconds; any longer counts as an interruption.

External interruptions, a colleague at your desk, a phone call, get three moves: inform, negotiate a time, call back as agreed. Mark a dash for each attempt. Cirillo offers this as experience rather than data: emergencies that need an instant response are rare, and most requests can wait 25 minutes.

Under both sits the hard edge: a pomodoro is indivisible. One that is definitively broken off is void, as if it had never been set, and it earns no X. That sounds punitive until you see what it buys: a record you can trust. Rule nine of Cirillo's appendix supplies the recovery: the next pomodoro will go better.

Does the Pomodoro Technique actually work?

Three separate claims hide in that question, and the studies treat them differently: breaks help, fixed schedules beat choosing your own, and 25 minutes is special. Breaks have the oldest support: Mackworth's 1948 vigilance experiments showed attention on a monotonous watch task decays within the first half hour and a pause restores it; he studied radar operators, though, not knowledge work, and nothing in his data points you at 25.

Fixed schedules hold up next. Biwer and colleagues (2023) had 87 students work with scheduled breaks or breaks they chose themselves; the self-regulating group ended more fatigued and more distracted, with no difference in work completed. Before you quote it: the scheduled formats were 24/6 and 12/3, and both worked, so the result backs having a schedule, not any particular length.

The 25/5 format itself has one direct trial. Smits, Wenzel and de Bruin (2025) put 94 students through a two-hour study session on true 25/5, Flowtime, or self-chosen breaks: fatigue rose faster and motivation fell faster under Pomodoro, while productivity, task completion and flow did not differ. A follow-up with 176 students (2026) added a comprehension test and found no performance difference. A 2025 scoping review reads more positive, but its gains are self-rated, its trials ran 24/6 and 12/3, and 88 percent of its studies coming out positive says as much about publication as about the method. It also found structured intervals lowered fatigue, the opposite of Smits; the likeliest reason is the design gap, short interventions against a full two-hour session.

Two numbers you will keep meeting deserve correction. The '23 minutes to refocus' figure misreads Mark, Gonzalez and Harris (2005): they measured how long people took to return to interrupted work, not how long focus takes to rebuild, and the spread in their data exceeds the averages. The same paper quietly argues for the method: its workers averaged about 11 minutes in one working sphere before switching, so 25 unbroken minutes is ambitious, not timid. DeskTime's '52/17 rule' is vendor marketing with no published sample, and every interval it has promoted at least doubles a pomodoro.

The bell has a documented cost too. The old defense, that unfinished tasks stay active in memory (the Zeigarnik effect), failed a 2025 meta-analysis across 38 publications, though the pull to resume unfinished work is real. What replicates is attention residue (Leroy, 2009): part of your mind stays with an unfinished task and taxes the next one, and a bell that cuts you off mid-thought is exactly her costly case. Her tested remedy, a brief written plan for resuming, is the write-the-next-step-down habit the failure section above already gives you.

The verdict: timed breaks reliably change how working feels, and across three trials they have never changed what got completed or learned. The structure is better supported than the number; the feelings are better supported than the results. Keep your own tally and let it decide.

How long should a pomodoro actually be?

Between 20 and 35 minutes, 40 at most, and in Cirillo's own account the technique works best at 30. That surprises anyone who knows this as the 25-minute method, but his teams started with hour-long pomodoros because 25 felt too short, tried two hours, then 45 minutes, then 10, and settled on 30 from both directions.

No experiment fixed the number. The paper's one sentence of scientific backing cites, in its own bibliography, a study guide to Orwell's Animal Farm, most likely a numbering slip; either way, none of its 17 sources is a controlled experiment. The length is craft knowledge, and the trials above suggest the exact number matters less than committing to one.

So calibrate with the machinery the method already gives you. Run a week at 25 and read your record: sprints that keep dying early argue for 20, a bell that keeps cutting live focus argues for 30 or 35. If no fixed length fits your work, Flowtime, working until focus fades and then breaking, is the named alternative; its one head-to-head trial (Smits 2025, above) matched a fixed pomodoro on output without beating it. Past 40 minutes you are no longer running the technique, and your effort record stops being comparable day to day. That boundary is Cirillo's own.

How do you make it stick?

What should you ask yourself after the first week?

• What was the most common internal or external distraction during my sprints?
• How did my energy and focus levels change from the first sprint to the fourth?
• Which tasks fit neatly into one sprint, and which were harder to manage?

Common questions about the Pomodoro Technique

Where do you go from here?

If your distractions are mostly self-inflicted inbox checks, Task Batching removes the reason to check. Timeboxing uses the same clock pressure with a defined finish line, and Deep Work is where you go when 25 minutes starts to feel short. Not sure which kind of distraction you have? The page on focusing at work sorts the five by what each one keeps out. All 17 methods live in the method index.