Daniel sent us this one — he's parenting an eleven-month-old with his wife, no family nearby, no daycare, barely any babysitting, and he's finding that the context switching is destroying his ability to do deep work. He's treated on Vyvanse, mental health is solid, but the practical reality is that his brain gets pulled to another task and he can't pick up where he left off. He's asking for techniques — pragmatic, organizational, systems-level techniques — not therapy. And he specifically wants to know who even provides that kind of help, because general therapists keep treating the stress as psychological when the root problem is structural. I think this is one of those questions where the framing itself is half the insight.
It really is. And the first thing I want to name is that what he's describing isn't just context switching — it's the cost of re-entry after interruption. Those are two different things. Voluntary context switching, where you finish a task, stand up, get coffee, and deliberately move to the next thing — that's manageable. What he's living with is involuntary interruption-driven fragmentation, where your attention is yanked mid-thought. And for an ADHD brain, that distinction is everything.
Because when you choose the switch, your brain has time to save its state. When the baby cries, there's no save point.
There's a study from the University of California, Irvine — this was Gloria Mark's lab, two thousand five, and it's been replicated since — they found that after an interruption, it takes an average of twenty-three minutes and fifteen seconds for a neurotypical person to return to the original task. And that's not just twenty-three minutes of doing other things. That's twenty-three minutes of fragmented attention, partial re-engagement, false starts. For ADHD brains, the estimated resumption cost is forty to sixty percent higher. So we're talking thirty-five, forty minutes to fully reload your mental state after a two-minute interruption.
If you're getting interrupted every forty-five minutes — which, with an eleven-month-old, is optimistic — you literally never reach full re-engagement. You're perpetually in the loading screen.
The loading screen is the perfect metaphor. And what's happening neurologically is something called task-set reconfiguration. When you're doing deep work, your brain has assembled a specific attentional frame — it knows what's relevant, what to suppress, what the next three moves are. An interruption shatters that frame. Rebuilding it requires dopamine in the prefrontal cortex, and ADHD brains have baseline dopamine dysregulation. So every re-entry is more expensive, not because you're not trying hard enough, but because the neurochemical cost is structurally higher.
This is where I think the listener's frustration with therapy-first approaches comes in. You can't therapize your way out of dopamine depletion during re-entry. That's like trying to talk therapy your way out of a broken leg.
And I want to be careful here — therapy has its place, and for many people with ADHD the emotional layers are real. Shame, frustration, the feeling of constantly letting people down. But the listener is saying something specific: the organizational challenges are causing the downstream psychological stress, not the other way around. Treat the structure first. If you fix the re-entry cost, a lot of the overwhelm resolves because the overwhelm was a rational response to an impossible situation.
Let's start with what's actually happening in those twenty-three to forty minutes. You said task-set reconfiguration — break that down for me. What are the actual components of "where was I?
First, you have to remember where you were — literally, what was the last thing you typed, what file was open, what line of thought were you in. Second, you have to remember what you were about to do next — the intention that was forming right before the interruption hit. And third, you have to rebuild the attentional frame — the filter that tells your brain "this is relevant, that's noise." Each of those is a separate cognitive operation, and each one requires working memory. ADHD brains have working memory deficits. So you're trying to hold three fragile things in a system that's already bad at holding things.
The cruel part is, the more deeply you were engaged, the more state there is to lose. If you were surface-level answering emails, the re-entry cost is trivial. If you were three layers deep in a complex problem, the entire mental model collapses.
That's why the listener's co-workers describe him as someone who produces prodigious work in concentrated blocks. He's a deep-work specialist. And deep work is the most expensive kind of mental state to rebuild after interruption. It's like the difference between losing your place in a magazine article versus losing your place in a dense technical specification while you're mid-architecture-decision.
We've established the problem is real, measurable, and structural. Let's talk about the engineering approach. You mentioned something in our prep about a "state file" metaphor — like how programmers save context before a context switch.
In programming, when you're working on a feature and something urgent comes up, you run "git stash." That saves your current changes — not as a finished commit, just as a snapshot of exactly where you were — so you can switch to the urgent thing, then come back and restore your state exactly. Most knowledge workers don't have a git stash for their brain. And ADHD brains need one desperately, because we can't trust working memory to hold that state.
What does a brain git stash look like in practice?
The simplest version is what I call an externalized state file. Before you stand up from your desk — or ideally, the moment you sense an interruption coming — you capture three things: where you are, what you were about to do, and what the next action is. This can be a sticky note, a voice memo, a text file. The format matters less than the consistency. I know a software engineer parent who tapes a three-by-five card to their monitor. Left side says "where I was" — could be "line four hundred twelve of auth module, refactoring the token validation." Right side says "next three things" — "one, finish the error handling branch. Two, write the unit test. Three, merge to dev." When they come back after dealing with the baby, they don't have to remember any of it. They just read the card.
Because it offloads the most expensive part of re-entry — the remembering — onto an external artifact. You're not using your brain to store the state, you're using your brain to read the state.
There's good research behind this. A twenty twenty-two study in the Journal of Attention Disorders found that ADHD adults who used external memory aids — notes, alarms, voice memos — reduced task-switching errors by thirty-four percent compared to those who relied on internal memory alone. Thirty-four percent. That's not marginal. That's the difference between spending your workday in a fog of partial engagement and actually finishing things.
This also leverages something called the Zeigarnik effect — the tendency to remember interrupted tasks better than completed ones. The brain keeps pinging you about unfinished business. But if you write down exactly where you left off, the Zeigarnik tension releases. Your brain goes "okay, it's captured, I can let go.
The act of externalizing tells your brain the task is "handled" — not completed, but handled. The information is safe. You can stop the background loop of "don't forget, don't forget, don't forget.
Which, for someone with ADHD, that background loop is consuming dopamine the entire time it's running. So you're not just saving the state — you're stopping the resource leak.
Now, let's talk about the second piece, which is time architecture. The listener said he doesn't have concentrated blocks anymore. And the standard advice — "block off four hours of deep work" — is useless for a parent with an eleven-month-old. But the alternative isn't giving up on deep work. It's redesigning the blocks.
I've seen the Pomodoro technique suggested for this — twenty-five minute sprints. But I've always found that frustrating. By the time I'm actually deep into something, the timer goes off.
Pomodoro fails for ADHD deep work for exactly that reason. Twenty-five minutes is long enough to load the mental state but not long enough to use it. What works better is a forty-five minute sprint with a fifteen-minute re-entry buffer. The forty-five minutes is your actual work window — long enough to make meaningful progress. The fifteen-minute buffer is not a break. It's insurance. It absorbs the resumption cost if you get interrupted. And if you don't get interrupted, you roll that buffer into the next sprint or use it for low-cognitive tasks.
You're not scheduling four hours of work. You're scheduling three forty-five minute sprints across the day, each with a buffer, and you treat those sprints as sacred.
You align them with your medication window. The listener mentioned he's on Vyvanse. Vyvanse has a characteristic plasma concentration curve — it peaks around three to four hours after dosing, and the effective window for most people is about eight to ten hours, but the peak focus period is narrower than that. If you know your peak window — say, nine thirty AM to one PM — you put your highest-value forty-five minute sprints in that zone. You don't try to stretch coverage across the whole day. You concentrate firepower.
That's a military metaphor that actually works. You're not trying to hold the entire front. You're identifying the two or three engagements that actually matter and bringing everything to those.
The rest of the day, you do what I call "low-state work.Reading that doesn't require deep comprehension. Tasks where interruption doesn't cost you much because there's not much state to lose.
We've got the state file for capturing where you are, and we've got time-boxed sprints aligned with medication. But there's a third piece here that I think is crucial, which is the interruption itself. The listener can't control when the baby needs attention. But can he control how the interruption happens?
This is where an interruption protocol comes in. The idea is to pre-agree with your partner on signal levels for different interruption severities. Green means "I'm in shallow work, interrupt freely." Yellow means "I'm in a sprint, interrupt only if genuinely urgent." Red means "I'm in the final ten minutes of a sprint and trying to land the plane — interrupt only for blood or fire.
The key word there is pre-agree. You're not negotiating this in the moment while stressed and interrupted. The contract exists before the crisis.
And it has to go both ways — when your partner is in a yellow or red window, you respect it too. This isn't about one person's work being more important. It's about both people acknowledging that fragmentation has a real cost and trying to batch interruptions where possible.
There's also something here about context anchoring — using sensory cues to signal "I am now in deep work mode" even when the window is short. Because one of the problems with fragmented time is that your brain never gets the signal that it's time to focus.
Yes, and this is where you can hack your environment to do some of the work for you. Pick a specific playlist that you only play during sprints. Not background music you always have on — a specific album or playlist that your brain associates exclusively with deep work. Change the lighting — a desk lamp angled differently, a specific color temperature. Even something as simple as moving your chair to a different position. These are what I call "context anchors." They're external triggers that tell your brain "this is the mode now," and they work because ADHD brains are highly cue-dependent.
It's basically Pavlovian conditioning for your own prefrontal cortex.
I wouldn't have put it that way, but yes. And it works surprisingly fast. After about two weeks of consistent pairing — this playlist equals this mental state — the playlist alone starts to trigger the attentional shift. You're borrowing your brain's association machinery to shortcut the re-entry process.
Let's talk about the interruption taxonomy for a moment, because I think not all interruptions are created equal. The baby crying is one category. But there's also internal drift — you're working and suddenly you realize you've been researching something completely unrelated for fifteen minutes.
External interruptions — baby, partner, phone, doorbell — and internal interruptions — task drift, hyperfocus collapse, the sudden conviction that you need to reorganize your entire file system right now. External interruptions are harder for ADHD brains in a specific way: they violate what I call the dopamine contract. You were engaged, you were getting the neurochemical reward of progress, and then it's ripped away. Your brain doesn't just lose the state — it experiences a miniature withdrawal. That's why coming back feels so aversive. You're not just reloading information, you're overcoming a motivational deficit.
That explains something I've noticed but never had language for. When I'm interrupted mid-flow, I don't just forget what I was doing — I actively resent returning to it. The task that was engaging thirty seconds ago now feels repulsive.
That's the dopamine crash. And the fix isn't willpower — it's reducing the friction of re-entry to the point where the aversion doesn't have time to set in. If your state file is right there, and your context anchor is still playing, and you can resume in under thirty seconds, the motivational hit is much smaller. You're back in before your brain fully registers that it left.
The state file isn't just a memory aid — it's a motivational prosthetic.
That's exactly what it is. And this is why I keep coming back to the engineering frame. Every technique we're talking about is designed to make context switching cheaper. Not to eliminate it — you can't eliminate it with a baby in the house. But to reduce the per-switch cost from forty minutes to five. If you can do that, three interruptions a day costs you fifteen minutes instead of two hours. That's the difference between functional and drowning.
Let's get into some specific frameworks that already exist and can be adapted. The listener asked about organizational systems, and I know you've got opinions on GTD — Getting Things Done.
GTD has a principle called "next action" that's useful here. The idea is that for any project or task, you always identify the very next physical action required. Not "work on the report" — that's vague and requires your brain to do planning work before it can start doing actual work. Instead, "open the Q2 data spreadsheet and add the revenue column." That specificity matters enormously when you're re-entering a task. If your state file says "work on report," you come back and your brain has to figure out what that means. If it says "add revenue column to Q2 spreadsheet," you can execute immediately.
Because you've offloaded the planning to your past self, who had full context.
Past you, who knew what was happening, did the thinking. Present you, who is frazzled and contextless, just executes. It's a gift from your past self to your future self.
There's also the two-minute rule from GTD — if something takes less than two minutes, do it immediately rather than tracking it. But I wonder if that breaks down in an interruption-heavy environment. If you're getting interrupted every ten minutes, "do it now" might mean you never get back to the main task.
That's a good critique. The two-minute rule works when interruptions are occasional. When they're constant, you need a modified version: if it takes less than two minutes and it's related to your current sprint, do it. If it's unrelated, it goes in the parking lot.
The parking lot being?
A single notebook or digital note where you dump everything that's in your head when you're interrupted — every half-formed thought, every "oh I should remember to," every tangent your brain wants to chase. The rule is: nothing in the parking lot gets acted on during a sprint. It just gets captured. Your brain learns that it can let go of things because they're not lost — they're parked. This is particularly important for ADHD because the fear of forgetting is a major driver of internal interruption. Your brain interrupts itself because it's terrified the thought will evaporate.
Which it will.
Which it absolutely will. So you externalize the fear. The parking lot is a promise to your brain that nothing gets lost. You'll review it between sprints.
Let's talk about one more technique before we move to the practical implementation side — the "don't break the chain" method, adapted for this context. The original version is about doing something every day and marking it on a calendar. How does that work for sprints?
The adaptation is this: instead of tracking "did I do deep work today," which is binary and demoralizing when you fail, you track "did I complete my scheduled sprints this week." If you scheduled nine sprints across the week and you hit six, that's not a failure — that's data. You now know that in your current life configuration, six sprints a week is realistic. Next week you aim for seven. The chain is about consistency, not perfection. And the visual feedback of seeing the chain build is motivating for ADHD brains — it's external dopamine.
You're not trying to be the person who never misses a sprint. You're trying to be the person who knows their actual capacity and gradually expands it.
And this connects to something I want to emphasize: the goal here is not to eliminate context switching. It's to make it cheaper. If you can reduce your average resumption cost from thirty-five minutes to seven, you've effectively created an extra hour of productive time per day without changing anything about your schedule or your childcare situation. That's not "coping." That's an engineering win.
Alright, let's shift to the practical question of how to actually implement this when you're already overwhelmed. Because I think that's where a lot of advice falls apart. It assumes you have the executive function to set up the system in the first place.
This is the minimum viable system question. What's the absolute smallest thing you can do that still produces meaningful results? I think it's three things. One: a single sticky note on your monitor. Left side, where you are. Right side, next action. That's it. You do that every time you stand up or hear the baby monitor. Two: one forty-five minute sprint per day, aligned with your medication peak. Not three, not two — one. Prove to yourself that the system works before you scale it. Three: a parking lot — one notebook or one note on your phone. Everything goes there.
That's the onboarding ramp. You're not asking someone to overhaul their entire workflow. You're asking them to adopt three micro-habits that collectively reduce the cost of their biggest problem.
Once those three are stable — give it two weeks — you add the interruption protocol conversation with your partner. Then you add a second sprint. Then you experiment with context anchoring. You're building the system in layers, each layer making the next one easier because you're less cognitively depleted.
I want to talk about something the listener asked specifically: who provides this kind of help? Because he's right that general therapists often aren't equipped for it. The clinical training model treats everything through a psychological lens, and if you present with overwhelm, they look for the emotional root cause rather than the structural one.
The field he's looking for is ADHD coaching — specifically organizational skills coaching for neurodivergent professionals. This is distinct from therapy. Coaches don't diagnose or treat mental health conditions. They work on practical systems: time management, task initiation, environmental design, interruption management. The good ones understand the neuroscience but operate in the engineering domain.
There are actual organizations that credential these people?
The Attention Deficit Disorder Association — ADDA — has a directory of ADHD coaches. CHADD, which is Children and Adults with Attention Deficit Hyperactivity Disorder, also maintains one. There's also a growing field called executive function coaching, which is even more pragmatic — it focuses specifically on the organizational skills that ADHD undermines: planning, prioritization, working memory strategies, task initiation. Some of these coaches work remotely, which is relevant for the listener since he's an expat and might not have local options.
I'd also flag that some of the best ADHD coaching content is free. The YouTube channel "How to ADHD" has practical, systems-level content. The "Translating ADHD" podcast is run by two coaches who think in terms of mechanics, not therapy. Russell Barkley's work — he's a researcher, not a coach, but his framework for treating ADHD as a performance disorder rather than a knowledge disorder is foundational to this whole approach.
Barkley's key insight is that ADHD isn't about not knowing what to do — it's about not doing what you know. The knowledge is there. The performance system is what's broken. So you don't need insight — you need scaffolding. External structures that do what your internal executive functions can't reliably do.
Which brings us back to the listener's frustration with therapy. Therapy often aims at insight. He doesn't need insight. He needs a git stash for his brain.
There are two books I want to recommend that operate in this exact space. One is "Order from Chaos" by Jaclyn Paul — it's specifically about organizational systems for ADHD adults, written by someone who has ADHD and lives the reality. The other is "The ADHD Effect on Marriage" by Melissa Orlov, which is relevant because the interruption protocol we described is fundamentally a partnership negotiation. When both partners understand the neurological cost of interruption, the conversation changes from "you're not helping enough" to "how do we design our interruption patterns to protect both of our cognitive resources.
I also want to recommend something the listener can do starting tomorrow that costs nothing and requires no setup: time confetti mapping. For one week, every time you're interrupted, you jot down two things — what caused the interruption, and how many minutes it took you to fully re-engage. Not how long the interruption lasted — how long until you were back in the work.
This is powerful because it turns a vague sense of "I'm constantly interrupted" into data. And what you typically find is that eighty percent of your lost time comes from twenty percent of your interruption types. Maybe it's not the baby — maybe the baby interruptions cost you fifteen minutes total per day. Maybe it's your phone, or your own task drift, or the way you and your partner signal needs to each other. Once you have the data, you can target the expensive interruptions specifically rather than trying to fix everything at once.
The act of tracking itself can be revealing. You might discover that what you thought was a forty-minute re-entry was actually twelve minutes — or that it was ninety. The subjective experience of lost time is often wildly inaccurate. Data corrects the narrative.
There's a broader point here about the way we talk about ADHD and productivity. The dominant cultural narrative is that focus is a matter of discipline — that if you're struggling to context-switch, you just need to try harder or want it more. That narrative is not just wrong, it's harmful. It takes a structural neurological limitation and reframes it as a moral failing. What we're describing here is the opposite approach: acknowledge the structure, work with it, build systems that compensate for it. That's not weakness. That's engineering.
It's the difference between blaming the user and fixing the interface. If a piece of software crashes every time you try to switch tasks, you don't tell the user to switch more carefully. You fix the software. The state file, the sprints, the interruption protocol, the parking lot — these are all interface fixes.
I think there's a forward-looking dimension here too. The listener is in an unusually intense season of life — eleven-month-old, no childcare, no family support, two expats figuring it out alone. That season won't last forever. But the skills he's forced to develop right now — cheap context switching, externalized state management, ruthless prioritization — these are meta-skills that will serve him for the rest of his career. As remote work and caregiving continue to blend, the ability to context-switch efficiently is becoming a competitive advantage.
He's not falling behind. He's doing R and D on a problem most knowledge workers are going to hit in the next five years.
That's exactly the right reframe. The struggle is real, but it's also skill-building. Every time he writes a state file note before attending to the baby, he's training a muscle that most professionals haven't even identified yet.
Let's pull this together into a concrete set of takeaways. If you're the listener, and you're exhausted, and you can barely brush your teeth, what's the Monday morning version of all this?
One: build a resumption ritual. It's thirty seconds. When you're interrupted, you stand up, you say aloud what you were doing — literally out loud, the auditory encoding helps — and you write one sentence about where you left off. That's it. The ritual does two things: it externalizes the state, and it creates a clean psychological boundary. You're not being ripped away from your work. You're deliberately saving and stepping away. That reframe alone reduces the dopamine crash.
Two: do the time confetti mapping for one week. You don't have to change anything. Just track every interruption and its resumption cost. At the end of the week, you'll know exactly which interruptions are eating your life. Maybe it's Slack. Maybe it's the baby monitor placement. Maybe it's your own brain's tendency to drift toward news sites at hour three of the medication window. Whatever it is, you can't fix what you can't measure.
Three: create a parking lot. Everything goes there. Half-formed thoughts, random ideas, things you need to remember, tasks that aren't part of the current sprint. When your brain says "don't forget this," you say "it's in the parking lot" and you keep working. This one habit, by itself, can reduce internal interruptions by a noticeable margin within days.
If you want to go further — if you have the bandwidth to set up more — look into ADHD coaching. ADDA and CHADD both have directories. Search for "executive function coaching" specifically. The good ones work remotely, they understand the difference between therapy and systems design, and they can help you build the scaffolding that your brain needs but can't provide internally.
The books we mentioned — "Order from Chaos" by Jaclyn Paul and "The ADHD Effect on Marriage" by Melissa Orlov — are both worth your time. But I'd start with the three micro-habits and the one-week tracking. Don't try to implement everything at once. That's the fastest way to fail. Pick one thing, prove it works, then add the next.
The listener's core insight — that this is an organizational problem creating psychological effects, not a psychological problem creating organizational effects — is one of the most important distinctions in ADHD management. Most advice gets this backwards. Most advice assumes that if you process your feelings about being overwhelmed, the overwhelm will become manageable. The reality is usually the reverse: if you reduce the overwhelm through better systems, the feelings become manageable on their own.
That's the note I want to end on. The problem is real. It's not a personal failing. It's a structural challenge that responds to structural solutions. You don't need to fix your brain. You need to give your brain better tools.
Now: Hilbert's daily fun fact.
Hilbert: In the eighteen sixties, a pigment maker in the Solomon Islands discovered that mixing crushed coral with fermented coconut milk produced a vivid crimson dye — but only if the mixture was stirred exactly counterclockwise while chanting a specific guild verse. The color, known locally as "fire blood," was so prized that the guild's stirring chant was a closely guarded trade secret, passed only from master to apprentice on the winter solstice.
...right.
Here's the open question I want to leave listeners with. What happens when we stop treating fragmentation as a personal failing and start treating it as a systems design problem? Because the listener isn't broken — he's operating in an environment that his brain wasn't designed for, using tools that weren't built for his brain. The solution isn't to try harder. It's to redesign the interface.
If you're in a similar situation — parenting without a village, working in fragments, feeling like you're constantly falling behind — know that the skills you're forced to build right now are valuable. Cheap context switching, externalized state management, the ability to do meaningful work in forty-five minute windows — these are not consolation prizes. They're competitive advantages in a world that's getting more fragmented for everyone.
This has been My Weird Prompts. Thanks to our producer, Hilbert Flumingtop. You can find us at myweirdprompts dot com. If you found this useful, leave us a review — it helps other people find the show.
We'll be back next week.
