An internal podcast is good at one narrow thing and bad at several others. Here is how to tell which of your messages belong in audio.
By Will Nash
5 October 2026
Internal comms teams are asked to land more messages than anyone has the attention to read. The all-staff email goes out, the intranet post follows, and a fortnight later a good share of the organisation has registered neither.
A podcast does not fix that by itself. It is useful for one narrow job: carrying the reasoning behind a decision, in a voice people recognise, to employees who spend most of their day away from a screen.
What an internal show is actually good at
Reasoning, rather than conclusions. A written announcement gives people the decision. It rarely gives them the argument that produced it, because the argument is long and the email has to be short. Audio has room for the argument.
Letting people hear a leader think. There is a difference between reading a statement attributed to your managing partner and hearing them work through why the firm turned down a piece of work. The second is much harder to fake and much easier to believe.
Explanations you have to give repeatedly. Induction is the obvious one. If somebody on your team explains the same thing to every new joiner, that explanation is a recording waiting to happen.
What it is bad at
Anything urgent. Audio is slow to make and slow to consume, and the person you most need to reach may not listen until Thursday.
Anything that needs a record, an acknowledgement, or a legal reading. Policy changes, terms, and anything an employment lawyer would want to see stay in writing.
Bad news that gives people no way to respond. A recording is a broadcast. Announcing something difficult in a format nobody can reply to reads as avoidance, and people are good at spotting it.
It is not for everybody in the company
The instinct is to make one show for the whole organisation, which produces episodes aimed at an average employee who does not exist. A show for client-facing staff and a show for the operations teams are different shows, and running one of them well beats running one badly for everyone.
Start with the group whose work changes most often. They have the most to gain from hearing the reasoning early, and they are the easiest group to ask whether it helped.
What it takes from people
Less than teams expect from the leaders, more than they expect from themselves. A leader who can give you a proper twenty minutes every few weeks is enough raw material. The work that actually needs resourcing is the deciding: who this episode is for, what question it answers, and whether it is worth making at all.
Where to put it
A private feed people can subscribe to in a normal podcast app is usually the right answer, because it meets employees where they already listen. An intranet player is fine but tends to get opened at a desk, which is the one place audio has no advantage.
Where this does not help
If trust in leadership is low, more of leadership's voice is not neutral. It can harden the view rather than soften it. Audio makes a leader more present, which is an advantage when people broadly believe them and a liability when they do not.
If the problem is that people disagree with the decision rather than misunderstand it, a clearer explanation will not change their minds, and treating it as a comprehension problem tends to annoy everyone.
In short
An internal podcast earns its place when your organisation keeps needing to explain why, to people who are not sitting at a desk. It is a poor substitute for a written record and a worse one for a conversation. Decide which of your messages are actually explanations, and start there.
We are an AI-native podcast agency, and most of the internal work we build starts with one leader who keeps having to explain the same decision. We turn that into episodes without putting a standing commitment in their diary. If your internal channels are carrying more explaining than they can hold, get in touch.
Related: Audio for internal comms
