Most productivity advice treats focus like water from a tap: open it, work, close it when done. The assumption is that the limiting factor is discipline. If you just sit down and stop procrastinating, the cognitive capacity is there waiting.

It isn’t. Focus is more like a muscle under load. You can push it hard, and for a while it responds. But at some point the output degrades, the errors creep in, and what feels like continued effort is mostly friction. The tap metaphor is wrong, and building your day around it is why you end a long workday feeling wrecked but not particularly productive.

What actually happens when you concentrate

Sustained attention isn’t passive. It draws on glucose, on neurotransmitter availability, on prefrontal resources that take time to replenish. Researchers studying mental fatigue have found that performance on demanding cognitive tasks tends to decline over time, not because people stop trying, but because the underlying substrate gets depleted.

This doesn’t mean you crash after 20 minutes. High-stakes motivation, novelty, and genuine interest can extend effective focus significantly. But the general direction is real: the longer you push without recovery, the shallower the work gets, even when it doesn’t feel that way in the moment. One of the subtler costs of cognitive fatigue is that your ability to evaluate your own output deteriorates alongside the output itself. You stop noticing the drop.

Ultradian rhythms and the rough 90-minute cycle

There’s a body of research, some of it from sleep science, suggesting the brain operates in cycles during the day that loosely mirror the 90-minute cycles of sleep stages at night. These are called ultradian rhythms. Peretz Lavie and others documented performance fluctuations across the day that roughly tracked this periodicity.

It’s worth being honest about what this research does and doesn’t say. The 90-minute figure is an average, not a rule. Individual variation is real. External demands and caffeine and stress all shift things. You can’t look at a clock and say “my ultradian peak ends at exactly 10:30.” What the research does suggest is that attention has natural ebbs and flows across a working day, that these are partly biological rather than just volitional, and that working against them has a cost.

The practical implication isn’t that you should rigidly stop at 90 minutes. It’s that if you’re building a work schedule, building in recovery somewhere in that range is likely smarter than assuming focus is flat across an 8-hour block.

Attention restoration: what actually restores you

Attention restoration theory, developed by Rachel and Stephen Kaplan in the late 1980s, proposes that certain kinds of environments and activities allow directed attention to recover. Natural settings, low-stakes activities that hold interest without demand, space where the mind can wander. These tend to be restorative. Activities that still require directed attention are not.

This is why a phone scroll is not a break. You are redirecting attention, but you’re not releasing it. Social media is deliberately engineered to claim attentional resources: the notifications, the variable reward, the reactive emotional content. Your prefrontal cortex doesn’t get to rest. It’s still making small decisions, still processing, still being pulled. When you pick up your phone between focused work blocks, you’re refueling a depleted battery by running a second device off it.

Genuinely restorative breaks tend to involve at least one of: physical movement, actual rest (eyes closed, lying down), natural light and outdoor exposure, or low-demand social interaction. A short walk outside scores well on most of those. Sitting at your desk refreshing email between tasks scores near zero.

There’s also something to be said for duration. A 5-minute walk probably does something. A 20-minute walk does more. Most people under-recover because they treat breaks as dead time to minimize rather than as part of the work itself.

Designing recovery into the day on purpose

The default is not recovery. The default is that you finish one task, feel briefly untethered, and immediately reach for the next input: another tab, another message, another thing to process. This happens automatically. The path of least resistance is continuous engagement, which turns out to be continuous depletion.

Designing recovery in means making it structural, not optional. A few things that actually work:

Treat the break as a commitment, not a concession. Schedule it the same way you’d schedule a meeting. When the work block ends, the break starts, even if you feel like you’re in flow. Especially then, sometimes, because momentum makes it easy to ignore the fatigue accumulating underneath.

Match the break to what you need. If the work was emotionally intense, social noise isn’t restorative. Quiet is. If the work was sedentary and screen-bound, movement helps more than stillness. Recovery isn’t one-size: what depletes you shapes what restores you.

Protect the transition. The hardest moment is the threshold between work and break. There’s a pull to “just finish this one thing,” which stretches into another thing, and the recovery window closes. Having a hard stop (an alarm, a scheduled block, something external) makes it more likely the break actually happens.

And after the break, re-entry is usually faster than people expect. The anxiety that you’ll lose context or momentum if you stop tends to be unfounded. In practice, a real recovery break often improves the quality of what comes after, and the time cost is smaller than it feels.

How Flow approaches this

Flow is built around the idea that recovery isn’t an interruption to deep work. It’s load-bearing structure. The app schedules your work blocks adaptively and builds in breaks that respond to your energy levels rather than a fixed timer. It doesn’t just tell you to take a break at 25 minutes because that’s what Pomodoro does. It tries to fit the recovery to your actual state.

The Pomodoro technique does get one thing right: it makes recovery structural. But its rigidity is also its limitation. If why Pomodoro often fails is that a fixed timer doesn’t match how human energy actually moves through the day, then the answer isn’t to abandon structure. It’s to make the structure responsive.

If you’re building a work practice where recovery is treated as part of the work, not as lost time you’re trying to minimize, Flow is in early access and you can join the list here. The core bet is simple: better-timed recovery produces better-quality deep work. The research is suggestive, and in practice, that tends to hold up.