Frank
Think of it like a spotlight on a stage with no stagehands.
When the spotlight finds something, it lights that thing up completely. Every detail. Every possibility. The rest of the stage goes black and silent. You’re not ignoring it, you genuinely cannot see it. And there’s nobody running the controls. The spotlight moves on its own schedule, for its own reasons, answering to nobody.
That’s hyperfocus. That’s what it actually is, right now, in 2025, from where I’m standing.
The Spotlight Doesn’t Care What’s Scheduled
I’ve built real things with this brain. HookHouse Pro exists because I couldn’t stop thinking about it for three weeks straight. Cookslate got its core feature set in a weekend where I barely left my chair. HomeBase went from concept to running Docker container faster than most people finish reading documentation.
None of that happened on a schedule. None of it happened because I sat down at 7pm and blocked out “app development time” on a calendar. It happened because the spotlight found the thing and I had no choice but to follow it.
That sounds romantic. It isn’t. It’s actually a pretty brutal way to try to build anything sustainable, because the spotlight doesn’t care what’s scheduled. It doesn’t care that you promised Kimberly you’d be done by dinner. It doesn’t care that the Falcons are on. It especially doesn’t care that you had three other things you were supposed to finish first.
I will absolutely build a complex automation system to avoid doing a boring task once. Not because I’m lazy. Because the moment the boring task showed up, the spotlight swung somewhere else, found the automation idea interesting, and that was it. The boring task is still sitting there three weeks later. I have a very clean script though.
What Actually Gets Finished
Here’s the honest state of things: the projects that survived are the ones that stayed interesting long enough for me to build critical mass before the spotlight moved.
SunoHarvester didn’t make it. Good idea, real need, built maybe 60% of it. Then something about the Puppeteer implementation got frustrating, the spotlight wandered, and it’s been sitting there abandoned ever since. I’m not ashamed of it. That’s just what the data shows. When the friction exceeds the interest level, the spotlight finds somewhere else to point.
Cookslate survived because recipe management turns out to be a surprisingly deep rabbit hole. Every time I thought I was done, I found another corner of the problem that got interesting again. The spotlight kept coming back. That’s the only reason it’s live at cookslate.app right now.
The pattern is consistent once you see it. It’s not about discipline or motivation. It’s about whether the problem is complex enough to hold the light.
The Schedule Graveyard
I’ve kept exactly zero productivity systems for longer than about six weeks. Task managers, time blocking, GTD, Pomodoro, weekly planning sessions — you name it. All of them worked great for a while. All of them are dead now.
Because here’s what happens: I set up the system during a hyperfocus episode on productivity itself. It’s elaborate. It’s well-considered. It has color coding and tags and maybe a custom integration I built to automate the capture process. Then the spotlight moves, and maintaining the system becomes one of those boring tasks, and now I’ve got an empty task manager with a really clean API wrapper sitting next to it.
The irony is almost funny. The thing that made me build the perfect system is the same thing that makes me stop using it.
The Firehose, Right Now
What I actually know today, having had a name for this for a few years now, is that fighting it wholesale is a waste of energy. The spotlight isn’t going away. It’s structural. It’s how this brain routes power.
What works is shaping the surrounding environment instead of against it. Smaller projects that can reach a meaningful milestone before the light moves. Breaking bigger projects into pieces where each piece is its own discrete interesting problem. Letting the hyperfocus sessions run when they show up, because the quality of work during one of those windows is genuinely different – faster, deeper, better than anything I produce by forcing it.
What doesn’t work is building a system that requires the spotlight to check in on schedule. It won’t. It never has.
The apps got built. The schedules didn’t survive. Both of those things are completely true, and they come from exactly the same place.
The spotlight gave me everything I’ve actually finished. It also torched every clean plan I ever made. I stopped being surprised by either one a while back.
