Why Combining Shows is a Recipe for Disaster

I saw on Reddit where someone was potentially making the classic blunder of podcasting: mixing unrelated shows into one feed.

You know, like if you went to a restaurant for a burger but ended up with sushi on the same plate. I point out that our buddy Joey has a bi-weekly podcast that covers both video games and TV shows. With a measly two downloads per episode, Joey's mixing it up like a bad cocktail.

The main takeaway? Split those shows!

Seriously, if someone clicks on a gaming episode expecting a deep dive into Mario Kart, they don’t want to suddenly hear about the latest Netflix binge. We’re all about giving the audience choices here, folks.

Keep it simple, keep it focused, and let them pick what they want to listen to. It’s like letting them pick their own adventure instead of forcing them to read the whole book. So, if you’re in this boat, don’t wait for a big audience to fix it. Tweak it now, while the stakes are low.

Trust me, you’ll thank yourself later when you’re not scrambling to split your shows down the line. And with the right media host, like Captivate or Transistor, you can have multiple shows without breaking the bank. Why wait until it’s a mess?

Takeaways:

1. Don't make the rookie mistake of merging unrelated podcast topics into one show, just don't.
2. Split your podcast episodes into separate feeds to give listeners their power of choice, ya know?
3. Tuning your podcast like a guitar should happen when you have fewer listeners, not a packed house.
4. Using the right media host can save you from the headache of splitting up your shows later on.

Links Mentioned:

School of Podcasting

Captivate

Transistor

This content may contain affiliate links, meaning I earn a small commission if you purchase through these links at no additional cost to you. I only recommend products or services I trust and believe will provide value to you. Thank you for your support!

This podcast uses the following third-party services for analysis:

OP3 - https://op3.dev/privacy