You’ve probably heard of the Pomodoro Technique. Set a timer for 25 minutes, work until it beeps, take a 5-minute break, repeat.
It works for some people.
But what if you’re finally in the zone, deep into a complex task, and that timer goes off?
You lose your train of thought. You break your momentum. You spend the next work block trying to get back to where you were.
The Flowtime Technique solves this problem.It’s flexible.
It respects your natural rhythm. And it gives you real data about when you do your best work. Here’s how it works
Where Flowtime Came From and Why It Exists
Zoë Read-Bivens created the Flowtime Technique around 2016 as a direct response to Pomodoro’s limitations.
She found that forced 25-minute intervals disrupted her flow state. Once she was deeply focused on a task, stopping felt counterproductive.
The technique builds on Mihaly Csikszentmihalyi’s concept of “flow.” That’s the psychological state where you’re completely immersed in what you’re doing.
Time seems to disappear. The work feels effortless even though you’re producing your best output.
Pomodoro ignores flow. It treats all tasks the same. Twenty-five minutes of data entry gets the same treatment as 25 minutes of strategic planning.
Flowtime adapts to the task and to you.
If you’re writing a complicated report and you’re on a roll, you keep going.
If you’re doing repetitive admin work and your attention starts wandering after 20 minutes, you stop then.
How the Flowtime Technique Actually Works
The mechanics are simple.
Pick a single task. Start a timer or stopwatch. Work with complete focus until you feel genuine mental fatigue or distraction creeping in. Stop. Record how long you worked.
Then take a break.
The break length depends on how long you worked. Different people use different formulas, but a common one is dividing your work time by 5.
Worked for 50 minutes? Take a 10-minute break.
Worked for 90 minutes? Take an 18-minute break.
Some people prefer fixed brackets. Work 25 to 50 minutes, take 5 to 10 minutes. Work 60 to 90 minutes, take 15 to 20 minutes. Work over 90 minutes, take 20 to 30 minutes.
The key is logging everything. Start time, end time, total duration, break length, and what task you worked on.
Over time, these logs show you patterns. You’ll see when your longest focus sessions happen. You’ll notice which types of tasks hold your attention and which ones drain you quickly.
Setting Up Flowtime with Your Remote Team
Start by having each team member choose a single high-impact task at the beginning of each work block.
Examples: drafting an article, building a report, cleaning CRM data, researching competitors.
They start a timer and note the start time.
They work with complete focus on that one task until they genuinely feel their concentration slipping.
They stop, record the end time and total duration, and log which task they completed.
Then they take a proportional break based on the formula you’ve agreed on together.
The agreement part matters. Sit down with your team and decide on break rules together.
Maybe it’s 5 to 10 minutes after 25 to 50 minutes of work, and 15 to 20 minutes after 60 to 90 minutes.
Write it down. Make it clear.
Using Flowtime Data to Improve Team Performance
The real value of Flowtime appears in weekly reviews.
Pull up your team’s time logs. Look for patterns.
Does someone consistently log 75-minute sessions in the morning and 30-minute sessions in the afternoon?
That person is a morning worker. Schedule their most complex tasks before lunch.
Does another team member have scattered 20-minute sessions throughout the day with no long focus blocks?
That might indicate constant interruptions, unclear priorities, or tasks that don’t engage them. Dig into what’s happening.
This kind of analysis requires looking at aggregated data over time.
Common Flowtime Mistakes and How to Avoid Them
The biggest mistake is working too long in a single session.
Some people push for 2 or even 3 hours without a break because they’re afraid to lose momentum.
This leads to mental exhaustion and declining output quality.
Set soft caps. Even if you’re still focused, aim to pause before 120 minutes. Take a real break. Your brain needs it.
Another common issue is vague task definitions. If someone logs “work on blog” for 90 minutes, that doesn’t tell you much. Was it research? Outlining? Writing? Editing?
Require specific task descriptions for each Flowtime block.
For team members managing multiple clients or projects, context switching destroys the benefit of Flowtime.
One person might work for three different clients in a single day. If they’re switching contexts every hour, they never reach deep focus.
The solution is batching. Dedicate entire Flowtime blocks to one client and one project.
Save context switches for transitions between major work blocks, not within them.
Making Flowtime Work for Your Team
Start small. Pick one or two team members who do a lot of deep work.
Have them try Flowtime for two weeks while logging every session.
Review the data together. Look for patterns. Adjust break formulas if needed. Refine task definitions.
Once it’s working, expand to more of your team.
When you get that balance right, people work longer, produce better output, and report higher satisfaction with their workflow.