ALLY GUIDE / LINUX BRAINS, WINDOWS WORLD

Support every kind of brain at home.

This guide translates research and lived-experience notes into practical scripts for neurotypical partners, housemates, and family. Think of it as the compatibility layer between firmware — built so no one has to pretend their operating system is broken.

Start with the truths Learn the scripts

Safety + disclaimer

We are not medical professionals. Everything here paraphrases sources like the NHS, National Autistic Society, CHADD, and ND-led creators listed in research/nd-creators.md. Always defer to qualified clinicians for diagnosis, medication, or crisis intervention.

How to use this guide

  • Check in with the ND person before introducing new supports.
  • Pair scripts with the resources directory for referrals.
  • Update household agreements regularly; capacity shifts daily.

Foundations

Core realities to anchor on

ND brains aren’t malfunctioning—they’re running different firmware. Holding these truths reduces shame and keeps allyship collaborative rather than corrective.

  • Executive function isn’t willpower. Task initiation, working memory, and time perception are neurological differences, not laziness (NHS, CHADD).
  • Sensory load fluctuates. Lighting, noise, texture, and temperature can change capacity moment to moment (NAS – Sensory differences).
  • Masking burns energy. Many ND folks “perform normal” in public and crash at home (Autistic Women & Nonbinary Network, Dr Devon Price).
  • Language matters. Minimising phrases (“everyone forgets things”) signal you won’t help build scaffolds.
  • Consent + autonomy are vital. Directives (“Just do it now”) can trigger demand avoidance, especially for PDA profiles (PDA Society).

Everyday ally scripts

Use these prompts when you’re tempted to “fix” or minimise. They keep agency with the ND person while offering concrete scaffolds.

Situation Say this Why it helps
Task overwhelm “What’s the next tiny step and how can I scaffold it?” Breaks chaos into one action and signals collaborative planning.
Time blindness “We leave in 30 minutes. Want me to set a 15-minute check-in?” Provides external cues while honouring autonomy (CHADD).
Sensory overload “Lights feel harsh—want me to dim them or grab your headphones?” Offers concrete adjustments instead of platitudes.
Decision fatigue “Here are two options I can own. Which feels lighter?” Reduces branching choices while respecting agency.
Post-masking crash “Do you want company, quiet, or a stim walk?” Normalises decompression and avoids forcing conversation.

Language to retire (and what to offer instead)

Don’t say Impact Offer instead
“Everyone struggles with chores.” Minimises neurologically driven executive dysfunction. “Let’s design a key drop spot or reminder that suits your brain.”
“Just try harder.” Frames disability as effort failure; fuels rejection sensitivity. “What part of this system is fighting you? Let’s redesign it.”
“Use my planner.” Ignores that many ND folks need multi-sensory aids or accountability. “Want me to co-create something in the tool you already like?”
“Calm down, you’re overreacting.” Invalidates sensory/emotional data; escalates meltdowns (NAS – Meltdowns). “I see this is intense—want space, compression, or for me to run interference?”
“You did it yesterday.” Ignores variable capacity and encourages masking. “Capacity feels different today—do we pause, swap, or get backup?”

Environmental supports

  • Shared external brain: keep chores/projects in a shared visual tool (Vikunja, Notion, Trello).
  • Predictable routines + buffer: default day/week structures with explicit recovery slots.
  • Sensory zones: low-light, low-noise spaces or stim baskets (noise cancel, weighted blankets, fidgets).
  • Transition cues: multi-sensory reminders 24h → 1h → 15m before commitments.
  • Consent for touch/interruption: agree signals before breaking hyperfocus.

Co-regulation tips

  • Body-doubling/parallel work for task initiation.
  • Shared check-ins (“What’s support look like today?”).
  • Celebrate pattern-spotting, creativity, monotropism as loudly as you flag risks.

Pair with the Field Notes trait table to tailor supports per neurotype.

Handling meltdowns or shutdowns

  1. Remove non-essential demands; offer short, concrete choices.
  2. Adjust environment (lights, noise) and offer agreed regulation tools.
  3. Shield from external scrutiny—answer the door, pause calls, cover childcare.
  4. Debrief later: “What helped? What didn’t? What should we prep for next time?”

Reference sources

When you need cooperation (without triggering demand avoidance)

  • Frame as collaboration: “Can we problem-solve this for 15 minutes?”
  • Offer meaningful choice: channel, order, or tool choice reduces threat response.
  • Explain the why: link tasks to shared values (“So meds don’t lapse”) over authority.
  • Build trade options: allow swaps or rain-checks; track agreements in the shared task board.

Dive deeper via PDA Society communication strategies.

Quick ally checklist

  • ☑ Ask “What does support look like today?” before offering help.
  • ☑ Keep crisis scripts handy (who to call, meds, grounding tools).
  • ☑ Use body-doubling or co-working when motivation dips.
  • ☑ Log shared tasks in one trusted system; no verbal-only requests.
  • ☑ Celebrate wins as loudly as you log friction.

Further learning

Keep the loop tight

Pair this guide with the Neurodiversity Field Notes and friction scenarios to understand how household dynamics interact with systemic failures.

Visit the resources hub