The Pomodoro Technique: how 25 minutes gets more done than a whole morning

You sit down at nine. By eleven you notice fourteen open tabs, a new message in chat, and the task you actually sat down for hasn't moved. The morning wasn't wasted exactly – but you wouldn't call it productive either.

Sound familiar? Then it's worth understanding a technique that's over thirty years old and still outperforms most of the systems invented since.

What the Pomodoro Technique actually is

The whole thing in one sentence: you work for 25 minutes with zero interruptions, then rest for 5. That's one "pomodoro". After four of them, take a longer break of 15–30 minutes.

The name was an accident. In the late 1980s an Italian student named Francesco Cirillo couldn't make himself study for exams. He bet himself he could last ten minutes with his textbooks and grabbed the first thing at hand to count them down – a kitchen timer shaped like a tomato. Tomato in Italian is pomodoro. The name stuck.

The irony is that an entire productivity system grew out of trying to survive ten minutes. Not from theory, not from research – from exam-week desperation.

Why 25 minutes beats "just sit down and do it"

There's no magic in the number. Three fairly ordinary mechanisms do the work.

The barrier to starting drops to almost nothing. "Write the report" is intimidating: you don't know how long it will take or when it ends. "Work on the report for 25 minutes" is something even a tired brain agrees to. You're not promising yourself a result, only a slice of time. That's a completely different level of commitment.

A deadline appears where there wasn't one. When you have "all day", work expands to fill it: read a bit more, check one more thing, reread what you wrote. When the timer says 25 minutes, a different mode kicks in – you start choosing what genuinely matters within that slice.

Interruptions become visible. Normally you don't notice switching to email, your hand just does it. But during a pomodoro, any switch is a deliberate broken promise. You won't stop getting distracted immediately, but you'll start noticing. Noticing is the first step to stopping.

How to run it, step by step

Step 1. Pick one task. Exactly one. Not "do some work" but "write the first section of the proposal". If the task is big, carve off a 25-minute piece.

Step 2. Set a timer for 25 minutes. Any timer: phone, kitchen, the one built into your tracker. What matters is that it counts down on its own so you're not watching the clock.

Step 3. Work until it rings. No email, no chat, no "I'll just check something". If a stray thought arrives, see below.

Step 4. When it rings, stop. Even if it's going well and you want to keep going. This rule feels wrong, but it's what makes the system sustainable: you leave on a high rather than wrung out, so starting the next one isn't scary.

Step 5. Five real minutes of rest. Stand up, stretch, get water, look out a window. Not scrolling – your brain doesn't rest from that, it just keeps processing.

Step 6. After four pomodoros, take a long break. Fifteen to thirty minutes. Now you can eat, walk, do something unrelated to work.

The real problem: people keep interrupting you

Twenty-five perfect minutes in a vacuum sound lovely. In reality a colleague walks over, a client calls, and your brain volunteers "you never paid that invoice".

Cirillo proposed a simple split.

Internal interruptions are the ones your own head produces. A reminder about the invoice, a sudden idea, a memory of something undone. The rule: don't act on it. Write one line in a "later" list and go back to the task. A thought stops circling the moment it's captured – which is exactly why it has to leave your head instead of being held there.

External interruptions are people and notifications. Three moves handle these: tell them (say you'll be free in twenty minutes), note what they want, come back to them in the break. If something genuinely can't wait, the pomodoro is broken and doesn't count. Not "half done" – not done. You start over.

That sounds harsh, and that's the point. A pomodoro is either whole or it isn't.

Five mistakes that kill the habit

Skipping breaks. The most common one. Breaks feel like lost time, so people run three pomodoros back to back. By the fourth, focus is gone and the whole thing is just a marathon with a timer attached.

"Resting" on your phone. Five minutes of social feeds isn't rest, it's swapping one information stream for another. You come out of the break more tired than you went in.

Treating pomodoro count as the goal. "Twelve pomodoros today" sounds impressive and says nothing about results. A pomodoro is a unit of attention, not a unit of achievement. You can spend four of them on something that shouldn't have been done at all.

Forcing everything into it. The technique suits focused work: writing, analysis, figuring things out, coding. It fits badly around meetings, calls, and anything that takes three minutes.

Quitting after one bad day. For the first few days you'll catch yourself drifting constantly, and it will be annoying. That's normal: your focus didn't get worse, you just started seeing what was already happening.

25 minutes isn't sacred

The classic 25/5 is a good starting point, not a law. People adjust the intervals, and they're right to.

• 50/10 – for work that needs a long ramp-up: writing, analysis, code. By the time you're warmed up, 25 minutes is over.
• 15/3 – if focus is genuinely hard right now, anxiety is high, or you're coming back after a long break.
• 90 minutes – for one big block of deep work, but then the rest has to be real, not five minutes.

The rule of thumb: the interval should end before you're spent. If you're checking the timer at minute twenty, it's too long.

Where the technique pays off most

It's a general-purpose method, but the payoff differs by situation. Here are four cases where it helps most, and what to change in each.

Students and anyone studying

Studying is exactly the problem the method was built for: Cirillo was a student who couldn't sit down with his textbooks. Big material, distant deadlines, little interest – perfect conditions for putting it off until the last night.

What to change: one pomodoro, one topic – not "study". Twenty-five minutes summarising one chapter, twenty-five on problems from it. Don't check your phone in the break: after a screen, going back to text is harder than after a window. And count your pomodoros per day – by exam week you'll have an honest picture of how much you actually prepared, rather than how long you sat next to a textbook.

If focusing is genuinely hard for you

For some people twenty-five minutes is a lot. Not out of laziness: attention simply slides off faster. The standard "just concentrate" is useless here.

What to change: start at 10–15 minutes with a 3-minute break, not 25. The task for one interval should be small enough that putting it off feels silly: not "deal with email" but "reply to one message". For the first few days the goal isn't output, it's reaching the timer once. When ten minutes stops feeling like an achievement, grow the interval.

Working from home

At home there are no external edges: nobody sees when you started, and the workday spreads across all sixteen waking hours. Pomodoros give the day both a start and an end.

What to change: commit to a number of intervals, not a number of hours. Eight pomodoros and the day is done, even if the clock says four. That also fixes the other problem of remote work: the feeling that you're always slightly working and never actually resting.

On a team

Pomodoros can run together – across a whole team or just with one colleague. For twenty-five minutes nobody pings anybody, then for five minutes anything goes.

What to change: agree on the start time and on the fact that messages during the interval are not urgent. It works remotely too: a shared timer in the channel, started at 10:00. The side effect is nicer than the main one – people stop messaging each other over every small thing, because they know a window is coming in twenty minutes.

Pairing it with planning your day

Pomodoros answer "how do I not slip away once I've started". They don't answer "what should I be starting". On their own they produce a strange outcome: eight honest intervals spent on work that shouldn't have been done.

The pairing is simple. In the morning you pick two or three important tasks and estimate how many pomodoros each takes. Write a section – two. Clear the inbox – one. A call – off the count, pomodoros don't work for meetings. Add it up: if the plan needs fifteen intervals and the day fits eight, the plan was fiction before you started.

By evening you have two numbers: how many intervals you planned and how many you actually did. A week of that shows your real capacity. For almost everyone it's lower than expected, and that's the most useful discovery there is – plans stop being wishful.

What to time it with

Anything that counts down on its own and makes a sound will do.

A kitchen timer. The original. The non-obvious upside: it's physical, you have to pick it up and turn it – a small ritual for entering work. The downside: it keeps no history.

Your phone. Always at hand, which is exactly the problem: you pick it up to set a timer and surface from the feed ten minutes later. If you use your phone, set it and put it face down, out of reach.

A desktop app. Convenient if the work is at a computer anyway: the timer is visible, intervals count themselves. What matters is that it doesn't live in a separate tab you'll close on day two.

A timer inside your task tracker. The most durable option, because it needs no separate tool: you mark the task, start the interval, and the count lands in that day by itself.

Making the breaks actually work

The break isn't a gap between work, it's part of the method. Spend it wrong and the next interval is worse than the last.

Works: stand up and walk, get water, look out of a window at something far away, stretch, step outside. What these share is a change of posture and distance from a screen. Your eyes need range, your back needs movement, your head needs the absence of a new stream of information.

Doesn't work: social feeds, news, messengers, any short video. That isn't rest, it's swapping one information stream for another. The brain keeps processing, now in fragments. Five minutes of scrolling and you come back more scattered than you left.

The long break after four intervals is a special case. It's the one people skip – "I'm in the zone, I'll keep going". A couple of hours later focus drops and the last intervals run empty. Fifteen to thirty minutes pays for itself by keeping the second half of the day usable.

When to skip it

Honestly: it isn't for everyone, and not always.

If your job is a stream of incoming requests – support, inbound sales, any role where reacting fast is the job – rigid pomodoros will just annoy you. Better to defend one or two protected hours a day and work reactively the rest of the time.

If a task needs deep immersion and you're already in flow, stopping because a timer rang is bad advice. Flow is rare enough as it is; breaking it for the sake of a method is silly.

And if you already sit down and do the work without drama, you don't need this. It treats one specific ailment: not being able to start, and sliding off constantly. No ailment, no medicine.

How to start today

Don't rebuild your whole workflow. Do one thing:

1. Pick the task you've been putting off longest.
2. Set a timer for 25 minutes.
3. Run exactly one pomodoro.

One. Not a day of the method, not a week – one slice. That's enough to tell whether it fits the way you work.

Frequently asked questions

How long is one pomodoro?

The classic interval is 25 minutes of work and 5 of rest. After four cycles you take a longer break of 15–30 minutes. That's a starting point, not a law: the interval can and should be adjusted to you.

What if someone interrupts me mid-pomodoro?

If it can wait, write it down in one line on a later list and go back to the task. If it genuinely can't, the pomodoro is broken and you start a fresh one afterwards. There's no such thing as half a pomodoro.

Can I work longer than 25 minutes?

Yes. Work that needs a long ramp-up fits 50 minutes on, 10 off. If focus is genuinely hard right now, a shorter 15/3 helps. One rule holds: the interval should end before you're spent.

Should I stop when the work is going well?

By the classic method, yes – and that's what makes it sustainable: you leave on a high rather than wrung out. But if you've hit that rare state of full immersion, breaking it for the sake of a method makes no sense.

How many pomodoros a day is normal?

Most people land between six and twelve on a working day, and that's already a lot of focused time. Chasing the number is a mistake: a pomodoro is a unit of attention, not a unit of output.

Does it help with procrastination?

That's exactly where it works best. Procrastination is usually less about laziness and more about fear of a big, undefined task. A deal of "I'll work on this for 25 minutes" drops the barrier to almost nothing.

How is it different from time blocking?

Time blocking answers "when will I do this" and lays tasks out across the calendar. Pomodoro answers "how do I not slip away once I've started". They work fine together: a block in the calendar, pomodoros inside it.

In Do It Today the focus timer is built into the daily tracker: pomodoros are counted automatically, and you can see how many you've done today and this week. No separate app, no tallying slices by hand.