How to Use the Flowtime Technique (and When to Choose It Over Pomodoro)

The timer rings at the exact moment the paragraph starts to work. You've spent twenty minutes circling the idea, the sentences have finally started landing, and a chime tells you to stop and stretch. You can obey it and lose the thread, or ignore it and feel like you're doing the method wrong. Either way the timer has become the problem it was meant to solve.

Person sitting cross-legged writing in a notebook while flying a kite, illustrating the open-ended work sessions of the Flowtime Technique

The Flowtime Technique is the fix one writer built for that moment. It keeps everything from the Pomodoro Technique except the fixed interval: you still work on one task, still take real breaks, still keep a record, but you decide when a session ends by watching your attention rather than a countdown. This guide covers how the method works, the one experiment that tested it head-to-head against Pomodoro, how to run it with a notebook or a stopwatch, and how to tell which of the two methods your day needs.

What Is the Flowtime Technique

The Flowtime Technique is a time management method in which you choose a single task, note the start time, work until your focus fades, note the stop time, and then take a break whose length depends on how long you worked.

It was described on 17 August 2016 by Zoë Read-Bivens, writing on Medium under the name Urgent Pigeon, as the second part of a short series called "Abandoning Pomodoros." Her complaint was the one in the opening of this article: 25-minute blocks kept cutting her off mid-thought, and her output suffered for it. Rather than throw out the Pomodoro Technique, she kept the parts that were doing the work (one task at a time, breaks you take on purpose, a written log of each session) and removed the alarm. You'll also see the same idea called Flowmodoro, a later name that some timer apps adopted. The description below follows her original post; where we add our own suggestions, we say so.

The word "flow" in the name is a nod to the state of total absorption that psychologist Mihaly Csikszentmihalyi named, and that our deep work guide covers in detail. Flowtime doesn't promise flow. It promises not to interrupt it if it turns up.

Flowtime vs Pomodoro: What Actually Changes

The two methods share more than they differ. Both put one task in front of you at a time, both make breaks part of the plan, and both ask you to record what happened. The difference is who decides when a session ends.

QuestionPomodoroFlowtime
Session lengthFixed, usually 25 minutesOpen; ends when focus fades
Who ends the sessionThe timerYou
Break length5 minutes, longer after fourSized to the session
Timer typeCountdownStopwatch or clock
What you logPomodoros completedStart, stop, breaks, interruptions
Hardest partStopping mid-flowStopping at all
Easiest partStartingStaying in

In Pomodoro, the stop decision is made for you, in advance, by a rule. That is a feature when you don't trust yourself to stop, and a bug when the rule fires at the wrong moment. Flowtime hands the decision back to you and asks for something in return: you have to notice your own attention fading, and you have to act on it. The log is what makes that honest. Without a record of how long you worked and when you broke, "working until focus fades" turns into "working until I'm exhausted," and the method stops being a method.

How to Use the Flowtime Technique

You need a clock, something to write on, and one task. Here is the loop.

  1. Pick one task and write it down. Make it specific enough to have a finish line: "edit section two," not "work on the report." Flowtime has no bell to break up a vague task, so the task itself has to supply the boundary.
  2. Note the start time. On paper, in a spreadsheet, or by starting a stopwatch. This is the whole setup.
  3. Work until your focus fades. Watch for the signals rather than the clock: you've read the same line three times, your hand is drifting toward your phone, your shoulders have crept up, or you've started tidying your desktop instead of the document. The first clear signal is the stop, not the third.
  4. Note the stop time. Write it next to the start. That gives you the session length.
  5. Take a break sized to the session. Use the table below, and set a timer for the break; Read-Bivens did, and it's the one countdown in the method. Get up and away from the screen; a break spent in another tab is a task switch, not a rest.
  6. Log any interruptions. A tally mark for each one, as in Pomodoro. Over a week the marks show you which hours of the day are yours and which belong to other people.
  7. At the end of the day, read the log. Two minutes. Where were the long sessions? What was the task? How did you feel after the breaks? That review is what tunes the method to you.

How Long Should a Flowtime Break Be

Read-Bivens published a short table of break lengths, and it is the part of the method most guides reproduce:

Worked forBreak for
Up to 25 minutes5 minutes
25 to 50 minutes8 minutes
50 to 90 minutes10 minutes
More than 90 minutes15 minutes

She offered these as suggestions, with shorter or longer breaks allowed when you need them. Our advice is to treat them as a floor: if you come back from a 10-minute break after a 90-minute session and your attention is still gone, the break was too short, and the log should say so. The 2025 study described below used three brackets instead of four: 5 minutes after up to 25 minutes of work, 8 after 25 to 50, and 10 after anything longer than 50, with no separate step at 90 minutes. Use that version if you prefer fewer rules; neither table has been tested against the other.

What a Flowtime Log Looks Like

A page of a Flowtime log has six columns and reads like this by mid-afternoon:

TaskStartStopInterruptionsWorkedBreak
Edit section two9:059:52||47 min8 min
Edit section two10:0011:20|80 min10 min
Reply to client11:3011:4818 min5 min
Outline talk13:1013:34||||24 min5 min

That last row is the useful one. Four interruptions in 24 minutes after lunch says more about when to schedule outlining than any productivity article can. If you already keep a short note between tasks, the log slots into it; our guide to interstitial journaling describes the same habit with a sentence of context added to each timestamp.

Does the Flowtime Technique Work? What the Research Says

Flowtime has been tested by name exactly once, as far as we can find, and the surrounding research on breaks is more useful than any single verdict.

The head-to-head test: no winner

In 2025, Eva Smits, Niklas Wenzel and Anique de Bruin at Maastricht University randomised 94 psychology students into three two-hour study sessions: breaks whenever they liked, 25/5 Pomodoros, or Flowtime with the 5/8/10-minute break table. Pomodoro breaks produced a faster rise in fatigue, and both Pomodoro and Flowtime produced a faster drop in motivation than self-chosen breaks. Over the full two hours, though, fatigue and motivation ended up at similar levels, and productivity, task completion and reported flow didn't differ between the groups.

A larger 2026 study leaned the other way

In July 2026, Göksu, Wiradhany and de Bruin gave 176 students a reading task on climate change with either a 3-minute break every 12 minutes or breaks whenever they chose. A comprehension test showed no significant difference between the groups, though the authors note the test may not have been sensitive enough. Students who chose their own breaks reported better mood, more energy, concentration and motivation, and less distraction. This wasn't a test of Flowtime, and 12/3 isn't classic Pomodoro, but it stops the next study from becoming a general rule.

The earlier warning about choosing your own breaks

Two years before, Felicitas Biwer and colleagues at the same university ran a full study day with 87 students, comparing self-chosen breaks with two fixed schedules (24 minutes on, 6 off, and 12 on, 3 off). Students who chose their own breaks worked in longer stretches, and that came with more fatigue and distraction and lower concentration and motivation. Task completion was the same across groups. The self-regulated condition wasn't Flowtime, because it had no break table and no log, but it is the failure mode Flowtime is most exposed to: left alone, people stretch sessions past the point where they're still sharp.

Put the three Maastricht studies together and the summary is short. These short experiments have not established a clear advantage for either fixed or flexible breaks in reported task completion, and the 2025 authors note their sample may have been too small to detect one. How the breaks felt differed by study: choosing your own came with more fatigue and less concentration in 2023, and with better mood and concentration in 2026. Fixed breaks guarantee the rest and sometimes land at the wrong time; flexible breaks risk drifting long. All three lasted a few hours or a day, all used students at one university, and none followed people for weeks. Nobody has shown that either method beats the other on output.

Three findings from the wider research explain where Flowtime's advantages and risks come from.

Breaks restore energy more reliably than they restore output. A 2022 meta-analysis by Patricia Albulescu and colleagues, published in PLOS ONE, pooled 22 samples and 2,335 people and found that micro-breaks of ten minutes or less had small but reliable effects on vigour and fatigue, and no significant effect on overall performance. Two details matter for Flowtime: the longer the break, the larger the effect on performance, and the performance benefit showed up only for less demanding tasks. The authors suggest that recovering from heavy cognitive work may need more than ten minutes. Flowtime's table, which gives longer breaks after longer sessions, is pointing the same way.

Stopping mid-task leaves a residue. Sophie Leroy showed in two 2009 experiments, published in Organizational Behavior and Human Decision Processes, that people who switch away from an unfinished task carry part of their attention with them and perform worse on the next one; she called the carry-over "attention residue." Her experiments were about switching from one task to a different task, not about pausing and coming back to the same work, so they don't show that a Pomodoro break carries this cost or that Flowtime avoids it. The link to Flowtime is our interpretation: stopping at a natural seam leaves less unfinished business to carry into the break. Leroy also found that time pressure helped people disengage, but only when they had completed the first task under it. Read that as a reason to give each session a finishable target ("finish this subsection"), not as proof that any soft deadline makes stopping easier.

The switch itself is the expensive part. Gloria Mark and colleagues at UC Irvine found that when office workers were pulled off a task they later returned to the same day, 25 minutes and 26 seconds passed on average before they got back to it, with about two other pieces of work handled in between. That describes how long a detour runs, not a fixed concentration penalty per interruption, and the study didn't compare long sessions with short ones. Flowtime doesn't protect you from interruptions; a closed door, silenced notifications and a blocker for the sites you drift to each cover part of that. What Flowtime protects is the stretch of work between them.

When to Use Flowtime and When to Stick With Pomodoro

The research hasn't separated the two methods on output, so pick by the problem you have today.

Use Flowtime when getting into the work is the easy part

Writing a draft, debugging, modelling in a spreadsheet, reading a dense paper: tasks where the first fifteen minutes are spent loading context into your head, and an interruption at minute 25 throws it away. This is the work Read-Bivens built the method for.

Use Pomodoro when starting is the hard part

If you've been avoiding the task, a 25-minute commitment is a smaller promise than "work until focus fades," which can feel like signing up for the whole afternoon. The timer also guarantees the break, which Flowtime can't. Our guide on how to stop procrastinating covers why the first minute costs so much more than the rest.

Use Pomodoro when you have a history of grinding

If your Flowtime log shows three-hour sessions and skipped breaks within a week, the method is confirming a habit rather than fixing it. Biwer's self-regulated students are the warning. Go back to fixed breaks for a while.

Combine them: a timed start and a Flowtime finish

The most practical version for many people is a hybrid. Start a 25-minute timer to get over the threshold, and when it ends, don't stop if you're working well. Note the time, keep going, and take a break sized to the whole session when focus fades. You get Pomodoro's low cost of starting and Flowtime's protection of the stretch that follows.

Flowtime also sits comfortably inside time blocking. Block two hours on the calendar for one project, then run Flowtime inside the block: the block decides when the work happens, the log decides when the breaks do.

Flowtime Timers and Tools

Flowtime needs less equipment than Pomodoro, because nothing has to ring while you work; the only countdown in the original method is the one for the break.

Paper and a clock. A notebook page with the six columns above is the original setup and still the best one for noticing patterns, since the whole week is visible at once.

A stopwatch. Your phone's clock app counts up and that's all the timer Flowtime requires; put the phone face down once it's running. Any time tracker that logs sessions against a task does the bookkeeping for you, and our roundup of time tracking software covers the ones worth paying for.

A Pomodoro timer that can keep counting. This is the hybrid from the previous section in one tool. When a session on our Yellow Tomato Chrome extension ends, you can let it keep counting, up to four times the session length, and your blocklist stays on until you take the break. The web Pomodoro timer on this site runs fixed sessions only, so it suits the timed start but not the Flowtime finish. To compare other browser timers, see our Pomodoro Chrome extensions roundup.

A blocker. Whatever timer you use, the long sessions Flowtime protects are the ones a single notification can cost you. A website blocker that stays on until you say otherwise pairs well with a method that has no bell.

Common Flowtime Mistakes

Try Flowtime for One Week

Draw the six columns on a page and add a seventh for a few words on what you finished and how you felt after the break. Tomorrow morning, write down one task and the time, and work until the first clear sign your attention is slipping. Write the time again, take the break the table gives you, and repeat. Do that for five working days without changing anything else. On Friday, read the page and ask three questions. Did you finish what you set out to do in each session, compared with how that kind of task usually goes? Did the breaks leave you recovered? Were starting and stopping manageable? Three yeses mean Flowtime fits you, whether the sessions ran 20 minutes or 80. If the breaks disappeared by Wednesday, or the log shows long sessions with little finished, you've learned something just as useful, and a timer that rings is the right tool for now. If you're studying, end each session with a two-minute recall check so the "finished" column means something.

Frequently Asked Questions

What is the Flowtime Technique?

The Flowtime Technique is a time management method in which you pick one task, note the time, work until your focus fades, note the time again, and take a break sized to how long you worked. It keeps the Pomodoro Technique's single-tasking, breaks and record-keeping but drops the fixed 25-minute interval. Zoë Read-Bivens described it in 2016 after finding that Pomodoro's bell kept interrupting her mid-thought.

Flowtime vs Pomodoro: which is better?

Neither has been shown to produce more finished work. The one study that compared them directly, with 94 students over two hours, found no significant difference in self-rated productivity, task completion or flow, and its authors note the sample may have been too small to detect one. Pomodoro is better at getting you started and guaranteeing breaks; Flowtime is better at protecting a long stretch of concentration once you have it. Which is "better" is a question of fit, and many people use a timer to start and Flowtime to finish.

How long should a Flowtime break be?

Size the break to the session: about 5 minutes after up to 25 minutes of work, 8 minutes after 25 to 50, 10 minutes after 50 to 90, and 15 minutes after anything longer. Those are the guidelines the technique's creator published, and they are a starting point. If you come back still tired, take longer next time and note it in the log.

Is Flowtime the same as Flowmodoro?

Mostly. Flowmodoro is a later name for the same idea, work until focus fades and then break in proportion, and some apps that use the name fix the ratio at one minute of break for every five minutes of work. Flowtime, as originally described, uses a short table of break lengths instead of a ratio. In practice the two produce similar breaks for sessions under an hour.

Is there a Flowtime timer?

Any stopwatch works, because Flowtime counts up rather than down, and a notebook or spreadsheet does the logging. Several small apps now call themselves Flowtime or Flowmodoro timers. A Pomodoro timer that can keep counting past the end of a session, as the Yellow Tomato Chrome extension can, gives you a timed start with a Flowtime finish and keeps your blocklist on throughout.

Does the Flowtime Technique work for studying?

It can, and the research on choosing your own breaks is mixed. In a 2023 Maastricht study, students who chose their own breaks drifted into longer sessions and reported more fatigue and less concentration than students on fixed breaks; a larger 2026 study from the same group found better mood and concentration with self-chosen breaks and no difference on a comprehension test. If you use Flowtime to study, keep the log honest, stop at the first clear sign of fading focus, and take the break the table prescribes. For exam revision in particular, pair it with a method that has a visible output, such as active recall, so a long session produces something you can check.

You may also like