The architecture of not quitting

Adam Ashton co-hosts What You Will Learn, a book-a-week podcast now in its sixth year. He’s reflecting on why it’s still going. He doesn’t credit grit, or vision, or strategic positioning. He credits something more mundane.

“If it was me, I would have probably done somewhere between 7 and 15 episodes — and then that would have been it.”

The honest version of how the show survived: the other Adam. Both hosts have gone through “waves where we’ve wanted to pull the pin,” he says. The reason the show is still running is that those waves never coincided. When one was down, the other was up. When the other was down, he was up. Six years of weekly episodes, all of them carried by whichever Adam wasn’t in the dip that week.

The standard indie-podcasting wisdom treats survival as personal. Push through the dip. Stay disciplined. Find your why. The implicit picture is of an individual podcaster whose persistence is the variable that determines whether the show lasts. If the show fails at episode twelve, the conventional reading is that the podcaster lacked something — consistency, vision, motivation.

If these field notes spark your thinking, you'd like the Podtalk Community — a small forum where indie podcasters talk craft, not hype.

podcaster.community/

Ashton’s experience names a different variable. He didn’t survive because he was more disciplined than the indie podcaster who quits at episode twelve. He survived because there was something catching him when his discipline failed. The catcher was another person. It could have been other things. But it had to be something.

Most solo indie podcasters don’t have that something. No co-host, no accountability partner, no structure that picks up the slack when they’re tired or doubting or busy. The architecture supplies nothing. The only thing keeping the show alive is the podcaster’s own resolve — and the conventional wisdom pretends resolve is sufficient.

It isn’t. Everyone’s resolve fails periodically. That’s not a character flaw; it’s how resolve works. The relevant question isn’t whether you’ll have weeks where you want to quit, because you will. The question is what happens during those weeks. If the answer is “nothing — the show waits for me to feel motivated again,” then your show is a one-failure-mode system. The first time the dip lasts longer than your willingness to keep pushing alone, the show ends.

This doesn’t generalize into “get a co-host.” Some shows require solo voice, and forcing a partnership onto a show that didn’t need one would solve the wrong problem. Identify what catches you when you’re down. If something does, you have an architecture. If nothing does, you have a podcast whose continued existence is dependent on the variable most prone to fluctuation in any creative life: how you happen to feel on a given Tuesday.

You can’t tell whether your show is stable until something tests it. The solo podcaster who’s been running their show for two years on willpower alone doesn’t know they’re operating without a safety net until the week they need one. Up until that week, everything looks identical to a show with structural support. The willpower-alone show and the well-supported show ship the same episodes, hit the same publishing dates, build the same listener relationships. The difference doesn’t show up until the difference matters.

Most solo podcasters who quit don’t quit because they failed at podcasting. They quit because their architecture didn’t include a catcher, and the dip lasted long enough that nothing in their setup was capable of producing the next episode. The advice “be consistent, push through” cannot tell them what they actually needed, because the advice misnames the problem. The problem wasn’t insufficient willpower. The problem was a system designed to require willpower to function.

If your podcast is built so that nothing but your discipline keeps it alive, you’ve built a podcast that will end when your discipline fails. Not if. When.


This field note references the Podtalk episode “Practice with Adam Ashton,” published March 8, 2022.

This work was produced using AI language models directed through an editorial system designed by Craig Constantine. The author selected all source material, designed the creative framework, directed the editorial process, and made all acceptance and revision decisions. The prose was generated by AI under sustained human editorial direction.