Flowtime Technique: Steps, Break Table, and When to Use It

By Suraj Giri, productivity researcher at The Blog Timer. Updated 2026-07-31.

The Flowtime technique replaces Pomodoro’s fixed 25-minute box with a simple rule: pick one task, note the time, and work until your focus breaks on its own. Then take a break sized to how long you actually worked. No alarm cuts you off mid-thought. The clock records what happened instead of dictating it, which is why Flowtime fits deep, absorbing work that fixed intervals keep interrupting at the worst possible moment.

Where Flowtime comes from

The method traces to a 2016 Medium essay titled The Flowtime Technique, written by software engineer Zoë Read-Bivens under the byline Urgent Pigeon. Her complaint about Pomodoro was specific: the timer kept ringing while she was mid-thought, and racing it produced an anxiety she called “PomoStress.” Her fix kept everything useful about Pomodoro — one task at a time, honest records, real breaks — and removed the one part that fought the work: the fixed interval.

The exact steps

1. Pick one task. Flowtime keeps Pomodoro’s single-task rule. Write the task at the top of a log sheet before you start.
2. Record your start time. Open a stopwatch and let it run, or simply note the clock time in your log.
3. Work until your focus naturally breaks. You catch yourself rereading the same sentence, reaching for your phone, or arriving at a clean stopping point. That is the signal to stop — not an alarm.
4. Record the stop time. Stop minus start is your work length for the session.
5. Take a proportional break, using the lookup table below. Time the break with a countdown so it actually ends.
6. Log interruptions. Every time something pulls you off task, add a tally mark. Within a week the log becomes an accurate picture of your real focus span.

The break lookup table

Read-Bivens published rough break guidelines in the original essay, scaled to the work block that preceded them:

The numbers are deliberately loose. Longer focus builds more fatigue and needs more recovery; if you feel wrung out after a 70-minute session, take the 15 rather than the 10. Run the break on a countdown — a 10-minute timer covers the most common case, and a 15-minute timer handles the long sessions — because an untimed break is how a pause becomes an afternoon.

The flow-state research behind it

Flowtime’s core bet is that the mental state psychologist Mihaly Csikszentmihalyi named “flow” is worth protecting at almost any cost. In Flow: The Psychology of Optimal Experience (1990), he described full absorption in a task: time distorts, self-consciousness drops, and the work seems to propel itself. Decades of follow-up research, summarized in Nakamura and Csikszentmihalyi’s The Concept of Flow, identifies the conditions that produce it: clear goals, immediate feedback, and a challenge matched to your skill. Nothing in those conditions mentions 25 minutes. Absorption arrives on its own schedule, and an arbitrary alarm is precisely the kind of external interruption that collapses it.

Breaks still matter, though, and Flowtime does not abolish them. In a 2011 study in Cognition, Ariga and Lleras showed that performance on a sustained-attention task declines steadily over time but that brief breaks preempt the slide, apparently by reactivating the task goal. Flowtime’s answer is to keep the breaks and move them to the natural seams in your attention rather than dropping them on a fixed grid.

Flowtime vs Pomodoro vs 52/17

Pomodoro is the strongest anti-procrastination tool of the three; committing to 25 minutes is easy. The 52/17 rule keeps fixed intervals but stretches them to fit deeper work. Flowtime is the elastic option. For the head-to-head between the two fixed methods, see the 52/17 vs Pomodoro comparison; for running 52/17 through a real workday, the 52/17 implementation guide has schedule templates; and Pomodoro vs Flowtime covers that pairing in more depth.

How to run Flowtime with a stopwatch

The whole apparatus is a running clock and a log sheet with six columns: task, start, stop, work length, break length, interruptions. Start the stopwatch when you begin, glance at it when your focus breaks, write down the elapsed time, and start a break countdown. That is the entire loop.

Treat the first week as data collection rather than performance. Most people discover a surprisingly consistent natural session length — perhaps 40 minutes in the morning and 25 after lunch — and that number is worth more than any borrowed ratio. If you tend to drift without any external structure, run a silent 25-minute timer alongside the stopwatch and treat its alarm as a question (“still focused?”) rather than an order to stop. Keep working if the answer is yes.

When Flowtime beats fixed intervals, and when it doesn’t

Choose Flowtime when the work has a high setup cost — code, proofs, long-form writing, anything where reloading context eats ten minutes — and when your focus span varies too much for one interval to fit. It also suits people who find alarms genuinely jarring; some of us lose more to the interruption than we gain from the rest.

Skip it when you are procrastinating. An open-ended commitment is easy to never start, and Pomodoro’s small fixed box is the better lever on those days. Fragmented admin work, study rotations across subjects, and team-synchronized cycles also favor fixed intervals. The honest summary: Flowtime is as much a measurement instrument as a work method. After two weeks of logs you will know your real focus span, and you can stay elastic or switch to fixed intervals sized to what the log actually shows.