The Bias Hiding in Your Change Communications

One email. One tone. Sent to finance, the shop floor and senior leadership, all at once, all expecting the same reaction.

It is the default because it is easier. Write one message, send it once, move on to the next thing. But a single message written for one imagined reader will always land better with some people than others, because it was never really written for all of them. It was written for whoever the author was picturing when they sat down to write it.

That is the bias. Not exec bias. Practitioner bias.

Change managers are quick to point out where leadership gets it wrong. Sponsors who do not understand the frontline. Directors who assume a slide deck counts as engagement. All fair criticism.

But turn the same lens on your own comms plan. When you sat down to write last week's update, who were you picturing? Probably someone you know well. A specific person in the business whose reactions you can predict. That instinct is not wrong, it is actually useful, but it only covers the part of your audience who resemble that person.

Everyone else gets a message that was not really written for them, wrapped in the same tone and the same framing regardless.

This is where it connects back to the basics. WHO, in the Change Triangle, is not a list of names. It is an understanding of how differently each group needs to hear the same thing.

Segmentation is not a nice-to-have layered on top of good comms. It is the antidote to this specific bias. A shop floor operative and a finance manager are both stakeholders in the same programme, but they do not need the same message delivered the same way. One needs to know what changes for them on Monday morning. The other needs to know what changes for their reporting cycle. Same programme, same underlying truth, different framing.

When WHO gets flattened into one imagined reader, WHAT and WHY get flattened with it.

The impacts you describe end up generic, because specific impacts only make sense to the people they actually affect. The benefits you lead with end up abstract, because a benefit that matters to leadership is not the same one that matters to the person doing the work differently from next week. Communication that ignores WHO ends up technically accurate and practically useless, because nobody reading it feels like it was written for them.

The fix is not more empathy, or a longer comms plan. It is making the segmentation you already do instinctively for one or two people into something visible and repeatable for everyone.

This is what Stakeholder groups are for. Instead of holding "how would Rachel react to this" in your head, or in a spreadsheet nobody else can see, group stakeholders by how they experience the change, not by department or org chart position. Group by impact, then write for the group.

It does not need to be complicated. A handful of groups is usually enough. What matters is that the groups exist somewhere real, get referred to before comms go out, and stay current as the programme moves. That is the difference between segmentation as an idea and segmentation as a habit.