Change programmes rarely fail at the announcement. They fail in the retelling, three layers down. Here is how to make the reasoning survive the journey.
By Will Nash
7 October 2026
Change programmes rarely fail at the announcement. The deck is good, the town hall goes fine, and the first week looks like it has landed.
They fail in the retelling. By the time the reasoning has passed from the executive to the division to the team meeting, it has been compressed into a sentence that sounds like cost-cutting, and nobody can remember who said it.
The cascade breaks at the line manager
Most change communication depends on managers explaining it to their teams. That is a reasonable plan and it mostly does not happen, because the manager was given a slide and a bullet list and is not confident enough in the argument to take questions on it.
So they do the safe thing. They forward the email, say leadership has explained it better than they can, and move on to the agenda. The reasoning stops one layer above the people it was meant for.
People need the argument, not the summary
A summary tells someone what is changing. It does not tell them why this option was chosen over the two that were rejected, what the alternative would have cost, or what the leadership team found hard about it.
That is the part that makes a decision feel legitimate rather than arbitrary, and it is the first part cut when the message gets shortened for an email.
Audio is unusually good here because length is cheap. Twenty minutes of somebody genuinely explaining their thinking costs the listener a commute and costs you nothing extra to distribute.
What to record, and when
Not before the announcement. A recording that arrives first makes people feel managed rather than informed, and the questions it answers are not yet the questions they have.
Shortly after it lands, record the why. One leader, the person who actually made the call, talking through how the decision was reached and what they considered instead. This is the episode most programmes never make.
A few weeks in, record the answers. By then you will have a genuine list of what people are asking, gathered from managers and from wherever questions get submitted. Work through them honestly, including the ones with unsatisfying answers.
Near the end, record what changed. Programmes tend to go quiet once the difficult part is over, which leaves people assuming it fizzled. A short closing episode that says what actually happened is cheap and does more for the next programme than anything else on this list.
Answer the questions people actually asked
The temptation is to answer the questions you wish they had asked. It is obvious when that happens and it costs you the audience for the rest of the programme.
Collect the real ones. Take the awkward one first, in its original wording, and answer it in the first two minutes. If the honest answer is that a decision has not been made yet, say that; people handle uncertainty better than they handle being handled.
Who should speak
The person who owns the decision, not the person who communicates best. A polished delivery from someone one step removed reads as a message that has been through a process, which is exactly the impression you are trying to avoid.
Give them an interviewer. A leader talking alone into a microphone drifts into speech mode. A colleague asking real questions keeps them in explaining mode, which is the register you want, and it lets somebody push gently when an answer is thin.
What must stay out of audio
Individual outcomes. Nobody should learn about their own role from a recording.
Anything with legal weight: consultation processes, contractual changes, anything an employment lawyer needs to sign off. Those stay in writing, and audio can reference them rather than replace them.
Anything you are not willing to have quoted. Assume every recording leaves the building, because sooner or later one will.
How to tell whether it worked
Listen to how managers explain the change six weeks later. If the reason coming back matches the reason you gave, the argument has travelled. If it has flattened into cost-cutting, it has not, whatever the engagement numbers say.
The other useful signal is the repeat question. When the same question keeps arriving through three separate channels, it has not been answered anywhere people can find it.
Where this does not help
If the decision itself is the problem, better communication is not the remedy, and staff will read the extra effort as persuasion. Say less, more plainly, and accept the disagreement.
If your programme is genuinely a series of small operational changes rather than one significant shift, this is too much machinery. A short written note that people can skim is a better fit, and making a production out of it invites a weight of scrutiny the change does not need.
In short
The reasoning behind a change is the thing most likely to be lost, and the thing most likely to determine whether people accept it. Record the argument in full, answer the questions people really asked, and keep individual outcomes and anything legal firmly in writing. Then check, six weeks on, whether the reason coming back up is the one you sent down.
We are an AI-native podcast agency, and a fair amount of what we build is exactly this: one leader explaining a decision at length, and an episode made from the questions people actually submitted. If you have a programme starting and the explaining is the part you are worried about, get in touch.
