OLD SCRIPT DETECTED
“I felt guilty for being interrupted and not staying focused”
Try this response:
“Recovery time after switching tasks is real. I can plan for it instead of pretending it doesn't cost anything.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“I felt guilty for being interrupted and not staying focused”
YOUR RECORDED RESPONSE
“Recovery time after switching tasks is real. I can plan for it instead of pretending it doesn't cost anything.”
ONE PRIVATE MOVE
When you're interrupted today, name it: write down what the interruption was, whether it was actually necessary, and whether you would make the same call if someone else asked. Do not stay late to recapture that time. Notice whether the day still counts as a work day.
The Three Pings That Meant You Wasted the Morning
Deep in it, until the notification lights up
You're forty minutes into real work—the kind where your editor scrolls past and you stop counting lines. A Slack notification. Then another. Then a calendar invite for right now. You see the meeting title and your stomach tightens. Not anger yet, just a cold certainty: the day is about to be taken from you. You join the video call, your mind still half in the problem you were solving.
The math that doesn't add up until evening
The meeting was thirty minutes. But at 5 p.m. you're still here, still looking for the thread you lost. You order dinner to the desk. By 8 p.m., you've finally got something to show for the day—but it's code you would have written by 2 if no one had interrupted. The interruptions cost you three hours of real work. Except you spent three additional hours trying to get it back. The guilt isn't about the meeting. It's about the fact that you couldn't just move on.
One interruption you actually name as collaboration
Tomorrow, your colleague asks a real question in Slack. You help. It takes eight minutes. Instead of resenting the context switch, you write it down: 'Helped unblock Chen's deploy. This was necessary.' No guilt. No phantom recovery hours. Just a day that included both deep work and the work of knowing other people need things too. It turns out that's not failure. That's how teams actually work.
TRACE · 01/04
How this script runs you
- You resent the people who interrupt you, even when their question is legitimate, because you cannot separate the interruption from the feeling that you've failed to protect your own time.
- After being pulled into a meeting or a Slack thread, you spend the next hour unable to restart on your original task, and you count those hours as wasted no matter what else you accomplished.
- You stay late or work weekends to compensate for the interruptions, treating the collaborative parts of your day as time you need to steal back instead of time you planned for.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Context-Switch Guilt
If I can't protect myself from interruptions, I'm not in control of my work. And if I'm not in control, then fragmented days prove I'm failing. Everyone else manages to get deep work done, so the interruptions reveal something broken about how I organize time.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Recovery time after switching tasks is real. I can plan for it instead of pretending it doesn't cost anything.
- A day that includes collaboration isn't a day I lost to interruptions—it's a day with both types of work in it.
- The interruption isn't proof I failed. How I respond to the interruption is the part I actually control.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“I felt guilty for being interrupted and not staying focused”
I say
“Recovery time after switching tasks is real. I can plan for it instead of pretending it doesn't cost anything.”
Then I do one thing
When you're interrupted today, name it: write down what the interruption was, whether it was actually necessary, and whether you would make the same call if someone else asked. Do not stay late to recapture that time. Notice whether the day still counts as a work day.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "I felt guilty for being interrupted and not staying focused". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
Why does an interruption feel like personal failure when interruptions are part of collaborative work?
The thought isn't really about the interruption itself—it's about losing control. When you can't predict or choose when you're interrupted, it feels like a threat to your competence. But competence isn't the same as uninterrupted focus. It includes managing transitions well.
If attention residue is real and takes 23 minutes to clear, doesn't that prove the interruptions genuinely cost me hours?
Attention residue is real, but 23 minutes of recovery is not the same as three hours of wasted time. If you plan for the recovery instead of treating it as evidence of failure, you can work within reality instead of resenting it.
What counts as proof that a fragmented day isn't automatically a failure?
A single day where you acknowledged an interruption as legitimate, took the recovery time you needed without guilt, and still shipped something meaningful. One day like that is enough to question whether interruption always equals failure.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Productivity Variations Among Software Developers and Teams: The Origin of 10x — McConnell, Construx, 2020
- The SPACE of Developer Productivity — Forsgren, Storey, Maddila, Zimmermann, Houck & Butler, ACM Queue, 2021
- Burnout in software engineering: A systematic mapping study — Tulili, Capiluppi & Rastogi, Information and Software Technology, 2022
- Two Sides of the Same Coin: Software Developers' Perceptions of Task Switching and Task Interruption — arXiv, 2018