If you're not a 1 man band, the hosts and guests are more important than the content. I listen to @arseblog ArsecastExtra with @gunnerblog religiously and when one of the two aren't there, I delete the episode.
As one of my podcasts approaches 1.5m downloads and the the other 50,000, I thought I'd share a few things that I've learnt over the past 3 years on building a successful podcast 👇
If you're not a 1 man band, the hosts and guests are more important than the content. I listen to @arseblog ArsecastExtra with @gunnerblog religiously and when one of the two aren't there, I delete the episode.
To the naked ear, your audience can't tell the difference between 10/10 audio and 8/10 audio. The content is more important. If it's gripping and good people will stick around even if the audio quality is average.
Be consistent with your distribution whether it's a day of the week, or consistently after an event. Podcasts are audio on demand, but most podcasts retain listeners by becoming part of their weekly routine.
Use your latest episode as an anchor piece on your social media profiles/website. Everything you do post launch, should be done with an aim to draw as many impressions to your pinned anchor piece of content as possible.
If someone takes their time to reach out and tell you they enjoy your show, ask for something back. Ask them to review your show and share your latest episode. Getting an audience is one thing, generating growth through them is another.
Some of us have our attention grabbed by visuals. Use graphics and social cards whenever you post your show. The impression and link click rates are often a lot higher and it also shows your podcast to be something that is 'more than audio'.
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.