What Is the Pomodoro Technique and How Do You Use It?

The Pomodoro Technique is a time-management method that breaks work into 25-minute focused intervals separated by 5-minute breaks. Francesco Cirillo created it in the late 1980s and named it after the tomato-shaped kitchen timer he used as a university student. You pick one task, set a timer for 25 minutes, work until it rings, then rest. After four rounds, you take a longer 15-to-30-minute break.

What Is the Pomodoro Technique?

The Pomodoro Technique is a focus method that splits work into fixed 25-minute sprints, each followed by a short break. Francesco Cirillo, an Italian developer, invented it as a student in the late 1980s and documents the full method on Cirillo's official Pomodoro Technique page.

"Pomodoro" is Italian for tomato, and the name comes from the kitchen timer Cirillo used. One pomodoro equals 25 minutes of work plus a 5-minute break. The unit is the whole point: you stop measuring your day in vague hours and start counting completed focus blocks.

The technique rests on one strict rule. A pomodoro is indivisible. If you break it to check Slack or answer a text, that pomodoro does not count, and you start a fresh one. This constraint is what makes the method work instead of becoming a loose suggestion.

How Do You Actually Run a Pomodoro?

You run a pomodoro in five steps, and the whole loop takes about 30 minutes. The method is deliberately simple so there is nothing to configure and no excuse to skip it.

You might also like

How Much Does Project Management Software Cost?

Should I Raise Money for My Startup? An Honest Answer

How to Organize Business Tasks Effectively: A Real Playbook

How to Communicate With a Different Personality Type

1. Pick one task. Write it down. One task per pomodoro, no bundling.
2. Set a timer for 25 minutes. Any timer works; the ticking is optional but many people like it.
3. Work until the timer rings. No email, no phone, no context-switching. If a distraction hits, note it and keep going.
4. Take a 5-minute break. Stand up, drink water, look away from the screen. Do not start new work.
5. After four pomodoros, take a longer break of 15 to 30 minutes to reset attention.

A few rules keep the system honest:

• One task cannot be paused mid-pomodoro; protect the 25 minutes.
• If a task takes more than 5-7 pomodoros, break it into smaller tasks.
• If a task takes less than one pomodoro, batch it with other small tasks.
• Log each completed pomodoro so you can see your real capacity.

Why Do 25-Minute Blocks Work for Founders?

Twenty-five minutes works because it is short enough to start and long enough to make progress. The bigger reason is the cost of interruption: refocusing after a break is expensive, so a method that walls off distraction pays for itself fast.

Research from Gloria Mark at UC Irvine found it takes an average of about 23 minutes to fully return to a task after an interruption. Her work on attention and multitasking is summarized on Gloria Mark's UC Irvine faculty page. If a single Slack ping costs you that much recovery time, a rule that forbids pings during a pomodoro is not rigid; it is math.

The technique also fights two founder-specific problems. First, it makes work countable, so you can plan a day in units instead of guessing. Second, the break structure reduces the burnout of grinding for hours without pause. This is the same principle behind Cal Newport's argument for protected focus in Cal Newport's writing on deep work, just packaged into a timer any solo operator can run today.

How We Ship Software in Pomodoros at Botensten

We build production software with AI every day, and pomodoros are how we keep AI-assisted work from turning into an endless tab-switching haze. When you code with an AI agent, the temptation is to babysit it, refresh five things, and lose the thread. A 25-minute block forces one scoped task: write the migration, or review the diff, not both while also reading email.

Here is the honest trade-off we hit. Deep architecture work does not fit in 25 minutes, and forcing it there broke our flow. So we split our day: pomodoros for shippable, well-defined units, like fixing a bug or writing a route, and longer 90-minute blocks for design work where interruption is worse than the timer.

What actually changed our output was logging. We started writing down completed pomodoros next to what shipped, and the ledger exposed how few truly focused units a "busy" day contained. Some days it was four. Naming that number is uncomfortable, and it is also the fastest way to reclaim time you did not know you were losing.

Which Timer and Tools Should You Use?

Any timer that counts down 25 minutes works, and you should not spend money before you have run the technique for a week. The method matters more than the app. Below is how the common options compare.

Start with what you already own. A physical timer has one advantage worth naming: your phone stays out of reach, which removes the biggest interruption before you begin.

What Should You Do When a Pomodoro Gets Interrupted?

When a pomodoro is interrupted, Cirillo's rule is to distinguish internal from external interruptions and protect the block either way. If the distraction is internal, like remembering an errand, write it on a list and keep working. If it is external, like a colleague, use a quick strategy: inform them you are busy, negotiate a time, and call back when the pomodoro ends.

If the interruption is unavoidable and you truly stop, that pomodoro is void. You do not get partial credit. Start a new one when you resume. This sounds harsh, but the all-or-nothing scoring is exactly what trains you and the people around you to respect the block.

Related reading

• How to Organize Business Tasks Effectively: A Real Playbook
• How to Reduce Meetings at Work: an Operator's Playbook