The History of the Pomodoro Technique: From Athenian Water Clocks to Cirillo's Tomato Timer

By Victor Hoang · Updated Oct 24, 2026

Picture a student in a shared flat with an exam coming and a mind that would not settle. That student was Francesco Cirillo. His account does not start with a grand system. It starts with a question small enough to try that afternoon.

The Pomodoro Technique began in Italy in the late 1980s. Cirillo, then a university student, used a tomato-shaped kitchen timer to test whether he could concentrate for a very short stretch. His own site says he began developing the technique in the 1980s, and describes it as created in the late 1980s. The throughline is simple: a personal fix for wandering attention became a free book, then an agile team practice, then a subject for research.

This article follows that question from its ancient ancestors, which timed work and speech with water, bells and stopwatches, to the way people use it today. It also keeps one distinction in view: timed intervals are old, but the named technique, with its rules, records and book, is Cirillo's.

Timeline at a Glance

The Timed Hours (c. 430 BCE-1911)

Water, bells and stopwatches teach people to work to a clock

Precursors first, because none of them is the Pomodoro Technique. In the courts of classical Athens, a litigant stood and spoke while water ran from one pot into another below it. According to the University of St Andrews history of mathematics, the judicial water clock was in common use around 430 BCE, used to keep trials and speeches from running too long, with the amount of water depending on the type of case. In the Kenyon translation of Aristotle's Constitution of the Athenians, the allowance is spelled out: ten gallons for a case involving more than five thousand drachmas. An official chosen by lot also closed the supply tube whenever the clerk read a law or affidavit, so the reading did not use up the speaker's time. The Athenians, then, had a fixed budget of time, a device that enforced it, and a rule for pausing it. But the clock limited a speech. It did not tell anyone to rest.

The next precursor concerns the whole working day. The Rule of Benedict, written between 530 and 560 CE according to the Benedictine order's own site, prescribes times for common prayer, meditative reading and manual work. Chapter 48 opens with a line that reads like a time-management maxim: Idleness is the enemy of the soul. It then assigns the brothers to labor and reading at fixed hours, with summer work running from the first hour to about the fourth, and a first signal for the hour of None telling each monk to set aside his work. This is a rhythm imposed by a community and a bell, not chosen by an individual.

The third precursor is closer to the factory. In The Principles of Scientific Management (1911), Frederick Taylor described the pig-iron handlers at Bethlehem Steel. A man standing over the worker with a watch told him, Now pick up a pig and walk. Now sit down and rest. Taylor argued from what he called the law of heavy laboring: a first-class workman handling 92-pound pigs could be under load only 43 per cent of the day, and frequent rest was needed for the muscles to recover. This is a scheduled work-rest cycle, built from timed observation. The difference matters for what follows. Taylor's rest was physical, set by an engineer and enforced by a supervisor. For more on the stopwatch tradition, see our history of time and motion studies, and for the fight over how long a working day should be at all, the history of the 8-hour workday.

What it means for teams today: a timer is an old way to protect a limited resource. What changes across the centuries is who holds it, a judge, an abbot, a supervisor or the worker.

The Tomato Timer (late 1980s-1990s)

A student tests two minutes of focus and keeps the timer

The named technique starts with Cirillo. According to the official site, he created it as a student with a tomato-shaped kitchen timer and a struggle to focus. The site records the first experiment as a question: "Can I study for just two minutes without interruption?" Another page on the site says he was preparing for a university exam and used the timer to test concentrating for a very short period, and that the experiment grew into the full method. The name is the timer's: pomodoro is the Italian word for tomato, and a research chapter on the technique notes it is named for a common kitchen timer in the shape of a tomato.

Cirillo's own pages say the 1980s, and the book's description says the late 1980s. No exact year is given for the first session. What the record does show is that the method grew from a tiny test. The early form is the one researchers later summarized: 25 minutes of focused, uninterrupted work on one task, then 5 minutes of rest, with rules to protect each interval. One of those rules is strict. A pomodoro cannot be split, and if an interruption is not deflected, the pomodoro is treated as if it never began.

The 1990s moved the idea from a desk to a team. In his work as a software development mentor, Cirillo says he suggested the method to struggling clients. Most laughed, but one team tried it, and they began sharing results at conferences, which carried the technique through the software community. Note what is missing from this stage: no book, no website, no certification. It spread by being easy to try and by a small number of teams that said it worked.

What it means for teams today: the starting experiment was two minutes, not twenty-five. If a team's focus is badly broken, a smaller trial may get adopted where a full routine would be ignored.

The Free Book (2006-2008)

A PDF turns a private habit into something people can cite

For years the method lived in practice and in conference talks. In 2006 Cirillo wrote it down. According to Penguin Random House's author page, he published a 130-page guide to the technique in 2006 and offered it as a free download. It was later cited in agile research as an XPLabs technical report, version 1.3, published June 15, 2007. Cirillo's site says the book began as a free PDF, and that when it reached two million downloads his team published it as a book.

The book changed what the technique was. A timer plus a rule is a trick. A timer plus a daily process is a method, and the book supplied the process. Its five stages, as later described by researchers, are planning, tracking, recording, processing and visualizing: decide the day's activities, gather raw data on effort, keep an archive, review it, and chart it. A pomodoro became a unit of effort that could be counted and estimated, not just a block of time. Cirillo's site today says the Technique is much more than a sequence of 25-minute sessions, and that breaks are part of the practice, not a reward for doing more.

The first academic treatment cited in later work came in June 2008, when Federico Gobbo and Matteo Vaccari presented "The Pomodoro Technique for Sustainable Pace in Extreme Programming Teams" at the XP2008 conference in Limerick. A later chapter that cites the paper notes that the technique, originally meant to optimize personal work and study, had by then been widely applied by Italian agile teams.

What it means for teams today: a written method can be tested, taught and criticized, which a habit cannot. If your team has a working practice nobody has recorded, the first step toward improving it is to write it down.

The Agile Years (2008-2010)

Developers adopt the tomato and test it against sustainable pace

Agile teams were looking for exactly this. Kent Beck's Extreme Programming Explained (2000), cited in the same research, had made a fast but sustainable pace a core idea, and the Pomodoro Technique offered a concrete way to produce it. The research chapter on the technique reports that two tutorials on it were given at Agile 2009, the international agile conference, a sign that awareness was growing beyond Italy.

A second book followed from outside Cirillo's circle. Staffan Nöteberg's Pomodoro Technique Illustrated was, by a December 8, 2009 review, now shipping from Pragmatic Bookshelf. The reviewer, a developer and trainer, described the key idea as using a timer to discipline yourself to focus on one thing for a short time.

The team case came from Milan. Xiaofeng Wang, Federico Gobbo and Michael Lane studied the Sourcesense Milan team in a chapter published in 2010 in Agility Across Time and Space, titled "Turning Time from Enemy into an Ally Using the Pomodoro Technique". It asked a question the book had not answered: how does a technique designed for one person work for a team spread across sites? The chapter reports that the team adapted it, including a shared pomodoro, and that the team had positive results using it. That is a modest finding from one team, not proof it works everywhere.

What it means for teams today: a personal technique needs adaptation before a team can use it. Agree on what counts as an interruption, and what the team does when a colleague needs something inside a pomodoro.

The Evidence Years (2011-2023)

Researchers test whether short breaks actually protect focus

Once a method is popular, someone tests it. The research does not start with the Pomodoro Technique, and neither study below tests 25 minutes as a special number. Two studies are worth knowing.

In 2011, Atsunori Ariga and Alejandro Lleras of the University of Illinois published a paper in Cognition. Participants did a visual vigilance task while holding digits in memory. When they retrieved the digits only at the end, performance declined steeply. When they were asked to recall the digits now and then during the task, the vigilance decrement was averted. The authors read this as a challenge to the view that attention is simply depleted. It is lab work on brief task switches, not a test of the Pomodoro routine, and the researchers did not use that name.

In 2023, Felicitas Biwer and colleagues at Maastricht University published a direct comparison in the British Journal of Educational Psychology. Eighty-seven students studied for one day under one of three conditions: self-chosen breaks, a 6-minute break after every 24 minutes (labeled the Pomodoro technique), or a 3-minute break after every 12 minutes. Students who regulated their own breaks studied and rested longer, with more fatigue and distraction and less concentration and motivation. There was no difference between groups in invested mental effort or task completion. The authors concluded that systematic breaks had mood benefits and appeared to have efficiency benefits, and that more research is needed. Note the 24-minute block: this was a close variant, tested on one day.

The pattern in these studies fits an older idea. Taylor argued in 1911 that workers need rest at regular intervals, not when they feel like it. The newer work asks the same question about attention. For where the break fits among other focus habits, see our guide to disciplined breaks.

What it means for teams today: the evidence supports planned breaks over improvised ones, at modest strength. Treat 25 minutes as a starting point to adjust, not a law.

The Mainstream (2013-present)

The free PDF leaves the web and the book reaches the shelf

This era runs alongside the research years above, because the book's commercial path and the lab studies moved in parallel. In 2013, according to the publisher's author page, Cirillo removed the PDF and limited access to his personal website, after it had passed 2 million downloads, about 250,000 a year. On August 14, 2018, the first retail edition was published as The Pomodoro Technique, a 160-page hardcover that sets out the five stages. The publisher describes it as the first time the book was available through retail channels. Cirillo's site says the book has since been translated into many languages.

Today the technique is known to most people as a timer: 25 minutes on, a short break, repeat. The official site presents something broader, with five connected processes: internal, core, daily, weekly and team. Its principles include being gentle with yourself and improving gradually, and its team process is about collaborating without monitoring people. That last point answers Taylor's supervisor with a watch: the person doing the work holds the timer.

The wider story belongs to the history of how knowledge work reshaped the day, covered in our history of knowledge work, and to the other tools people use to plan it, such as day planners, the to-do list and Getting Things Done. The umbrella story of how people learned to budget their hours is the history of time management. For where this fits in the full arc, see the history of productivity.

What it means for teams today: most people use the first half of the technique, the timer, and skip the second half, the records. Counting pomodoros for a week shows where the day actually goes.

Key People

Key Facts

• Cirillo says he began developing the technique in the 1980s as a university student, with a tomato-shaped kitchen timer.
• The core routine in early research was 25 minutes of focused work, then 5 minutes of rest.
• The free 2006 book passed 2 million downloads, about 250,000 a year, before the PDF was removed in 2013.
• The first retail edition was published on August 14, 2018.
• A 2023 study of 87 students found pre-set breaks had mood benefits over self-chosen breaks, with similar task completion.
• Athenian courts used water clocks to limit speeches around 430 BCE.

The Pattern Behind the History

Our synthesis, which we call the Small Test, Free Spread Pattern. It repeats across the timeline:

1. A personal problem sets the question. Cirillo could not focus on his studies.
2. A tiny experiment answers it. Two minutes, one cheap tool, no system.
3. The tool gets rules. Intervals cannot be split, and interruptions are handled or the interval is void.
4. Giving it away spreads it. A free PDF reached millions before a publisher printed it.
5. Teams adapt it and researchers test it. The method meets sustainable pace, shared pomodoros and lab studies.

What It Teaches Teams Today

• Start smaller than you think. The method began as a two-minute test, and a team can trial it for a week without changing a process.
• Let the worker hold the timer. Taylor's version had a supervisor with a watch. Cirillo's has no one watching.
• Protect the interval, not the minute count. The rule that matters is that an interrupted pomodoro is void, so agree how your team handles a colleague who needs you.
• Treat 25 and 5 as defaults. The research supports planned breaks, but the two studies above do not prove those exact numbers.
• Keep the records. The counting and review stages are half the method, and most people skip them.