You've felt it even if you've never named it: a stretch where the work just flows, followed by a wall where the same task suddenly feels like wading through treacle. We usually blame ourselves for the wall — not enough discipline, too much coffee, a bad night. One possible contributor is a shorter-than-daily, or ultradian, fluctuation. But task difficulty, sleep, time of day, food, stress and ordinary fatigue can produce the same feeling. The dip is useful feedback even when its clock is unknown.
What ultradian rhythms are
A circadian rhythm is the roughly 24-hour cycle that governs sleep and wakefulness. An ultradian rhythm is any biological cycle shorter than a day. The one that matters for work traces back to sleep researcher Nathaniel Kleitman, who proposed the Basic Rest-Activity Cycle: through the night we move through sleep stages in cycles often near 90 minutes, and Kleitman suggested that a related oscillation continues during waking hours.
That waking extension remains a hypothesis, not a universal productivity law. Some studies detect ultradian patterns in physiology or arousal; other work finds no clear 1.5-hour rhythm in cognitive performance during daily life. The defensible practical conclusion is smaller: focus is not constant, and planned recovery is useful. Ninety minutes is one interval worth testing—not a cycle your body is guaranteed to follow.
The cost of fighting the trough
Most of us treat the trough as a failure to override. We reach the dip and reach for caffeine, sugar, or sheer willpower to force another hour. It sort of works — and it quietly compounds a debt. Overriding the recovery phase with stimulation means you never actually recover; you just push the fatigue forward, and it accumulates across the day into the fog, irritability and mistakes of late afternoon.
A dip is not automatically a lack of willpower. Treat it as a prompt to check fatigue, task fit and recovery—not proof that a biological timer just expired.
The practical alternative is simple: when performance and comfort clearly fade, pause instead of automatically forcing another hour. A genuine 10–20 minute break may help you return fresher. Measure the result in your own work rather than assuming the next 90 minutes will follow a predetermined wave.
How to spot your own cycle
You don't need a lab — you need a day or two of paying attention. Watch for the signals of the trough, which are the same signals we usually push through:
- Rereading the same sentence or line of code without it going in.
- A sudden urge to check your phone, snack, or "just quickly" do something else.
- Fidgeting, yawning, stiffness, a drop in mood or motivation.
- Simple things feeling disproportionately hard.
Jot down the time whenever you notice these for a couple of days. You'll usually see a pattern, but it may not be stable or 90 minutes long. Use the notes to choose a repeatable work-block length, then revise it when the task, sleep or time of day changes.
Scheduling around the wave
Treating 90 minutes as a hypothesis turns a fuzzy all-day slog into a measurable experiment:
- Choose a test block. Try 60–90 minutes on one demanding task. Shorten it if you repeatedly fade early; extend it only if the quality holds.
- Break when the evidence says stop. When the dip signals cluster, pause for 10–20 minutes and compare the quality of the next block.
- Match the task to the phase. Save the hardest, most creative work for the top of the wave; leave email, admin and other shallow tasks for the recovery phase when deep focus isn't available anyway.
- Protect your best time of day. Identify it from experience instead of assuming everyone peaks in the morning.
If a 90-minute block feels like a lot, that's usually a sign you're used to a fragmented day, not that your cycle is shorter. Start with 60 and extend as you get better at protecting the focus. The rhythm matters more than the exact number — what counts is honoring the peak and the trough instead of steamrolling both.
Break at the trough — automatically
StopBurnout counts active input and applies the work-and-break interval you choose. Start with 60–90 minutes, review how you feel and perform, and adjust the schedule instead of treating any interval as biologically mandatory. Free for 14 days, no account, with work history stored locally.
What to do in the trough
The break only pays off if it actually restores you, which means the trough is the worst time to switch to another screen. Give the recovery phase what it's for:
- Move. A short walk is the classic ultradian break — it shifts your body out of the static work posture and clears the head.
- Get daylight. Stepping outside, even briefly, is a strong reset for alertness.
- Eat or hydrate on cue. The trough often coincides with genuine hunger or thirst. Feed it here instead of fighting it at the desk.
- Let your mind idle. Staring out a window isn't wasted time — it's the default-mode rest that often surfaces the answer you were stuck on.
The deepest shift here is one of self-trust. A dip is not evidence that you're lazy or undisciplined. Stop treating variable attention as a moral failure. Use a repeatable schedule, notice when it helps, and change it when it does not.
What the evidence does—and does not—show
A review of cognition in daily life reported no evidence for a universal 1.5-hour rhythm in cognitive performance. A clinical-neurology review describes basic rest–activity periods as approximately every one to two hours but irregular and stochastic, rather than a precision clock. That supports cautious experimentation with work blocks, not the claim that every brain demands a break at minute 90.
General wellbeing information, not medical advice.