Pomodoro is the technique where you focus on a single task for a fixed time (usually 25 minutes), take a short break, then repeat. After four cycles, you take a longer break.
It’s a strict, timer-driven flavour of time-blocking — and a scaffolding tool for deep work when full uninterrupted blocks aren’t realistic.
That’s the mechanic. The reason it actually works is sneakier: the timer is permission to stop.
When I have six things pulling at me on a Monday morning, the cost of starting any one of them feels enormous. The pomodoro lowers the activation energy — I’m not committing to finishing the PRD, I’m committing to 25 minutes. Quitting is built in, so starting becomes cheap.
How a session goes
- Decide what you’re working on
- Set a timer (25 minutes is the default; adjust to taste)
- Work without switching tasks or chasing distractions
- When it goes off, take a short break — usually 5 minutes
- Repeat. After 4 cycles, a longer break (15-30 minutes) closes the session
When I started, and what it fits
I picked this up about six years ago at ManageEngine, when I realised PMs spend the day juggling context constantly — strategy work, doc reviews, customer calls, design syncs all in the same afternoon. Switching modes between them leaves you fatigued without much to show for it. Pomodoro became the way I carved single-task focus out of a job built to fragment it.
It works best for individual contributor tasks — writing, reviewing, building, thinking. In theory it could work for teamwork too, but it requires every person to commit to the same rhythm, and I’ve never come across a scene where that played out cleanly.
The failure mode: interruptions
The pomodoro breaks the moment someone walks up to your desk or a chat ping pulls you out. Office life is full of these — coworkers dropping by for both work and personal reasons, and there’s no foolproof way to deflect them all.
There are partial defences — Do Not Disturb modes for remote work, busylights at the desk for office work. None foolproof, but they raise the cost of casual interruptions enough that most never start.
Threads I’m still chewing on
- Why 25 specifically? 20 feels too short, 40 feels long. Cirillo named it after his tomato timer — but is there anything principled there? → Why 25 minutes?
- What’s actually happening when focused work alternates with breaks? Ultradian rhythms? Attention residue? → The science behind focus and breaks