OLD SCRIPT DETECTED
“Staying late is how I reclaim the deep work I lost to meetings”
Try this response:
“Deep work is constrained by the calendar I inherit, not by my refusal to claim it.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Staying late is how I reclaim the deep work I lost to meetings”
YOUR RECORDED RESPONSE
“Deep work is constrained by the calendar I inherit, not by my refusal to claim it.”
ONE PRIVATE MOVE
Block one afternoon meeting (ask to reschedule or attend async). Write down what deep work actually fits in the remaining hours. Notice what stays undone—then skip staying late that day.
The 6pm recovery project
The 3pm interruption
Two meetings back-to-back knock out your afternoon. You close your laptop at 5:15, and the code review you promised yourself isn't started. That deep work—the kind where you need 40 minutes unbroken—is now tomorrow's problem. So at 6, after the office empties, you open the laptop again.
The hollowed evening
After three weeks of 6pm sessions, staying late feels like the only way to be a capable engineer. You skip dinner with a friend because 'tonight I finish the architecture docs.' Your evening isn't free time anymore—it's a second work shift where you pay the meeting tax. The real cost isn't tiredness. It's that your off-hours stop being yours.
The unopened code
One morning you arrive with a fresh idea for the module. You find yourself actually making progress before 10am—no meetings until noon. You stop at 11:30, realizing you're still building ideas, and the work feels complete without the evening rescue mission.
TRACE · 01/04
How this script runs you
- After meetings interrupt your flow, you calculate what deep work you can salvage after work hours.
- You guard your evening as non-negotiable work time to 'make up' for collaboration hours.
- Leaving the office by 6pm feels irresponsible because that work is still incomplete.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Context-Switch Guilt
If the workday gets fragmented by others, I'm obliged to carve out my own time to do 'real work.' Evening is my proof of competence.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Deep work is constrained by the calendar I inherit, not by my refusal to claim it.
- Meetings are a feature of my role. The cost of reclaiming time is paid by my personal hours.
- I can name which work requires deep time and which thrives on interruption.
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
“Staying late is how I reclaim the deep work I lost to meetings”
I say
“Deep work is constrained by the calendar I inherit, not by my refusal to claim it.”
Then I do one thing
Block one afternoon meeting (ask to reschedule or attend async). Write down what deep work actually fits in the remaining hours. Notice what stays undone—then skip staying late that day.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Staying late is how I reclaim the deep work I lost to meetings". 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
Isn't it true that some work genuinely needs unbroken time after meetings steal the day?
Yes—but 'after hours' isn't the only solution. The real question is which work actually needs unbroken time and which doesn't. Many tasks that feel like they need deep work are actually habit or avoidance. And even genuine deep work has options: shifting it to another day, breaking it into smaller pieces, or adjusting your meeting load, not your personal time.
What if my teammates expect me to be available during the day for collaboration?
They do—and that's real. But there's a gap between 'available for collaboration' and 'available on zero notice, any time.' Blocking focus time isn't selfish; it's naming the fact that you can't do both simultaneously. The alternative to 'I'll catch up alone at night' is 'I need protected afternoon time to deliver both collaboration and depth.'
If I don't stay late, won't the work just not get done?
Sometimes yes. But that's not evidence the thought is right—it's evidence that the workload or meeting culture needs to change. Staying late is a personal Band-Aid that masks a scheduling problem. It works in the short term and makes the problem invisible.
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