What Is the Pomodoro Technique?

The short answer

The Pomodoro Technique is time management with a very small footprint: you work a defined interval, stop for a short break, and take a longer break after a set number of completed intervals. That is the whole method. Everything else in this guide is about the three variables hidden inside that sentence — how long the interval is, how real the break is, and what you do with the count.

By convention: 25 minutes of work, a 5-minute short break, a 15-minute long break, and the long break after 4 completed focus intervals. Those are defaults, not laws. What matters is that each completed interval is a unit with a name — one pomodoro — because naming the unit is what lets you count it, and “I did five pomodoros today” is a statement about effort that “I worked all day” cannot make.

• Work: one defined interval of undivided attention on one task.
• Short break: a real pause that arrives on schedule after every interval.
• Long break: a bigger pause after a fixed number of completed intervals.
• The count: completed intervals are what you track — not hours at the desk.

Where it came from — and one popular claim I will not make

The method comes from Francesco Cirillo, who developed it as a university student in the late 1980s. The story is plain: he wanted a way to make himself start studying, so he wound a kitchen timer, promised himself to work only until it ran down, and repeated the promise. The timer was shaped like a tomato, which is why the technique carries the Italian word for it.

Now the claim I will not make. You will read, in almost every article about this, that 25 minutes is special because it matches a natural attention cycle of fixed length. I cannot support that here. Bodily cycles are real research — the sleep cycle is well documented at roughly 90 minutes — but nobody has established that focus capacity rises and falls on a 25-minute schedule, or that the technique’s interval was chosen to match your biology. Treat the fixed attention cycle as folklore, and notice that it does not matter, because nothing in the method depends on it.

The interval is a decision, not a discovery. Its job is to be long enough to get somewhere and short enough that saying it out loud feels true. If a different number serves you better, the method is intact — section five shows you how to pick one.

Why the structure helps

The first job of a fixed endpoint is to make starting cheap. Procrastination on a large task is usually not laziness but pricing: “work on this until it is done” has no known cost ceiling, and things with no cost ceiling are hard to begin. “Work on this for 25 minutes” has a known cost, and it is small. You are not committing to finishing; you are committing to being with the task until the timer ends — and being with the task is the part that is hard to start.

The second job is the break. If you rest only when work naturally pauses, you will wait a long time, because open-ended work never pauses; and every pause you take early feels like quitting, so you stop resting and feel guilty instead. A scheduled break inverts that: stopping when the interval ends is not quitting, it is what the plan said, and a pause you were scheduled to receive lands as a reward rather than a theft. This is also why the break has to actually happen — a reward that is never paid out stops working as a reward.

The third job is the count. A completed interval is a legible record of effort: discrete, and verifiable in a way that elapsed hours are not. “I worked four hours” includes the stretches where you stared, emailed, and re-read the same paragraph. “I did six pomodoros” means six stretches you each agreed, at the time, to be real. Over weeks it also becomes data about how long tasks actually take you — the estimate almost everyone is bad at.

None of that is a research finding. These are design properties — why a timer with scheduled breaks behaves differently from an intention to concentrate — and they are the only reasons this guide claims.

How to run your first pomodoro

Here is one full round, with every decision made in advance so the only thing left is working.

The arithmetic of a full round: four 25-minute focus intervals come to 100 minutes of work, the three short breaks between them add 15, and the long break adds 15 more — 130 minutes from start to finish. One discipline point: an interval you abandon partway does not count as completed. That is bookkeeping, not moralising — once partial credit is allowed, the count stops meaning real work and starts meaning time you said you worked.

• Pick one task. Write it down — one task, not your whole day.
• Start the timer for the focus interval. 25 minutes, if you have no reason to change it.
• Work only on that task. When something else intrudes, write it on a scrap of paper and continue.
• When the interval ends, stop — even mid-sentence — and jot one line about where you left off.
• Mark the interval as completed, then take the 5-minute break away from the work.
• Repeat. After 4 completed focus intervals, take the 15-minute long break instead of a short one.

When 25 minutes does not fit your work

Twenty-five minutes is the interval Cirillo happened to use, not a calibrated constant. Two common situations call for moving it; the method survives as long as you keep its shape.

Shorter when you are interrupted a lot

If you are on call, teaching, parenting, or in an office where a shoulder gets tapped every ten minutes, a 25-minute interval is a promise you will break repeatedly, and a broken count is worthless. Drop to 10 or 15 minutes. The point of an interval is that you expect to finish it; an interval you complete one time in five is theatre. Short intervals also help with tasks that are merely unpleasant: the cost of starting feels proportional to the number you said.

Longer for deep work

For writing, design, or anything where 25 minutes is barely enough to get oriented, stretch the focus interval instead. Fifty minutes of work with a 10-minute break is the variant people land on by themselves; some writers go to 90. All four values are editable on the linked timer, so 50/10 is just two numbers to type in.

What to preserve when you change the numbers

Whatever you change, four properties are what make this a technique rather than a stopwatch, and they survive any numbers you pick.

• The proportion. Keep the break roughly a fifth of the focus interval — 5 out of 25, 10 out of 50. Too short and you reset constantly; too long and the break stops feeling like a reward.
• That the break arrives. A longer interval bought by skipping breaks is not a longer interval, it is an unbroken stretch — which is exactly what the technique exists to prevent.
• A fixed count before the long break. Four is conventional; anything from three to six works, as long as the big pause is predictable enough that you can lean on it.
• The count itself. Two 90-minute intervals in a day still count as two. The record survives any renumbering.

Interruptions, endings mid-thought, and breaks that count

Three moments decide whether the technique lasts, and they all show up in the first afternoon.

When you are interrupted mid-interval

The core move is: write it down and return. The email that needs answering, the thing you just remembered, the sudden urge to check something — each goes on a scrap of paper beside the timer in one line, and you go back to the task. Not from stoicism, but from cost: the damage of an interruption is rarely the thirty seconds it takes, it is the two minutes of re-orientation afterwards. A written line gets the thought out of your working memory without getting your hands off the task. When an interruption cannot be deferred — a real emergency, a person standing over you with a real deadline — stop cleanly and do not count that interval.

When the interval ends mid-thought

You will hate this the first time: two sentences from the end of a paragraph, and the phase has changed. Stop anyway, and spend ten seconds writing one line about where the thought was going — “next: the funding paragraph, start with the counterexample”. That line is what makes stopping survivable, because the expensive part of resuming is almost never the work, it is re-deciding what you were doing. The next interval starts faster when you already know its first sentence. If you are genuinely mid-sentence in something that would be silly to abandon, finish — but then start a fresh interval rather than quietly extending the old one, so the count keeps meaning something.

Why the breaks have to be real

Break means away from the thing you were doing. Not a different browser tab, not your phone, not email — those are other screens asking for attention, and they give you neither of the two things a break is for. Physically: stand up, walk, get water, look out of a window, let your eyes do nothing. Functionally, the break has to be different enough from work that your brain registers it as a pause — its power comes from being a reward you can actually taste. Breaks that blur into scrolling leave the next interval starting with the friction of a continuation. And keep five minutes honest: they will not fit a coffee run, so choose a break that fits inside them.

Combining the technique with a task list

The method is built to hang on a task list, and the pairing changes how the list works. Before you start, take each item and write a guess next to it: 2 pomodoros, 5, 12. Most people dislike this step, and it is the most useful thing in the technique, because it forces a number onto a task before you have started avoiding it.

Two rules of thumb fall out of the guesses. Anything you estimate above four or five intervals is not a task, it is a project — break it into pieces until each part comes under that size, because you cannot start a project, only a piece of one. Anything under one interval should be batched with other small things into a single item, or your count fills with trivia. Then mark completed intervals against the task itself, not one global tally, and at the end of the day compare the ticks to the guesses.

The linked timer has no task list — nothing on that page pairs intervals with items — so the list lives on paper or in your notes app, and the timer just supplies the honest count to write next to it.

Pomodoro for studying and revision

The technique transfers well to studying — it was invented by a student for exactly that — and the resizing rules above apply unchanged. What changes is what you do inside the interval, which for students matters far more than its length.

Study sessions

Use an interval as a unit of engagement, not a unit of the syllabus. Twenty-five minutes is good for anything that asks something of you: working problem sets, writing a summary of a chapter from memory, building flashcards, drafting an essay section. Dense material may want 15; anything with real build-up — a long proof, a lab write-up, a piece of music — often runs better at 50. What does not fit the method is “read the textbook this afternoon”: that plan has only time, and time without an endpoint is exactly what the technique replaces.

Revision: retrieval, not re-reading

If you pomodoro your revision, spend the interval recalling rather than reviewing. Close the notes and write down everything you can remember from the topic, then open them and mark what you missed. Do practice questions. Explain the concept out loud as if to someone who is not in the room. Re-reading feels productive and is the weakest use of an interval, because it asks nothing of memory — you can do it for 25 minutes and retain very little. Retrieval is harder, and a fixed deadline turns the difficulty into a game: the score is what you get down before the phase ends. Check what you missed after the break, when your mind is rested.

The count as a study log

Write your day as ticks grouped by subject: four on organic chemistry, one on history, one on admin. Two things usually become visible within a week — you spent less time on the subject you find hard than you believed, and your total real attention is a smaller number than your hours in the library. Both are worth knowing before exam week rather than during it. Keep the log yourself: the timer stores nothing, and its counters start from zero each time the page is opened.

Two ways it quietly stops working

The stopwatch you ignore. This usually develops in the second week: you start glancing at how much time is left, postponing the break because you are nearly done, treating the focus interval as a soft suggestion. Nothing visibly goes wrong — you still work — but the mechanism is gone. The method works because the endpoint was decided in advance and honoured; a timer you override whenever it disagrees with you is just a clock you consult, and clocks do not make starting cheaper or breaks real. The tell is a session counter that almost never advances on schedule. The fix is mechanical: keep the timer visible, take every break, and treat the numbers you typed in this morning as decisions rather than negotiations.

The quota that punishes you. The other failure is the count becoming a target, so a three-pomodoro day feels like evidence of failure. That is a category error. The count is a record, not a verdict, and plenty of legitimate days are low-count days: illness, admin, a meeting-heavy Tuesday, work that genuinely wants 70 uninterrupted minutes and does not fit 25 at all. And once the number hurts, people start inflating it — calls taken with the timer running, desk-sitting recorded as intervals — at which point the number measures time-you-said-you-worked instead of work. If the count starts hurting, change the interval length or drop the counting for a week. Do not push through on guilt.

What this pomodoro timer does — and the one thing it cannot do

The tool linked below is a plain implementation of everything above: 25 minutes of focus, a 5-minute short break, a 15-minute long break, and the long break arriving automatically after every 4 completed focus sessions. All four values are editable, the next phase starts on its own, and a full round runs without you managing the sequence.

Now the limitation, and it lands right on the most important sentence in the technique: you have to notice the transition. This timer switches phases silently. There is no sound, no notification, and no vibration — when a phase ends, only the label on screen and the border colour change. If the tab is in the background, it can slip into the next phase and even finish it without you seeing anything. So keep the tab visible while you work, or add your own alarm and let the timer handle the counting. If you need the page to make the noise for you, this is not it.

Two more behaviours worth knowing. The countdown is recomputed from a deadline rather than counted tick by tick, so if your browser throttles a backgrounded tab, the timer corrects itself when you come back — but only by one phase: an hour spent with the tab buried lands you one interval along, not several intervals deep in catch-up. And nothing is saved: no history, no total focus minutes, no statistics, and the counters reset when the page is reopened. If you want a record, the paper log from the task-list and study sections is where it lives.

• Silent, visual-only phase changes — bring your own alarm, or watch the tab.
• No task list, no skip control, no statistics — keep the list and the record on paper.
• Nothing persists — every reopen starts at zero, by design.

Frequently asked questions