OLD SCRIPT DETECTED
Try this response:
“Attention residue is real, so I budget time for it and speak about it instead of pretending it doesn't exist.”SEE THE PRACTICE
THE THOUGHT
“I should be able to switch tasks instantly without losing focus”
YOUR RECORDED RESPONSE
“Attention residue is real, so I budget time for it and speak about it instead of pretending it doesn't exist.”
ONE PRIVATE MOVE
Pick one interruption from today or yesterday. Calculate: the actual task (5 min), plus the mental refocus afterward (10-15 min). That total time is real recovery, not wasted time. Note it in a calendar or text file as 'context-switch + recovery.' Repeat this three times over a…
SCENE_01
You're twenty minutes into deep work—notes spread across your desk, the problem finally starting to untangle. A Slack thread bubbles up: a teammate needs clarification on your code before they can unblock their own task. You switch tabs, answer in five minutes, switch back. The notes are still there. Your brain isn't.
SCENE_02
You spend the next sixty minutes retrieving what you were holding—rereading your own comments, reconsidering the design. It feels wasted. The Slack interruption wasn't an emergency; it was someone else's schedule spilling into yours. Now you're behind, and staying late feels like the price of admitting you couldn't protect your own time. That's the real failure: not the meeting itself, but your inability to say the day is structured for collaboration, not for you alone.
SCENE_03
Attention residue is physical—it takes roughly twenty-three minutes for your mind to resettle on a new task. That's not laziness or poor planning; it's how human focus works in a connected world. Instead of resenting the time lost, name it: 'I've got a context-switch ahead. I'll buffer ten minutes after this call before reopening deep work.' When you schedule recovery time and speak about it plainly, the fragmented day stops feeling like your failure and starts looking like what collaborative work actually is.
TRACE · 01/04
SOURCE_LOCATED · 02/04
The Context-Switch Guilt
Interruptions mean I'm not in control of my time, and not being in control is failure. A day without deep work is a wasted day, no matter what else I built.
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
“I should be able to switch tasks instantly without losing focus”
I say
“Attention residue is real, so I budget time for it and speak about it instead of pretending it doesn't exist.”
Then I do one thing
Pick one interruption from today or yesterday. Calculate: the actual task (5 min), plus the mental refocus afterward (10-15 min). That total time is real recovery, not wasted time. Note it in a calendar or text file as 'context-switch + recovery.' Repeat this three times over a…
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
No. Attention residue is how the human brain transitions between unrelated tasks under real-world conditions. It's not evidence of weakness; it's a known mechanism. Accounting for it in your schedule is the move that works, not pretending it doesn't exist.
Some interruptions are necessary—that's collaborative work. The thought assumes you *should* be able to refuse all of them instantly without friction. In practice, a team's work sometimes genuinely needs your input. The move is being clear about which interruptions are optional and which aren't, then budgeting recovery time after the real ones.
It can prove you care, but it also proves you're treating collaboration as a personal debt instead of a job requirement. The alternative is to count interruptions as legitimate work hours and schedule recovery time during the day, so staying late isn't the price of helping someone else.