ADHD-Friendly Systems: What Actually Works

← lab

ADHD-Friendly Systems: What Actually Works

The meta-post about building systems for a scattered brain. Automation beats willpower, traffic lights beat dashboards, conversations beat menus.

I’ve tried every productivity system.

GTD. Bullet journals. Notion. Obsidian. Time blocking. Pomodoro. Weekly reviews.

Most lasted a week. Some lasted a month. None stuck.

The Pattern of Failure

Here’s why productivity systems fail for ADHD brains:

  1. They require setup — Creating the system is fun. Maintaining it is not.
  2. They require memory — “Just remember to check your todo list!” Cool, I forgot.
  3. They require discipline — If I had discipline, I wouldn’t need a system.
  4. They require energy — Processing a backlog of tasks is exhausting.

The common thread: They assume I’m neurotypical.

I’m not. So I needed different rules.

The Three Principles

After years of failed experiments, I found what actually works:

1. Automation > Willpower

If a system requires me to remember something, it’s broken.

Bad system: “Check your finances every Monday.”

Good system: Traffic light financial status updates automatically. Turns red if there’s a problem. I only look when the color changes.

Bad system: “Review your calendar every morning.”

Good system: AI Chief of Staff surfaces what’s next when I ask. No manual review needed.

The goal isn’t to build better habits. It’s to build systems that don’t need habits.

2. Traffic Lights > Dashboards

Dashboards require interpretation. Traffic lights require a glance.

Dashboard: “You have $12,453 across 3 accounts, with $4,200 due in 12 days, spending $387/day on average…”

Traffic light: 🟢 Green. You’re fine.

Dashboard: “86% battery, 120W solar input, 50W load, 4.2 hours to full…”

Traffic light: 🟢 Green. Don’t think about power.

Dashboard: “Your server has 2.3GB RAM used, 15% CPU, 42GB disk free…”

Traffic light: 🟢 Green. Everything’s running.

I don’t want data. I want to know if there’s a problem.

3. Conversations > Menus

Navigating UIs drains mental energy. Asking questions doesn’t.

Menu-based: Open app → Navigate to Finances → Select Account → View Transactions → Filter by Date → Export CSV → Calculate in spreadsheet

Conversational: “Where did my money go last week?”

Menu-based: Open calendar → Find next week → Check for conflicts → Cross-reference with project deadlines → Make decision

Conversational: “Can I schedule a meeting Tuesday afternoon?”

The conversational interface removes navigation overhead. Just ask.

What I Actually Built

These principles led to Neatworld:

Financial monitoring:

  • Auto-sync bank accounts (SimpleFIN)
  • Auto-categorize transactions (rules engine + AI)
  • Traffic light status (green/yellow/red runway)
  • Conversational queries (“Can I afford this?”)

Calendar management:

  • Auto-sync Google Calendar
  • Surface next events on demand
  • Conflict detection
  • Context-aware scheduling suggestions

Email triage:

  • Auto-sync Gmail (two accounts)
  • Semantic search
  • AI-powered summarization
  • Draft suggestions

Infrastructure monitoring:

  • Server health checks
  • Starlink performance tracking
  • Battery status (van solar)
  • Automatic alerts for problems

The common pattern: I don’t check things. Things tell me when they need attention.

What Failed Along the Way

Systems I tried that didn’t stick:

Weekly reviews — Lasted 3 weeks. Too much ceremony. Too easy to skip one week and never restart.

Time blocking — Lasted 2 months. Rigid schedules don’t survive chaos. And my life is chaos.

Detailed todo lists — Became anxiety-inducing backlogs. Never cleared. Always guilt-inducing.

Manual expense tracking — Lasted 1 week. Every transaction requires logging? Not happening.

Habit tracking — Lasted 1 month. Tracking habits became a habit I failed at.

The lesson: If it requires ongoing manual effort, I won’t do it. Automate or abandon.

The ADHD Tax

Not having systems costs money:

  • Missed payments → late fees
  • Forgotten subscriptions → wasted money
  • Impulse purchases → budget chaos
  • Lost receipts → missed deductions
  • Disorganization → buying duplicates

I’ve paid thousands in ADHD tax over the years.

The ROI on building these systems isn’t just productivity. It’s actual money saved.

Design Patterns That Work

Specific tactics I use across all systems:

Reduce Cognitive Load

Bad: Show me 47 tasks and let me prioritize.

Good: Show me the 3 things that matter today.

Bad: Display all financial data on homepage.

Good: Hide numbers unless status is yellow or red.

Default to Automation

Bad: “Remember to sync your bank accounts.”

Good: Cron job syncs every hour automatically.

Bad: “Categorize your transactions weekly.”

Good: AI categorizes automatically, I correct exceptions.

Make It Conversational

Bad: Navigate through 5 screens to check runway days.

Good: Ask “What’s my runway?” Get answer.

Bad: Open multiple apps to plan a purchase.

Good: Ask “Can I afford this?” Get context-aware answer.

Surface Only What Matters

Bad: Notifications for everything.

Good: Only alert on status changes (green → yellow, yellow → red).

Bad: Daily digest of all activity.

Good: Weekly summary of exceptions and anomalies.

The Technology Stack

What I actually use to build these systems:

  • FastAPI — Backend for all services
  • PostgreSQL — Data storage
  • Claude APIConversational AI interface
  • SimpleFIN — Bank aggregation
  • Google APIs — Gmail, Calendar
  • Systemd + Cron — Automation and scheduling
  • Git — Version control for everything (including 3D models)

It’s not complex. It’s just connected.

The Mental Shift

The breakthrough wasn’t technical. It was philosophical:

Old mindset: “I need to build better habits.”

New mindset: “I need to build systems that don’t require habits.”

Old mindset: “I should check my finances regularly.”

New mindset: “My finances should tell me when there’s a problem.”

Old mindset: “I need to be more organized.”

New mindset: “I need systems that organize for me.”

Accepting my brain’s limitations freed me to design around them.

What You Can Steal

You don’t need my exact setup. But you can steal the patterns:

  1. Identify friction points — What do you forget? What drains energy?
  2. Automate the boring parts — Sync, calculation, monitoring.
  3. Reduce to traffic lights — Green/yellow/red beats detailed dashboards.
  4. Make it conversational — If possible, ask questions instead of navigating.
  5. Surface only exceptions — No news is good news.

The tech doesn’t matter. The principles do.

The Cost

Building this took time. Hundreds of hours over a year.

But compare that to the cumulative time lost to:

  • Checking bank accounts 5x/day
  • Manually categorizing transactions
  • Forgetting appointments
  • Missing deadlines
  • Context-switching between tools

The ROI is positive within months.

What’s Still Broken

Things I haven’t solved:

Physical organization — My van is still a mess. No code solution for that.

Project prioritization — Knowing what to work on is still manual. AI can’t decide business strategy yet.

Deep focus — Systems handle shallow work. Deep work still requires discipline I don’t have.

Social obligations — Remembering to respond to people. Still terrible at this.

Systems solve some problems. Not all of them.

The Takeaway

The best productivity system is one that doesn’t require productivity.

If you’re constantly “managing” your management system, it’s not working.

Automate the tedious parts. Let AI handle synthesis. Surface only what matters. Make it conversational when possible.

Build systems that work with your brain, not against it.

That’s the only way they stick.