The Superpower I Didn’t Choose: Why Do I Lose My Train of Thought So Easily?

Challenge: Why Do I Lose My Train of Thought So Easily?

A designer opens a mockup with a modal in it, and before they can walk me through the flow, I’ve already lost the thread. Not because the mockup is bad. Because a modal just covered the thing I was looking at, and now I have to hold two states in my head at once: what I was doing, and what just popped up over it. By the time it closes, I’ve forgotten my own question.

That’s not a design opinion. That’s how my brain works. I have ADHD. Split attention costs me more than it costs most people, and hidden state — anything I can’t see right now — tends to disappear. For a long time I treated that as something to manage around: more notes, more reminders, more willpower spent holding onto things that shouldn’t have needed holding onto in the first place.

Want help turning a constraint like this into shipped product rules? Get implementation help from Just In Time AI’s AI Systems Setup and Coaching.

🎓 Lesson

• ADHD: Losing your train of thought when something covers up what you were looking at is the cost of hidden state, not a personal failing.
• Others: Hidden state costs you too, even though it costs more for someone with ADHD.

What: What Design Rule Keeps Hidden State From Costing You Your Place?

The gap I finally saw wasn’t in my brain. It was in the tools. Every product team I’d ever worked with treated "accessible" and "low cognitive load" as a compliance checklist — something you audit after the real design is done, for a hypothetical user who isn’t in the room. Nobody was designing from the actual cost of losing your place, because nobody writing the rules paid that cost personally. That was the opportunity: stop treating my ADHD as a personal workaround problem and start treating it as the sharpest, most honest design constraint available to me, the same shift the companion piece What systems actually work for how ADHD attention operates? walks through in more detail. If a pattern breaks my flow, it will break someone else’s flow too — they just won’t tell you, because they don’t have a name for what went wrong. I do.

So I wrote it down as a rule, not a preference. No hidden actionable state. No modal popups for normal flow — expand in place, or slide in from the edge, so the thing I was looking at never disappears. Every side panel remembers the width I left it at. Every value I might have to type by hand gets checked for the letter-pairs a dyslexic reader swaps, because I have dyslexia too, and a mistyped credential is not a UX nuance, it’s a locked door. And the system has to remember state for me — what I was doing, what changed since I last looked — because I will not reliably remember it myself, and pretending otherwise just relocates the failure to a worse time — the same principle covered in How Do I Remember Tasks With ADHD?.

🎓 Lesson

• ADHD: A binding rule — no hidden actionable state, no modal popups for normal flow, panels that remember their width, fields checked for swappable letters — removes the need for willpower to hold onto your place.
• Others: Writing the fix as a rule everyone must follow, instead of a personal workaround, makes it hold up for every user who hits the same gap.

🎉 Tip: If your product has one screen where people quietly stop trying, you can turn that into a written rule this week. Start with the one hidden-state problem you already know about, and give yourself credit for catching it before anyone had to tell you.

Why: Why Does Designing for the ADHD Cost Make Every User’s Experience Better?

Here’s the concept underneath all of that: design for the user who cannot afford to lose their place, and you end up building something that works better for everyone, including the user who could have tolerated the loss. A one-click path to context isn’t an ADHD accommodation, it’s just a shorter path. A system that remembers so you don’t have to isn’t a disability feature, it’s less friction for every returning user. Accessibility done right isn’t a tax on the design — it’s a forcing function that catches the same laziness that would have annoyed everyone eventually, it just catches it sooner because someone in the room feels it immediately instead of eventually.

Without that constraint, the failure is quiet. Nobody files a bug for "I lost my train of thought." Nobody escalates "I had to retype a sixteen-character code and got it wrong twice." Those costs just show up later as churn, support load, or a user who quietly stops trying — and by then nobody can trace it back to the modal, or the unlabeled field, or the state that vanished on refresh. Silent attrition in front of a real user is a worse outcome than a loud failure, because nobody learns from it.

The easier path was to treat this as a personal accommodation — ship the generic pattern, keep a private list of workarounds for myself, move on. I didn’t take it. I wrote the constraint as a binding rule that applies to every tool I use as an end user, checked it against real specs before they shipped, and carried the same principle — external, durable memory instead of asking a person (or an AI agent) to hold everything in their head — into a separate piece of software I built and released publicly, so the idea would have to hold up outside my own head too. The tradeoff I accepted: slower design reviews, because "would I lose my place here?" is a real question you have to sit with, not a box you check.

🎓 Lesson

• ADHD: The feature that keeps you from losing your place is usually just less friction for every other user too.
• Others: Silent attrition costs more than a loud failure, because nobody can trace a quiet drop-off back to its cause.

Bottom Line: What Should You Change Starting Tomorrow?

If you run a product team, the question worth stealing isn’t "is this accessible." It’s narrower and more useful: whose actual, personally-felt cost is currently absent from this design review? Find that person, or be honest that you’re designing from theory. My ADHD isn’t a caveat on my engineering judgment — it’s part of the reasoning the ADHD as a SuperPower series works through post by post. It’s the reason the judgment is sharper than it would otherwise be.

Starting tomorrow, write your own binding rule the same way: pick the one flow on your product where state disappears, remove the modal or auto-reset that causes it, and replace it with a pattern that keeps the prior state visible. You will know it is working when support tickets and churn tied to that flow drop, and when a user can walk away mid-task and come back without re-reading anything. Skip this and the cost does not disappear — it moves downstream into churn, support load, and users who quietly stop trying, the same silent attrition described above, repeating every release cycle.

🎓 Lesson

• ADHD: A rule you can point to tomorrow beats a feeling you try to remember.
• Others: Watch for the downstream cost — churn and quiet drop-off — not just the upfront complaint.

🎉 Tip: Picking just one flow to fix starting tomorrow is a reasonable goal, and you already have what you need to spot it.

Frequently Asked Questions

Losing Focus and Attention

Why do I lose my train of thought so easily?

Losing your train of thought this easily usually comes from a split-attention cost: something covers up what you were looking at, so you have to hold two states in your head at once, what you were doing and what just appeared. That happens because hidden state, anything you cannot see right now, tends to disappear, and holding onto it instead of seeing it costs real attention.

🎉 Tip: You are not losing focus because something is wrong with you. Naming hidden state as the real cost means you already did the hardest part, just by noticing it.

The fix is to keep the thing you were looking at visible instead of hiding it behind a popup, so there is nothing to reconstruct when it closes. Read more: https://danstolts.com/blog/the-superpower-i-didnt-choose/#challenge-why-do-i-lose-my-train-of-thought-so-easily

What does split attention mean?

Split attention is the cost of holding two states in your head at once, such as what you were doing before an interruption and what just appeared on top of it. It costs some people, including those with ADHD, more than others, and the fix is a design that avoids forcing that split in the first place.

🎓 Lesson

• ADHD: Split attention costs you more than it costs most people, because holding two states at once competes for the same attention.
• Others: The fix is the same for you: a design that never forces the split in the first place.

Read more: https://danstolts.com/blog/the-superpower-i-didnt-choose/#what-what-design-rule-keeps-hidden-state-from-costing-you-your-place

Modal and Panel Design

Why do side panels reset their width every time?

Side panels that reset their width are treating that width as a throwaway render detail instead of data worth saving. That costs every user a small tax, and it costs a user who cannot afford to redo the setup even more.

🎓 Lesson

• ADHD: A panel that forgets its width asks you to redo work you already did, every single visit.
• Others: Persisting that state removes a small, real tax for you too, even if you can tolerate paying it.

Persisting panel width, scroll position, and open-or-closed sections removes that tax for everyone, not only the person who feels it hardest. Read more: https://danstolts.com/blog/the-superpower-i-didnt-choose/#bottom-line-what-should-you-change-starting-tomorrow

ADHD, Memory, and Context

Do people with ADHD need reminders?

Yes, reminders help, but they are not the full fix, because they still ask you to manage your own memory. That memory-management step can fail under interruption, which is exactly when you need it most.

🎉 Tip: Building a system that remembers for you is not giving up, it is a design decision you can make with confidence. You can set that memory up once and let it do the holding on for you.

The more durable fix is a system that remembers what changed and what you were doing, so you do not have to rebuild that context yourself. Read more: https://danstolts.com/blog/adhd-capture-memory-before-it-is-lost-how-to/

What is context switching ADHD?

Context switching is the cost of moving your attention from one task or state to another and then having to reconstruct where you were. For someone with ADHD, that reconstruction fails more often, which is why a tool that preserves state across the switch removes the cost instead of just managing it.

🎓 Lesson

• ADHD: Reconstructing where you were after a context switch fails more often for you, which is why the state should be saved, not remembered.
• Others: A tool that preserves state across the switch removes the cost for you too, instead of just asking you to manage it.

Read more: https://danstolts.com/blog/adhd-as-an-operating-advantage/

Dyslexia and Typing

Why do I keep typing letters in the wrong order?

Typing letters in the wrong order is usually dyslexia, not a mistake you made on purpose. Dyslexia makes certain letter pairs easy to swap, which turns into a design problem whenever a mistyped field can lock you out.

🎓 Lesson

• ADHD: Swapping letter pairs when you type is dyslexia at work, not a mistake you are making on purpose.
• Others: Checking entered values for those swappable letters catches it before it becomes a locked door for you too.

Checking entered values for those swappable letter-pairs catches the mistake before it becomes a locked door. Read more: https://danstolts.com/blog/the-superpower-i-didnt-choose/#why-why-does-designing-for-the-adhd-cost-make-every-user-s-experience-better

ADHD as a Strength

How is ADHD considered a superpower?

ADHD becomes a superpower when you treat its real cost as a design constraint instead of a workaround to hide. That shift turns personal experience into the sharpest available test for whether a design actually works, because a pattern that breaks your flow will break other people’s flow too, even when they never report it.

🎉 Tip: Your own ADHD cost can be the sharpest design test in the room. You already have that test running, so trust it the next time a pattern feels off.

The step is to write what breaks your flow down as a rule everyone must follow, not a private workaround you keep to yourself. Read more: https://danstolts.com/blog/adhd-as-a-superpower/

Accessibility Practice

What is an accessibility audit?

An accessibility audit usually checks a finished design against a compliance checklist, for a hypothetical user, after the real design decisions are already made. That timing means the problems it catches were already locked in before anyone really felt them.

🎓 Lesson

• ADHD: An audit that checks a finished design against a checklist comes too late for you, after the decisions are already made.
• Others: Designing from a cost someone in the room actually feels catches the same problem sooner, for you as well.

Designing from a cost someone in the room actually feels, instead of auditing for it afterward, catches the same problems sooner. Read more: https://danstolts.com/blog/series/adhd-superpower/