Issue #36 — The AuDHD Founder: When Two Wiring Patterns Collide in One Business

🎯 TL;DR

AuDHD (autism + ADHD) is not ADHD with extra rules or autism with extra energy. It's a third operating system where deep systems thinking and rapid pivoting fight for the same steering wheel. This week: how to build a company that respects both drivers instead of forcing them to take turns.

This week: Why the AuDHD founder wins by designing for contradiction, not around it.

Read time: 5 minutes

🌀 The Paradox That's Not A Personality Flaw

You spent three weeks perfecting a project management system in Notion. Relational databases, custom views, automated status rollups. It was beautiful. On Monday morning you opened your laptop and never touched it again.

You spent two hours in a customer call obsessing over one pricing edge case nobody else noticed. Then you skipped the next three calls because "I already know what they'll say." You crave routine and you sabotage it. You need silence but you need seven browser tabs of stimulation. You will die on the hill of one detail and pivot your entire business model over a burrito.

None of this is a character weakness. If you happen to be autistic and ADHD — what researchers and clinicians now call AuDHD — this is the predictable output of two wiring patterns sharing one nervous system. And once you name it, you can finally stop trying to fix it with a better calendar app.

🧬 What The Research Actually Says

Until 2013, the DSM-IV forbid clinicians from diagnosing ADHD and autism in the same person. The DSM-5 quietly reversed that rule, and the numbers that came out of it were staggering. Multiple studies since — including work summarized in the Journal of Attention Disorders and by the UK's Embrace Autism clinic — put the overlap between 50% and 70% of autistic adults meeting ADHD criteria, and roughly 30–40% of ADHD adults meeting autism criteria on structured assessment.

The interesting part is not the overlap. It's the interaction. Dinah Murray's monotropism theory frames autistic attention as a deep, narrow channel — one interest at a time, but all of you in it. Russell Barkley's model of ADHD frames attention as chronically under-regulated — many channels, shallow depth, dopamine-hungry. AuDHD wires both circuits in parallel. You get monotropic depth and polytropic drift, often within the same afternoon.

That's why the standard productivity playbook fails so hard. "Just batch your tasks" ignores the autistic need to complete a thought fully. "Just follow your energy" ignores the autistic need for a working routine. You are not one archetype badly executed; you are two archetypes running simultaneously.

Trait	Pure ADHD Founder	Pure Autistic Founder	AuDHD Founder
Systems	Builds five, uses none	Builds one, uses forever	Builds perfect ones, abandons cyclically
Pivots	Weekly, shallow	Rare, painful	Sudden, deep, then locked in
Communication	Tangents, interruptions	Literal, precise	Both, on rotation
Burnout trigger	Boredom	Sensory + social load	Both, stacked
Superpower	Fast pattern-matching	Deep model-building	Deep models that can pivot fast

"AuDHD folks often experience their brains as two people arguing. The systemizer wants order and completion. The novelty-seeker wants to burn it down." — Dr. Devon Price, Unmasking Autism

Steve Silberman's NeuroTribes documented how many founders who shaped early computing showed both traits long before diagnostic categories caught up. The pattern isn't new. What's new is that we finally have a word for it.

🛠️ How To Actually Run A Company With This Brain

Stop optimizing for one side. The mistake most AuDHD founders make is picking a productivity religion — GTD, Deep Work, whatever — and then blaming themselves when half their brain revolts against it.

Design in two modes: Build Mode and Burn Mode. Build Mode is monotropic — one project, deep dive, no meetings, no context switching. Burn Mode is polytropic — inbox, calls, decisions, ship the small stuff. Block them on the calendar as literal modes, not tasks. Most AuDHD founders need 2–3 Build days and 2 Burn days per week. Mixing them hour by hour is what breaks you.
Codify your specifics, automate the ambiguity. Autism loves clear rules. ADHD hates administrative overhead. Split the difference: write your operating agreements, refund policies, hiring criteria, and pricing logic once, in obsessive detail. Then hand execution to tools (Zapier, a VA, Stripe rules) so the ADHD side never has to touch the boring part again.
Pre-decide your pivots. Give yourself a rule like: "I will not change the business model between the 1st and 15th of the month." This satisfies the autistic need for structure and gives the ADHD novelty-brain a container to bounce inside. When the pivot urge hits mid-week, you write it in a doc and revisit on the 16th. 80% of those urges die there.
Hire your inverse, but translate for them. Neurotypical operators execute steadily but often can't read your fast pivots or your obsessive detail. Write them a translation guide: "When I disappear for two days, I'm in Build Mode. When I send twelve Loom videos at midnight, don't act on any of them until we sync Thursday."

⚡ The ADHD Angle

Executive function in AuDHD isn't "impaired." It's bimodal. When the topic aligns with your interest, you get autistic-level task persistence — the kind that lets you code for eleven hours, forget to eat, and produce genuinely novel work. When the topic misaligns, you get ADHD-level shutdown — often worse than pure ADHD, because you also feel the autistic pain of a broken routine on top of the dopamine crash.

Rejection Sensitive Dysphoria hits AuDHD founders harder because the autistic side already runs a background process of "am I being weird?" A single sharp Slack message can trigger both a dopamine crash and a social-processing spiral that lasts two days. Recognizing this is not self-indulgent. It's operational. If you're going to survive investor calls, hard hires, and customer churn, you need to build recovery time the way an athlete builds rest days — not because you're fragile, but because your nervous system is doing two full jobs.

🎯 This Week's Challenge

Audit your last three abandoned systems. Write down what you actually needed from each one — depth, novelty, control, ease. Look for the pattern. That pattern is your real operating spec.
Block one Build Day next week. No meetings, no Slack, one project. Notice how different your brain feels compared to a fragmented day.
Write your pivot rules. One page. When are you allowed to change direction? What has to be true? Post it somewhere you can see it when the urge hits.

See you Tuesday, L-P

P.S. — If you've been told you're "too much detail" and "too scattered" in the same performance review, forward this to the person who said it. Then forward it to another founder who thinks they're broken for the same reason. We're not broken. We're just running two operating systems on one machine — and once you accept that, you can finally start designing for it.

Divergent — Strategy for brains that don't do boring.