ChronoClockTime intelligence
UTC
--:--:--

Guide

How to use the Pomodoro technique

Work in timed blocks, take enforced breaks, and stop negotiating with yourself about when to start.

What the technique is

The Pomodoro technique is a work rhythm: you pick one task, set a timer for 25 minutes, work on nothing else until it rings, then take a five-minute break. After four rounds you take a longer break of 15 to 30 minutes. That is the whole method. Francesco Cirillo invented it as a university student in the late 1980s using a tomato-shaped kitchen timer, which is where the name comes from.

It helps to know where the 25 minutes came from, because people treat it as a discovered constant. Cirillo tried intervals from roughly 5 to 30 minutes and kept 25 because it suited him and his timer. He presents it as a starting point, not a result. No study derived it, and no study has since shown it beats other lengths. If you want the reasoning behind picking a different number, the guide to choosing your interval goes through it.

Running your first session

1. Write down one task, not a list

Before the timer starts you should be able to say out loud what you will be doing at minute 12. "Work on the report" fails that test. "Draft the second section of the report" passes. If the task is too big to name that precisely, your first pomodoro is for breaking it down, which is a legitimate use of one.

2. Set the timer where you can see it

A visible countdown does something a mental estimate cannot: it tells you the block is finite. That is most of the psychological work. The ChronoClock timer keeps the countdown in the browser tab title, so it stays legible even when the tab is in the background, and it can send a browser notification when the interval ends.

3. Work until it rings, then actually stop

The stopping matters as much as the starting. If you push through the break because you are on a roll, you have converted the method into ordinary open-ended work with an annoying alarm in it. Cirillo's rule is that a pomodoro is indivisible: either you complete it or you void it and start again. That sounds fussy, but it is what makes the block a unit you can count and estimate with.

4. Log the block

Put a mark next to the task for each completed pomodoro. After a week you will know roughly how many blocks a code review, a lesson plan or a client email batch actually takes. That number is far more useful than your intuition. People systematically underestimate their own completion times, and the reliable fix is checking what similar work took last time. The task list stores a focus-session estimate per task and can start the timer for whichever one you picked, so the count builds itself.

5. Handle interruptions in writing

When something intrudes, note it on a scrap of paper in a few words and keep going. For an interruption you cannot defer, stop the pomodoro rather than half-attending to both things. Sophie Leroy's work on attention residue showed that switching away from an unfinished task degrades performance on the next one, which is the real cost of the "quick question" you tried to answer mid-block.

What to do with the break

The five minutes are not bonus work time and they are not for your phone. The point is to give attention a genuine gap, which means getting your eyes off the screen. Stand up, refill water, look out a window, walk to another room. Ariga and Lleras showed in 2011 that brief interruptions of a long task preempt the slow decline in sustained attention; their explanation is that attention fades because the goal stops feeling novel, and a short break restores it.

Two things people get wrong here. First, scrolling a feed keeps the visual and cognitive load running, so it rests less than it feels like it does. Second, the break is a bad time to check messages, because a message can start a task you did not plan and the next block begins with residue from it.

What the evidence supports

Be careful about strong claims here, including from people selling timers. There is one randomized head-to-head trial. Smits, Wenzel and de Bruin (2025, Behavioral Sciences) put 94 students through two-hour study sessions under three conditions: self-regulated breaks, strict Pomodoro, and Flowtime, where you work until attention drops and then break. Strict Pomodoro produced faster-rising fatigue, and both structured conditions showed motivation declining faster than in the self-regulated group. Productivity, task completion and flow showed no differences at all.

So what is the technique good for? The honest answer is that it lowers the cost of starting. Agreeing to 25 minutes of a task you have been avoiding is much easier than agreeing to an open-ended session, and starting is where most lost time goes. It also forces breaks that people otherwise skip, and it produces a count of blocks that makes future estimates less fictional. Those are real benefits. A specific optimal interval is not one of them.

The corollary is that a strict timer can cost you something when the work is already going well. Interrupting genuine absorption to obey a bell is a bad trade. Use short fixed blocks for tasks you resist, and longer or self-directed blocks for work that pulls you in on its own. The research overview covers the wider evidence on breaks, interruptions and planning.

Mistakes that make people quit

The most common failure is treating the technique as a scheduling system for the whole day. Eight back-to-back pomodoros is not a plan, it is a fantasy. Ericsson's work on deliberate practice found that even elite performers rarely sustain more than about four hours a day of genuinely effortful practice, and most people have far less uninterrupted time than that. Four to six good blocks is a strong day.

The second failure is skipping the planning. If you spend the first six minutes of each block deciding what to do, you lose a quarter of your focused time to a decision you could have made the night before. End every session by writing where you stopped and what the next action is. Leroy and Glomb (2018) found that a one-minute ready-to-resume note measurably reduced the performance damage of switching. The Get It Done workflow builds that note into the end of the session, and the daily planner is where to put the blocks you actually intend to run.

The third is quiet abandonment: you keep the timer running but stop honoring it, and after a week it is decoration. If that happens, shorten the interval rather than pushing harder. A 15-minute block you actually respect is worth more than a 25-minute block you ignore.

Frequently asked questions

Do I have to use 25 minutes?

No. The number is Cirillo's personal preference, not a finding. Pick a length you can complete without cheating, then adjust. See what is the best Pomodoro duration for how to choose.

What if I finish the task before the timer rings?

Cirillo's rule is to use the remaining minutes for review or small improvements on the same work rather than starting something new. In practice, if five or more minutes remain, it is reasonable to start the next task on your list instead. What you should not do is spend the remainder on messages.

Should I count a block that got interrupted?

No. Void it and restart. The count is only useful for estimating if a block means the same thing every time, and a half-attended 25 minutes is not the same unit as a focused one.

Is it bad to break flow when the timer goes off?

Sometimes, yes. If you are genuinely absorbed and the work is going well, stopping to obey a bell costs more than the break returns. That is an argument for using strict timers mainly on tasks you avoid, and letting engaging work run longer.

How many pomodoros should I do in a day?

Fewer than you think. Four to six focused blocks is a productive day for most people with jobs, classes and other obligations. Planning twelve and hitting three teaches you nothing except that you failed.

Related tools