5. What ADHD Taught Me About Building Systems for Everyone
Over the past four posts, I’ve made the case that work systems fail because of design, not discipline — and walked you through a specific, lightweight approach to lead tracking that’s built around how people actually work, not how they imagine they should. If you’ve been following along, you may have noticed that the principles I’ve described don’t sound like standard productivity advice.
There’s a reason for that. They came from somewhere specific.
I have ADHD
I was diagnosed as an adult, which means I spent years before that diagnosis doing what most people with undiagnosed ADHD do: trying harder, blaming myself, wondering why things that seemed easy for other people felt so much harder for me.
Living with ADHD means operating under conditions of constant change, interruption, and uncertainty. Working memory — the cognitive scratch pad you use to hold information while you’re doing something else — is less reliable. Sustaining attention on tasks that aren’t immediately engaging is genuinely difficult, not a matter of not trying hard enough. Transitions are harder. Restarting after interruption is harder. Keeping context across gaps in time is harder.
These aren’t character flaws. They’re the neurological reality of how my ADHD brain works.
Systems designed for neurotypicals mostly don’t work for me
Most productivity systems are built on assumptions that don’t hold for people with ADHD: that you can sustain consistent attention across a workday, that you’ll remember to check a system you set up last month, that a well-designed process will feel motivating enough to maintain, that a bad week is an exception rather than a recurring feature of how your life works. Basically: that you have capacity which (for you) does not exist.
For years I tried to make those systems work. And for years they failed — not because I wasn’t trying, but because the gap between what the systems required and what I could reliably provide was simply too large for them to succeed.
The turning point wasn’t trying harder. It was asking a different question: what would a system look like that was actually designed for how I work?
Solving these problems turned into solutions that help everyone
When I started designing systems around my actual constraints — limited working memory, variable attention, frequent interruption, unreliable consistency — something unexpected happened. The systems I built didn’t just work for me. They worked for the solo practitioners and small business owners I started sharing them with, most of whom don’t have ADHD at all.
It turns out that the conditions ADHD creates — cognitive overload, interruption, context loss, inconsistency — aren’t unique to neurodivergent people. They’re the normal conditions of modern solo practice, just at a much greater intensity.
The methods that work for people with ADHD work better for everyone, because they’re built around human cognitive limits rather than against them. Low overhead. Fast capture. Easy re-entry. Preserved context. Survivable under stress.
These aren’t accommodations for a disability. They’re just good design.
What I actually do
I’m an Agile and ADHD coach. The Agile part comes from 20+ years working in project management and systems thinking — Agile methodology, originally developed for software teams, turns out to be remarkably well suited to the unpredictable, iterative reality of solo practice. The ADHD part comes from lived experience and from the work I do with clients who are neurodiverse, or who work with neurodiverse clients, or who simply keep finding that standard approaches don’t fit their reality.
My work focuses on the operational layer underneath the patterns that aren’t working: reducing cognitive friction, adapting to real capacity, building sustainable systems, preserving continuity under stress and interruption.
Some clients understand exactly what’s happening and have strong self-awareness but keep losing continuity when life gets complicated. Some are exhausted by the gap between what they know they should do and what they’re actually able to sustain. Some have tried every system and abandoned all of them.
What they share is that willpower-based solutions haven’t worked — and that reframing the problem as a design problem, rather than a personal one, tends to change everything.
Why I give this talk
The lead-tracking system I’ve described in this series is a small, concrete example of a much larger set of ideas. When I give this talk to business groups and professional communities, my goal isn’t just to give people a useful tool — though I hope it does that. It’s to demonstrate what it feels like to have your particular constraints taken seriously, and to show that designing around reality rather than against it is both possible and practical.
For some people in those rooms, that reframe is the beginning of something larger.
What’s next
If this series has resonated — if you’ve found yourself nodding along, or thinking of someone this might help, or wondering what it would look like to apply these ideas more broadly to how you work — I’d love to talk.
I offer a free consultation where we look at what’s actually getting in your way and find the smallest significant change that will make the biggest difference. There’s no obligation and no pitch — just a conversation.
And if you organize a professional community, a business group, or any gathering of people who run their own practices — I give this talk for free. You can find more information at agile4adhd.com/speaking.
