The Pomodoro technique is a timer method: work for 25 minutes, break for 5, and after four rounds take a longer break of 15 to 30 minutes. Each 25-minute block is one "pomodoro".
It is one of the few productivity methods simple enough that you can start using it in the next thirty seconds, and one of the few that still works after the novelty wears off.
Where it came from
Francesco Cirillo developed it as a university student in the late 1980s. Struggling to focus, he challenged himself to study for ten uninterrupted minutes using a kitchen timer shaped like a tomato — pomodoro in Italian. The name stuck, and the interval eventually settled at 25 minutes.
Cirillo's original method has a formal structure with recording sheets and daily planning. Almost nobody uses the full version, and that is fine. The core mechanic carries most of the benefit.
The cycle
- Pick one task. Not a category. One.
- Set a timer for 25 minutes.
- Work on only that task until the timer rings.
- Take a 5-minute break. Stand up, leave the screen.
- Repeat. After four pomodoros, take a longer break of 15 to 30 minutes.
Two rules make the difference between the technique working and not working:
A pomodoro is indivisible. If you break it, it does not count. You do not get 18 minutes of credit. This sounds harsh and is the entire mechanism — it is what makes you resist the urge to check something for "just a second".
Interruptions get written down, not acted on. When a thought arrives mid-pomodoro (an email to send, a thing to look up), write one line on a scrap of paper and carry on. Handle it in the break. Most of them turn out not to matter.
Why it works
It enforces single-tasking. Task switching has a real cost, and the cost is larger than it feels because the switch back is incomplete for several minutes. A pomodoro is a commitment to one thread.
It makes starting cheap. "Work on the report" is unbounded and therefore easy to postpone. "Work on the report for 25 minutes" has a visible end. Committing to something finite is far easier, which is the same principle behind the two-minute rule applied to focus rather than habits.
Breaks are scheduled, not earned. Without a structure, most people work until concentration collapses and then take an unplanned, guilt-tinged, and much longer break. Scheduled breaks arrive before the collapse.
It measures effort honestly. After a week you know how many pomodoros a day you actually manage. For most people the honest number is four to eight, not the twelve they assumed. That number makes planning realistic, and it pairs naturally with the 1-3-5 approach in a daily planning system.
It gives feedback on invisible work. Thinking, writing, and coding produce nothing visible for hours. A count of completed intervals is something concrete.
Common mistakes
Working through the break. You are in flow, so you skip the break, and by pomodoro four you are running on fumes. The break is not a reward, it is maintenance. Skip it occasionally when genuinely deep in something; do not skip it by default.
Spending the break on a screen. Scrolling is not recovery. Stand, walk, look out of a window, get water. The point is to unload attention, not redirect it.
Planning in pomodoros you do not have. If your realistic ceiling is six a day, planning ten sets you up to fail. Track the real number for a week first.
Using it for the wrong work. Meetings, conversations, and reactive support work do not fit into fixed intervals. The technique is for self-directed focus work.
Treating 25 minutes as sacred. It is not. Cirillo picked it for himself. See below.
Adapting the interval
| Variant | Work / break | Best for |
|---|---|---|
| Classic | 25 / 5 | General focus work, studying, admin-heavy days |
| Short | 15 / 3 | Low motivation, tasks you are avoiding, poor concentration days |
| Extended | 50 / 10 | Writing, coding, design — work with a long warm-up |
| Deep | 90 / 20 | Research, complex problem-solving, aligned with natural energy cycles |
| Micro | 10 / 2 | Getting started when nothing else is working |
Two things to keep constant whichever length you choose: the break is roughly a fifth of the work block, and there is a longer break after about two hours of accumulated work.
If you consistently find 25 minutes too short and resent the interruption, move to 50/10. If you consistently cannot reach 25, drop to 15/3 rather than concluding the technique does not suit you. The interval is a dial, not a doctrine.
A realistic day
- 09:00 Pomodoro 1 — the big task, cold start, slowest one.
- 09:30 Pomodoro 2 — the big task, now warmed up.
- 10:00 Pomodoro 3 — the big task.
- 10:30 Pomodoro 4 — the big task, then a 20-minute long break.
- 11:15 Pomodoros 5 and 6 — medium tasks.
- Afternoon Two or three more if the day allows.
Six to eight pomodoros is a genuinely strong day of focused work. If you are managing that consistently, you are ahead of most people, including most people who claim otherwise.
Making it a habit
The technique is easy to try and easy to drop. Treating "focus session" as a tracked habit rather than a technique you occasionally remember changes that — track it with a timer goal, aim for a modest daily target, and let the streak do the reminding.
Start with two pomodoros a day as the goal. That is 50 minutes of genuinely focused work, which is more than most days currently contain, and it is small enough to hit on a bad day. Raise it only once it is boring.
Try it
Set a timer for 25 minutes, pick one task, and start. If you want the sessions to accumulate into something you can look back on, Productivity Dashboard has built-in timer habits with daily goals — free, no account, all local.