OLD SCRIPT DETECTED
“I should be able to say no to interruptions”
Try this response:
“Answering in ten minutes isn't refusing—it's finishing what I already opened.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“I should be able to say no to interruptions”
YOUR RECORDED RESPONSE
“Answering in ten minutes isn't refusing—it's finishing what I already opened.”
ONE PRIVATE MOVE
Set a ten-minute timer, mute one notification banner, and keep working on what you already had open—then check what's still true once it ends.
The Half-Second Before You Say "Sure, Now Works"
- 01 / The Ping Mid-Sentence
You're three lines into a function, still holding the shape of it in your head, when someone taps your shoulder or drops a message: "got a sec?" You haven't finished reading the question before your mouth or your keyboard has already answered. "Sure, what's up." You didn't decide that. It just happened, the way it always happens.
- 02 / Yes Now, Resent Later
The thought arrives late, after you've already said yes: I should be able to say no to this. But saying no in the moment feels like it costs more than just answering does—no awkward pause, no explaining yourself, no chance of looking unhelpful. So you take the question, lose your place, and the interruption ends fast and clean. That quick relief is exactly what makes the next person feel safe walking up ten minutes later, because you've never once made them wait.
- 03 / The Ten-Second Hold
There's a real gap between "got a sec?" and your answer, even if it's only a second wide. That's the place to work with, not the interruption itself and not the resentment afterward. Notice the reflexive "sure" forming before it leaves you, and try holding it for one breath. You're not deciding whether to help. You're deciding whether to answer now or in ten minutes.
TRACE · 01/04
How this script runs you
- You say "sure, one sec" before you've fully looked up from the screen.
- You rehearse a version of "not right now" in your head but never actually say it.
- You keep your status set to available because changing it feels like admitting you can't handle being asked.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Context-Switch Guilt
Turning down a request, even a small one, marks you as difficult or unreliable, so instant availability feels safer than giving a real answer that might be a no.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Answering in ten minutes isn't refusing—it's finishing what I already opened.
- I can say "give me a bit" without owing anyone an explanation for it.
- Being reachable every second isn't the same as being useful.
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 should be able to say no to interruptions”
I say
“Answering in ten minutes isn't refusing—it's finishing what I already opened.”
Then I do one thing
Set a ten-minute timer, mute one notification banner, and keep working on what you already had open—then check what's still true once it ends.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "I should be able to say no to interruptions". 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
Doesn't answering the interruption right away actually make it shorter overall?
It shortens that one exchange, but it also confirms you're reachable the instant someone asks, which is why the next interruption tends to arrive sooner rather than later.
What if the person interrupting genuinely needs an answer immediately?
Some do—but most "got a sec?" moments can survive a short, named delay. Reserving instant yeses for the requests that truly can't wait keeps the signal meaningful.
Won't holding my answer for even a few minutes make me look unavailable?
A specific delay reads differently than silence. Naming a return time, even privately to yourself first, is a decision people can work with, not a disappearance.
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