The Calendar as ScoreboardYou open Monday's calendar and count the blocked squares before you count anything you actually built. A 30-minute standup and a 45-minute planning call look like two lost hours, so you quietly write the day off as a bad one before it starts, even though nothing has happened yet.
OLD SCRIPT DETECTED
“Meetings are killing my productivity”
Try this response:
“A meeting and a shipped feature aren't competing for the same scoreboard.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Meetings are killing my productivity”
YOUR RECORDED RESPONSE
“A meeting and a shipped feature aren't competing for the same scoreboard.”
ONE PRIVATE MOVE
Tonight, look at tomorrow's calendar and write next to each meeting one thing it's actually deciding or unblocking.
The Two Hours That Vanished After the 10am Standup
Why the Next Hour Feels Broken TooThe drag you feel isn't only the meeting itself. Part of your attention stays parked on whatever the meeting raised, so the coding you resume afterward moves slower than it would on a clear morning. That lag gets misread as proof the meeting itself erased an hour of output, when it actually cost you a slower re-entry.
Testing the Scoreboard for One WeekTonight, look at tomorrow's calendar and write down, next to each meeting, one thing it's actually deciding or unblocking. At day's end, jot how long it took to feel back in the code after each one. One week won't prove the myth wrong, but it will show you whether the loss is the meeting or the reentry.
TRACE · 01/04
How this script runs you
- You open your calendar every Monday and count the blocked hours before you count anything you actually shipped.
- After a status meeting runs ten minutes long, you cancel your lunch walk because you feel you owe the day extra coding to make up for it.
- You start declining optional design reviews entirely, telling yourself it's the only way to protect any real output at all.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Context-Switch Guilt
If a block on your calendar isn't spent producing code, it counts as a loss against your worth as an engineer, no matter what the meeting actually accomplished or unblocked for the team.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- A meeting and a shipped feature aren't competing for the same scoreboard.
- I plan for the slow twenty minutes after a meeting instead of expecting to snap back instantly.
- Some days are built for coordination. That's not a wasted day, it's a different kind of work.
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
“Meetings are killing my productivity”
I say
“A meeting and a shipped feature aren't competing for the same scoreboard.”
Then I do one thing
Tonight, look at tomorrow's calendar and write next to each meeting one thing it's actually deciding or unblocking.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Meetings are killing my productivity". 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 the meeting hour count as an hour of lost coding, full stop?
The meeting occupies the hour, but the coding loss you feel afterward is mostly the re-entry lag, not the meeting time itself. Counting only the calendar block skips the part you could actually shorten.
What if I genuinely ship less on days with three or more meetings?
That can be true and still not mean meetings are the enemy. A day built around coordination produces different output than a day built around solo coding; measuring both by the same yardstick will always make the meeting-heavy day look like a failure.
Should I just decline every meeting that isn't strictly mandatory?
Blanket declining trades one distortion for another: it treats all meetings as equally worthless instead of testing which ones actually cost you re-entry time and which ones you barely notice losing.
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