The Pomodoro Technique: how it works and when 25 minutes does not fit
The Pomodoro Technique means working on one activity for a fixed stretch, usually 25 minutes, then taking a break, and writing down what happened. The timer is the easy part. What makes it useful is the record: how often you were pulled away, and how long things really took. Whether 25 minutes suits your work is something you can check against your own days instead of arguing about it.
What the method asks you to do
Francesco Cirillo started developing the technique in the 1980s with a tomato-shaped kitchen timer, and his own sites describe it as a complete system for dealing with time, not only a sequence of 25-minute sessions. The tools are a timer, pencil and paper: an Activity Inventory that collects possible work, a To Do Today Sheet for choosing what to do and estimating effort, and a Records Sheet for what actually happened.
In daily use that comes down to a short loop. Pick one activity, run the timer for a session, work on that one thing, take a break when it rings, and note any interruption, whether it came from someone else or from your own urge to check something. At the end of the day you compare the estimates with the records. His materials also say breaks are part of the practice, not a reward.
Cirillo's book The Pomodoro Technique, first published online in 2006, gives the numbers most timers copy: a break of 3 to 5 minutes after each Pomodoro, and every four Pomodoros a longer break of 15 to 30 minutes. It also has a rule that a Pomodoro is indivisible: one that is definitively interrupted counts as void, as if it had never been set, rather than as half done. That rule is why the record counts whole sessions and marks interruptions, instead of adding up minutes.
Pomodoro is a registered trademark; the official pages offer a book, an online course and free worksheets for the full method. This post covers the timer and the review, and how to test them on your own work.
Why a fixed block can help
Cirillo's own account of the mechanism is about boundaries. A day of work can feel like one continuous stream of demands, and a timer cuts out a small piece of it that you can observe. Inside that piece you notice how often you want to switch to something else, you see an interruption before it disappears into the background, and you see the gap between what you planned and what happened.
He also treats an interruption as information, not a failure of discipline: it may point to an unclear priority, an unrealistic plan, or an environment that needs to change. So the session length is a starting guess, and the records are what let you correct it.
The official pages do not claim that 25 minutes is the best length for everyone, so treat the number as a starting default rather than a finding.
The closest controlled test is small. In a 2023 study in the British Journal of Educational Psychology, Biwer and colleagues had 87 university students study for one day with breaks they chose themselves, with a 6-minute break after every 24 minutes, or with a 3-minute break after every 12. Students who chose their own breaks studied and rested in longer stretches and reported more fatigue and distraction and lower concentration and motivation, while task completion and reported mental effort did not differ. One day of student self-study supports scheduled breaks more than it supports 25 minutes in particular.
When 25 minutes does not fit coding or writing
Work that needs a lot of loaded context, such as tracing a bug across five files or holding the argument of a long draft in your head, can take ten or fifteen minutes just to get into. If the timer rings at minute 25, the break lands right after you finally had the whole thing in view, and the restart can cost almost as much as the first start did. A longer block, say 45 to 90 minutes, is the obvious thing to try, keeping the break habit but not the 25.
The opposite case exists too. For a task you keep avoiding, a short block of 10 or 15 minutes tends to be easier to begin, because the commitment is small and has an end. And for reactive work such as support, review queues or meetings, a block of uninterrupted time may not exist, so the timer mostly measures how often you were broken in on.
Cirillo's own pages say different tasks and circumstances call for different choices, and that you should observe what works and adapt. So changing the length is within the spirit of the method, as long as you keep recording what each length gives you.
Variations that keep the useful part
Longer blocks are the common one: 50 minutes of work and a break, or a block that ends when you reach a natural stopping point instead of at a fixed minute. A task-sized variant lets one session equal one small step, such as one function or section, so the block ends on a finished thing.
Another keeps the timer loose and the tally strict: you work in whatever blocks the day allows, and you mark each interruption with its source on paper. After a week the marks show which two or three sources produce most of the breaks, which is often more useful than any block length.
None of these is an official version or a tested ranking. They are ways of keeping the two parts that Cirillo's materials stress, a boundary around one activity and a record you review.
Checking it against recorded sessions
Hina 0.6.0, a macOS menu bar app, does not have a Pomodoro timer, a countdown or task estimates, and it does not know where your sessions start and stop. What it does record is which app was in front, for how long, with counts of key presses and clicks, and it keeps that on your Mac. It takes no screenshots, and the only permission it asks for is Accessibility. Window titles and page paths are off until you turn them on in Settings, Privacy. The app reaches the network only when you click, in three places: the checkout page, activating a purchased key, and Check for Updates, and none of them sends activity.
That is enough to test the length of your blocks. In the Trail tab, each hour shows the active time, up to two main projects and, when you switched apps more than once, the number of app switches, with rows for each stretch and the time it ran until. In the Day tab, Deep work counts continuous stretches holding at least 10 minutes of work-category time (Coding, Writing, Design and Meetings are the work categories). Short non-work visits under 5 minutes do not split a stretch, and neither does time away from the keyboard of up to 15 minutes, so a five-minute break can sit inside one block, though the break itself is not counted as work time.
A simple experiment: run timer sessions for a week, then open the Trail at the end of each day and look at the hours where you worked. If your stretches regularly run well past 25 minutes while you ignore the timer, or the Deep work list in the Day tab mostly shows blocks of 45 minutes or more, your natural length is longer. If every hour shows many switches, the Interruptions card in the Week tab names which apps broke into work, and which sites when page paths are turned on, and an interruption there means a break under 5 minutes in the middle of work. Waiting on an AI and coming back does not count. Today's Day tab and Trail stay readable without a licence, while the Week tab needs the trial or a licence.
These numbers show app time, not thought. Reading a long document in a browser, or thinking away from the screen, looks different from typing, and Hina cannot tell a stuck hour from a productive one, so use the records to spot patterns and judge the hour yourself.
Breaks and the sit-too-long reminder
Hina does not run your Pomodoro breaks, so keep a timer for them. What it has is a Sit-too-long reminder, found in Settings, General and on by default: after a long continuous stretch at the keyboard, a small card appears with a line that follows the time of day: in daytime it rotates through Loosen your shoulders, Go refill your water, Take a short walk and Look into the distance, in the evening it reads Step away from the screen, and late at night it is a bedtime reminder. Daytime and evening cards have Later and Take a break buttons, the bedtime card only Got it.
It is not a Pomodoro clock. It appears at most three times a day, stays silent while you are paused, away, locked, on a call or in a full-screen app, and puts no countdown in the menu bar. It also writes nothing to the Daily report. If your timer already gives you breaks, you can turn it off.
Pause recording in the Hina menu keeps time off the clock out of the Trail.
When to drop it
Drop the timer when it adds stress, interrupts work you are already deep in, or your job is mostly responding to other people. Cirillo writes that he is wary of readings of productivity that turn every pause into a problem, and that the goal is a better relationship with time, not more completed Pomodoros.
You can drop the timer and keep the rest. Write down what you plan to do, mark what interrupts you, and look back at the end of the week. That is the part of the method that tells you something you did not already know.
If you want the full system, including the weekly timetable and team practices, the official Pomodoro site and Cirillo's book are the place to learn it. A recording tool like Hina is a different thing: it answers what happened, and only you can decide whether the answer should change your blocks.