# What’s wrong with Pomodoro

POMODORO is a popular way to manage your time. The idea is that instead of half-working all day, you work in intense 25-minute stints, with 5-minute breaks (or occasionally longer) in between, marked by an alarm:

![](https://cdn-images-1.medium.com/max/800/1*knwdU-0_Gei8yRP_2EsY3g.png)

Invented by Francesco Cirillo in the 1980s, Pomodoro was named after a tomato-shaped timer. Even back then there was nothing new about working for fixed periods until an alarm goes off. For centuries, schools have taught lessons this way, ending with a bell.[^wthl98ridfr] And there are various other techniques (listed below) for working in fixed time intervals against the clock. I call such methods ‘clock-work’.

The good
--------

Clock-work has various benefits, principally:

*   Each period is an achievable, bite-sized chunk of work. This makes it easier to start on a daunting project, and to plough on to the next break when a task gets hard or tedious.
*   Each period has a short-term deadline, which focuses your mind and creates a slight sense of urgency.
*   You get regular breaks to maintain your [energy](https://repository.ubn.ru.nl/bitstream/handle/2066/162122/162122.pdf?sequence=1&isAllowed=y), [attention](https://www.sciencedaily.com/releases/2011/02/110208131529.htm), [decision](https://www.pnas.org/content/108/17/6889)-[making](https://discovery.dundee.ac.uk/ws/files/32014711/HEA_2018_0965R2_Revised_Manuscript221218_CLEAN_Submitted.pdf), [performance and well-being](https://www.apa.org/monitor/2019/01/break). They also provide an opportunity to step back and reconsider what you're working on (though thinking about work doesn't make a restful break).
*   The fixed lengths simplify planning, such as school schedules/timetables; similarly, Pomodoro users treat the 25-minute stints as a unit to plan and track their work.

The bad
-------

Though clock-work suits some people, tasks and situations, it has big problems too. Years before I’d even heard of Pomodoro, I devised a similar system using hour-long work stints. But I could never stick to it for more than a few days at a time, as it kept going wrong. Eventually I abandoned it altogether, and figured out why it kept failing:

### No fixed work length is best

How long should each stint last? There’s no consensus between rival time management systems, experts and scientific research at all:

*   Productivity author Mark Forster [recommends](http://markforster.squarespace.com/blog/2021/9/20/using-a-timer.html) starting with **5-minute** bursts, and progressively extending them to **40 minutes**.
*   Medical professor Dr James Levine [suggests](https://www.nytimes.com/2012/06/17/jobs/take-breaks-regularly-to-stay-on-schedule-workstation.html?_r=0) **15 minutes’** work at a time.
*   Though Pomodoro advocates **25 minutes**, many users choose their own length.
*   **30- and 60-minute** stints worked equally well for computer operators in one [study](https://pubmed.ncbi.nlm.nih.gov/7957021/).
*   School classes typically last **30–90 minutes**, and it’s [unclear](https://digitalcommons.dartmouth.edu/cgi/viewcontent.cgi?article=1000&context=educ17whitepapers) what length is best.
*   Time-tracking software DeskTime [found](https://desktime.com/blog/17-52-ratio-most-productive-people/) their most productive users average **52 minutes’** work, plus a 17-minute break.
*   The best music students practised for about **80 minutes** at a time in a well-known [study](https://mrbartonmaths.com/resourcesnew/8.%20Research/Explicit%20Instruction/Deliberate%20Practice.PDF).
*   The Ultradian system advocates working for **90 minutes**, and it’s based on [biological cycles](https://en.wikipedia.org/wiki/Basic_rest%E2%80%93activity_cycle) lasting up to **two hours**.

This vast range — 5 minutes to two hours — shows that there’s no one best work length. Which is hardly surprising: how long you can stay productive depends on your attention span, stamina, and motivation. These [vary](https://www.apa.org/monitor/2019/01/break) with the individual, the time of day, and the task at hand; one size won’t fit all.

### Clock-work hinders creativity

The regular pattern of clock-work can be good for grinding through monotonous tasks. But more creative, intellectual work needs flexibility. When you’re ‘in flow’, you want to keep going — alarms and breaks are annoying and counterproductive.

Conversely, if you finish a task early, Pomodoro tells you to spend the rest of the 25 minutes reviewing or planning; the fixed time periods are sacrosanct. But why can’t you just stop, or begin something else when it suits you?

![](https://cdn-images-1.medium.com/max/600/1*zaw2gqVGj-bsot9q8xoh0Q.jpeg)

Annual [protests](https://en.wikipedia.org/wiki/La_Tomatina) against Pomodoro

### Clock-work conflicts with other people

School schedules/timetables work because everyone has to follow them. But with meetings, calls and interruptions, you can’t expect others to obey your tomato. So when these happen, you have to stop what you’re doing and cut a stint short — disobeying the system.

This means clock-work is mostly for working alone, perhaps just for part of the day. And you’re unlikely to stick to a system you can only use part-time.

### Clock-work fails in emergencies

Crises and deadlines don’t obey your tomato either; when they arise, you may have to skip breaks and keep working. Again, if a system breaks down when push comes to shove, you’ll probably end up abandoning it.

In short, **clock-work techniques like Pomodoro are too rigid**. Your work, your attention, other people, and external events won’t fit into neat time-blocks.

An alternative proposal, called [Flowtime](https://medium.com/@UrgentPigeon/the-flowtime-technique-7685101bd191), suggests working and breaking freely, while keeping a timesheet of what you’ve done and any interruptions, to see what patterns emerge. Though there’s nothing new about starting and stopping when you like (which dates from the Stone Age), it does avoid the rigidity of clock-work. The trouble, though, is that it’s too loose. If work isn’t regulated, your breaks have to be, to avoid lapsing into laziness. Timesheets are also a chore.

A solution
----------

All these problems are solved by my new technique, called [Third Time](https://www.lesswrong.com/posts/RWu8eZqbwgB9zaerh/third-time-a-better-way-to-work). The gist of it is:

**Work for as long or as short as you like**, until you want or need to break. Then **break for up to one-third of the time you’ve just worked**.

So after 15 minutes of dealing with emails, you could stop for up to 5 minutes. After an hour-long meeting, you can take a nice 20-minute coffee break. And if a task bores you after 3 minutes, you can even break then — but only for 1 minute!

![](https://cdn-images-1.medium.com/max/800/1*L0o4WJqCTZy6h-jDTmFkHg.png)

Third Time’s work stints can be any length; breaks are (up to) one-third of the time just worked

Because you can stop whenever you like, you can fit work around meetings, calls, interruptions, meals and errands. It’s completely flexible. But the limit on breaks guarantees you're working for (at least) three-quarters of the day.

Full details on Third Time are in [this post](https://www.lesswrong.com/posts/RWu8eZqbwgB9zaerh/third-time-a-better-way-to-work). (And if you still like Pomodoro, you can even use it alongside Third Time, which fixes its flaws.)

[^wthl98ridfr]: And for many decades, British high schools have used much the same pattern of breaks as Pomodoro: typically 5 minutes between lessons, a longer mid-morning break, and another for lunch. 

*Thanks to Cat and Ari for suggestions & comments*