How to build an ADHD system that survives a bad week

Why systems fail on schedule

Most systems you were handed assume a steady week. When the week stops being steady, they offer two options: full performance or nothing. A weekly review that needs forty five quiet minutes, a clean desk and the emotional room to face everything unfinished holds up, in the book's experience, for about two weeks. Then a trip, an ill child, a rush at work or a few bad nights come along, and one review gets skipped.

The review after that costs the forty five minutes and more: clearing the backlog, rebuilding lost context and facing all the things that never happened. When the full version is out of reach, the system has no acceptable next step to offer. That is a single point of collapse.

ADHD is a neurodevelopmental condition with functional impairment, and clinical guidance includes changes to the environment and structured support as part of managing it. A system that depends on a perfect week leaves you relying on memory and intention alone, and that is worth designing out.

The mechanism: return cost, not continuity

A streak measures how long you lasted. A restartable system cares more about what it cost to come back, and since interruptions are certain, a cheap return is the more useful goal.

When a routine drops away, the task itself is seldom all that is waiting for you. Waiting with it are a backlog, lost context, missed deadlines, unread messages, doubt about where things stand, shame about the delay and pressure to come back flawlessly. The book calls that bundle the comeback tax. It explains how a five minute routine can seem impossible after three weeks off, even though the routine itself is still five minutes long.

The fourteen day abandonment test

Choose a system you care about and picture fourteen days in which nobody touches it. Then answer six questions.

1. What damage accumulates?
2. What information goes stale?
3. What expires?
4. What becomes hard to look at?
5. What single safeguard would reduce that damage?
6. What would return me to a state I can trust within ten minutes?

Think of it as recovery engineering. Planes have checklists because mistakes are costly however good the pilot is, and software is built with recovery states because interruptions happen. Your own systems deserve the same care with far less machinery.

The stress test

The abandonment test asks about two weeks away. The stress test asks about an ordinary bad day, and it ignores how organized the system looks. The questions:

• Will it work after a bad night?
• Will it work on my phone when I am out?
• After three weeks away, can I still see the next action?
• Does it keep working when one tool or one person is missing?
• Is Low Power far lighter than Full Power?
• Can I Restart without wading through the entire backlog?

A system that ordinary disruption can break was only ever a temporary performance. Fix the failed answers one at a time.

Example: a weekly review that survives

Take the weekly review above and give it three versions.

Current

Weekly review has a Full Power, Low Power and Restart version on one card.

Next

Run the Low Power version on the next tired week.

Check

First workday after the next missed review.

• Full Power: go through the calendar, projects, things you are waiting on and priorities. Pick three outcomes for the week and set up the first actions.
• Low Power: scan the coming seven days. Pick out one deadline, one appointment and one consequence worth protecting, and write the three on a card you can see.
• Restart: leave the old backlog alone for ten minutes. With the calendar open, find the nearest expensive consequence and write down the next physical action. Then put a state note at the restart marker, ready for the next review.

The state note has three lines: Current, Next, Check. Current records the situation today, Next names one visible step, and Check sets when you will return.

Missed days are not debt

If you skipped three daily reviews, review where things stand today, once. After two weeks without exercise, there is no need for fourteen make-up workouts. A consequence may need fixing, but the ritual you missed is not a debt to pay back.

This is different from letting yourself off the hook, which would make the consequence disappear. A cheaper return removes the friction and leaves the consequence in sight. A system you keep coming back to holds you to account better than a flawless one you run from.

Failure modes

• The state note turns into a journal. Three lines is the limit. When you find yourself writing a paragraph, Next is still too vague.
• Restart turns into a complete redesign. Leave your tools alone while you are still disoriented. Get the current state back before anything else.
• A broken streak turns into evidence that nothing works. Interruptions were always coming. What counts is whether the system helped you get back.