Vitality, not virality (or, a Few Thoughts About Online Audio, CBC Radio, and “Going Viral”)

If you work in or care about public radio, podcasting, or online audio, I strongly recommend Stan Alcorn’s terrific piece Is This Thing On? Why Audio Never Goes Viral.

In it, Alcorn digs into some of the reasons audio is a second-class citizen online: the web is a primarily visual medium, audio content is difficult to index, search, and skim through, etc.

But he also drops some telling data points about just how non-viral audio really is. For instance (emphasis mine):

In June 2013, the list of the 100 most-shared news articles on Facebook included three from NPR, but none included audio.

And this:

“Radiolab” and “This American Life” — public radio shows that are among the most popular podcasts and the aesthetic guiding lights for young public radio producers — are both approaching a million digital listens for each new episode. For these shows, the occasional episode will get shared more than others, but that “viral” bump is on the order of 10 to 20 percent, and even that seems driven less by social media than old-fashioned word of mouth.

Needless to say, Alcorn got me thinking a lot about the way we approach online audio and social media at CBC Radio, which at the moment seems to be placing an increasing level of importance on online metrics like pageviews and audio streaming.

If virality is indeed a worthy goal for a public broadcaster (and I’m not convinced it is, but more on that later), what are some things that CBC Radio could do to help make that happen? If we want more of what we do to (pause for cringe) “go viral,” how do we create the best possible conditions for that to happen?

Here are a few thoughts.

More pupose-built audio tools

When CBC Radio producers make radio shows, we use tools purpose-built for audio. In studio, we use pro-level audio gear. We mix and edit sound using software built specifically for radio.

But online, we use tools that were never really intended for audio.

Most CBC Radio websites run on a blogging engine built for text. Our audio content lives at a CDN that describes itself as an “online video platform.”

Should we be surprised when tools built for sharing text and video don’t work particularly well for a completely different medium with its own set of strengths, weaknesses, and modalities?

If you want me to mash potatoes, don’t hand me a whisk.

So then, it comes as absolutely no suprise when Alcorn writes, “If there is any company attempting to create a modern web alternative to the podcast, it’s SoundCloud.”

Why? Because SoundCloud was built from the ground up to be an audio platform.

Speaking of tools…

Build audio players with sharing and spreadability in mind

The existing embedded CBC audio players are terrible. I’d embed one here, but I don’t want to put you through that. How terrible are these players? Let me count the ways:

They’re built in Flash. They don’t work on iOS. You can’t embed them on Facebook. By default, they auto-play. They’re wasteful, because they start downloading and playing an audio file regardless of whether the user clicks play or not. They don’t link back nicely to related non-audio content. And finally, the CBC has an agressive expiration policy for archived audio. The player enforces this, even if the underlying audio is still available.

Luc Latulippe summed it up nicely:

Trying to embed the CBC’s audio player is like trying to nail Jell-O to a tree

Public broadcasters can’t realistically expect listeners to share and spread radio stories if the experience of doing so is absolultely miserable.

Slice it up

As I wrote back in 2011, segmentation matters:

People want what they want when they want it. Offering easy access to individual stories (like TAL does, or how Quirks and Quarks offers a segmented podcast) helps people share and spread the stories they love. It helps create the conditions for virality.

Things are getting better at the CBC. We’re slicing up audio, and making individual stories available. But this kind of thing is still far too common:

“Fast forward to 10:34″ or “Skip ahead to 23:30″ is a terrible user experience.

The good news is that there are tools and specs built to address this very problem. Audio deep-linking is possible. There’s a whole W3C recommendation for media fragments. Groups like Podlove are actively building tools that address these issues.

Pay attention.

Vitality, not virality

The subtitle of Alcorn’s piece comes from this quote:

“Audio never goes viral,” writes radio and podcast producer Nate DiMeo. “If you posted the most incredible story?—?literally, the most incredible story that has ever been told since people have had the ability to tell stories, it will never, ever get as many hits as a video of a cat with a moustache.”

The thing is, so many people in public radio world really want it to. They want so very badly for audio to be able to (again, pause for cringe) “go viral.”

When you stop and think about it, if you swap out the word “audio” for something else, the whole question seems a bit silly.

People eat food all the time. Why doesn’t taste go viral? Almost everyone has a nose. Why don’t smells go viral? Is it because hip Berlin startup-types have yet to build SmellCloud? I doubt it.

There’s something more basic going on here, and Alchorn gets at it when he asks:

is a hit-machine for audio possible? And is it something anyone even wants?

Other than radio execs, I’m not sure anyone does. And I’m not sure that virality should be a goal for public radio. I’m not sure it’s achievable. Past performance suggests it’s not, at least when we measure success using the metrics of other media.

The last thing public radio needs is a cargo cult approach of aping what works for other media, then acting all disappointed when it doesn’t work out so well for us.

A very savvy CBC executive once advised the Spark team to “fish where the fishes are.” I think that applies to CBC Radio more broadly.

Radio excels in certain contexts. For instance, commuting. In Canada, 82% of commuters travel to work by car. Audio is great in cars, and tech-wise, lots of exciting things are happening in cars: iOS in the car and the Open Automotive Alliance to name two. So then, what is public radio’s car strategy? What is CBC Radio’s car strategy? Analog transmission?

Part of CBC’s mandate is to ensure our programming is “made available throughout Canada by the most appropriate and efficient means and as resources become available for the purpose.”

I would much rather CBC Radio’s digital efforts go towards figuring out how to do a better job of what we’re already good at, rather than trying to get good at making empty-calory web content (listicles, memes, GIFs, etc.) that simply cannot compete with the stuff coming out of Upworthy, BuzzFeed, and others.

I don’t know exactly what digital success for public radio looks like. But I do know getting it right means embracing the best qualities of the medium itself, not shoving radio stories into listicle-sized holes.

Filed under: Public Radio

Comments

  1. Laurence Stevenson says:

    As usual, you hit all the points well. ‘Viral’ should not be any kind of priority. That being said, IF someone were to try an experiment to take audio material ‘viral’, I would recommend going into the Archives and digging out Radio Drama’s ‘3 Minute Theatre’. There are 4-5 episodes, each in 3 1-minute parts, with lots of punch and ‘cliffhangers’. If ever there was material for ‘viral’, those should do it. I’d start with the ‘James Bond’ one.

  2. Andrew says:

    I have read the original article about three times, and am still going through it.

    One thing I have been curious about is how seldom radio producers simply upload their work onto YouTube with a single image. YouTube is the number one site for streaming music- why not streaming audio as well?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>