How to Use the Pomodoro Technique: 25-Minute Focus Sessions That Actually Stick

The Pomodoro Technique is 25 minutes of focused work, a 5-minute break, repeated four times, with a longer 20-30 minute break after the fourth round. That's the whole rule. The reason it works isn't the tomato or the bell — it's that a 25-minute commitment is small enough to actually start, and the structured breaks keep you from burning out before lunch.

Francesco Cirillo invented it in the late 1980s with a tomato-shaped kitchen timer while studying at university. It's been studied in peer-reviewed research ever since. Below is how to run one, the problems most people hit in the first week, and when to skip the technique entirely.

Quick answer

One pomodoro is a 25-minute timer plus one task. When the bell rings, you stop and take a 5-minute break. After four pomodoros, you take a longer break of about 20 to 30 minutes. Repeat for as much of the day as the work needs.

The technique is older than most productivity apps, and Cirillo's official Pomodoro Technique site still recommends starting with two or three pomodoros a day rather than eight. The habit matters more than the volume.

Step-by-step: running your first pomodoro session

Pick one task before you start the timer

Most people start the timer first and figure out what to do during the first three minutes. Don't. Write the task down. Cirillo's full method uses three sheets — an Activity Inventory for everything you might do, a To-Do Today list for what you're committing to, and a Records sheet for what you actually finished. The sheets aren't required to start, but a specific task is.

Set the timer to 25 minutes and start

The act of starting matters. Cirillo used a wind-up tomato timer because the physical wind was part of the commitment. A phone timer works just as well — what matters is that pressing start is a decision, not a reflex. Move your phone to another room. Turn off notifications. Close the email tab.

Work until the bell — no exceptions

A pomodoro is indivisible. If someone interrupts you in the middle, you have two choices: write the interruption down and return to it after the break, or abandon the pomodoro and start a new one. You don't pause the timer and resume. The fixed 25-minute structure is what gives the technique its shape.

Take a 5-minute break, then start the next one

After four pomodoros — about two hours of focused work — you take a longer break of 20 to 30 minutes. Eat. Walk. Do something away from a screen. The longer break is part of the method, not optional.

Record what you finished

This is the part most people skip and most people regret skipping. At the end of the day, write down how many pomodoros you completed and what you got done. Over a week or two, you start to learn how long things actually take — three pomodoros to write a client proposal, two for the weekly invoice run, six for a real coding feature. That data is what makes next week's plan honest.

Common problems and fixes

"25 minutes is too short for me"

For deep coding, long writing, or design work, 25 minutes can feel like the bell rings right as you've warmed up. Cal Newport, who wrote Deep Work, recommends 50-minute chunks with 10-minute breaks for serious focused work. Other practitioners on Indie Hackers report using a 52/17 split — 52 minutes of work, 17 minutes off. The 25/5 cadence is a starting point. Pick a ratio that fits your work and keep the structure intact: fixed work window, fixed break window, no negotiating in the middle.

"The bell breaks my flow"

If you're already deep in flow, stopping for a forced break can feel worse than useful. Use the technique selectively. Pomodoros are best for getting started on tasks you'd otherwise procrastinate on — not for protecting a flow state you're already in.

"I keep burning through my breaks"

A 5-minute break that turns into 20 minutes of social media isn't a break. It's a context switch. Newport calls the alternative a deep break — short, intentional time away from work that doesn't pull your attention into something else demanding. A walk to the kitchen for water. A few minutes of staring out the window. Daydreaming about how the work will turn out. What to avoid: email, Slack, your inbox, a related-but-different work task. Each of those leaves a residue that makes restarting harder.

"Clients keep interrupting me"

The original method has a four-step pattern for interruptions: inform the other person you're in a focused session, negotiate a time to come back to it, schedule that time, and call back. For freelancers and indie hackers, this is mostly a Slack and email problem. Block notifications during the work block, batch your replies into one of the breaks, and tell clients up front when you're reachable.

"It feels like overkill for some tasks"

It is. Don't run a pomodoro for a five-minute task. The technique is for work you'd otherwise stretch out, procrastinate on, or do half-attentively while checking your phone.

Doing this with Pomlo

The Pomodoro Technique is a habit, and habits last when the tool you use is already on your phone.

Pomlo treats focus sessions as first-class time entries. Start a 25-minute focus session attached to a specific project or client, and when the bell rings, you have a clean, billable record instead of a vague estimate. Three things matter here. Focus sessions log the work you actually concentrated on rather than just total hours at the desk. Time tracking turns each pomodoro into a tidy entry you can invoice without rounding guesswork. Reports show how many focused sessions you completed this week versus how much shallow work crept in. Pomlo runs on iOS, Android, and the web, so the timer is wherever your work is.

Download Pomlo on the App Store or Google Play to start your first pomodoro today.

Frequently asked questions

How long is one pomodoro?

A standard pomodoro is 25 minutes of focused work followed by a 5-minute break. Every fourth pomodoro is followed by a longer 20-30 minute break.

What if I get interrupted during a pomodoro?

A pomodoro is meant to be indivisible. The original method says you either record the interruption and come back to it later, or you abandon the pomodoro and start a new one. Don't pause the timer and resume — the fixed structure is what makes the technique work.

Can I make pomodoros longer than 25 minutes?

Yes. Many people doing deep coding, writing, or design work use a 50/10 or 52/17 ratio instead. The 25/5 cadence is a starting point; the underlying idea is a fixed work window followed by a fixed break.

Does the Pomodoro Technique actually work?

Peer-reviewed evidence suggests yes for focus-heavy work. A 2023 study in the British Journal of Educational Psychology and a 2025 meta-analysis both found structured Pomodoro breaks produced lower fatigue and better sustained performance than self-regulated breaks.

When should I skip the Pomodoro Technique?

Skip it for tasks that need uninterrupted flow longer than the bell allows, or for short tasks that don't need 25 minutes. Use it for tasks you tend to procrastinate on, repetitive work, or anything where starting is the hardest part.

Where to go next

Start with two pomodoros tomorrow. One task each, timer on, phone in another room. At the end of the day, write down what you finished. That's the technique — and after a week of doing it, you'll have a more honest picture of how long your work actually takes than most productivity advice will ever give you.

For more on focus and how to run an honest week as a freelancer or indie hacker, read more articles on the Pomlo blog.