How to Build a Routine in ADHD (and Why It Keeps Breaking)

I set up a new system. It works perfectly for two weeks. In the third week it disappears.

I lived this cycle so many times that for a while I gave up building systems altogether. I thought, "I am not someone who is suited to this kind of thing." Now I think something else: the systems I built were designed for how I am on a good day, and I am not that person every day.

Why it breaks

Automaticity is slow. For a behavior to become something done without thinking takes repetition. In ADHD this number of repetitions is higher, so the "it has become a habit now" point comes later. The novelty ends before you reach that point. In Barkley's (1997) model this is explained by strain on the mechanisms that regulate behavior from inside.

The system itself was producing the reward. A new notebook, a new app, a new color code. What works is not the system but the stimulation the novelty gives. This is called the new notebook effect, and when the stimulation ends the system ends too. I covered how this looks with apps in the article app hunting.

It is built too complicated. Systems built in the first burst of enthusiasm are generally too detailed to sustain. Seven categories, three colors, a daily review. Possible in a good week, impossible in a bad one.

A single lapse ends everything. When a day is skipped the chain breaks and all-or-nothing thinking kicks in. In Brown's (2005) framework ADHD is treated as a set of interconnected functions; when one part of that set is strained, the whole system is affected and a single disruption grows in a chain.

A system that breaks is not a bad system. It is usually a system built on a good day that cannot withstand a bad one.

What the lasting ones share

Little. A single place, a single list, a single rule. Complexity is always the enemy of sustainability.

Visible. A system that goes into a closed drawer gets forgotten. The principle of visibility is covered in detail in the article the visible place system.

Added to something existing. Instead of building a new habit from scratch, attaching it behind something already being done: habit stacking. "After I make the coffee, I look at the list."

Designed for the bad day. If you build the system for how it is on your best day, it lasts two weeks. If you build it for how it is on your worst day, it stays.

Writing the bad-day version

This is the one practice that changed everything for me, so it deserves its own heading.

When I build a system I write two versions. The first is the normal version: what I will do on a day when things are going well. The second is the bad-day version: on a day when I am sleepless, sick or tired, what is the smallest form of the same system?

Let me give an example. The normal version of my weekly review takes an hour. The bad-day version is a single question: "Is there a date I missed this week?" It takes five minutes and that day counts as a review done too.

The real job of this second version is not productivity. It is not breaking the streak. Because a streak that has been broken once often does not come back in ADHD.

How long it takes for a routine to settle

There is a number that gets repeated often: a habit settles in so many days. You need to be cautious with exact numbers like this, because they vary greatly from behavior to behavior and person to person.

The more useful frame for ADHD is this: you do not tell when a behavior has become automatic by looking at the calendar; you tell by looking at yourself. The sign is this: if you do not have to think about doing it, it has settled. If you are still asking "will I do it today," it is still something done by decision.

This distinction has a practical counterpart. A behavior in the decision stage needs outside support: a reminder, a visible cue, a fixed hour. Removing that support early removes the behavior too.

The rule that worked for me: I do not remove the support because the behavior has held. It is cheap anyway; let it stay. Every time I removed one, I saw the behavior fade within a few weeks, and rebuilding it afterward cost more than never having let go.

Practical rules

• One change at a time. Building three new habits at once means all three ending.
• Shrink the step to a laughable size. Not "exercise every day" but "put on your sneakers." A small step lasts, a big step lasts two weeks.
• Continue when the chain breaks. Skipping a day does not end the system. The rule can be: never skip two days in a row.
• Fixed anchor hours. Two or three fixed events that divide the day let the rest settle around them. The morning's own order is in the article morning routine.
• Review once a week. Setting aside separate time to fix the system matters more than building it. Details in the article weekly review.
• Accept the need for novelty. Changing the look of the same system from time to time lets novelty in without harming the system.

Evaluate the system the day after it breaks, not on the day it breaks. On the day a system breaks everything looks pointless, and the decision made in that moment is usually "I'm giving this up." Asking the same question the next day gives a completely different answer: you see what did not work, and the system is shrunk instead of being thrown away entirely.

Three common mistakes

Taking building the system for the work itself. Color codes, templates and setup feel more rewarding than the actual work. If the setup runs past ten minutes, you are probably procrastinating.

Building a brand-new system when one breaks. The new system works for a few weeks on the stimulation novelty gives and breaks at the same place. Shrinking the old one almost always gives a better result.

Treating routine as a character test. The sentence "I couldn't manage this one either" makes the next attempt harder. Building a routine is not a personality test; because automaticity develops more slowly, more outside support is needed, that is all.

When something else is needed

As the consensus statement of the World Federation (Faraone et al., 2021) lays out, ADHD is a persisting condition that affects functioning across a wide area. So systems help but on their own do not change the picture.

If none of the systems you build hold and daily life is clearly faltering, this may not be a problem of method. Talking about support options with a specialist gives faster results than trying more notebooks.

And one more thing

Using alarms, looking at a list and setting reminders is not a sign of weakness. A structure built from outside stands in for the structure that cannot be built from inside.

Accepting this took me a long time, because for a long time I thought "the real point is not needing these things." Now I think the opposite: when I set up the support I need, I spend my energy on the work rather than on fighting the system. I covered the general mechanism of building a habit in the article building a habit.