Pomodoro Technique
The Pomodoro Technique is a personal time-management method designed by Francesco Cirillo. It splits work into pomodoros: 25-minute units given to a single task, each followed by a 5-minute break, with a long break after every four units. A pomodoro is indivisible. If an interruption stops it, it is void and the person starts a new one. Two records kept on paper make it a measurement technique: the estimate of each task in pomodoros, compared with the number spent, and the interruption log, where the person notes each interruption and then defers it. From them the person reads where the day goes and in which direction their estimates go wrong.
Goal
The Pomodoro Technique organises one person's work into fixed units of time, the pomodoros, and records what happens in each. It protects the attention given to a task, makes interruptions visible and corrects effort estimates.
Pomodoro is Italian for tomato. The name comes from the tomato-shaped kitchen timer with which Francesco Cirillo developed the method as a student.
The technique supports a personal decision: how many pomodoros to commit today and to which tasks. The deliverable fits on paper. The To Do Today Sheet carries the estimate and the actual of each task, plus the interruption marks; the Records Sheet archives these figures day after day.
The technique shares the word "timebox" with time boxing, which Cirillo counts among his influences. Yet the two techniques fix different things.
| Time boxing | Pomodoro | |
|---|---|---|
| What is fixed | The length of the iteration or phase | 25 minutes of focus on one task |
| What flexes | The scope, to fit the time | Nothing: the scope is one task |
| For whom | A team | One person |
| What comes out | The list of what was cut to fit | Estimate against actual and the interruption log |
The pomodoro limits one person's work in progress to one task. The cumulative flow diagram shows the same effect at team scale: at constant throughput, the more work is started in parallel, the longer each item takes to come out. Fast finish also uses a short time limit, but to force a group to produce ideas.
Usage
When to use it
- Writing or modelling alone: acceptance criteria, specifications, a data model, any work that splits into 25-minute blocks.
- Preparing a workshop or an interview: the agenda, the questions and the document analysis are done alone, before the session.
- Personal estimates that keep slipping: estimate and actual in pomodoros show the gap and its direction.
- A fragmented day with no known cause: the log counts the interruptions and gives their source.
- Remote work with instant messaging: each incoming message is noted and deferred as an external interruption.
- A task put off day after day: the commitment is one pomodoro, not the whole task.
When not to use it
- A day made of workshops, interviews and facilitation: there is no solo work to protect; block meeting-free slots in the calendar for analysis.
- A support or customer-facing role: the interruption cannot be deferred; regulate the flow at team level with a kanban board and WIP limits.
Description
The pomodoro and its rules
A pomodoro is 25 minutes of work followed by a 5-minute break. After four pomodoros, the break lasts 15 to 30 minutes. During a pomodoro, the person works on a single task.
A pomodoro is indivisible. It cannot be paused. If an interruption stops it, it is void, as if it had never started. The person then takes a 5-minute break and starts a new one. On the To Do Today Sheet, each completed pomodoro gets a cross. A void pomodoro gets none, but the mark of the interruption that voided it stays on the task's line.
A pomodoro that has started must ring. If the task finishes early, the person reviews the work until the timer rings: rereading, checking, consolidating. The next task waits for the next pomodoro. The one exception: if the task finishes within the first five minutes, the pomodoro does not count.
Above five to seven pomodoros, split. In the Activity Inventory, the person breaks a task estimated higher into smaller tasks and estimates each one separately. Below one pomodoro, combine tasks: three short emails or two calls make one unit.
25 minutes is a starting value. Cirillo puts the useful length between 20 and 35 minutes, 40 at most, and reports that some teams settle on 30 minutes after trying. The person then keeps the chosen length: their estimates are counted in pomodoros and can be compared from one week to the next only if the unit stays the same.
The timer and the three sheets
The timer must be wound by hand, tick audibly, show the time left and ring at the end. Winding the timer commits the person to the task. Cirillo therefore prefers a mechanical timer to a software one.
- The Activity Inventory lists every known task. The person picks the day's tasks from it.
- The To Do Today Sheet lists the committed tasks in order of priority, with their estimate, one cross per completed pomodoro and the interruption marks. Its Unplanned & Urgent section takes whatever comes up and cannot wait until the next day.
- The Records Sheet archives, day after day, the date, the task, the number of pomodoros spent and notes.
A day in five stages
In the morning, the person plans: they take the day's tasks from the inventory, rank them by priority and estimate them in pomodoros. During the day, they track their work: one cross per completed pomodoro, one mark per interruption. In the evening, three stages turn these marks into figures. The person records the day on the Records Sheet. They then process the data: for each task, they calculate the gap between actual and estimate and count the apostrophes and hyphens. The gap is actual minus estimate: a positive gap flags an underestimated task. Finally, they visualise the gaps of several days side by side, so that a bias in one direction shows.
Handling an interruption
The person marks each interruption on the To Do Today Sheet, next to the current task, as soon as it occurs.
An internal interruption comes from the person: an idea, the urge to check email, a forgotten task that resurfaces. The person marks it with an apostrophe (') and writes the item down at once: in the Unplanned & Urgent section if it must be handled the same day, otherwise in the Activity Inventory, marked U and with a deadline if needed. Then the pomodoro continues.
An external interruption comes from someone else: a colleague at the door, a call, a message. The person marks it with a hyphen (-). They inform the other person that a pomodoro is running, negotiate when to answer, then call back as agreed. They write the request on the To Do Today Sheet or in the Activity Inventory. According to Cirillo, a delay of 25 minutes to two hours suits almost everything that people at work call urgent.
An interruption that cannot wait voids the pomodoro: the person handles it on the spot. Cirillo observes that, on review, most items in the log were not urgent. The log shows who interrupts, on what subject and at what time, and the person acts on these causes.
Estimating in pomodoros
When planning in the morning, the person estimates each task on the To Do Today Sheet in pomodoros. Each completed pomodoro adds a cross. At the end of the day, the number of crosses gives the actual, which the Records Sheet archives.
Progress shows in the direction of the gaps. A person who always underestimates or always overestimates has a bias, even if their mean gap shrinks. Estimation improves when overestimates and underestimates balance out.
A team compares what it committed with what it delivered, then adjusts its next commitment. The pomodoro applies this loop to one person, on units short enough for the gap to show the same day.
The pitfalls
Treating 25 minutes as a law. A person who regularly loses focus around the twentieth minute tries a shorter length, then keeps it. Their earlier estimates then drop out of the comparison, which restarts from zero with the new length.
Answering the "just a minute" interruption. A quick answer to a colleague voids the pomodoro. If the person counts that pomodoro anyway, the To Do Today Sheet shows focus time that never happened, and the log loses the interruption it was meant to show.
Moving on to the next task when the first one ends early. The pomodoro then holds two tasks, and the actual of each becomes wrong. The ringing rule protects the figures as much as the attention.
Negotiating a callback with a line manager. In a strongly hierarchical organisation, telling a head of department "I'll call you back in twenty minutes" does not always go down well. The person then handles the interruption on the spot, counts the pomodoro as void and keeps the hyphen in the log: how often this happens is itself data.
Turning the sheets into a productivity indicator. The figures stay honest as long as the person keeps them for themselves. A manager who asks for the number of pomodoros per week gets inflated pomodoros and unreported interruptions.
Timing free time. Cirillo excludes leisure: cutting it into pomodoros turns free time into planned, goal-directed time, which defeats its purpose.
AI considerations
A language model reads the free text on the sheets. It classifies task labels by type and interruption-log notes by source and subject. Classified this way, the log shows the colleague or the question that comes back every day. The spreadsheet then calculates the gap between estimate and actual per task type and brings out a constant bias, for example writing tasks that are always underestimated. The calculation stays in the spreadsheet: a model that miscounts corrupts the figures the technique produces. The model can also propose a breakdown for a task estimated above seven pomodoros; the person corrects that breakdown and estimates each piece themselves.
The estimate stays with the person. A model that estimates for them takes away what they learn by comparing their own estimates with the actual. The log names colleagues and subjects: these are personal data under the FADP, and the person anonymises them before sending them to a hosted service. A chat assistant open during a pomodoro serves the current task as long as the question concerns that task. A question on another subject is an internal interruption, which the person marks with an apostrophe.
Examples
The To Do Today Sheet of a business analyst at a pension fund, taken at 17:00, shows estimate against actual and the interruption log on one page.
| Task | Estimate | Actual | Internal (') | External (-) |
|---|---|---|---|---|
| Write the acceptance criteria for the "Change of address" story | 3 | X X X X | ' ' | - |
| Review the data model of the insured members' portal | 2 | X X | ' | |
| Prepare the agenda for Thursday's workshop | 1 | X | - | |
| Answer the tester's questions in one batch | 1 | X | ||
| Write the decision note on the exchange file format | 1 | X X | ' ' | - |
| Total | 8 | 10 | 5 | 3 |
| Unplanned & Urgent | ||||
| Call back L. Rochat, business team: agreed for 11:00 | ||||
| Answer the project manager on the acceptance test date: agreed for 14:00 | ||||
| See the tester about test case 17: agreed for 16:00 | ||||
| Confirm the delivery date of the exchange file to the partner pension fund: before 17:00 | ||||
The three callbacks correspond to the three hyphens. The fourth line comes from an apostrophe. The other four internal interruptions went to the Activity Inventory. Both overruns point the same way. One day is not enough to conclude. If the Records Sheet shows writing tasks underestimated for three weeks, the analyst raises their writing estimates.
Visualisations
A cycle of four valid pomodoros, with one pomodoro voided by an interruption and then replaced by a fresh one.
Cost
| Phase | Level | Justification |
|---|---|---|
| Preparation | Low | A timer and three sheets. The Activity Inventory is filled in once, then kept up day by day. |
| Execution | Medium | The discipline costs more than the tool: noting every interruption, negotiating every callback, voiding the pomodoro that an interruption stopped. |
| Documentation | Low | Copying to the Records Sheet, calculating the gaps and presenting them, at the end of the day. |
Tooling
A mechanical kitchen timer is enough. The sheets fit in a notebook. A software timer, on a computer or a mobile phone, suits a shared office where the ticking would disturb colleagues; it loses the winding by hand. A spreadsheet takes over the Records Sheet when the person wants to review several weeks of records: it calculates the gaps per task type and charts them, which covers processing and visualising. The To Do Today Sheet stays in the notebook, so that the person can note an apostrophe or a hyphen without opening an app in the middle of a pomodoro. Turning off chat and email notifications during a pomodoro reduces the number of interruptions to note.
Sources
- Francesco Cirillo, The Pomodoro Technique: The Acclaimed Time-Management System That Has Transformed How We Work, Crown Currency, 2018, ISBN 9781524760700: the method, its rules, its sheets, the five stages of the day, the handling of interruptions and estimation in pomodoros. Cirillo designed and named the technique. It rests on this single author: no professional body publishes it.