The Pomodoro Technique: 25 Minutes at a Time

The Pomodoro Technique: 25 Minutes at a Time

At 10:47 on a Tuesday you have four tabs open, a half-written email, and no memory of the decision you were about to make. The problem is not discipline. It is that “work on the project” has no edges.

Why 25 minutes works

A pomodoro is a bounded promise: one task, 25 minutes, then stop. The length is short enough that starting feels cheap and long enough to get past the first messy minutes. The break is not a reward; it is what keeps the next block from degrading.

The classic cycle is four blocks of 25 minutes with 5-minute breaks, then a longer break of 15 to 30 minutes.

Run one block

The stopwatch and timer has both modes you need, and runs in the browser tab.

  1. Pick one task with a finish line — “draft the intro,” not “write the report.”
  2. Open the Timer tab, set 0 hours, 25 minutes, 0 seconds, and start.
  3. Work only on that task. When a stray thought arrives, write it on paper and return.
  4. At the alarm, stop mid-sentence if you have to. The point is the boundary.
  5. Take 5 minutes away from the screen. Walk, stretch, refill water.
  6. After four blocks, take 15 to 30 minutes.

The countdown is based on wall-clock time, not interval ticks, so a throttled background tab does not make it drift. The completion alarm plays a hosted sound and shows a browser alert; the alert fires even if the sound cannot load. Keep the tab open — closing it cancels the timer.

When 25 is wrong

Writing and coding often need longer to reach depth. Try 50/10. Low-focus chores can take 15/3. The number is a default, not a doctrine.

Use the Stopwatch tab with Lap if you prefer counting up: lap at the end of each focus block and you get a record of actual lengths, including the ones that ran long.

Track blocks, not hours

Put a tally mark on paper for each completed block. Four honest blocks beat eight fragmented hours, and the tally makes the difference visible.

If a block ends and you cannot name what you finished, the task was too vague — split it before starting the next one.