Issue #6 β Executive Function Insurance: Build Systems That Survive Your Worst ADHD Days

π§ The Crash Scenario
You know the day.
Maybe it's a sensory overload spiral. Maybe it's the depression weight. Maybe you slept 3 hours and your brain is fog soup. Whatever it is, you're at 40% capacity.
Here's the question most productivity advice won't touch:
What happens to your business when you're at 40%?
If the answer is "everything falls apart," you don't have a productivity problem. You have a systems problem.
π The Insurance Framework
Executive function insurance isn't about optimizing your best days. It's about surviving your worst ones.
Think of it like actual insurance: you don't buy fire insurance because you plan to have a fire. You buy it because fires happen, and the cost of not having it is catastrophic.
The Three Layers:
| Layer | What It Does | Example |
|---|---|---|
| Automation | Runs without you | Auto-invoicing, scheduled social posts, backup scripts |
| Delegation | Someone else runs it | VA handles email triage, contractor manages ads |
| Elimination | Doesn't need to run | That report nobody reads, the meeting that could be an email |
π§ Layer 1: Automation (The "Set and Forget" Stack)
This is the stuff that literally runs without you touching it.
Quick wins:
- Finance: Auto-invoice generation (Ghost subscriptions, Stripe billing)
- Communication: Email autoresponders, Slack status auto-updates
- Content: Scheduled social posts (Late.app, Buffer)
- Ops: Daily backups, uptime monitoring, SSL renewal
ADHD tax alert: You've probably already paid for tools that could automate this. Check your subscriptions β you might be paying twice for the same function.
π€ Layer 2: Delegation (The "Human Backup")
Some things can't be automated. They need a human β just not necessarily you.
What to delegate first:
- Email triage β VA sorts, flags urgent, drafts responses
- Customer support β Base-level questions handled by someone who won't spiral
- Content distribution β Posting, cross-platform formatting, engagement
- Admin chaos β Scheduling, data entry, "where's that file?" work
The ADHD founder's dilemma: Delegation feels like losing control. But here's the reframe β delegation isn't losing control. It's buying insurance against the day you can't control anything.
βοΈ Layer 3: Elimination (The "Does This Need to Exist?" Audit)
Here's the radical option: what if the thing just⦠didn't happen?
I know, I know. You've been taught that every task is essential. That dropping a ball means failure.
Let me introduce you to a concept from emergency medicine: triage.
When resources are limited (your executive function), you don't treat everyone equally. You treat the people who will die without it first. The rest can wait.
The Triage Test: Ask this for every recurring task:
- "If I don't do this for 2 weeks, what actually breaks?"
- "Would my customers notice?"
- "Would my revenue drop?"
If the answer to all three is "no" β congratulations. You've found something to eliminate.
π‘ The 40% Rule
Here's the mental model I use:
Design your systems for the day you're at 40% capacity.
Not 100%. Not even 70%. Forty percent.
On your 100% days, you'll crush it. On your 40% days, you'll survive β and that survival is what keeps you in business long enough to have another 100% day.
The 40% Checklist:
Run through this when you're building any system:
- Can this run for 3 days without me touching it?
- If I disappear for a week, does revenue still come in?
- Can someone else (VA, contractor, co-founder) run this with < 1 hour of training?
- If this breaks, do I have an alert that tells me before the customer notices?
π οΈ Real Example: How Divergent Runs at 40%
Let me show you what this looks like in practice.
Ghost newsletter:
- Automation: Scheduled publishing, auto-email to subscribers
- Delegation: None yet (solo operation)
- Elimination: No manual list management, no A/B testing (not worth the cognitive load)
Social media:
- Automation: Late.app schedules everything
- Delegation: None (voice is too personal to outsource⦠yet)
- Elimination: No daily engagement, no trending topic chasing
Revenue:
- Automation: Stripe subscriptions, auto-renewal
- Delegation: None
- Elimination: No invoicing, no payment chasing
Result: I could disappear for 2 weeks and the newsletter would still publish, subscribers would still get their issues, and revenue would still come in.
That's executive function insurance.
β‘ The ADHD Angle
Here's why this matters more for us:
Neurotypical founders can rely on consistency. They wake up, do the thing, move on. Their systems can assume a baseline of daily executive function.
ADHD founders can't. Our capacity is variable β sometimes wildly so. Building systems that assume consistency is like building a house on a fault line and pretending earthquakes don't exist.
The insurance framework isn't about admitting defeat. It's about designing for reality.
π― This Week's Challenge
Pick ONE system in your business. Run it through the 40% test:
- List every step required to keep it running for a week
- Mark each step: Automate / Delegate / Eliminate / Must Be Me
- For anything marked "Must Be Me" β ask: is this actually true, or am I just used to doing it this way?
Reply and tell me which system you audited. I'll send you my own 40% checklist as a thank you.
Next issue: The "Interest-Based Nervous System" β why your ADHD brain isn't broken, it's just running different hardware than everyone else.
Divergent β Strategy for brains that don't do boring.