PomodoroPomodoro, deep work and flow
Some work needs an hour just to load into your head. The method bends to fit that; the principles stay the same.
The complaint
The most common objection from programmers, writers, designers and researchers is this: "Just when I am fully inside the problem, the bell rings and throws me out." It is a fair complaint. Work that needs you to hold many things in mind at once takes time to build up, and a forced stop can cost that build-up. There are several good answers, and none of them is to give up on structure altogether.
First, give the classic length a fair trial
Try 25 minutes properly for a week before changing it. Many people who expect to hate the bell find that the short stop does little harm, because the thread is easy to pick up after five minutes of rest, and the breaks keep them fresh for far longer in the day. The feeling of being "thrown out" is strongest in the first days and often fades.
Leave a breadcrumb
When the bell rings in the middle of a thought, take twenty seconds to write one line: what you were about to do next. "Next: handle the empty-list case in sort()". "Next: second argument, cost example". Then take the break. With that line waiting, you are back inside the problem within a minute of returning. Many people find this habit alone removes the objection.
Use longer rounds
If the work truly needs longer stretches, lengthen the round and the break together:
- 50 minutes of work and 10 of break: a good fit for coding, writing and problem solving.
- 90 minutes of work and 20 of break: for the deepest work, two or three times a day at most.
The rules do not change: one task, no switching, a real break away from the screen. What changes is that you get fewer, longer units. Do not go beyond about 90 minutes without a break; past that point most people are sitting at the task more than working on it.
Link two rounds
Another way is to keep 25 minutes but treat the short break as a pause inside the same piece of work. Stand, stretch, sip water, do not look at any screen or talk about anything else, and return to the same task. The problem stays loaded in your mind through such a break. Two linked rounds give nearly an hour on one problem with a small rest for the body in the middle.
Timer as a starter only
Some people use the timer simply to begin. They promise one round, and if the bell finds them deep in the work, they let the timer run on and take the break at the next natural stopping point. This is a reasonable use, with one caution: set an outer limit, such as 90 minutes, after which you stop whatever happens. Without it, "flow" turns into four hours without water, and the rest of the day pays.
Protect the conditions for deep work
Long concentration depends less on the timer than on what surrounds it:
- A block of the day with no meetings or calls. Morning suits many people.
- Notifications off, phone away. See phone distraction.
- One clearly defined problem chosen before the block begins.
- Everything needed already open: files, references, data.
Which work for which rhythm
| Kind of work | Rhythm that often suits |
|---|---|
| Memorising, revision, routine practice, email | 25 and 5 |
| Problem sets, writing, coding, analysis | 50 and 10, or two linked rounds of 25 |
| Design, research, hard debugging, long-form writing | 90 and 20, once or twice a day |
| Tasks you are avoiding | A single short round, to start |
These are starting points from practice, not rules. Try a rhythm for a week, count what you finish, and keep the one that gives you the most good work with the least strain.
Questions people ask
Is it wrong to ignore the bell when I am in flow?
Not if you choose it knowingly and set an outer limit. Write the next step, take the break at the next natural stop, and do not let one long stretch cost you the rest of the day.
How many 90 minute rounds can I do in a day?
Most people manage two or three with full attention. Fill the rest of the day with lighter work in shorter rounds.
Do longer rounds count as more than one pomodoro?
Count them as what they are. If you switch between lengths, record minutes of focus instead of rounds, as the timer on this site does.
More guides
An independent site. The method described here was created by Francesco Cirillo, and Pomodoro Technique is his registered trademark. This site is not connected with him or his company. The timer is free, needs no login and keeps your settings and counts only in your own browser.