I Planned the Whole Thing and Then Didn't Record a Single Video for a Month: The Story of What Finally Changed

I had the whole thing planned. The onboarding redesign I'd been wanting to build for months—the one that would stop new members from watching passive training videos and actually walk them through getting a real result, step by step.

I sat with ChatGPT, engineered the entire structure, mapped out every module, and felt that particular kind of productive satisfaction that comes from having a clear plan. The whole thing was ready. It existed in a Google Doc. All I had to do was record.

And then I didn't record a single video for a month.

The Comfortable Illusion of a Good Plan

That month wasn't wasted, exactly. I was busy. There were calls to run, a platform to manage, a team to coordinate, a hundred small things that each felt legitimate and pressing in the moment. I told myself I'd get to the recordings when things settled down a bit.

Things don't settle down. Anyone who's run their own business knows this. "When things settle down" is not a real time that arrives. It's a story we tell ourselves while we avoid the thing that actually matters.

I tell everyone I work with to identify their Big Three—the up-to-three projects that will actually move the needle this quarter, the ones that deserve focused time and protected attention. I had literally built a framework around this idea. And I was violating it completely, running around doing thirty smaller things, each one feeling vaguely urgent, while my most important project sat perfectly planned and entirely unrecorded.

Here's the thing about planning a project and then not executing on it: the plan feels like progress. It has some of the emotional texture of real work. You did something. You thought hard. You have a document. The problem is that documents don't serve your clients, and they don't build your business. The recording does.

The Conversation That Changed Everything (And It Wasn't About Productivity)

The thing that finally broke the pattern wasn't a new system or a better calendar. It was a single metaphor, dropped casually into a Voxer conversation.

I was talking with my business partner, Timothy, and he was explaining how he works—this thing he does where he'll dive completely into one project, disappear from everything else for a stretch, and then resurface with something fully built. I'd noticed this pattern in him but never fully understood it.

He explained it like this: switching gears costs tokens.

He was borrowing language from AI—tokens, in that world, are the units of thought and memory that a language model processes. Every time you change contexts, you spend tokens. And here's the thing that hit me: human brains work remarkably similarly. When you switch from one type of work to another, you're not just changing topics. You're unloading the mental state that was supporting the first task and loading a new one. That reload costs more than the original load. Every time.

I already knew this, technically. The research on context switching has been around for years. I could have told you about the psychological effects of interrupted flow states. But Timothy made it vivid. He made it something I could see happening in my own daily pattern. It was sitting back in the mine as a resource, and he pulled it to the front, and I was forced to confront it.

Holy crap. I'm doing that. And I'm killing my productivity.

The Morning I Made the Decision

The decision was almost embarrassingly simple. I looked at my dashboard—this document I'd built in Claude Cowork that tracked everything I was responsible for, every project, every delegation, every moving piece—and I felt a particular kind of overwhelm that I recognized as a signal.

There was too much on the list. Not too much work—too many active contexts. Too many open loops, each one quietly claiming a piece of my cognitive bandwidth, each one generating its own mild version of the anxiety that comes from unfinished tasks.

I made a rule: in Pythos land, right now, the onboarding modules are the only thing I'm doing.

Not "the top priority among several things." The only thing. The must-not list activated. Everything else that wasn't showing up for scheduled calls went on hold. Not cancelled—held. Waiting in line, as it should have been all along.

I went to Florida with that commitment in place.

Within days, I had recorded half the training modules. By the time I was planning to leave on Tuesday morning, I was on track to have them all done—a project that had been perfectly planned and completely stalled for a month, moving again because I stopped pretending I could do it alongside twenty other things.

Why We Resist This (Even When We Know Better)

I've been thinking about why smart, ambitious people systematically resist this approach, even after they understand it intellectually. Because I did. I understood context switching. I teach productivity principles. And I still spread myself across too many projects.

Part of it is that breadth feels safer than depth. If you're working on five things, no single failure is catastrophic. If you're working on one thing and it doesn't land, that's a more direct confrontation with the result.

Part of it is that small tasks have an addictive quality—they're completable. You can finish them. The dopamine of crossing things off a list is real, and an inbox-zero day feels productive even if nothing of consequence got built.

And part of it—this is the one that Gemini named for me when I asked it to analyze our last strategy call—is that learning and perfectionism are just sophisticated procrastination. Spending another week refining the plan that's already good enough to execute isn't preparation. It's avoidance with better optics.

The cure isn't self-criticism. It's recognition. As soon as you can see it clearly, you can name it. And naming it breaks the spell.

What Daniel Did With a Snow Shovel and a Gun to His Head

Daniel, one of the members in our mastermind group, shared a story that stuck with me as the perfect illustration of where all this eventually leads.

Daniel is the kind of thinker who goes deep. He'd been wrestling with niche selection—one of those questions that can be genuinely complex but can also become an endless, comfortable vortex of analysis. He'd built a multi-page cell-referencing spreadsheet that was scoring every possible option. More study, more methods, more complexity.

And then one afternoon, he was outside shoveling snow. And he asked himself a question that cut through everything:

"Gun to my head. Within 30 seconds. A part of me already knows what niche I should specialize in for the next three months. What's the answer?"

He knew within 30 seconds.

He didn't throw out the study—it built genuine understanding. But the actual decision came from somewhere underneath all of it. The part of him that already knew had known for a while. The analysis was largely serving as a reason not to commit.

There's something liberating in that story, and something humbling. We often already know. The question is whether we're willing to stop analyzing and actually begin.

The Framework That's Keeping Me On Track Now

Here's what I'm doing differently now, and what I'd suggest to anyone who recognizes themselves in this story:

Define, then protect. The Big Three projects aren't real until they have a Must-Not list. Identify what you're not allowed to work on until meaningful progress is made. Write it down. Refer to it when you feel the pull toward something shinier.

Batch by cognitive category, not by project. On days when you're recording, just record. Don't sandwich a recording session between a billing task and a client call. You're not just switching topics—you're switching the version of yourself that shows up for work. Each switch costs more than you think.

Let the discomfort of one open loop be a feature, not a bug. The mild anxiety of an important incomplete project is actually useful information. Your brain is telling you the task has shifted from a want to a quasi-need. Use that signal as fuel to protect your focus on the project, rather than dispersing it across five others to quiet the noise.

Give yourself a re-entry ritual. Whether that's a physical reset—coffee, a brief walk, three deep breaths—or something more deliberate like the internal mental workspace Liesl described in our group (her secret island laboratory that she can access in about 20 seconds no matter what chaos is happening around her), build a way back into focus that doesn't rely on ideal conditions.

The Half-Finished Thing Is Not the Failure

I want to end here, because this is the part that matters most.

The half-finished onboarding project wasn't a failure. The planning wasn't wasted. The month of scattered work wasn't evidence of a broken work ethic. It was evidence of a system that needed tuning—specifically, a system that was trying to keep too many context windows open simultaneously.

The shift wasn't working harder. It was working with how the brain actually operates, rather than against it. Closing the extra loops. Giving one thing the full weight of attention it deserved.

Eighty percent of a major project completed in two weeks, after months of incremental progress, isn't a miracle. It's just what focused work looks like when nothing is competing with it.

You probably already have a project like this. Perfectly planned. Ready to execute. Waiting for you to stop treating it like one of twenty priorities and start treating it like the only one that matters right now.

The recording is waiting. The clients are waiting. The version of your business that has this thing finished is one focused stretch of work away.

If you're ready to figure out exactly what your Big Three should be this quarter and build the protection system around them, come work through it with us in the mastermind. The clarity is faster than you think. https://pykthos.com/mastermind