How to Use the Pomodoro Technique at Work

Knowledge work is fragmented, and the research on it is mostly small studies of real offices, so I treat the numbers as illustrations, not universal laws. Still, they match what most people feel at a desk:

• When researchers logged the computer activity of 40 information workers for two weeks, the median time spent on one screen before switching was 40 seconds. Shorter focus was linked to lower self-rated productivity at the end of the day.^[1]
• In an earlier observation of 24 information workers, 57% of their "working spheres" (units of work, like a project) were interrupted. Most interrupted work was resumed the same day, but only after more than two other activities.^[2]
• In a lab experiment, people who were interrupted finished their work in less time and with no loss of quality, but reported more stress, frustration, time pressure and effort.^[3] Interruptions don't just cost minutes; they make the same work feel harder.
• Switching tasks leaves "attention residue": when you move on from an unfinished task, part of your mind stays on it, and performance on the next task suffers. In those experiments, finishing the first task under some time pressure helped people let go of it.^[4]

You may have seen the claim that it takes exactly 23 minutes to refocus after an interruption. I couldn't find that number in the published papers it's usually credited to, so I don't use it. The papers above make the point well enough: constant switching is common, and it has a cost.

A pomodoro is a simple counter to all of this: one task, a fixed end point, and a rule that everything else waits until the timer rings.

Cirillo's method starts the day with planning, not with the timer: you pick the day's tasks from a longer list and write them on a "To Do Today" sheet.^[5] Here's the version I use:

1. Spend the first pomodoro planning (or the last one of the day before). Look at your calendar first: meetings decide how many full pomodoros you really have.
2. Count your free blocks. In my experience, a day with a couple of meetings leaves room for far fewer full pomodoros than it seems. Count them before you fill them.
3. Fill the blocks with one important task first, then the smaller ones. If the day goes wrong, the thing that matters most is already done.
4. Batch the small stuff. Email, messages and admin get their own pomodoros (for example one late morning and one late afternoon) instead of leaking into every other block.
5. Leave slack. I plan for fewer pomodoros than I have, because something unexpected always shows up.

A task list that counts pomodoros per task makes this much easier. The Pomodoro timer with tasks lets you set an estimate for each task, shows how many pomodoros you've actually spent on it, and gives you an estimated finish time.

Estimating in pomodoros sounds like a detail, but it's the part of the method that changed my planning the most. Cirillo's two rules: if a task will take more than five to seven pomodoros, break it down; if it takes less than one, group it with similar small tasks.^[5]

The reason to write estimates down is that people are reliably optimistic about their own tasks. In the classic studies on the "planning fallacy", participants underestimated how long their own tasks would take, mainly because they imagined how the work would go instead of remembering how similar tasks had gone before. In one of those studies, when participants were asked to connect their prediction to past experiences, the optimistic bias disappeared.^[6]

That's exactly what a pomodoro log gives you. In practice:

• Before starting, write your estimate next to the task ("3 pomodoros").
• Mark each pomodoro as you finish it.
• At the end of the day, compare. Over a few weeks, you'll see which kinds of tasks you underestimate, and by how much.
• When someone asks "how long will this take?", answer from that history instead of from the best-case scenario in your head.

Interruptions come from two places: your own head, and other people. They need different fixes.

Internal interruptions

The urge to check something, a sudden idea, a reminder about another task. Write it down in a few words and go back to work. Cirillo suggests marking these on your sheet so you can see how often they happen.^[5] Writing a concrete next step for an unfinished goal reduced intrusive thoughts about it in a series of lab experiments, so the list is doing real work.^[11]

External interruptions: inform, negotiate, call back

When a colleague, a client or a family member needs you, Cirillo's routine is to inform them that you're in the middle of something, negotiate when you'll get back to them, and then call back as agreed. In his experience, true emergencies are rare, and a delay of 25 minutes, or even a couple of hours, is almost always acceptable.^[5]

Notifications

Turn them off during pomodoros, including the ones you think you can ignore. In a lab study, simply receiving phone notifications during an attention task, without touching the phone, disrupted performance about as much as using it.^[7] I set chat apps to Do Not Disturb while the timer runs and check them in the break.

When you really have to stop

Then stop. The pomodoro is void, you deal with the issue, and you start a fresh one later.^[5] Before you switch, write one line about where you were. Given the research on attention residue, a note about the next step makes it much easier to come back.^[4]

Meetings don't fit in pomodoros, and they don't need to. The goal is to protect the time around them.

• Cluster meetings on the same half-day when you can. Two meetings at 10:00 and 11:30 break the morning into short pieces; the same two meetings back to back leave one long free block.
• Use short gaps for tasks you can finish. In the 20 minutes before a call, don't start the big report. Pick something that fits in the gap (an email, a review, a small fix), because leaving tasks unfinished is what creates attention residue.^[4]
• Protect one block a day. Two to four consecutive pomodoros for your most important work, marked in your calendar like a meeting. In my experience, people respect a block that looks like an appointment far more than an empty slot.
• Use meetings as natural long breaks only if they're genuinely light. A tense meeting isn't rest; take a few minutes to reset before the next pomodoro.

• Work at your best time of day. Attention and memory vary across the day, and the best time depends on your chronotype: a morning person and an evening person peak at different hours.^[8] Put your protected block where you personally focus best, and keep admin for the dips.
• Make your status visible. Headphones in an open office, a status message on chat, or simply telling the people at home "I'm free at 10:25".
• Keep the phone out of reach during pomodoros, not just face down.
• Close the inbox tab. If your job requires fast replies, agree on a response time with your colleagues (for example "within the hour") and check between pomodoros.
• Pick the right length for the work. For writing or coding, 25 minutes can feel short; a 50/10 timer or a 90-minute deep work block may fit better. Or keep the classic 25/5 on a focus timer in a pinned tab.

Short breaks are one of the better-studied parts of all this. A meta-analysis of breaks of 10 minutes or less found small but real improvements in energy ("vigor") and reductions in fatigue. The effect on performance was smaller and not statistically significant overall; it showed up mainly for less demanding tasks, and longer breaks were linked to bigger performance gains. The authors suggest that recovering from very demanding work may need more than 10 minutes.^[9]

What that means at work:

• Take the short breaks, but don't expect them to fix a draining day on their own.
• Take the long break after a set of pomodoros seriously: 15 to 30 minutes, away from the screen.
• Get up. Walking to get water or stepping outside is a better break than switching to another screen.
• Keep work conversations and email out of the short break, as Cirillo recommends.^[5]

Unfinished work follows people home. A 2026 meta-analysis of studies with workers found that having unfinished tasks was linked to more work-related thoughts during time off, especially rumination.^[10] Those are correlational studies, but they match the experimental finding that making a specific plan for an unfinished goal reduces intrusive thoughts about it.^[11]

So my last pomodoro of the day is a shutdown routine:

• Count today's pomodoros and compare them with the estimates.
• For every unfinished task, write the very next action.
• Draft tomorrow's list, with the most important task first.

It takes a few minutes, and the next morning starts with a decision already made.

Planning a perfect day

A plan with zero slack fails at the first unexpected email. Plan fewer pomodoros than you have, and treat the leftover time as a bonus.

Using pomodoros for meetings and messages

The timer is for focused, individual work. Collaborative sessions follow their own rhythm. Batch messages into dedicated pomodoros instead of timing every reply.

Spending breaks on your phone

Five minutes of scrolling rarely stays five minutes, and it's not much of a rest for your eyes or your attention.

Giving up after a messy day

Some days are all interruptions. That's not a failure of the method; it's information. If you void pomodoros every day, look at what keeps interrupting you and fix that at the source.

Treating the count as a score

Ten pomodoros on the wrong tasks is worse than three on the right one. The count is there to improve your estimates, not to compete with yourself.

No study I know of shows that the Pomodoro Technique multiplies anyone's output. The direct research is limited to small experiments with students. What I can tell you from using it every day is more modest: I start faster, I finish more of what I start, my estimates have become far more realistic, and I end the day knowing where the time went.

Give it two weeks, keep the log, and judge it on your own numbers. If a different rhythm works better for you, use that instead: the research on breaks suggests the details matter less than having a structure you'll actually follow.