Work in Intervals, Not in Marathons
The Pomodoro technique is a scheduling trick with a simple premise: a fixed block of focused work followed by a fixed break is easier to start than an open-ended session. Twenty-five minutes is short enough that beginning feels cheap, and the break is scheduled rather than earned, so you stop before fatigue forces you to.
The timer above runs those intervals and counts your completed blocks. Nothing needs configuring to start, press the button and work until it rings.
How to Use the Pomodoro Timer
The method matters more than the tool, and most of it is about what you do when the timer is running.
- Decide what the next block is for before you start it. "Draft the introduction" works; "work on the report" tends to dissolve into browsing.
- Start the timer and work on that one thing until it rings. If something else occurs to you, write it down and return to it in the break.
- Stop when the timer rings, even mid-sentence. Stopping at a natural break point sounds better but quietly turns the interval into an open-ended session again.
- Take the short break away from the screen. Standing up, refilling a glass and looking out of a window all work; checking messages does not, because it is the same kind of attention you were just using.
- After four blocks, take the long break, fifteen to thirty minutes. This is the part people skip, and it is the part that makes the afternoon possible.
- Count your completed blocks. Over a week they tell you how much focused time a day actually contains, which is usually less than expected.
Why the Interval Length Matters
Twenty-five minutes is a starting point, not a rule. It is short enough to defeat the reluctance to begin, which is the problem it was designed for. If your work needs a long run-up, writing, debugging, anything where you hold a lot of state in your head, a 25-minute block can end just as you get going, and a 50 or 90-minute block will suit you better.
The break length should scale with the work block, roughly one part break to five parts work. What matters more than the exact ratio is that the break is real: a break spent on a screen restores far less than one spent away from it, which is why the classic advice is to physically leave the desk.
Common Interval Patterns
Four patterns that people actually use, and what each is good for.
| Work | Short break | Long break | Best for |
|---|---|---|---|
| 25 min | 5 min | 15–30 min after 4 | The classic, admin, study, starting when you do not want to |
| 50 min | 10 min | 30 min after 3 | Writing, analysis, work that needs a run-up |
| 90 min | 20 min | after 2 | Deep work, matched to a natural alertness cycle |
| 15 min | 3 min | 15 min after 4 | Low energy, illness, or getting restarted after a long break |
If you cannot make it to the end of a 25-minute block, the interval is not too short, the task is too vaguely defined. Try naming a smaller, more concrete first step rather than shortening the timer further.
Where the Technique Breaks Down
It does not survive contact with a calendar full of meetings, and it is poorly suited to reactive work where interruptions are the job. It also fights against genuine flow: if a block ends while you are deep in something and going well, finishing the thought is the better call. The technique is a tool for starting and for pacing, not a rule to be obeyed at a cost.
The most common failure is treating the counter as a productivity score. Four solid blocks on the right problem beat ten on the wrong one, and inflating the count by starting a timer for work you were doing anyway teaches you nothing about your own capacity.