OLD SCRIPT DETECTED
Try this response:
“Answering that question cost me a few minutes, not the whole doc.”SEE THE PRACTICE
THE THOUGHT
“Every interruption proves I can't protect my own time”
YOUR RECORDED RESPONSE
“Answering that question cost me a few minutes, not the whole doc.”
ONE PRIVATE MOVE
Next time you get pulled away, jot the start and end time of the interruption in a private note, then compare it to how much work you actually finished. Keep the note to yourself.
SCENE_01
You are three paragraphs into a design doc, the argument finally lining up, when a Slack notification slides across the corner of your screen. It is a teammate asking which endpoint handles refunds. You answer it in ninety seconds. Then you sit there, cursor blinking where you left off, and the thought arrives fully formed: "Every interruption proves I can't protect my own time."
SCENE_02
The doc stops being the thing you're building and becomes evidence you're gathering against yourself. You scroll back through the morning's tabs, tallying how many times you got pulled away, as if the number itself were the verdict. You start closing Slack between every paragraph, then reopening it out of a different fear, and the doc gets shorter passes each time you return to it, because half your attention is still on the tally.
SCENE_03
A more accurate read: the ping cost you the endpoint question and a bit of re-entry, not the doc. Open your calendar or a blank note and mark, in one line, how much of the doc actually got written today versus how much time the interruption itself took. The gap between those two numbers is usually smaller than the story you told yourself while counting.
TRACE · 01/04
SOURCE_LOCATED · 02/04
The Context-Switch Guilt
The hidden rule is: any interruption you didn't personally schedule counts as a failure to defend your time, even if it took ninety seconds and you chose to answer it. The thought treats a brief detour as if it erased the whole session, so a single ping gets to decide how the day is scored.
FORGING_REPLACEMENT · 03/04
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
When I think
“Every interruption proves I can't protect my own time”
I say
“Answering that question cost me a few minutes, not the whole doc.”
Then I do one thing
Next time you get pulled away, jot the start and end time of the interruption in a private note, then compare it to how much work you actually finished. Keep the note to yourself.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
Because the thought scores the day by the number of interruptions rather than the minutes they actually took. A short, answered question gets filed as a failure the same way a long derailment would, so the tally grows faster than the real cost does.
Timing the actual cost is useful; counting interruptions as a verdict on your discipline is not. The difference is whether the note tells you something concrete about your day or just adds to a running case against yourself.
Re-entry time is real and worth naming separately from the interruption. Writing down both the ping's length and the re-entry pass shows they're usually a fraction of the session, not proof the whole block was lost.