Most podcasters quit by episode 7.
I’ve watched it happen for 12 years. Across 350+ shows and more than 70,000 episodes produced, the pattern is almost identical. Launch day feels like a win. By episode 4, editing starts to feel heavy. By episode 7, there’s a backlog, the publishing schedule is slipping, and the host is mentally drafting a “we’re taking a short break” post.
Sometimes that break is permanent. Most of the time, it is.
This isn’t a motivation problem. It looks like one from the inside, but it isn’t.
Why Episode 7
Episode 7 is roughly the point where the launch energy runs out and the workflow has to carry the show by itself. Episodes 1 through 3 are powered by adrenaline. Episodes 4 through 6 are powered by the fact that you already told everyone you have a podcast now. By episode 7, neither of those is enough.
If the workflow underneath the show isn’t carrying its weight, the host has to pick it up. And hosts are usually busy. So the show slows. Then the host blames themselves.
That self-blame is the part I want to push back on, because it’s almost always misplaced.
The Misdiagnosis
When a show starts slipping, the first instinct is to assume the problem is the host. Not disciplined enough. Not consistent enough. Not focused enough.
Then comes the second instinct: hire someone. Usually an editor. Sometimes a VA. The thinking is “if I hand this off, the show keeps moving.”
Sometimes it does. More often it doesn’t, and the host concludes they hired the wrong person.
The editor is rarely the problem. The hire is rarely the problem. What’s actually broken is the system around the host. The handoffs, the checklists, the safety nets. The thing that turns one episode into the next without anyone having to remember.
Three Things that Break Consistency
After producing podcasts since 2013, I can tell you the same three things break almost every show that quits.
1. Recall There’s No Clean Handoff
The host finishes recording. Then what?
In a healthy workflow, the next step is automatic. The file lands in a known location, the editor knows it’s there, the timeline starts. In an unhealthy workflow, the file sits on the host’s desktop for three days while they intend to “send it over.” Then it sits in Dropbox while the editor isn’t sure if it’s the final version. Then it sits in editing while the host hasn’t told them which intro to use.
Each pause is small. Stacked together, they kill release rhythm.
The fix isn’t more discipline. It’s a single shared place where every episode lives, with a simple status that anyone on the team can see. That’s it. The rest follows.
2. Editing is Treated as a Task, Not a Workflow
A task is something you do once. A workflow is something that runs the same way every time.
When editing is a task, every episode starts from scratch. The editor opens the file, listens through, makes choices, asks questions, sends a draft, gets feedback, makes changes, exports, hands it back. Every episode costs full effort.
When editing is a workflow, decisions are made up front and reused. Intro and outro are baked. EQ presets are saved. The naming convention is consistent. Feedback happens in one round, in one place, with timestamped comments. The editor can produce three episodes in the time it used to take to produce one, with the same quality.
The shows that last 100+ episodes don’t have superhuman editors. They have repeatable workflows.
3. There’s No Safety Net
This is the one no one talks about, and it’s the one that ends the most shows.
Hosts have lives. They get sick. They travel. They have a quarter where work blows up. In a fragile system, any of these things stops the show. In a resilient system, none of them do.
A safety net looks like this: there’s a buffer of one or two episodes already edited and ready to publish. There’s a backup editor who can step in. There’s a publishing template that anyone can run. The show doesn’t depend on any single person being available on any single day.
When a show is built like that, the host doesn’t have to feel guilty when life happens. The show keeps going. They come back to it without a stack of catch-up work waiting for them.
That’s what consistency actually feels like.
What “a System” Actually Means
People hear “system” and picture something complicated. Project management software, color-coded spreadsheets, automation tools.
A system, for a podcast, is much smaller than that. It’s three things:
1. A clear path for every file from recording to publishing
2. A repeatable way of editing so the work doesn’t start from zero each time
3. Enough buffer and shared knowledge that one busy week doesn’t break the show
You can run a show with a system that lives in one Google Doc. You can run a show with a system that lives in Notion or Airtable or Trello or a Slack channel. The tool doesn’t matter. The fact that the workflow exists at the same level as the content does.
The Shift that Changes Everything
The shows that last all share one quiet thing in common: the host isn’t the only one moving the show forward.
That doesn’t mean the host hands off everything. Most hosts I work with stay deeply involved in the content. They’re picking the guests, shaping the questions, leading the conversation. What they’re not doing is being personally responsible for whether episode 12 gets edited on time.
The show has its own momentum. The host gives it energy where it matters. The system carries the rest.
That’s the shift. From “I am the engine” to “I am the spark.”
If You’re Already Feeling It
If you’re three episodes in and already behind, you’re not broken. The system around you just hasn’t been built yet.
If you’re at episode 7 and considering a “short break,” the gap isn’t your motivation. The gap is structural. The good news is that structural gaps are fixable. Motivation gaps usually aren’t, because they were never the real problem to begin with.
Build the handoff. Turn editing into a workflow. Put a small safety net in place. Then come back and see if the show feels different.
It will.



