The Pomodoro Technique: what if focus only took 25 minutes?
The Pomodoro Technique is Francesco Cirillo's focus method: work on one task for 25 minutes, take a five minute break, and repeat, with a longer break after four rounds. It suits people who work in bursts, struggle to start, or lose whole hours to distraction, and it asks for no equipment beyond a timer. Cirillo named it after the tomato-shaped kitchen timer he used as a student. The shape of the method matters more than the folklore: a start line small enough to cross on a bad day, and a finish line close enough to see from the start.
How do you run a Pomodoro sprint?
- Choose one task to work on.
- Set a timer for 25 minutes and work with zero interruptions.
- When the timer rings, stop and take a 5-minute break away from your screen.
- After four sprints (Pomodoros), take a longer 15-30 minute break.
Why do short sprints beat long intentions?
Starting is the expensive part of focus. A vague intention to work on the report all afternoon offers your brain a large, shapeless commitment, and shapeless commitments are what procrastination feeds on. Twenty-five minutes is a different proposition: short enough that refusing feels silly, long enough that real work happens inside it. The timer also gives distraction a price tag. An interruption no longer costs a moment; it costs the sprint, and that visibility changes how you treat it.
The breaks are half the method. Attention wears down quietly, and the five minute pause resets it before the wear shows. Skip the breaks and you have not made the method more serious, you have removed its suspension.
The timer is a container, not a race.
When does the tomato timer work against you?
The method jars with work that needs long immersion. If you write or code your way into a state where the world disappears, a bell every 25 minutes interrupts exactly the state you were trying to reach, and a longer container like Deep Work will serve you better. It also strains in meeting-heavy jobs where you rarely own 25 unbroken minutes; there, the honest first move is clearing the space, not starting the timer.
And when a sprint ends mid-thought, write the next step down before you stand up. The break is mandatory; losing your thread is not.
The classic mistake: Skipping the breaks or letting interruptions derail a sprint. The breaks are a mandatory part of the technique.
How do you make it stick?
Protect the Sprint
Treat the 25 minutes as an unbreakable appointment with yourself. Defer all interruptions.
Adjust Duration
If 25 minutes feels too long, start with 15. Consistency is more important than duration.
Decide Before You Start
Know exactly what you'll work on during the sprint before the timer starts.
What should you ask yourself after the first week?
- What was the most common internal or external distraction during my sprints?
- How did my energy and focus levels change from the first sprint to the fourth?
- Which tasks fit neatly into one sprint, and which were harder to manage?
Where do you go from here?
If your distractions are mostly self-inflicted inbox checks, Task Batching removes the reason to check. Timeboxing uses the same clock pressure on a single task with a defined finish line, and Deep Work is where you go when 25 minutes starts to feel short. All 17 methods live in the method index.