Quick answer: This guide looks back at August 24–30, 2026—ISO week 35. A 90-20 focus cycle pairs 90 minutes of focused work with a 20-minute break, but it is a scheduling experiment, not a scientifically established prescription for every brain. Use it for substantial tasks, protect the break, and shorten the session when your work or energy calls for it.
The week 35 question: how long should focused work last?
The question behind this retrospective is practical: when does a longer work session help, and when does it become an excuse to push through fatigue?
The supplied reading list put biological rhythms alongside familiar productivity advice. Asian Efficiency’s ultradian-rhythm guide describes work periods of 60–90 minutes followed by breaks of 20–30 minutes. Lateral Action’s article similarly connects ultradian rhythms with productivity. These provide context for the appeal of longer focus blocks—not proof that one timer setting suits everyone.
A dating caveat matters for this retrospective: the supplied list contains an October 7 date for Welltory and an August 9 date for loggd.life. Those do not establish publication during August 24–30. This guide therefore treats the reading list as thematic context rather than a verified record of articles published that week.
The useful takeaway is not “your brain requires exactly 90 minutes.” It is that demanding work deserves protected time, and recovery deserves a place on the calendar too.
What ultradian rhythms do—and do not—tell us
An ultradian rhythm is a biological cycle that repeats within a day. The term describes a category of rhythms, not a single universal productivity clock.
Sleep offers a familiar example. The National Institute of Neurological Disorders and Stroke’s guide to sleep explains how people cycle through non-REM and REM sleep. That establishes cycling during sleep; it does not, by itself, establish that everyone should work for 90 minutes while awake.
Separate the biological idea from the scheduling technique
Three different claims often get bundled together:
- Biology: bodily processes can fluctuate on timescales shorter than a day.
- Personal experience: attention and energy can feel uneven across a working day.
- Scheduling advice: work for 90 minutes, then rest for 20.
The first does not automatically prove the third. A work schedule also has to accommodate task difficulty, sleep, interruptions, meetings, and individual preferences.
For practical ultradian rhythm work, treat 90-20 as a repeatable structure you can evaluate. You do not need to believe that a timer detects your biological state. It simply gives a task a boundary and makes the next break explicit.
A timer is not a reason to ignore discomfort
Ninety minutes is a planned session length, not an instruction to remain motionless or stare continuously at a screen. Stand, change position, or briefly look away when needed. If you feel unwell or your concentration has clearly deteriorated, stop rather than waiting for permission from the timer.
When 90-20 fits—and when a shorter cycle is better
Long sessions are most useful when the task takes time to enter: understanding a codebase, developing an argument, analyzing material, or solving a multi-step problem. They are less convenient when your role requires frequent responses or your day is already fragmented.
| Work structure | Useful starting situation | Main trade-off | Sensible adjustment |
|---|---|---|---|
| 25 minutes work / 5 minutes break | Starting a difficult task or working in a short gap | The break may arrive before a complex task feels settled | Group related tasks into successive sessions |
| 52 minutes work / 17 minutes break | A substantial task with limited calendar space | Less uninterrupted time than a 90-minute block | Choose a smaller deliverable |
| 90 minutes work / 20 minutes break | Writing, coding, studying, or analysis that benefits from continuity | Requires a protected 110-minute window | Begin with one cycle rather than filling the day |
| Custom cycle | Variable energy, access needs, or unpredictable availability | Requires some experimentation | Change one timing variable at a time |
These are scheduling options, not a ranking of biological effectiveness. For another middle-length option, see NGUMU’s 52-17 work rhythm retrospective.
If getting started is the main obstacle, extending the timer may make the task feel larger. The approach in building better habits with small focus sessions may be a better first step.
Design one realistic 90-minute session
A useful session begins with a specific outcome, not simply an intention to “be productive.”
1. Choose a deliverable that fits the block
Write a one-sentence target before starting. For example:
- Draft the argument and supporting points for one report section.
- Reproduce a software bug and test one likely fix.
- Complete a set of practice problems and review the mistakes.
- Compare three proposals against an agreed set of requirements.
Avoid targets such as “finish the project” or “catch up on everything.” A good target makes progress visible even if the wider project remains unfinished.
For tasks with substantial setup, NGUMU’s deep work guide for developers and creators offers related planning ideas.
2. Prepare the working environment
Open the documents and reference pages you expect to need. Close unrelated tabs. Put your phone somewhere that makes checking it a deliberate action rather than an automatic reach.
For browser work, configure website blocking before the session. Keep legitimate research resources accessible. If a social platform is part of the assignment, make a precise access decision rather than blocking it indiscriminately or leaving every distracting site available.
3. Use a loose internal structure
A sample 90-minute block might look like this:
- Minutes 0–10: review the target, gather context, and choose the first action.
- Minutes 10–75: work on the main task, noting unrelated thoughts without pursuing them.
- Minutes 75–90: consolidate progress, save the work, and write the next step.
This is a planning example, not a physiological formula. You do not need alarms for each segment. Its purpose is to prevent the whole session disappearing into setup or ending without a clear stopping point.
4. Leave a restart note
Before the break, write something concrete: “Next: check the assumptions in row 18,” or “Next: explain why the second example differs.”
A restart note gives the next session an entry point. It also makes it easier to step away without mentally rehearsing unfinished work throughout the break.
Make the 20-minute break genuinely different
A break filled with email, news, and short videos may be a break from your assignment, but it is not necessarily a break from screens or incoming information.
Choose the break before you begin. Walk a short route, get water, prepare a snack, stretch comfortably, or sit somewhere away from the workstation. The right activity depends on your circumstances; the useful distinction is that it does not quietly become another work queue.
Do not feel obliged to optimize every minute. A break can simply be unstructured time away from the task.
Keep eye breaks separate from the long break
A 90-20 routine should not mean waiting 90 minutes before looking away from a display. The American Optometric Association’s computer vision syndrome guidance recommends the 20-20-20 approach: every 20 minutes, look at something 20 feet away for 20 seconds.
Those brief pauses can sit inside a longer work block. They do not require opening another app or abandoning the task. Read NGUMU’s 20-20-20 eye-strain guide for more on separating eye rest from longer recovery breaks.
Use NGUMU to support the routine
NGUMU: Screen Time Control is a browser extension for Chrome, Edge, Brave via the Chrome Web Store, and Firefox. Its role here is practical: help structure browser sessions and reduce distracting access, not measure or synchronize biological rhythms.
Configure the cycle and distractions
Choose NGUMU’s 90-20 timer for this experiment. Other supported options include Pomodoro 25/5, 52-17, the 20-20-20 eye rule, and custom cycles.
Set up website blocking for focus sessions using blocklists, allowlists, or curated social media, video, and news presets. Use tab management to limit distracting tabs while keeping the materials needed for the task available.
NGUMU also provides a pre-break “blink warning” eye-rest overlay and a full-screen break overlay that discourages returning early. Treat these as reminders supporting your plan—not as proof that recovery is complete or that your next concentration peak has arrived.
Review progress without confusing time with output
Session tracking includes focus time, session counts, and daily or weekly goals. Those measures show whether you followed the routine. They do not independently show whether the work was accurate, useful, or finished.
Pair the timer record with a short manual note about the deliverable. Core features collect no personal data, and session data is stored locally. A Pro upgrade includes advanced analytics, extended timers, detailed blocklist controls, and persistent history; none of those replaces evaluating the work itself.
Run a small experiment before changing your whole week
Start with one protected cycle on a few suitable days. Pick broadly comparable tasks where possible, and avoid testing only on an unusually quiet day.
Record four things after each attempt:
- Outcome: What concrete work moved forward?
- Attention: When did useful concentration become difficult?
- Interruptions: What actually broke the session?
- Recovery: Did you take the planned break, and how did returning feel?
These notes are observations, not a clinical assessment of your rhythms.
If useful concentration repeatedly fades well before the end, shorten the block. If external interruptions dominate, address availability and environment before changing the timer. If the break keeps disappearing, reserve the full 110 minutes in your calendar rather than scheduling only the work portion.
An illustrative morning could run from 9:00 to 10:30 for focused work, 10:30 to 10:50 for a break, and then move into meetings or routine tasks. You do not have to repeat the cycle all day for the experiment to be worthwhile.
The retrospective takeaway: protect focus, not a magic number
Looking back at week 35, the useful idea behind ultradian rhythm work is deliberate alternation: give demanding work room, then step away. The less useful leap is treating 90 minutes as a universal law or interpreting ordinary fatigue as a precisely timed biological signal.
Choose a meaningful task, test one cycle, and keep the timing only if it fits your work and leaves room for recovery. A shorter session that produces good work is better than a longer one completed merely to satisfy the clock.
Ready to try a structured session? Install NGUMU for Chrome, Edge, Brave via the Chrome Web Store, or Firefox, and start with one realistic focus block.