Why Podcasts Fail: It Is Almost Never The Idea

People ask us why podcasts fail, and the guess is almost always the concept. So here is the version we see from inside a studio in El Paso. The idea is rarely the problem. Shows stop because the work after the recording was never on anyone's calendar. Then one busy week arrives with nothing banked behind it, and the feed goes quiet. Ultimately that is a scheduling failure rather than a talent one. Of course, it is also the kind of failure you can design out before episode one.

Why Podcasts Fail: The Short Answer

Podfade, And Why The Feed Just Stops

Podfade is the word for a show that stops publishing without ever formally ending. There is no final episode and no announcement. So the feed simply goes quiet, and the archive stays up as though the show might come back. Nobody plans it. It is what happens when the next episode keeps not being the priority.

The most widely cited figure is that roughly nine in ten shows stop publishing by episode three. However, other counts put the number closer to half. So those figures disagree, because they count differently. Meanwhile every count agrees on the shape: the drop-off is early, and it is steep.

The disagreement is worth understanding rather than resolving. Counting a show as finished depends on where you draw the line, and different studies draw it in different places. So the headline number moves depending on who published it, while the underlying pattern does not move at all.

So the number is not the useful part. The shape is. Whatever the true rate, the risk sits in the first few weeks, before a show has any momentum to carry it. Of course, that is also the window where the workload is heaviest and the audience is smallest. For a wider view of how shows are run, the Podcasters Association publishes podcasting industry practice material.

The Four Causes At A Glance

First, it helps to separate the causes, because they get treated as one problem. They are four different failures, and only one of them is really about effort.

Why Podcasts Fail: Four Causes, Not One

Cause one is the hours nobody counted. You budget the recording. Then the transfer, the cut, the levels, the clips and the show notes all turn up afterwards, and none of them were on the calendar. So the show starts eating the evening it was supposed to fit inside.

Cause two is the second guest. First interviews get booked on enthusiasm. Then the follow-up depends on somebody else's diary, and one cancellation leaves a week with nothing in it.

Cause three is having nothing banked. A show with three finished episodes in reserve survives a bad week. By contrast, a show with none does not, because the bad week and the missed episode are the same event.

Cause four is the founder's spare time. The schedule quietly assumed a free evening. Then the quarter got busy, the evening went, and the show went with it.

What The Shows That Survive Actually Changed

They stop doing the part they dislike. The parts that genuinely need you are the talking and the final approval, and the rest can go to someone else. So the founder keeps the hours that matter and gives away the ones that do not.

They record several episodes in one sitting. Then they keep a buffer of finished episodes, so one bad week no longer breaks the feed. Of course, none of that changes the concept. It changes the calendar.

Our own show runs the same way. For example, the Minerva Torres Shelton episode and the recaps beside it exist because the recording days were blocked out in advance rather than squeezed in.

None of that is glamorous. Handing off the levelling, keeping two spare episodes on a drive, blocking a recording day instead of an evening: it reads like admin rather than strategy. That is rather the point. The shows that keep going are rarely the ones with the sharpest concept. They are the ones where the work found a place in the week that it could hold.

Batching, And Why It Fixes Three Causes At Once

Batching means recording several episodes in one sitting rather than one at a time. First, it removes the repeated setup. Then it gives you a buffer. It stops the show depending on any single free evening.

So three of the four causes fall away in one change. The hours shrink, because setup happens once. The bank fills, because you finish more than you publish. Meanwhile the calendar stops mattering week to week, since the next episode already exists.

Cause two, the cancelling guest, survives batching. However, it hurts far less once you have episodes in reserve, because a gap in the diary is no longer a gap in the feed.

A Scheduling Problem, Not A Talent Problem

That distinction matters, because the two have opposite fixes. A talent problem asks you to be more interesting. Meanwhile a scheduling problem asks you to move the work somewhere it fits.

So the honest test is simple. Look at the week you record and the week after it. If the second week is where the show really lives, the show is competing with your actual job. Then your actual job wins, every time.

In short, none of that reflects on the idea. The Small Business Administration publishes guidance on marketing a business, and a podcast only works as marketing while it keeps publishing. Ultimately the shows that stop rarely got far enough for anyone to judge the concept at all.

What To Settle Before You Record Episode One

First, decide who edits. Not later, and not after the first three episodes. If the answer is you, decide which parts you actually want to keep and hand off the rest.

Second, decide how many episodes exist before the first one publishes. Then set the cadence from that number rather than from ambition. Weekly is a promise, and a promise with nothing banked behind it is the exact shape of podfade.

Third, decide where you record. At our El Paso podcast studio for rent the room, the microphones, the cameras and an engineer are all here, so a session is a booking rather than a project. Also, if you want the audio finished as well as captured, audio recording and voiceover covers that side of it.

Four Questions Worth Answering Honestly

So before episode one, run these four. Any answer is fine. A shrug is a cause waiting to happen.

• Who does the edit next month? Not this month, while the enthusiasm is high. The month after the novelty wears off.
• How many finished episodes exist on launch day? Then set the cadence from that, and not from what sounds impressive on a launch post.
• What happens when a guest cancels? A solo format or a banked episode both answer it. Nothing answers it on the day.
• Which evening is this replacing? If the honest answer is a free one, name the week that evening disappears.

If those four have answers, the schedule holds. However, if two of them are still vague, the show is already running on hope. Meanwhile, a finished episode is the easiest way to see what a banked one actually looks like.

Frequently Asked Questions

Why Podcasts Fail Less With A Studio Behind Them

So why podcasts fail is mostly a question about the weeks around the recording, and not about the recording itself. Book the room, bring the guests, and walk out with several episodes captured and an engineer already holding the rest. Then the only thing left on your calendar is the talking. Ultimately that is the version of a show a working week can actually carry.