How to Use the “Pomodoro Technique” for Maximum Focus

If the Pomodoro Technique has felt either too rigid or too easy to ignore, look past the timer. The method has three working parts beyond “25 minutes on, 5 off”: sizing tasks to fit the interval, handling interruptions without abandoning the session, and knowing when a longer interval suits the work better.

This guide covers all three. Start with the classic 25/5 cycle for admin and dreaded tasks. Protect each interval with Francesco Cirillo’s interruption protocol. Then switch to 50/10, a 90-minute block or an open-ended Flowtime session once the timer starts cutting into deep problem-solving.

Where the 25 minutes came from, and what it is not

Cirillo developed the technique as a university student in the late 1980s. He used a tomato-shaped kitchen timer to see whether he could study for just ten minutes without drifting. His own account of the method’s origin stresses that the timer was a tool for observing and shaping effort, not a stopwatch for squeezing out output.

The 25-minute length is a behavioural choice, not a biological limit. No good evidence shows that attention collapses at minute 25. The longer cycles researchers do describe, such as Nathaniel Kleitman’s basic rest-activity cycle, run closer to 90 to 120 minutes. A short interval works because it lowers the cost of starting and gives every distraction a clear answer: not now.

That answer matters because interruptions cost more than they seem to. In Gloria Mark’s observational research at UC Irvine, interrupted workers compensated by working faster, finishing in similar time but reporting more stress and frustration. A protected interval removes the need to rush to make up lost ground.

Running the classic cycle

1. Write a short To Do Today list and pick one task from it. If choosing is the hard part, sort the list with the Eisenhower Matrix first.
2. Set the timer for 25 minutes and work only on that task.
3. When it rings, stop and mark an X next to the task.
4. Take a 3 to 5 minute break away from the screen.
5. After four Pomodoros, take a longer break of 15 to 30 minutes.

Two rules make the cycle hold. First, a Pomodoro is indivisible: if you abandon it halfway, it does not count, and you start a fresh one later. Second, if you finish the task with time left, spend the remaining minutes reviewing or polishing the work rather than starting something new.

The break is part of the method, not a reward for finishing. What you do in it determines whether the next interval starts fresh; our guide to managing your breaks covers which activities actually restore attention.

Size every task before you start the timer

Most frustration with Pomodoro comes from tasks that do not fit. Cirillo’s sizing rules are blunt: break down activities that are too large, and combine those smaller than a single Pomodoro. A practical cut-off is four: anything you estimate above four Pomodoros gets split into parts that each have a visible finish line.

Consider a freelance web accessibility auditor facing a full site audit estimated at nine Pomodoros. As one item, it stays vague all week. Split, it becomes: run automated checks and list the page templates (2), keyboard and screen-reader pass on navigation and the homepage (3), test the forms and checkout flow (3), write up the findings (1). Each piece can be started and finished in a sitting.

The opposite problem is just as common. Sending an invoice, answering two short emails and booking a call are each ten-minute jobs, and giving each its own Pomodoro wastes the interval. Group them into one admin Pomodoro, the same logic behind batching similar tasks.

Handling interruptions: inform, negotiate, call back

Interruptions come in two kinds, and Cirillo treats them differently. Internal ones are your own urges: check the bank balance, look up that word, reply to that message. Write the thought on a separate list, mark an apostrophe (‘) next to the current task, and return to work. The thought is captured, so you no longer need to hold it.

External interruptions come from other people, and the protocol has three steps:

• Inform: tell the person, briefly, that you are in the middle of something.
• Negotiate: offer a specific time to deal with it, usually right after the current interval.
• Call back: add it to your list and actually follow up when you said you would. This step is what makes people trust the first two.

Mark a dash (-) next to the task for each external interruption. If something is genuinely urgent, stop, deal with it, and void the Pomodoro rather than pretending it continued.

Scripts that work in practice:

• Colleague at your desk: “I’m mid-way through something. Can I come find you at 10:40?”
• Chat message: leave it unread until the break, or set a status: “Heads-down until 11:00, will reply then.”
• Family member at home: “I’ve got 15 minutes left on this. Can it wait until the timer goes?”

At the end of the day, count the marks. Five apostrophes on one task usually means it was poorly defined or dreaded; five dashes means you need a better signal to the people around you.

Choosing an interval: 25/5, 50/10, 90/20 or Flowtime

The most common complaint about Pomodoro is that the timer rings just as the work gets good. For writing, coding or design, a forced stop at 25 minutes can break the absorbed state described in our guide to flow. Match the interval to the task instead of forcing every task into 25 minutes.

Researchers have started testing fixed and flexible formats head to head; a 2025 comparison of Pomodoro, Flowtime and self-regulated breaks among university students is one example. Studies like this are small and student-based, so they offer starting points at best; your own record of estimates and actuals should decide the adjustments.

Be wary of precise-sounding ratios. The popular 52/17 rule did not come from research on elite performers: it originated in DeskTime’s 2014 analysis of its own app users’ activity data, and when the company reran the analysis in 2021, the ratio shifted to 112/26.

A simple switching rule: if you override the timer on the same kind of task three sessions out of four, lengthen the interval. If you drift before it rings, shorten it. A 90-minute block also fits naturally inside a calendar plan built with time blocking.

When the timer works against you

• You lose the thread after every break. Before stopping, write the next action in one line, such as “next: retest the date picker with a screen reader.” Restarting becomes reading, not remembering.
• Five-minute breaks become twenty. Time the break too, and keep it off-screen. Scrolling feels like rest but loads new information.
• Estimates are always wrong. Record actuals for two weeks before changing anything. If a task overruns its estimate, re-estimate the remainder rather than abandoning tracking.
• Your day is mostly meetings. Count gaps, not hours. A 50-minute gap holds one Pomodoro plus a buffer; three such gaps is a productive day.
• Counting Pomodoros replaces finishing work. Judge the day by tasks completed, and use the count only to improve estimates.

A daily Pomodoro sheet to copy

Here is a filled example for a sales-operations specialist with a weekly forecast due and a pile of small requests from account managers. Copy the columns into a notebook or spreadsheet.

Before each session, check four things: the task is under four Pomodoros, the interval matches the work, notifications are silenced, and the interruption list is open beside you. At day’s end, compare estimates with actuals and scan the marks column. That two-minute review is what turns a timer into a method.