Someone asks me a quick question. Thirty seconds to answer. Should be nothing.

But now I’ve lost where I was. The mental state I spent 45 minutes building is gone. I stare at my screen trying to remember what I was doing, why I was doing it, and what comes next. Twenty minutes later, I’m maybe back to where I was. If I’m lucky.

Research says the average context switch costs 23 minutes of recovery time. For ADHD brains, I’d double that. We have less working memory to hold our place, more difficulty filtering out the interruption, and weaker internal cues to guide us back.

TL;DR

The problem: Context switches destroy focus and cost massive recovery time Best defense: Prevent switches by batching, protecting focus time, and building routines Best recovery: Written breadcrumbs, immediate capture, ritual re-entry Key insight: You can’t prevent all interruptions, but you can reduce the damage

Why Context Switching Hits ADHD Harder

Every task requires mental setup. You need to load the relevant information, remember where you were, understand what comes next, and filter out everything else.

Neurotypical brains do this in the background. ADHD brains do it manually. Each context switch forces us to consciously reconstruct what should be automatic.

Working memory overload. We can’t hold the old task while processing the new one. The old task gets dumped.

Re-engagement is harder. Getting into a task takes ADHD brains longer. We don’t just lose the context, we lose the momentum that took half an hour to build.

Attention residue. Part of our attention stays on the interruption. “Did I answer that correctly? What if they have a follow-up question?” The task changes but our brain is still processing the old context.

Executive function tax. Deciding what to focus on requires effort. Each switch forces another decision, draining already-limited executive function resources.

The Hidden Cost of “Quick” Interruptions

My coworkers think they’re asking for 30 seconds. They’re actually asking for 30 minutes.

Even if I answer the question quickly, here’s what happens:

1. I lose my mental state (instant)
2. I process their question (30 seconds)
3. I answer (30 seconds)
4. I try to remember what I was doing (2-5 minutes)
5. I rebuild the mental context (10-20 minutes)
6. I’m finally back to full focus (if nothing else interrupts)

This isn’t dramatics. This is the actual math of my attention. Each “quick question” costs half an hour of productive work.

Strategy 1: Prevent Switches Before They Happen

The best context switch is one that doesn’t happen.

Batch Similar Tasks

Instead of email-work-email-work-email, do all email at once. Process all communication in one block. Then switch to deep work.

My batches:

• Morning: Process yesterday’s messages (email, Slack, texts)
• Late morning: Deep work session (one project only)
• After lunch: Meetings (clustered when possible)
• Afternoon: Second deep work session
• End of day: Tie up loose ends, prep tomorrow

This isn’t perfect. Unexpected things happen. But the structure reduces switches from dozens to maybe 4-5 major ones per day.

Protect Focus Time

I block my calendar for focus time. 2-3 hour chunks labeled “Do Not Book.”

During those blocks:

• Slack goes to Do Not Disturb
• Phone goes face-down
• Email tabs get closed
• If possible, I work somewhere physically separate

People get used to delayed responses. The ones who don’t weren’t respecting my time anyway.

Design Your Environment

Same place for same work. I do deep work at my desk. Email happens on the couch. The physical location becomes a context cue. Less mental energy spent on “what am I supposed to be doing here?”

Visible cues. I have a small sign on my desk: “FOCUS MODE - Return at 2pm.” It redirects in-person interruptions.

Headphones always. Even without music, headphones signal unavailability. Plus, noise-canceling reduces auditory distractions.

Strategy 2: Minimize Damage When Switches Are Forced

Some interruptions are unavoidable. Kids, bosses, emergencies, biological needs. The goal shifts from prevention to damage control.

Leave Breadcrumbs Before Switching

When interrupted, take 15 seconds to write down:

1. What you were doing
2. What you were about to do next
3. Any details you’ll forget

I keep a sticky note on my desk that says “WHEN INTERRUPTED, WRITE HERE FIRST.”

Example breadcrumb: “Writing the ‘recovery strategies’ section. Next: cover the breadcrumb technique. Current paragraph: context switching for meetings.”

This note is the rope back to where I was. Without it, I spend 20 minutes reconstructing what 15 seconds could have captured.

Capture the Interruption Completely

If someone asks a question that will stick in my brain, I write down my answer AFTER I give it verbally. This clears the “attention residue.” My brain knows the answer is stored somewhere and can let go.

If I can’t resolve the interruption immediately, I capture it: “Follow up with Sarah about budget numbers tomorrow.” Now it’s in my task system instead of my working memory.

Acknowledge the Cost

Don’t pretend the switch was free. If someone says “sorry for the interruption,” I say “no worries, I’ll need about 20 minutes to get back on track.”

This isn’t passive-aggressive. It’s honest about ADHD. And it sometimes makes people think twice before interrupting next time.

Strategy 3: Rebuild Context Faster

After an interruption, you need to reload the mental state. Here’s how to do it faster.

Re-Entry Rituals

Instead of staring at the screen hoping context returns, build a ritual:

1. Read your breadcrumb. (This is why you wrote it.)
2. Read the last paragraph/section you wrote. Scan, don’t analyze.
3. Ask: “What was I about to do next?” Your breadcrumb should answer this.
4. Start typing/working immediately. Even if it’s garbage. Movement rebuilds momentum.

The whole ritual takes 2-3 minutes. Without it, reconstruction takes 10-20.

The “Where Was I?” Note

I keep a dedicated “Where Was I?” document open during deep work. Every 15 minutes, I update it with one sentence:

• “11:15 - Working on the section about email batching”
• “11:32 - Finished email section, starting calendar protection”

If interrupted, this document is my map back. If not interrupted, it also helps with time blindness. I can see what I actually did versus what I thought I did.

Momentum Starters

Sometimes context won’t reload. You stare at the work and nothing clicks.

Try these:

• Re-read the last 2-3 paragraphs out loud. Auditory processing can trigger memory.
• Scroll through the whole document. Visual scanning sometimes rebuilds context.
• Start with something tiny. “I’ll just fix this one typo.” Small actions can restart the engine.
• Take a 5-minute walk first. Movement clears the attention residue from the interruption.

Strategy 4: Meetings (The Worst Context Switch)

Meetings destroy context like nothing else. You leave your work, enter someone else’s mental space, contribute for 30-60 minutes, then return to work with no idea where you were.

Pre-Meeting Protection

Before any meeting:

1. Write a breadcrumb for current work
2. Clear any urgent tasks so they don’t distract you during the meeting
3. Have the meeting agenda ready (so you can mentally prepare)

Post-Meeting Recovery

After the meeting:

1. Take 5 minutes to capture action items from the meeting
2. Process any attention residue (things you’re still thinking about)
3. Read your breadcrumb
4. Do a physical transition (get water, stretch)
5. Then re-enter the work

I don’t go directly from meeting to deep work. There’s always a buffer.

Meeting Clustering

If possible, cluster meetings together. Back-to-back meetings are better than meetings scattered throughout the day.

4 meetings from 1-5pm = one context switch for “meeting mode” 4 meetings spread across the day = 8+ context switches

I protect mornings. Meetings go in the afternoon. Deep work happens when I’m freshest.

The Realistic Picture

I still lose hours to context switches every week. The strategies reduce the damage. They don’t eliminate it.

Some days, the interruptions win. Kids need something. The urgent email can’t wait. The meeting runs long. By 5pm, I’ve done four hours of “work” but maybe 45 minutes of actual deep focus.

Those days aren’t failures. They’re what happens when ADHD meets a world built for neurotypical attention.

The goal isn’t perfection. It’s improvement. Fewer preventable switches. Faster recovery from unavoidable ones. More total minutes in actual focus.

The Bottom Line

Every context switch costs ADHD brains more than it costs neurotypical brains. We can’t change that. We can only:

1. Prevent switches through batching, focus protection, and environment design
2. Minimize damage through breadcrumbs and complete capture
3. Recover faster through re-entry rituals and momentum starters

The 30-second interruption isn’t 30 seconds. The “quick meeting” isn’t quick. The context switch you prevent is worth more than the recovery technique you master.

Protect your focus like it’s expensive. Because for ADHD brains, it is.

---

I was interrupted 7 times writing this. Each time, I wrote a breadcrumb. It took 5 hours to write what should have taken 2.