The Pomodoro technique, explained

Francesco Cirillo devised it as a university student in the late 1980s, using a tomato-shaped kitchen timer — pomodoro is Italian for tomato. The problem he was solving was not a shortage of hours. It was that he could not tell where they went.

That origin explains the method’s shape. It is not a productivity system with projects, contexts and reviews. It is a way of turning an amorphous afternoon into a countable number of finished units, so that at the end of it you know what happened.

1. Pick one task. Not a list — one. If it is too big to finish, pick the part you can start.
2. Work for 25 minutes without switching. No email, no messages, no “quick check”. If something arrives, write it down and keep going.
3. Take a 5-minute break. Away from the screen if you can. This is part of the method, not a reward for completing it.
4. After four rounds, take a longer break — 15 to 30 minutes.

One completed 25-minute stretch is a pomodoro. The unit matters more than it looks: it gives you something to count, and counting is what turns “I worked on it for a while” into a number you can plan with next week.

Three things happen when the clock is running, and none of them require believing anything exotic about the brain.

Starting gets cheaper. Committing to 25 minutes is a smaller decision than committing to a task of unknown length, and starting is where most of the resistance lives.

Interruptions become visible. The rule against switching does not stop distractions; it makes you notice them. Most people are surprised by how many there are the first time they count.

Breaks stop being negotiable. Left alone, most of us work until we flag and then rest badly — a scroll, a feed, nothing that restores much. A scheduled break is taken before you need it, which is when it is worth most.

A caveat worth stating plainly: there is no body of controlled trials showing that 25/5 beats other intervals. What is well supported is narrower — that switching between tasks costs you, and that rest before exhaustion beats rest after it. The specific numbers are a sensible starting point, not a finding.

Twenty-five minutes was chosen because it suited one student and one kitchen timer. Treat it as a default to move away from once you know your own numbers.

The useful question is not which pattern is best but which one you finish. A 50-minute session you abandon half the time is worth less than a 25-minute one you complete, and the difference only shows up once you track it.

Skipping the break because the work is going well. Understandable, and it is how the method stops working by the third hour. The break is what makes the next session possible.

Counting pomodoros as a score. Eight shallow sessions is not a better day than four that moved something. The count is a measurement, not a target.

Choosing a task too big to start. “Write the report” is not a session. “Draft the opening section” is.

Using it for work that cannot be interrupted. A conversation, a workshop or anything collaborative does not fit a countdown. The method is for solo work with a clear finish line.

Never changing the interval. The numbers are a starting point. If you consistently run over or stall at eighteen minutes, that is information.

You need a timer and one task. Nothing else, and no setup — the 25-minute timer runs in one click and keeps time correctly if you switch tabs.

1. Write down the single thing you will work on.
2. Start a 25-minute session and leave everything else alone.
3. When something pulls at you, note it rather than following it, and carry on until the chime.
4. Take the five minutes. Properly — away from the screen.
5. Do it four times, then take a longer break.

Do that for a week and you will know two things you almost certainly do not know now: how many focused sessions a working day actually holds for you, and what interrupts them.