Community, Elixir

Elixir Wizards Podcast Listener Survey Results

This summer we put together a listener survey, with a goal of getting some feedback and learning a little more about our Elixir Wizards audience.

Here's a quick overview of some of our findings.

Completion Rates

Image of completion data for the survey; 150 views, 113 starts, 45.1% completion rate, 10 minutes average time to complete

We were hoping to get at least 30 responses, so we were pleased to have 51 total completions at the end of our three week run.

How listeners found the podcast

Picture of a survey question "How did you hear about the podcast?" with responses: 33% podcast service, 26% social media, 16% Elixir forum/slack/subreddit, 8% search engine, 8% word of mouth

I was surprised at the number of listeners who found our podcast via their podcast player as opposed to social media or Elixir social forums. My expectation was that most listeners found us via the Elixir community directly; it is neat to know that listeners are finding us in other ways as well.

Listening habits

As our podcast episodes have gotten longer, we wanted to check in on typical podcast listening habits over the course of a week. 66% of our listeners typically listen to podcasts for an hour or more in a week's time, which is good sign for us since our episodes are currently running around 40-60 minutes.

Picture of a survey question "Do you listen to other technical podcasts?" Responses: 90% yes, 10% no

We also asked about whether folks listen to other technical podcasts, and if so, what some of their favorites are. All the other Elixir podcasts featured heavily in the responses, and The Bike Shed, Changelog, and Full Stack Radio each got several mentions.

Positive and Negative Feedback

The questions we asked prompting for positive and negative feedback on the podcast overall didn't get us super useful answers. Listeners did mention specific guests, episodes, and themes they enjoyed, but we didn't get much high level "do more of this / less of that" feedback. In hindsight, I think the wording of the questions could be improved to prompt for the kinds of feedback we were hoping to get.

Brand Recognition

Picture of a survey question that reads "Without looking it up, what is the name of the company that runs Elixir Wizards?"

Most respondents — 84% — got this one right! This is good news for us, since we run the podcast as a contribution to the community but also to help us gain visibility as a consultancy working with Elixir.

Pattern Matching Feedback

Image of survey question and responses. Q: "Would you prefer to listen to the Pattern Matching segments as standalone episodes or bundled at the end of full episodes?" A: 52% Bundled with full episodes, 48% Standalone

This season, we tested out an idea that friend of the podcast Todd Resudek had, which was to create mini-episodes or segments, focused on getting to know members of the community better: Pattern Matching with Todd. We tested out launching these as separate episodes as well as bundling them with full episodes, and were curious which the audience preferred.

Only about half of our respondents had heard a Pattern Matching segment, and of those who had, opinions were split evenly as to how they'd prefer to listen to them.


Overall we're glad we put the survey together; we got some good insights and have some good learnings to apply for the next time we want to gather listener feedback.

As always if you have feedback or ideas for the podcast, we'd love to hear them! Email your thoughts to us at [email protected].

Also we still have sticker packs left over from ElixirConf; if you'd like us to mail you one, fill out the request form here.

You've successfully subscribed to SmartLogic Blog
Great! Next, complete checkout for full access to SmartLogic Blog
Welcome back! You've successfully signed in.
Unable to sign you in. Please try again.
Success! Your account is fully activated, you now have access to all content.
Error! Stripe checkout failed.
Success! Your billing info is updated.
Error! Billing info update failed.