Why 25 minutes exactly?
There's no scientific basis to this figure: it's the length Francesco Cirillo found sustainable in practice. It's long enough to make real progress and short enough not to be daunting. Many people work better in 50 or 90 minutes — test for a week before deciding.
The Pomodoro method is probably the best-known time-management technique in the world, and one of the most poorly applied. Many sum it up as “work twenty-five minutes then take a break” — which is true, but misses what makes it effective. The timer is only a prop: the real mechanism is elsewhere.
This article revisits the method's origin, details the six steps as its author formulated them, explains why it works, and reviews the mistakes that make it fail as well as the variants that suit some jobs better.
Where the Pomodoro method comes from
The technique was formalised in the late 1980s by Francesco Cirillo, then an Italian student struggling with his focus. The founding anecdote is well known: he challenged himself to work ten minutes without getting distracted, using a tomato-shaped kitchen timer — pomodoro in Italian. The name stuck.
What matters about this origin is the initial intention. Cirillo wasn't trying to work longer, but to overcome time-related anxiety. The timer wasn't there to rush him: it was there to turn an undefined, anxiety-inducing mass of work into a short, concrete, finite unit. It's this reversal — time becomes an ally rather than a threat — that is the heart of the method.
The six steps of the method
In its original formulation, the technique fits into six steps:
- Choose a task — a single one, clearly defined. “Write the report introduction”, not “make progress on the report”.
- Set the timer to 25 minutes — this is the pomodoro, the basic unit.
- Work until the bell rings, with no interruption or task switch.
- Mark a cross on a sheet: the pomodoro is validated.
- Take a 5-minute break — actually get up, not open a social network.
- Every four crosses, take a long break of 15 to 30 minutes.
Two rules complete the setup, and they're the ones most often forgotten. The first: a pomodoro is indivisible. If it's interrupted, it doesn't count — you don't pause it, you restart it. The second: if you finish before the bell, you don't move on to something else. You use the remaining time to review or improve the work done.
Why it works
Three mechanisms combine, and none has a direct link to the length chosen.
The decision is moved upstream. The costliest moment of a work session is when you choose what to do — and it's also when procrastination rushes in. By deciding the task before starting the timer, you remove that decision during the session. All that's left is to execute.
The commitment is short, therefore acceptable. “Work on this file” is an open-ended, therefore threatening, prospect. “Work on it for twenty-five minutes” is a bounded prospect: you know when it stops. The psychological cost of starting drops, and starting is almost always the real obstacle.
Interruptions become visible. The indivisible-pomodoro rule forces you to note each interruption instead of merely enduring it. After a few days, you have a concrete measure: how many times an hour you're cut off, and by what. It's often the method's most useful discovery — more than the focus gain itself.
The five mistakes that make the method fail
1. Splitting a poorly defined task. If the task is vague, the timer is useless: you'll spend the twenty-five minutes looking for where to start. A task must be worded so that, at the bell, you know whether it has moved forward or not.
2. Treating the break as optional. This is the most common mistake. The break isn't a reward, it's a component of the system: it lets you keep going for several cycles in a row. Chaining six pomodoros without a break produces exactly what the method tries to avoid — a drop in quality by the end of the day.
3. Taking a break that isn't one. Five minutes on a social network doesn't rest your attention, it engages it differently. Get up, walk, drink water, look out the window. The break should change register, not screen.
4. Clinging to 25 minutes. Twenty-five minutes is a starting point, not a dogma. For work that needs a long warm-up — development, long-form writing, design — the bell often comes at the worst moment.
5. Counting pomodoros like a score. The goal isn't to do lots of them, but to know how many you can actually sustain in a day. Four to six pomodoros of real focus is already an excellent day.
The variants: 50/10, 90/20 and flowtime
Several adaptations exist, each suited to a type of work:
| Format | Rhythm | Suits |
|---|---|---|
| Classic Pomodoro | 25 / 5 | Short, varied tasks, returning to work after a period of distraction |
| 50/10 | 50 / 10 | Writing, analysis, work needing a warm-up |
| 90/20 | 90 / 20 | Development, creation, deep work — aligned with ultradian cycles |
| Flowtime | Free | Those the bell disturbs: note the start time, work as long as it flows, note the end |
The 90/20 format rests on the idea that attention follows natural cycles of about ninety minutes. Flowtime gives up the timer but keeps the measurement: you note your real focus periods, which preserves the main benefit — knowing where your time goes.
The right reflex is to test a format for a full week before judging. A single day says nothing: fatigue, meetings and mood weigh more than a fifteen-minute difference.
Who the method suits — and who it doesn't
The method gives excellent results for individual, measurable, splittable work: revision, writing, processing files, developing well-defined features. It's particularly useful for people who procrastinate at the start, since it lowers the cost of beginning.
It suits poorly, on the other hand, jobs where interruption is the work: customer support, management, incident handling. Splitting a day full of the unexpected into pomodoros mostly produces frustration. In those cases, it's better to protect a single focus block per day and accept that the rest is reactive.
It also suits meetings and any collective work poorly: the rhythm isn't yours.
How to apply it in the browser
A kitchen timer is enough — that's how the method was born. But if your work happens in the browser, the obstacle isn't timing: it's that distractions are one click away. A timer that rings while you're already on a social network isn't much use.
That's why the useful tools combine the two: the timer and the blocking. Nexily Focus works on this principle — sessions of 25, 50 or 90 minutes, active blocking of the sites you've designated for the whole duration, and focus statistics to see what you actually sustain in a week. The extension adds a layer of gamification (XP, badges, streaks) that helps build the habit over time, when the initial motivation fades.
A note of honesty to finish: no tool creates focus. Blocking prevents the reflex gesture, the timer bounds the effort, the statistics give a measure — but it's the well-defined task, chosen before starting the timer, that does the work. The rest is just support.
Nexily FocusPomodoro, site blocking and gamification.
Discover FocusFree: Unlimited site blocking
