Building Systems That Serve Both Brains: AuDHD Life Hacks

By Tim Williams · @AuDHD_Founder

You found a system that worked. You used it for eleven days. Then something small shifted — a busy week, a sick kid, a mood crash — and the system collapsed. You spent two weeks feeling guilty about it. Then you built another system, a better one, more comprehensive, with backup protocols. It lasted eight days.

If this is your life, you're not doing it wrong. You're running into one of the core contradictions of being AuDHD: you need structure to function, and you need novelty to survive, and those two needs are in constant friction with each other.

What's actually happening

AuDHD — the co-occurrence of ADHD and autism — creates a specific tension that neither diagnosis alone explains fully. The autistic nervous system often craves routine, predictability, and sameness. Routine reduces cognitive overhead. It makes the world feel safe. Deviations from routine are genuinely costly — they require rapid adaptation that the autistic nervous system wasn't designed to do cheaply.

The ADHD nervous system, meanwhile, habituates to repetition and loses interest. A routine that becomes fully automatic also becomes invisible to the dopamine system. It stops providing the engagement signal that keeps ADHD brains activated. So the very routines that make the autistic side feel safe become the routines the ADHD side stops being able to execute.

Research published in Neuropsychology Review has explored how co-occurring ADHD and autism create compounded executive function challenges that look different from either condition alone. Systems that serve one set of needs often undermine the other — which is why standard productivity advice tends to fail AuDHD people even more dramatically than it fails single-diagnosis people.

Why it feels this way

Most systems are designed by and for consistent people. The underlying assumption is that if something works and you do it correctly, you'll keep doing it. That's not how variable-attention, variable-energy brains work. A system that requires the same capacity every day will fail on the days when that capacity isn't there — which, for AuDHD people, is a significant portion of days.

There's also the shame spiral that attaches to system collapse. The system failing feels like you failing. You don't think "the system wasn't robust enough for my actual neurological variability." You think "I can't do anything right." That shame makes it harder to rebuild, which extends the collapse period, which generates more shame. It's a loop that's hard to interrupt once it starts.

The other piece is that AuDHD people are often very good at designing systems on paper. You can construct an elaborate, logical, comprehensive structure for your life. The design capacity is there. The execution capacity fluctuates wildly, and no amount of good design compensates for a day when your nervous system is in freefall.

What actually helps

1. Build systems with degradation modes, not just ideal modes.

Every system you build should have at least three tiers: the full version for when you have capacity, the stripped-down version for when you have partial capacity, and the minimum viable version for when you have almost none. The minimum viable version is the most important one. It's what keeps the thread alive on the hardest days. "I can't do my full morning routine, but I can do the one thing that prevents the worst outcomes" is a system that survives.

2. Make the structure fixed and the content variable.

The autistic side can tolerate repetition when the frame is consistent. The ADHD side needs novelty within that frame. A fixed morning block — same time, same general sequence — with rotating content (different podcasts, different tasks in a rotating order, different environments) often satisfies both needs simultaneously. The scaffolding stays, the experience changes.

3. Design for your actual life, not your aspirational life.

The systems that survive are calibrated to bad days, not good days. If your system requires perfect conditions to work, it will fail every time conditions are imperfect. Build in the sick days, the mood crashes, the unexpected chaos. A system that only works on your best days is a system that doesn't really work. Building systems that survive executive dysfunction means designing for the floor, not the ceiling.

4. Automate what you can and externalise what you can't automate.

Anything that can be made automatic — bill payments, recurring tasks, environmental setup — removes it from the daily decision-making pool. Anything that can't be automated should be visible and external: written checklists, physical cues, alarms that don't require you to remember to check them. The goal is a life that requires as few internal cognitive resources to maintain as possible, freeing those resources for the things that genuinely require them.

5. Track system collapses and learn from them without shame.

When a system breaks down, that's data. What day did it start failing? What changed? What was the capacity level? If you track this without judgment — as information, not evidence of failure — patterns emerge. Some systems fail at transition points. Some fail during sensory overload weeks. Some fail when the novelty expires. Knowing which ones fail for which reasons lets you build more targeted redundancy.

What doesn't help

"Just be consistent." Consistency is the output, not the input. Telling an AuDHD person to be more consistent assumes the inconsistency is a choice, or a lazy habit, rather than a feature of a variable nervous system. The path to more consistent outcomes runs through better systems, not more willpower.

"Find a routine that works and stick to it." This works for people whose brains don't habituate out of routines. It doesn't work when the ADHD side of your brain stops responding to the routine after two weeks, no matter how useful it is. "Sticking to it" isn't a solution to a neurological adaptation process.

"You just need more discipline." I'm going to let that one land without further comment.

The bigger picture

AuDHD system-building is a different discipline than productivity. It's not about optimization — it's about survival architecture. You're building structures that can absorb your worst days, flex with your variable days, and still produce something on your best days.

That's harder to design than a simple productivity system. It requires more self-knowledge, more iteration, and more willingness to let the ideal go in favor of the functional. The good news is that once you stop trying to build systems for the neurotypical productivity brain and start building for your actual brain, you stop failing at systems that were never designed to work for you.

SHIFT exists inside this framework — not as another thing to manage, but as a quick resource for the moments when your nervous system needs to reset before the system can kick back in. Transitions are often where systems break first. Having a tool for those moments closes one of the most common gaps.