OLD SCRIPT DETECTED
“Being blocked means I'm slacking”
Try this response:
“I'm blocked on infrastructure, not capability. I flag it and grab the next clear task.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Being blocked means I'm slacking”
YOUR RECORDED RESPONSE
“I'm blocked on infrastructure, not capability. I flag it and grab the next clear task.”
ONE PRIVATE MOVE
Open your task list right now. Find one thing you're genuinely blocked on. Write a one-line note describing what's blocking it and what you'll work on instead. Close the list. Do not send it anywhere.
The Commit You Scheduled at 6pm to Prove You Weren't Waiting
- 01 / The Waiting Starts Midday
It's 2pm. Your PR sits in the review queue. CI is red on a flaky test that fails one in five runs. You're not stuck on logic; you're stuck on time—someone else's calendar, a third-party service, a branch protection rule. Intellectually, you know the next block of work is there, but reaching it requires patience, not effort. The thought arrives quietly: if I'm waiting, I'm not producing. If I'm not producing, I'm wasting the day.
- 02 / The Loop That Feels Like Progress
So you fill the gap. You refactor a function that works fine, polish a UI detail nobody requested, or—most telling—you reschedule that commit you finished hours ago to land at 6pm, after standup notes are gone. The relief is immediate: your Slack dot stays green, your calendar shows unbroken focus, the timestamp proves motion. You're not actually unblocked; you're just visible doing something. The short-term payoff is real: no one asks why you're quiet, no awkward standup explanation, no whisper of underload. The loop holds because the system rewards the appearance of continuous output, and you've learned the cost of looking idle.
- 03 / The Moment to Recognize and Redirect
Next time you feel the urge to manufacture work because a dependency is pending, pause and name it first: "I'm blocked on [specific thing]. I'm going to flag it and move to [next unblocked task] instead." Don't send it to anyone yet—just write it in your own log or task tracker. The act of naming breaks the loop. You've acknowledged the block without hiding it, and you've claimed agency over what you do next. Within three minutes, you've reset. The day is still there; the work doesn't disappear. What changes is that you stopped treating visibility as a substitute for judgment.
TRACE · 01/04
How this script runs you
- You reschedule a finished task to land after hours or after a meeting, banking the timestamp as proof of late effort rather than early completion.
- Waiting for a review feedback loop or a CI re-run makes you uneasy enough to start cosmetic work, not because the code needs it, but because silence feels like admission.
- You bundle a rushed fix into a PR because shipping fast feels safer than waiting for clarity, and cleanup can happen later—except it rarely does.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Presence Theater
A quiet hour is a confessional. If the system can't see me working right now, the default assumption is that I'm not. So I must always have visible output, even if it's less important than the work I'm waiting on. The appearance of productivity is the only reliable proof of productivity.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- I'm blocked on infrastructure, not capability. I flag it and grab the next clear task.
- Waiting is part of the work, not a gap in it. How I spend the gap is my call.
- The refactor I skipped today will cost me debugging time in three months. That's the real timeline I'm on.
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
“Being blocked means I'm slacking”
I say
“I'm blocked on infrastructure, not capability. I flag it and grab the next clear task.”
Then I do one thing
Open your task list right now. Find one thing you're genuinely blocked on. Write a one-line note describing what's blocking it and what you'll work on instead. Close the list. Do not send it anywhere.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Being blocked means I'm slacking". 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
If I'm blocked and I flag it, won't my manager think I'm not resourceful enough to unblock myself?
Blocking and resourcefulness are different things. You can be resourceful about investigating the cause while still being blocked on the resolution. Flagging it early is actually the resourceful move—it surfaces the dependency for whoever can resolve it, instead of letting you drown in make-work for hours.
But I've always shipped faster and gotten better reviews when I'm visibly doing something every hour. How do I know quiet time won't tank my reputation?
Reputation compounds over years, not hours. What tanks it is a pattern of shipping hasty work that breaks in production, or missing the actual dependencies that were blocking the right solution. Visible busyness that costs you sleep and produces technical debt is measurable damage; quiet blocks followed by clear work is a pattern that scales.
What if I get blocked multiple times in a day and there's genuinely nothing left to do—am I allowed to stop early?
That's a conversation with your context, not a character failure. If you're blocked on the critical path and there's no parallel work, say so. Some days the system creates waiting time. What you don't do is invent work to hide it. If stopping early feels impossible, that's worth noticing—it usually means the hidden rule runs deeper than productivity, and that's separate work.
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