Guide
The Pomodoro technique works best for tasks you keep putting off, shallow admin and days when starting is the hard part. It works less well for deep work with a long warm-up, where the bell can break your concentration. A kitchen timer and paper are enough to run it. Dayflow, a free Mac app, is useful for seeing what happened between rounds and on days you never set the timer.
You set the timer for 25 minutes, open the document, and something feels wrong almost at once. Either the task is so dull that 25 minutes feels like an hour, or you finally get going and the bell rings at minute 22, just as the paragraph starts to make sense. You take the five-minute break because the method says to, pick up your phone, and the next round never quite starts.
Or it goes the other way. For a week it works beautifully. You clear the inbox, finish the expense report and write the email you’d been dodging. Then it quietly stops working, and you can’t tell whether you stopped using it or it stopped helping.
This guide covers what the Pomodoro technique is, why it helps with some kinds of work and gets in the way of others, and seven adjustments to try. Most of them need nothing more than a kitchen timer and a sheet of paper. A note up front: this guide is published by Dayflow, a Mac app we make. It comes up once, near the end.
The classic version is simple. You pick one task, set a timer for 25 minutes and work only on that task until it rings. Then you take a 5-minute break. After four rounds you take a longer break, roughly 15 to 30 minutes. The name comes from a tomato-shaped kitchen timer, and the whole thing was designed to run on that one object.
Several things make it helpful when it works:
It makes starting smaller. “Write the report” is vague and heavy. “Work on the report until the timer rings” is something you can agree to. Many people find the hardest part of a task is the first few minutes, and a short, fixed commitment takes some of the weight off that moment.
It makes time visible. A ticking timer, or even a number counting down, turns an open afternoon into pieces you can see. That alone keeps some people from drifting.
It decides when you stop. Without a stopping point, it’s easy to grind past the point where you’re doing anything useful, or to never really start because the session has no end. The bell takes that decision off your plate.
It goes wrong in some predictable ways, too:
Some work needs a long warm-up. Writing, design and debugging often take 15 or 20 minutes before the problem is fully loaded in your head. A bell at 25 can interrupt you just as the useful part begins.
The break becomes a doorway. Five minutes with a phone can turn into thirty. The break was supposed to rest you, and instead it pulls you out of the work.
It turns into a scoreboard. Counting rounds is satisfying, and before long the count becomes the goal. You can log eight rounds in a day and still not touch the one task that mattered.
Your day doesn’t have room. If meetings break your calendar into 20-minute gaps, a 25-minute method has nowhere to go, and missing rounds can feel like failure when it’s really just arithmetic.
None of this means the method is broken or that you are. It’s a tool with a particular shape, and the job is to bend it toward the work you actually do.
Before you adjust anything, try the original for a few days so you know what you’re changing. Use a physical timer if you have one. Winding a dial and hearing it tick is part of the design, and it keeps your phone out of your hand.
What to do: pick one task, set 25 minutes, work, take 5 minutes, and repeat four times before a longer break. Don’t change anything yet. At the end of each round, jot a word or two on paper about how it went: “good”, “slow start”, “bell interrupted me”, “drifted”.
Illustration: Someone sits down on a Monday with a stack of unanswered email and a half-written proposal. They do two rounds on email, which go well, and two on the proposal. Both of those end with “bell interrupted me”. That’s already useful information.
How to tell after a week: read back your one-word notes. If most say “good” for a certain kind of task, keep using the method there. If the same complaint shows up again and again, that complaint tells you which of the adjustments below to try first.
It often is, and changing it is allowed. The round length should fit the task, not the other way around.
What to do: sort your tasks into two groups. For tasks you dread or keep postponing, shorten the round to 10 or 15 minutes, because the point is to make starting almost too easy to refuse. For tasks that need a warm-up, lengthen the round to 45 or 50 minutes and the break to 10. Keep the four-round rhythm if you like it, or drop it.
Illustration: A person who has avoided a tax form for three weeks sets a 10-minute timer and promises only to find the right folder. They find it, keep going and fill in half the form. Later the same day they set 50 minutes for a design task, where 25 had kept cutting them off.
How to tell after a week: you should see fewer “slow start” notes on dreaded tasks and fewer “bell interrupted me” notes on deep ones. If short rounds still feel impossible to begin, the problem may be how the task is defined rather than how long the round is, which is what the next step is for.
A timer tells you how long. It doesn’t tell you what. A vague round (“work on the proposal”) is easy to fill with rereading and tidying. A specific one is easier to start and easier to judge.
What to do: on paper, before you start the timer, write one line describing what “done” looks like for this round. Keep it small and concrete. “Draft the pricing section, rough is fine.” “Reply to the three emails flagged yesterday.” When the bell rings, put a check or a cross next to the line. A simple running log works well for this, and the daily work log template is a ready-made page for it.
Illustration: Instead of “study chapter 4”, a student writes “make flashcards for the six terms in section 4.2”. The round has an edge, so the student knows when it’s over and whether it went well.
How to tell after a week: count your checks and crosses. A steady stream of crosses usually means your lines are too big. Halve them. A page full of checks on tasks that don’t matter means the planning, not the timer, needs attention.
The break is where many people lose the method. The fix is to make the break physical and to give it its own boundary.
What to do: during the 5 minutes, get up and do something that rests your eyes and attention. Refill water, stretch, look out a window, wash a mug, walk to another room. Leave the phone face down on the desk or in another room. If breaks keep stretching, set the timer for the break too, so something rings when it’s time to come back.
Illustration: Someone notices their “five minutes” always becomes twenty because the break starts with checking messages. They switch to a rule: the break happens away from both screens, and messages get their own scheduled round twice a day.
How to tell after a week: note on your tally whether each break ended on time. If most do and the next round starts more easily, keep the rule. If you come back from breaks more scattered than you left, try even shorter breaks, or a different kind, like a short walk instead of standing at the counter.
The timer exists to get you started and to stop you grinding past the point where you’re useful. It isn’t meant to cut off good work. When you’re truly absorbed, the bell can be the least useful thing in the room.
What to do: when the timer rings and you’re in the middle of something that’s going well, don’t just ignore it. Write a short parking note: where you are, what the next step is, any thought you don’t want to lose. Then decide. Keep going if it’s good. Stop if you’re tired or if something else is due. If you keep going, take a real break when the stretch ends naturally, because skipping every break tends to catch up with people later in the day.
Illustration: A developer’s bell rings while they’re tracing a bug through three files. They write “bug is in the date parse, next check timezone handling in utils”, keep going for another 20 minutes, fix it, then take a proper 15-minute walk.
How to tell after a week: look at whether those extended stretches produced finished work and whether the rest of the day held up after them. If long runs leave you wiped out by mid-afternoon, put a ceiling on them, say one extension per round.
Pomodoro counts are a surprisingly good measuring stick. They’re coarse enough to be easy and specific enough to show a pattern.
What to do: before a task, write how many rounds you think it will take. Afterward, write how many it actually took. Do this for every task you use rounds for during one week. Don’t try to correct your guesses yet. Just collect them.
Illustration: Over five days someone guesses “2 rounds” for a weekly report, a client follow-up and a slide deck, and they actually take 4, 3 and 6. The habit becomes clear: their first guess is consistently low on anything with a deliverable.
How to tell after a week: compare the two columns. Most people find their guesses miss in a consistent direction, and once you know that, you can plan around it. If you’d like to see how your sense of time lines up with a clock, the time estimation test is a short exercise for that. It isn’t a diagnostic. There’s also a longer explanation of why people underestimate how long things take.
Sometimes the timer isn’t enough on its own, and what helps is someone else working at the same time. This is often called body doubling, and it pairs naturally with Pomodoro rounds.
What to do: ask a friend, colleague or housemate to work alongside you, in person or on a video call with microphones muted. At the start, each of you says your one-line goal out loud. Run the same timer. At each break, take 30 seconds each to say how it went, then go again. There’s a fuller guide to what body doubling is and how to try it.
Illustration: Two friends who both work from home set a recurring 9:30 call on Tuesdays and Thursdays. Each morning they run three rounds together. They chat only during breaks, and both report that the first round is the one they would otherwise have skipped.
How to tell after a week: compare days with a partner to days without. If partner days get started earlier and more consistently, it’s worth protecting those sessions in your calendar. If you find yourself chatting through the rounds, add a rule that talk waits for the break.
A Pomodoro tally shows you the rounds you ran. It doesn’t show what happened between them, or on the days you never set the timer, and those are often the days you’d most like to understand. Reconstructing them from memory at 6 p.m. rarely works. If you want a fuller picture of where your day actually went, it helps to have a record you didn’t have to remember to make.
Dayflow is a free, open-source Mac app that records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. There’s no timer to start, so the record exists even on days the method fell apart. You can set the timeline next to your paper tally and see whether a “lost” afternoon was meetings, a rabbit hole, or real work you never counted.
The details below come from Dayflow’s own documentation for version 2.2.0, reviewed 2026-09-06. It runs on macOS 14 or later and is MIT licensed at $0, with an optional Pro plan at $20 a month (pricing). Recordings and the timeline are stored on your Mac. Analysis can run on local AI through Ollama or LM Studio, which keeps screenshots on-device. It can also run through your own cloud provider or through Dayflow Pro, both of which process selected screenshots off-device (how local and cloud processing differ). You can export a date range as Markdown. AI summaries can miss or misread work, so check them before you rely on them.
Dayflow publishes this article, so weigh that accordingly.
Be clear about what it doesn’t do.
It isn’t a Pomodoro timer. Dayflow doesn’t run rounds, ring a bell or remind you to take a break. If the timer is what you need, a plain kitchen timer wins. It’s simpler, it works away from your desk, and it keeps your phone out of the loop.
It doesn’t block anything. Dayflow has no website blocking. If distraction during rounds is the main problem, you’ll need a different kind of tool, or the low-tech version: phone in another room, one browser tab open.
It only sees your Mac screen. Reading on paper, sketching, calls on your phone and thinking on a walk don’t appear in the record. If a lot of your focused work happens away from the computer, a paper tally like the one in step 6 will tell you more.
It’s Mac only. It needs macOS 14 or later. If you work mainly on Windows, Linux or an iPad, it won’t run there.
It’s a record, not a coach. It won’t tell you which tasks to do, start your rounds for you, or make a hard task easier to begin. Steps 2, 3 and 7 above do more for starting than any record of what happened afterward.
It doesn’t do billing or team reporting. There are no invoices, payroll approvals or team reports. If you need those, look at the broader list of Mac time trackers instead.
You may not want screen recording at all. That’s a reasonable choice. A notebook and a timer give you most of what this guide describes.
The Pomodoro technique is a starting tool more than a working tool. It works best when the hard part is beginning: the dreaded form, the email you keep postponing, the afternoon that has no shape. It tends to get in the way when the work needs a long warm-up, when the break turns into a phone session, or when counting rounds replaces finishing things.
Try the classic version for a few days so you know what you’re adjusting. Then change the round length to fit the task, write one line before each round, make breaks physical, and let real flow run on purpose. Keep a paper tally for a week and judge the method by what moved, not by how many rounds you logged. If it helps with some kinds of work and not others, that’s a perfectly good result. Use it where it helps and drop it where it doesn’t.
You pick one task, set a timer for 25 minutes and work only on that task until it rings. Then you take a 5-minute break. After four rounds you take a longer break of roughly 15 to 30 minutes. The name comes from a tomato-shaped kitchen timer. The method keeps each commitment short and builds rest into the day, so you don't have to decide when to stop.
It depends on the work and the person. Many people find it very helpful for tasks they dread, because committing to 25 minutes feels manageable. It tends to help less with work that takes a long time to get into, such as writing or debugging, where a bell at minute 25 can break your concentration. Run it for a week on different kinds of work and keep it where it helps.
Twenty-five minutes is the classic length, not a rule. For a task you badly want to avoid, 10 or 15 minutes may be easier to start. For focused work that needs a warm-up, 45 or 50 minutes with a 10-minute break often fits better. Try one length for a few days, write down how each round went, and adjust from what you actually see.
You can keep going. The timer exists to get you started and to stop you grinding past the point of usefulness. It isn't there to interrupt good work. One option is to let the bell ring, write a one-line note about where you are, and decide on purpose whether to continue. If you continue, take a proper break when the stretch ends naturally.
Do something that rests the part of you that was working. Stand up, refill your water, look out a window, stretch or walk to another room. Checking messages or scrolling usually keeps your attention busy and can stretch a 5-minute break into 30. If the break keeps escaping you, set a second timer for it and leave your phone in another room.
Only partly. Rounds don't fit neatly between calls, and forcing them can make a fragmented day feel worse. On those days, use rounds only in the gaps of 30 minutes or more, and plan small tasks for them. Count meetings as their own block on paper so you aren't judging yourself for missing rounds that never had room to happen.
No. Dayflow doesn't run Pomodoro rounds, ring a bell or block websites. If the timer itself is what you need, a plain kitchen timer beats Dayflow. It's simpler, it works away from the computer and it costs nothing to try. Dayflow is a record of what was on your Mac screen. It's useful for reviewing your day afterward, not for structuring it while it happens.
Keep a simple tally for a week. Note each round you start, each one you finish, and what you were working on. At the end of the week, check whether the tasks you used rounds for actually moved, and whether starting felt easier. If you're finishing rounds but nothing important is getting done, the method is running but not helping, and it's time to adjust it.
It can be. Before you start, guess how many rounds a task will take. Afterward, write down how many it really took. After a week of guesses and real counts, you'll see whether you tend to guess low or high, and by roughly how much. That pattern is more useful than any single estimate, and you only need paper to track it.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required