What Stage Fright Can Teach Developers About Procrastination
You've built the project before. You know the tools. The readme is written. Everything is ready to go—and somehow you're 40 minutes into reorganizing desktop folders.
Often, this isn't a productivity problem or a discipline problem. It's a nervous-system problem. And once you understand what's actually happening in your body, the fix becomes obvious.
The Real Reason You Procrastinate
Here's the thing your brain doesn't tell you: when a project transitions from abstract planning to live execution, your nervous system registers a threat. Planning is private. Shipping is public. And the moment something becomes public, it becomes vulnerable to judgment.
For many people, high-visibility work triggers the same threat-detection systems involved in stress and uncertainty. The mundane chores your brain sends you toward aren't random. They're brilliant defense maneuvers. They offer completion (a quick dopamine hit), physical control, and a socially acceptable excuse to stay away from the screen.
Your conscious mind narrates this as "I just need to get organized first." Your nervous system is actually saying: "Not yet — too exposed."
The desk isn't safer because it's productive. It's safer because nothing can reject you there.
What Elite Speakers Do Backstage
Performers at major venues face a massive chemical cascade right before walking onstage. The brain's threat-detection networks often respond to public performance as if something important is at stake, flooding the body with adrenaline and cortisol.
The ones who freeze get shaky voices, mental blocks, and a constricted presence. The ones who've learned the override do something that looks almost irrational: they move.
Channel the surge: Running onto stage, pacing, or high-energy movement helps the body metabolize stress hormones and channel the surge into action.
Relabel the chemical state: Fear and excitement are physiologically almost identical. Physical movement gives the brain evidence to re-tag the surge as anticipation rather than panic.
Override passive mode: Standing still leaves the nervous system in a defensive crouch. Intentional motion shifts you into an active, dominant posture — you're moving through the environment, not reacting to it.
Your Screen is a Stage
The gap between "I have everything I need to ship this" and actually shipping it isn't intellectual. It's physical. The friction you feel before launching a project, opening a pull request, or sending that post — that's a developer's version of stage fright.
The project becomes threatening not because the work is hard, but because it introduces judgment, uncertainty, possible failure, and even the pressure of potential success. You are stepping out of the safety of control and into the vulnerability of exposure.
Waiting for the anxiety to pass by sitting quietly at your desk doesn't work. The body doesn't discharge nervous energy through stillness; it discharges it through motion. In other words: stop negotiating with the resistance and start moving.
The solution is almost embarrassingly simple:
When you catch yourself doing busywork, don't fight it mentally. Stand up. Walk briskly — outside if possible. Do 20 pushups. Anything with forward physical momentum. Then return to the keyboard while that wave is still moving.
This works because of how our visual system connects to our stress response. When you move forward through space, the visual stream passing your eyes — called optic flow — provides sensory evidence to your brain that you are progressing rather than trapped. Emerging research suggests that optic flow may help reduce perceived threat and defensive responding.
You return to the screen chemically different — not because you reasoned your way out of the freeze, but because you moved your way out of it.
The Practical Takeaway for Builders
The next time you find yourself on your fourth "quick" Slack check or tidying your workspace before starting the actual work, recognize it for what it is. Not weakness. Not laziness. Just biology.
Your nervous system is running an ancient protection script. You can reason with it all you want — or you can just go for a short walk and come back as someone different.
Most procrastination isn't resistance to the work. It's resistance to the exposure that comes after the work.
The code will be the same. You won't be.
TL;DR
Planning is private. Shipping is public. Pre-execution busywork is often a freeze response to anticipated emotional exposure, not laziness.
The desk feels safe because it offers total control; shipping introduces vulnerability and judgment.
Elite performers discharge stress by moving to help the body metabolize stress hormones and relabel the internal surge as excitement.
Optic flow (moving forward through space) provides visual evidence of progression. Emerging research suggests it may help reduce perceived threat and defensive responding.
The fix is physical, not mental — move your body to reset your nervous system, then open the IDE.
Top comments (5)
Thank you for this:
The Real Reason You Procrastinate
Here's the thing your brain doesn't tell you: when a project transitions from abstract planning to live execution, your nervous system registers a threat. Planning is private. Shipping is public. And the moment something becomes public, it becomes vulnerable to judgment.
For many people, high-visibility work triggers the same threat-detection systems involved in stress and uncertainty. The mundane chores your brain sends you toward aren't random. They're brilliant defense maneuvers. They offer completion (a quick dopamine hit), physical control, and a socially acceptable excuse to stay away from the screen.
Your conscious mind narrates this as "I just need to get organized first." Your nervous system is actually saying: "Not yet — too exposed."
This is a fascinating reframing of procrastination. The distinction between resisting the work and resisting the exposure that comes after the work gives a much more nuanced explanation for why we can be fully prepared to ship something and still find ourselves doing everything except the thing that matters.
A few ideas especially stood out:
“Planning is private. Shipping is public.” That distinction captures a major source of friction. Planning preserves control and possibility; execution introduces judgment, uncertainty, and the possibility of being wrong.
Busywork can be a protective behavior. Reorganizing folders, checking Slack, or tweaking the workspace can look like procrastination, but they also provide immediate completion and restore a sense of control without requiring exposure.
The desk isn't necessarily the safe place because it's productive. It's safe because nothing at the desk can reject the work. That is a subtle but powerful way to understand avoidance.
Stage fright is a useful analogy for developers. A pull request, launch, demo, or public post can function psychologically like stepping onto a stage. The technical ability may already be there; the nervous system is reacting to what becomes possible once the work is visible.
Movement changes the intervention. Instead of endlessly trying to reason yourself into action, the article suggests changing the body's state first. That shifts the question from “How do I convince myself to start?” to “What can I do physically to interrupt the freeze?”
Fear and excitement can share physical signals. The idea of relabeling the physiological surge is particularly interesting because it suggests that the sensations themselves don't necessarily determine the emotional interpretation we give them.
Optic flow adds an intriguing layer. Moving through space while experiencing forward visual motion may provide the brain with sensory evidence of progress. The article appropriately frames this as an emerging area rather than treating it as settled science.
The real trigger may be vulnerability, not difficulty. Sometimes the project isn't technically challenging at all. What makes it difficult to begin is knowing that the finished result can now be evaluated, criticized, accepted, rejected, or ignored.
“The code will be the same. You won't be.” That ending works because the intervention isn't about making the task objectively easier. It's about changing the state from which you approach the task.
The broader takeaway is compelling: procrastination sometimes needs to be treated less like a character flaw and more like a state-management problem.
When the work is already understood but action still feels strangely difficult, changing the body's state may be the missing step. Sometimes you don't need another productivity system—you need to get out of the chair.
The line "planning is private, shipping is public" names something a lot of developers feel but rarely say out loud. It also explains why the busywork is so specific: reorganizing folders offers completion and control with zero chance of being judged. Seeing that as avoidance of exposure, not laziness, is a kinder and more accurate frame than "I lack discipline."
The practical advice is easy to try, and I think it works even if you set aside the optic flow explanation, which is still an early-stage idea. Brisk movement reliably changes how people feel, and a short walk breaks the loop of sitting in a low-grade freeze. I'd treat the mechanism as a plausible hypothesis and the walk as a cheap experiment you can run on yourself.
One addition: pair the movement with shrinking the first step. Stage fright usually spikes at the moment of exposure, so the fix isn't only discharging energy but lowering the stakes of the first action. Open the file and write one ugly function, push to a draft PR, or share the post with one trusted person before the full audience. Getting one small piece "public" in a low-risk way often takes the charge out of the bigger launch.
I'd also add a caveat. If avoidance is constant, or comes with persistent dread, exhaustion, or trouble functioning, it can be more than a shipping-day nervous system quirk, and talking to a professional is worth it. For the ordinary "fourth Slack check" version, though, this is a useful reframe.
Thanks for a practical and humane piece. "The code will be the same. You won't be." is a great closer.
This is such a brilliant reframing of procrastination—I love the idea that the screen becomes a stage the moment planning turns into public execution.
The distinction between “planning is private” and “shipping is public” is incredibly sharp, because it explains why someone can be fully prepared and still mysteriously avoid pressing publish.
The connection between busywork and perceived safety really clicked for me; reorganizing folders suddenly looks less like laziness and more like an attempt to regain control.
The practical shift from mentally negotiating with resistance to physically moving through it is refreshingly actionable, especially the “move, then return to the keyboard” approach.
The optic-flow angle adds another fascinating layer: sometimes the fastest way to change your relationship with the work is literally to change what your body is doing first.
And that closing line is fantastic—the code may be exactly the same, but after moving through the fear of exposure, you’re no longer approaching it from the same nervous-system state.
It was so worth reading this essay thank you for sharing here!