WerasBlog

What's happening in AI, software, technology and science; plain and sourced.

Subscribe
Guides

What Is the Pomodoro Technique? A Guide Adapted for Desk Work

The core rules of the Pomodoro Technique, how to handle interruptions, alternative interval lengths and a sample plan adapted for a workday full of meetings.

What Is the Pomodoro Technique? A Guide Adapted for Desk Work
Image: Towfiqu barbhuiya · Unsplash · Unsplash License

The short answer to "what is the Pomodoro Technique?" is this: it's a time management method where you split work into uninterrupted 25-minute blocks, taking a 5-minute break after each block and a 15- to 30-minute break after every four. Francesco Cirillo developed the method in the late 1980s, and it takes its name from the tomato-shaped kitchen timer he used ("pomodoro" is Italian for tomato). Its power comes from breaking big, postponed tasks into small pieces you can actually start, and from making breaks part of the plan.

The core rules of the Pomodoro Technique

The classic version of the method has six steps:

  1. Choose the task you're going to work on.
  2. Set the timer for 25 minutes.
  3. Work only on that task until the timer rings.
  4. When the timer rings, note that you've completed one pomodoro.
  5. Take a 5-minute break.
  6. After four pomodoros, take a longer break of 15 to 30 minutes.

The most important rule is this: a pomodoro is indivisible. If you switch to email, your phone or another task during a pomodoro, it counts as incomplete and you start over. The rule may seem strict, but its purpose is to make genuinely focusing on one task for 25 minutes a habit.

Why it works

The practical benefits of the Pomodoro Technique fall under a few headings:

  • It makes starting easier. "Write the report" is intimidating; "work on the report for 25 minutes" isn't. Procrastination often comes from the size of the task, and short blocks lower that threshold.
  • It makes breaks deliberate. Instead of forgetting to take breaks and staring at a screen for hours, or the opposite, constantly sneaking off, breaks become fixed and predictable.
  • It sharpens your estimates. As you record how many pomodoros a task takes, you start estimating similar tasks more realistically.
  • It makes interruptions visible. Seeing how many pomodoros got cut short helps you notice how big your distractions really are.

How to handle interruptions

During a pomodoro, another task may pop into your head, or someone may ask you something. Cirillo's recommended approach can be summarized like this:

  • Internal interruptions (another task that comes to mind): Jot it down briefly on a piece of paper or a note next to you and keep working. Deal with it during the break or in your next planning session.
  • External interruptions (a message or a question): If possible, give the person a quick heads-up, for example, "Can I get back to you in twenty minutes?", and note the follow-up. If it's truly urgent, abandon the pomodoro and start a new one afterward.

Turning off notifications during a pomodoro prevents most interruptions in the first place. Putting your phone in another room or out of sight helps too.

Interval variations

The 25/5 pattern is a starting point, not a fixed rule. You can try different lengths depending on the nature of your work:

PatternGood for
25 / 5Tasks you struggle to start, admin work, email processing sessions
50 / 10Work that needs warm-up time, such as software development, analysis or long-form writing
15 / 3Getting started on tasks you've put off for ages or dislike
90 / 20Deep-focus work where you already slip into flow easily

For work where building context takes a while, like software development, 25 minutes can feel too short; you don't want to be interrupted at the most productive point of your flow. In those cases, try longer blocks.

What is the Pomodoro Technique's place in a day full of meetings?

The classic method assumes you can run pomodoros back to back all day. But most professionals' calendars are broken up by meetings. The solution is to fit pomodoros into the gaps in your calendar.

Sample daily plan

  • 9:00–9:15: Plan the day. Pick three tasks to finish today and write an estimated number of pomodoros next to each.
  • 9:15–11:15: Four pomodoros: the day's most important task. Notifications off.
  • 11:15–11:45: Long break, followed by an email processing session.
  • 12:00–1:00: Meeting.
  • 1:00–2:00: Lunch.
  • 2:00–3:00: Two pomodoros: the second most important task.
  • 3:00–4:00: Meeting.
  • 4:00–5:00: Two pomodoros: small tasks and emails awaiting a reply.
  • 5:00–5:15: End of day: note completed and unfinished pomodoros, and pick tomorrow's first task.

That plan has eight pomodoros a day, roughly three and a half hours of uninterrupted focus. The number may look small, but three or four genuinely uninterrupted hours produce more concrete output than many entire workdays.

Pomodoro in a team

In an open office or a team that messages a lot, the hardest part of using pomodoros is that other people don't know you're focusing. Use the status feature in your messaging app to leave a short note like "In a focus block, back at 11:15." Some teams set certain hours of the day as shared quiet time for everyone: no meetings are scheduled and non-urgent messages wait. An agreement like that makes protecting individual pomodoros much easier.

Common mistakes

  • Skipping breaks. You may not want to stop when you're in the flow, but back-to-back blocks without breaks turn into noticeable fatigue in the second half of the day.
  • Spending breaks on a screen. Five minutes on social media doesn't rest your mind.
  • Turning the pomodoro count into the goal. The aim isn't to rack up pomodoros; it's to move important work forward.

A simple tracking template

Paper or a plain note file is enough:

TaskEstimateActualInterruptions
Proposal text341 external
Budget spreadsheet review22-
Weekly report112 internal

At the end of the week, look at the table: which tasks do you consistently underestimate, and at what times of day do interruptions happen most? Those two questions are the easiest way to improve next week's plan.

Getting-started checklist

  • I've picked a timer (phone, desktop app or kitchen timer).
  • I turn off notifications during pomodoros.
  • I keep a place to jot down interruptions.
  • I step away from the screen during breaks.
  • I record my completed pomodoros at the end of the day.

For longer focus blocks and managing attention, take a look at the deep work article on our blog.

Conclusion

The Pomodoro Technique is a simple method that breaks big tasks into small, startable pieces and makes breaks part of the plan. Start with the classic 25/5 pattern, note your interruptions and adjust the intervals to the nature of your work. Even on a day full of meetings, a few protected pomodoros can be the most productive hours of your day.

#pomodoro#focus#time management#productivity

From Weras Labs

We can help you with this

We turn what you just read into working software for your business. You talk to the person writing the code; price and timeline are clear from day one.

Frequently asked questions

Why are pomodoros 25 minutes long?

25 minutes is the interval Francesco Cirillo used when developing the method, and it's short enough that most people can focus without interruption. Depending on your work, 50- or 90-minute blocks can also be used.

What should I do during a pomodoro break?

Step away from the screen: stand up, drink some water, take a short walk or rest your eyes. Checking email or social media during a break doesn't rest your mind and makes it harder to get into the next pomodoro.

What if something urgent comes up during a pomodoro?

If it's truly urgent, abandon the pomodoro, handle the issue and start a new one. If it isn't urgent, make a note and deal with it during the break or in your next planning session.

Is the Pomodoro Technique right for everyone?

It helps most people with tasks that are hard to start and prone to interruptions. For work that requires staying in flow for long stretches, 25 minutes can feel too short; trying longer blocks is the better fit there.

About the author

Habip Dayan

Habip Dayan

Founder of Weras Labs

Habip Dayan is the founder of Weras Labs, a company that builds software products for professionals and teams. He has been building software since 2018 and writes about AI, cloud architecture and product design.

Comments

Be respectful; no ads or personal data. Comments that break the rules are removed.