Why Employees Actually Finish Internal Podcasts and How to Measure It

Lululemon's internal podcast, produced by JAR, earned a 95% listen-through rate across multiple countries. The average corporate newsletter doesn't come close. And the gap isn't explained by Lululemon having unusually engaged employees or better writing. It's explained by format.

That distinction matters more than most internal comms teams realize. When completion rates are low — when all-hands recordings go unwatched, emails go unread, and intranet posts collect dust — the instinct is usually to fix the content. Write a better subject line. Shorten the newsletter. Add a summary. These are reasonable fixes for a misdiagnosed problem.

The problem isn't the writing. It's the behavioral ask.

What Email and Intranet Posts Actually Ask of Employees

A corporate newsletter, a long intranet update, or a recorded town hall replay all share one requirement: they need your employee to stop, sit down, close other tabs, and read. That's a substantial cognitive ask — and it competes with everything else on the screen at the same moment.

Expecting a team member to read an email longer than 500 words, in 2026, seems increasingly unrealistic. Not because people have gotten less intelligent or less dedicated, but because the environment they're reading in has gotten noisier. Slack threads, calendar invites, and task notifications are all pulling at attention simultaneously. Long-form text doesn't win that fight.

Audio doesn't enter that fight at all. It occupies a different behavioral slot. Employees listen while commuting, walking between meetings, making coffee, or completing low-focus tasks. The content reaches them during time that would otherwise be empty — which means completion rates improve not because audio is inherently more compelling, but because it doesn't require employees to carve out dedicated focus time.

This is the core diagnostic. Low internal comms engagement is almost never a sign that employees don't care. It's a sign that the format is competing for attention it was never going to win.

Why the Brain Treats Spoken Voice Differently Than Formatted Text

There's a cognitive dimension to this worth naming. When leadership explains a decision in their own voice, context comes through that formatted copy strips away. Tone, conviction, uncertainty, genuine enthusiasm — these signals are present in speech and absent in email. An announcement that reads as confident and directive in text might communicate something very different when heard, and that difference often determines whether employees trust the message.

This matters especially during periods of organizational change. A change-management podcast episode where a senior leader walks through the reasoning behind a restructure — in their actual words, with real pauses and honest acknowledgment of what's uncertain — lands differently than a polished written statement that sounds like it went through three rounds of legal review. Often, because it did.

The conversational format also signals something about the organization's relationship with its people. Branded internal podcasts that feel produced but human tell employees they're worth a genuine investment of time and craft. That's a culture signal, not just a communication format.

Covering complex material through audio also unlocks depth that email kills. The data from Lululemon illustrates this directly: when content is value-packed and professionally produced, employees will listen for 30 minutes, an hour, or more. That's not possible with a written update, regardless of how good the writing is.

The Three Design Decisions That Separate High-Completion Shows from Dead Ones

Not every internal podcast earns strong completion numbers. The ones that do share a consistent design logic — and it has nothing to do with production budget.

Audience specificity. The most common internal podcast design mistake is treating employees as one audience. A 45-minute leadership update designed for frontline warehouse workers is a fundamentally different design problem than a 15-minute manager briefing for a distributed software team. Shows designed for "all employees" end up relevant to none of them. High-completion internal podcasts name their audience precisely and design every episode to serve that specific person.

A defined job. "Keep people informed" is not a job. It's an aspiration with no measurable outcome attached. Shows that earn attention have a specific communication goal per episode — explain the rationale behind a policy change, help managers navigate a difficult conversation with their teams, reinforce why a cultural value matters during a period of growth. When an episode has a clear job, the listener feels the relevance immediately. When it doesn't, they drop off around the five-minute mark.

Format matched to the communication goal. Leadership updates, manager briefings, culture conversations, change-focused series, and internal storytelling formats all have different optimal lengths, structures, and tones. A culture story can run long if it's genuinely compelling. A change-management briefing needs to be tight and direct. Publishing cadence also belongs in this category. The right schedule is determined by how often meaningful updates need context — not by how often content can be produced. Organizations that publish weekly because they committed to weekly end up filling episodes with material that didn't need its own show. That's where completion rates fall.

These three decisions map directly to the JAR System's core framework: Job, Audience, Result. Applied to internal podcasts, this isn't just a philosophy — it's the operational logic that determines whether a show gets finished or gets skipped. You can read more about how JAR applies this framework at jarpodcasts.com/services/internal-podcasts/.

The Metrics That Tell You Whether It's Working

Listen-through rate is the headline number, and it's the right one to lead with. But it doesn't tell the whole story, and fixating on it alone misses what makes internal podcasting genuinely valuable.

A more complete measurement framework looks like this:

Listen-through rate tells you whether the episode held attention to completion. Anything consistently above 70% signals that your format and content are working together. Lululemon's 95% rate is exceptional — but it's a useful benchmark for what's possible when design is right.

Episode-over-episode retention tells you whether the show is building habit. If employees listen to three episodes and then stop, something changed — either the topic relevance dropped, the format drifted, or a cadence problem crept in. Episode-over-episode data surfaces this before it becomes a show-ending pattern.

Qualitative signals are often the most diagnostic. Did leadership hear fewer repeat questions after a change-management episode went out? Did a manager briefing show correlate with higher confidence scores in the next pulse survey? These downstream signals don't come from your podcast host analytics — they come from paying attention to what changes in the organization after an episode releases.

Participation in follow-up sessions is another useful proxy. If employees who listened to a preparatory episode showed up to a town hall more prepared, asked sharper questions, or needed less context repeated during the session, the podcast did its job. That's a result worth tracking.

One concern that comes up often, particularly from HR and legal stakeholders, is around individual listener identification. Internal podcasts distributed through private feeds or secure platforms capture engagement signals — completion rates, episode listens, retention — without identifying individual listeners. No names, no profiles, no individual behavioral records. This is important for trust, and it's worth stating clearly to any internal stakeholder who raises it as an objection.

For a broader look at how to think about podcast performance data, Podcast Analytics That Actually Matter covers the right framework for separating signal from noise.

Making the Case Before You Launch Anything

The Champion in any organization — the Head of Content, Director of Comms, or Internal Communications Manager who wants to bring this idea forward — needs something defensible before the conversation with the Economic Buyer happens.

The most effective framing isn't an ROI calculator. It's a comparison. How much collective time does the organization lose to all-hands calls where 60% of attendees are multitasking? How many critical messages sent via email get opened by a third of the intended audience and read in full by far fewer? What's the actual reach of the intranet post that announced last quarter's restructure?

Set that against the cost of a professionally produced internal podcast with a defined job and a measurable result, and the math shifts quickly. The question isn't whether an internal podcast is expensive. The question is whether the current approach is working — and at what cost.

There's also a common objection worth addressing directly: "We tried a podcast internally and it didn't work." This surfaces often, and the explanation is almost always the same. The show had no defined audience. It tried to speak to everyone. It published on a rigid calendar regardless of whether there was something genuinely worth saying. It was launched as a format experiment rather than a strategic communications investment.

Those are design failures, not format failures. American Airlines and Lululemon haven't built internal podcast programs because audio is fashionable. They've done it because the format, when designed properly, reaches employees in a way that nothing else does — and the completion data proves it.

Internal podcasts also don't replace existing communication channels. They add depth and context to messages that already exist. An intranet post announces the decision; the podcast explains the reasoning behind it. That combination — breadth plus depth — is what makes the shift in engagement real.

A Note on What "Professionally Produced" Actually Means Here

There's a version of "internal podcast" that gets recorded on a laptop microphone in a conference room and sent out as an audio file attached to an email. That's not what drives 95% listen-through rates.

Professional production in the internal context means editorial direction — someone thinking about the episode's job before a single question is asked. It means a format matched to the goal, not just a recording of a conversation. It means audio quality that signals to the listener that this was worth making. And it means a distribution system that reaches employees where they actually are, not where you hope they'll think to look.

The organizations that see the strongest engagement results from internal podcasting aren't the ones with the biggest budgets. They're the ones that started with a clear job, a defined audience, and a commitment to making content people actually want to hear — and then measured whether it worked.

That's the only way to know. And it turns out the numbers, when you look at them, are quite different from what a newsletter delivers.

If you're weighing whether an internal podcast makes sense for your organization, jarpodcasts.com/services/internal-podcasts/ is a good starting point. If you're ready to talk through your specific communication challenge, reach out at jarpodcasts.com/contact.