Red Light Fever

The paralysis of knowing it's blank right now — and that's OK.

Executive Summary

Red light fever is the paralysis that hits the moment execution has to start — whether that's a guitar solo, a blank Word document, or day one on a new job site. This piece walks through why it happens, borrowing from Kevin O'Leary's signal-vs-noise framing and Jeff Bezos's decision-energy habits, and lays out three practical ways back to motion: build real practices instead of chasing hacks, reframe the problem instead of grinding through it, and chase the part of the work you actually love, even out of order.


1 - The Red Light

As a musician, I've known the term "red light fever" for most of my life. You've rehearsed the part. You played it perfectly ten minutes ago, full of feel, full of confidence. Then someone hits record, the red light comes on, and you fall apart. Golfers know a version of it too — some of the best shots happen when a guy just walks up and swings, no time to think it to death.

Back in 2006, I was finishing a song I'd recorded almost entirely by myself — drums, bass, keys, every guitar part — because I wanted it to sound like a full band trading parts, not one guy overdubbing everything. I'd left the most important sixteen bars open on purpose: a lead solo I wanted to be the capstone of the whole track. I thought about it too much. I built it up in my head until it was too big to play. Take after take, I choked. I got frustrated, then more frustrated, and right at the edge of frustration turning into anger, something shifted. I stopped thinking. I turned the guitar up a little louder in the headphones and just played it. It's still one of the best solos I've ever recorded — because I finally got out of my own way.

That's red light fever. And if you've ever stared at a blank Word document, an empty project charter, or a code editor with a cursor blinking in an otherwise empty file, you already know the feeling. It isn't really about talent or preparation. It's about what happens the moment execution has to start.

2 - It Isn't Just Musicians

My work involves a lot of typing. I'm a software developer by trade, but I'm also equal parts project manager, UI designer, database builder, and business intelligence guy — Jack of all trades, master of a lot of them over time. When something lands on my desk, that's what it boils down to: a blank Word document, a blank template, a blank charter, an empty code editor, or tens of thousands of lines of someone else's code and no clear idea where to make the one change that needs to happen. That's red light fever for a knowledge worker.

Both of my sons work in the contracting trade, and they live a version of this too. You walk into a job, listen to what the customer needs, build the estimate, work it out with them, map the logistics, get the materials lined up — and you have a completely clear picture of what you're going to do and how. Then day one arrives. You've thought about this job for weeks, maybe months, and it is still hard to pick up the first tool and start. The blank wall doesn't care how good your plan is. It just needs the first cut to be made.

I think about the sports highlights I watch — Marshawn Lynch in beast mode, Bo Jackson, Barry Sanders, a quarterback pulling out a win from nowhere. Athletes who've been playing since they were kids in the backyard, and who still hit a moment where the whole thing is on them and they have to just go. Red light fever doesn't care how long you've been doing this. It shows up anyway.

3 - Why the Blank Page Hits Harder Than It Should

Part of what makes red light fever worse is that it rarely announces itself as fatigue. It shows up disguised as a difficult project, a scary blank page, a task you're apparently not in the mood for. But a lot of the time, it's simpler than that — you're just trying to do signal work in a noise window.

Kevin O'Leary tells a story about Steve Jobs that's stuck with me. Jobs defined "signal" as the three to five things that actually had to get done in the next eighteen hours — not the vision for the year, just today. Everything else was noise. O'Leary put Jobs at roughly 80 percent signal, 20 percent noise, and described Elon Musk going even further: close to 100 percent signal, zero noise, walking away from conversations the moment they stop being useful. That's an extreme most of us aren't built for and probably shouldn't chase. But the underlying idea is worth stealing: on any given day, only a handful of things are actually signal. The rest is noise wearing a work badge.

Assessment

The practical version of signal vs. noise isn't "do less." It's "know which hours you can trust." Jeff Bezos schedules mentally demanding meetings for 10 a.m. and avoids big decisions after 5 p.m., because his cognitive energy peaks in the morning and drains as the day goes on. "If I make three good decisions a day, that's enough," he's said — a line he borrowed from Warren Buffett. He isn't trying to do more. He's trying to protect the hours when his signal is actually strong enough to be worth trusting.

I know my own pattern now. My signal peaks early. That's when I plan and strike on the hard stuff — the writing that needs a real idea behind it, the code that needs to be right, the decision that's going to be expensive to unmake. Later in the day, when the noise has built up — meetings, interruptions, the general buzz of everything else that happened — I fall back to frameworks and checklists instead of trying to force fresh thinking I don't have anymore. That's not a discipline problem. It's an honest read of when the light is actually on for me.

4 - Motion Before Motivation

Todd Henry, who wrote The Accidental Creative, has spent his career studying exactly this moment — the gap between knowing what you need to do and actually doing it. His core argument cuts against how most of us were taught to think about inspiration: action makes ideas concrete, and it's the action that generates motivation, not the other way around. You don't wait to feel ready. You move, and the clarity shows up after, not before.

He also draws a line between hacks and practices. A hack gets you unstuck once. A practice is something you can return to every time the page is blank, because you built it on purpose instead of discovering it by accident under deadline pressure. I lean on templates for exactly this reason — a rough shape for a project charter, a structure for a piece of writing, a scaffold for a new piece of code. The templates start out as a lot of white space too. But white space inside a known shape is a very different kind of blank than a completely empty page. It gives you somewhere to put the first word.

Henry's other habit is reframing the problem instead of attacking it head-on — widening the frame, or looking at the same data from a different angle, until the block itself dissolves and a new way in appears. That's exactly what happens when the question shifts from "how do I finish this whole enormous thing" to something much smaller and much more honest: what's the one part of this I actually love?

5 - Chase the Thing You Love

That question is the tool I reach for most. When I'm genuinely stuck, I stop trying to work the project in order and I ask myself what the one thing is that's really pulling me toward it — the piece that has some fire in it. Then I start there. I'll open the paintbrush and go paint some happy little trees, Bob Ross style, in whatever corner of the work actually wants my attention, even if the rest of the plan says I should be somewhere else entirely.

As a programmer, the thing I love is the Rube Goldberg logic of a system — the delight of a chain reaction where a ball drops down a little ladder, hits a bird, the bird flies into a net, and the net trips the next thing. Whimsical, a little over-engineered, completely unnecessary to the deadline — and it's exactly where I find the energy that gets the rest of the project moving again. Sometimes that piece survives into the final work. Sometimes I throw it away entirely once it's done its job. Either way, it did its job — it wasn't wasted, because its whole purpose was to get me unstuck, not to ship.

You see this everywhere once you start looking for it. Picture someone tackling a new garden bed for the first time — soil tests, irrigation lines, companion-planting charts, a spreadsheet of bloom times. The planning alone is enough to keep the shovel in the shed all season. But that same person will happily lose an entire Saturday afternoon picking out heirloom tomato varieties, or building some overbuilt little trellis for the sweet peas that nobody asked for. That's not procrastination. It's the same move as my Rube Goldberg detour — find the part of the project that's actually alive for you, and let it pull the rest of the bed into existence around it.

Or think about someone taking up woodworking for the first time, staring at a cut list and a joinery diagram that might as well be written in another language. What actually gets them into the shop isn't the joinery. It's sanding a scrap piece of walnut down until the grain finally shows, just to see what's underneath. That fifteen minutes has nothing to do with the project plan, and everything to do with getting a person who was avoiding the garage to walk into it. Once they're in there, in motion, hands on the wood, the cut list stops being a wall and starts being the next thing to figure out.

This doesn't have to be a grand gesture. It can be a casual conversation with someone on your team about a part of the work you're excited about. It can be knocking out a task that's technically out of order but is the one you've been looking forward to since the project started. It doesn't need to be justified against the plan. The plan will still be there. What you're looking for is the part of the work that's yours — the part where you'd do it even if nobody asked you to.

Observation

You'll know when you've found it, because other people notice before you do. I remember playing a song with my band and hitting one particular part a certain way. One of the guys just smiled — not a big reaction, he probably didn't even know he was doing it. I played it the same way the next time, and got the same smile. He wasn't rating my technique. He was responding to the fact that I'd found something real in the middle of it. When you strike the part of the work you actually love, it shows, and it's contagious to everyone else around the table.

6 - The Blank Page Is Not a Verdict

Red light fever isn't a flaw you eventually train out of yourself. It's what happens at the exact moment intention turns into execution, and it will keep showing up no matter how many times you've done the work before. The goal was never to make the red light stop coming on. It's to have somewhere to go the moment it does — protect the hours when your signal is strong, build a real practice instead of waiting on inspiration, and when you're genuinely stuck, go find the part of the work you love and start there.

✓ - Quick Takeaways

If you're in it right now — staring down your own red light — here's the short version. None of this makes the blank page comfortable. It just gives you somewhere to go the moment it shows up.

  • Red light fever is universal, not a personal flaw. It hits musicians, contractors, athletes, and knowledge workers alike — the gap between preparation and execution catches everyone.

  • Know your signal hours and protect them. Figure out when your cognitive energy peaks, do the hard, high-stakes work then, and fall back to frameworks and checklists once the noise builds.

  • Motion comes before motivation. Don't wait to feel ready — action is what generates the clarity and momentum you're waiting for, not the other way around.

  • Build practices, not hacks. A hack gets you unstuck once. A template or a repeatable structure gives you somewhere to put the first word every time the page is blank.

  • Reframe instead of grinding. When a problem feels too big to attack head-on, shrink the question until it's honest and small — "what's the one part of this I actually love?"

  • Chase the part of the work you love. Jump to it out of order if you have to. It doesn't matter if it survives into the final product — its job is to get you moving again.

  • The blank page is a starting line, not a verdict. It's where every real thing begins, not a judgment on you or the work.

Further Reading: Todd Henry on Breaking the Block

Todd Henry's work is where I first found language for a lot of this, and if any of it resonated, his own material is worth going to directly. He's the author of seven books on creativity and leadership, including The Accidental Creative, and has hosted the podcast Daily Creative (formerly The Accidental Creative) since 2005. A few of his ideas that shaped this piece:

  1. Motion precedes motivation — action makes ideas concrete, and it's the action that generates motivation, not the reverse. toddhenry.com/theaccidentalcreative

  2. Build practices, not hacks — Henry's Focus, Relationships, Energy, Stimuli, and Hours framework for sustaining creative output over the long term, rather than relying on one-off tricks. toddhenry.com/theaccidentalcreative

  3. Reframe the problem — widening the frame or looking at the same data from a new angle to dissolve a block and reveal new opportunity. toddhenry.com/books

  4. For the full framework and his ongoing podcast: toddhenry.com and accidentalcreative.com. The book itself: The Accidental Creative: How to Be Brilliant at a Moment's Notice (Portfolio, 2011).

Mike Moegling · mikemoegling.com

Next
Next

The Lab Versus The Factory