Pomodoro Technique: Does It Work for Deep Work?

The Pomodoro Technique is a way to work in fixed, timed rounds: pick one task, work on it for 25 minutes without switching, take a short break of about five minutes, and after four rounds take a longer break of 15 to 30 minutes. It works well for starting work you are avoiding and for keeping steady on routine tasks. For deep work, such as writing, design or hard debugging, the evidence is weaker, and many people get better results from longer rounds like 50 minutes on and 10 off. The method, the research, the cases where it fails, and a template are below.

The method as Cirillo describes it

Francesco Cirillo says he created the Pomodoro Technique in the 1980s↗ (opens in a new tab) “with a tomato-shaped kitchen timer and a problem: I couldn’t focus on my university studies.” Pomodoro is Italian for tomato, and each 25-minute round is called a pomodoro. He also points out that the method is usually cut down to one line, “Work for 25 minutes, then take a break,” when the full system includes planning the day, handling interruptions and estimating effort.

1. Choose one task. Write it down. Only that task counts for this round.
2. Set the timer for 25 minutes and work until it rings. If an interruption arrives, note it on paper and go back to the task.
3. Mark the round as done. A tally on paper is enough.
4. Take a short break, about five minutes. Stand up, look away from the screen, do not check email.
5. After four rounds, take a longer break. Emory University Libraries’ summary of the steps↗ (opens in a new tab), taken from Cirillo’s materials, puts it at 15 to 30 minutes.

Two rules make it more than a timer. A pomodoro is indivisible: if an interruption you cannot put off stops you halfway, that round is voided, not counted, and you start a new one. And interruptions are written down rather than acted on, so they can be dealt with at the break or planned for later. That second habit is the part most one-line summaries leave out.

Variations: 50/10, 90-minute blocks and shorter rounds

Twenty-five minutes is a default, not a law. People adjust it to the work:

• 50/10: fifty minutes of work, a ten-minute break. A common choice for writing and programming, where the first ten minutes of a round are spent getting back into the problem.
• 90-minute blocks with a long break: closer to a time block than a pomodoro. Useful for one hard task a day.
• 15/3 or 12/3: shorter rounds for tasks you are avoiding, or on days when focus is low. Starting is the hard part, and a 15-minute promise is easy to keep.
• Pomodoro for a team: two people pairing on the same task agree on the timer, so nobody breaks the other’s focus mid-round.

Whatever length you pick, keep it fixed for a week before judging it. Changing the length every day makes it impossible to tell whether the method is helping.

What research says about breaks

There is little research on the Pomodoro Technique by name, and most of it is on students rather than workers. The research on breaks in general is more useful, and it is more modest than the productivity blogs suggest.

• Breaks help how you feel. A 2022 meta-analysis in PLOS ONE, “Give me a break!”↗ (opens in a new tab), pooled studies of micro-breaks of ten minutes or less and found small but significant effects on vigor and fatigue. It found no significant effect on overall performance. Performance improved only for tasks with lower cognitive demands, and the authors note that recovering from highly depleting tasks may need breaks longer than ten minutes.
• Fixed breaks may beat breaks you decide on yourself. A 2023 study of 87 university students, Biwer and colleagues’ comparison of Pomodoro and self-regulated breaks↗ (opens in a new tab), found that students who chose their own breaks reported more fatigue and distraction and less concentration and motivation. Task completion was the same across groups, so the fixed-break groups reached the same result in less time.
• Brief diversions can keep attention on a long task. In a 2011 study reported by the University of Illinois↗ (opens in a new tab), participants doing a 50-minute task who had two brief diversions kept their performance steady, while most participants in the other groups declined over the course of the task.

Read together: timed breaks reliably make long stretches of work feel less tiring, and they may help you finish routine work faster. They have not been shown to make hard thinking better. So the honest answer to “does it work for deep work?” is that the timer helps you start and stay put, but the 25-minute cut can interrupt the part of hard work that matters most.

When the Pomodoro Technique fails

• Days full of meetings. Paul Graham’s essay Maker’s Schedule, Manager’s Schedule↗ (opens in a new tab) makes the point that “A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in.” A timer cannot rescue a 40-minute gap between two calls. Protect a longer block first, then run rounds inside it.
• Deep coding and debugging. When you finally hold the whole problem in your head, a bell at minute 25 costs more than it saves. Many developers let the round run to a natural stopping point, or switch to 50/10 for this work.
• Work that is not yours to schedule. Support queues and on-call shifts are driven by what arrives. Rounds still help for the backlog between tickets, but not for the queue itself.
• The wrong task. A perfect pomodoro on something that did not matter is still wasted. Choosing the task comes first, which is where a priority method such as the Eisenhower matrix earns its place: pick what is important, then use the timer to do it.

A Pomodoro Technique template to copy

Paper works, and so does a plain text file. The point is to see the task, the rounds and the interruptions in one place:

Date: [Month day, year]
Round length: 25 on / 5 off, long break 20 after 4

Task (one at a time)                     Rounds   Done?
1. [Task title]                          [x][x][ ][ ]
2. [Task title]                          [ ][ ]
3. [Task title]                          [ ]

Interruptions (write, do not act)
- [Reply to Dana about the invoice]      -> at break
- [Idea: add export button]              -> new task
- [Server alert]                         -> urgent, stopped round 3

End of day
Rounds planned: [8]   Rounds done: [6]
What broke rounds: [two unplanned calls]

The “Rounds planned” line is the estimating habit Cirillo’s full system asks for. After a week you will know how many real rounds a normal day holds, which is usually fewer than you expected. That number is useful when you plan the day in blocks, covered in time blocking.

Pairing it with a board: one task in progress

A timer tells you how long to work. It does not tell you what to work on, and it does not remember what you were doing. A board does both. The simplest pairing: whatever is in In Progress is the only thing the timer is for. Before you start a round, look at that lane. If more than one task is there, the round has no single subject.

On fenbs, a board has four lanes, To Do, Next Up, In Progress and Completed, and every task has a priority from 1 to 10, where 1 is the most urgent. There is no timer, no calendar and no due date in fenbs, and no setting that limits how many tasks sit in In Progress, so keeping it to one is a rule you keep yourself. What it adds is the list the timer draws from: sort Next Up by most urgent first, drag the top task into In Progress, and run your rounds on it. Interruptions you wrote down become tasks, and a batch of them can go in at once with Add many, which turns a pasted list into tasks.

If you use an AI assistant during the day, connect it to the same board and ask it at a break: “List what is in In Progress and Next Up, and file the three interruptions I noted as tasks in To Do.” The assistant reads and writes the same tasks you see, and the board’s history records who changed what.