How to Communicate Change Without Losing Trust
Companies absorb hard change routinely — pivots, restructures, missed years, even layoffs — without losing the confidence of their people. What loses confidence is a specific set of communication failures around the change: hearing it late, hearing it from the wrong person, hearing a version that denies what it costs, or hearing something that does not match what everyone can plainly see. All four are avoidable, and none of them are about the substance of the decision. This page is the CEO-level version: change you decided, that affects the whole company, and that you have to announce.
What’s inside
Trust is lost in the gap, not in the change
Five things every change message needs
The sequence
What not to do with bad news
The second and third telling
When you cannot say everything
Where Blomma fits
Trust is lost in the gap, not in the change
When people learn something significant is changing, they stop working and start calculating — about their job, their team, their standing. Every hour between learning that something is happening and learning what it means is an hour of anxiety, and anxiety fills with the worse explanation, because a vacuum always does.
That is where trust is actually lost. Not in the decision, which most people will accept if it is explained, but in the interval where they had incomplete information and drew conclusions. And once a conclusion has formed — that this was political, that leadership is hiding something, that more is coming — correcting it costs far more than getting ahead of it would have.
So the operating principle for all company-wide change:minimise the gap between the first signal and the full explanation.Everything else follows from that. It is why leaks are so damaging, why partial announcements are worse than none, and why the instinct to wait until you have every detail settled is usually right in substance and wrong in timing — you settle the details first, then announce everything at once.
Five things every change message needs
Every company-wide change message needs all five. Missing any one produces a predictable failure.
The problem, before the change.People accept change when they recognise the problem it solves. Lead with the change and they will read it as arbitrary, or as politics, and immediately locate themselves in it. Two or three sentences on what was not working.
The change itself, plainly.No euphemism. If it is a layoff, say layoff. If it is a pivot, say the old plan is not working. Softened language does not soften the content; it just signals that you are managing them, which costs more than the plain version.
What it costs.Every real change costs someone something. Naming it is what makes the rest of the message credible — and your audience can already see it, so denying it only demonstrates that you either cannot see it or will not say it. “This will slow cross-team work for a quarter” or “some people are losing scope they cared about” buys you enormous credibility.
What is not changing.The most underused sentence in change communication. Uncertainty expands to fill available space; naming the boundaries reduces how much of the company treats the change as personally threatening. Cheap and highly effective.
What happens next, and when.Specific next steps and dates, including when you will say more. “We’ll have answers on team assignments by Friday” is worth more than any reassurance.
The sequence
Order matters as much as content, and the default — telling people as it becomes awkward not to — is the worst available option.
Anyone personally affected, individually, first.Before any group communication. Someone learning their role changed in an all-hands, alongside forty colleagues, is a small humiliation and the most reliable cause of resignations over process rather than substance.
Your executives and managers, with the reasoning, before they have to answer for it.They are the channel. A manager who learns the change at the same time as their team cannot answer questions, so they either deflect or improvise — and both damage trust in the layer people actually rely on. Give them the reasoning, not just the conclusion, and time to ask their own questions.
Then the whole company, live.Not a written note alone. Take questions in the room even when they are uncomfortable, and answer the uncomfortable ones directly. The willingness to be asked is a large part of what makes the message land.
Written summary the same day.Because people forget the meeting and re-read the document, and because anyone absent should not get it secondhand.
Compress all of this into a single day if you possibly can. A change that dribbles out over a week generates a week of rumour.
What not to do with bad news
Four specific failures, all common.
Do not bury it in good news.The sandwich structure is transparent and it teaches people to discount your positive statements. Lead with the hard thing.
Do not overclaim certainty about the future.“This is the last change we’ll need to make” is a promise you cannot keep, and breaking it costs more than the original news. “I don’t know yet, and I’ll tell you when I do” is more credible and durable.
Do not attribute it entirely to external forces.Some of it usually was your call. A message where nothing was anyone’s decision reads as evasive, and taking your share — “we hired ahead of the revenue and I got that wrong” — does more for trust than any amount of confidence.
Do not disappear afterwards.The instinct after a difficult announcement is to give people space. What they read is avoidance. Be visible, in the corridors and in the follow-up sessions, particularly in the first week.
The second and third telling
One announcement is not communication. Your repetition threshold is roughly a tenth of what the organisation needs.
The first telling is heard through anxiety, so most of the content does not land — people hear the part about themselves and little else. The second telling, a week later, is when the reasoning starts to register. The third, a few weeks on, is when it becomes the shared account of what happened.
So plan all three. Say the same thing, with the same reasoning, in different formats: the all-hands, the written follow-up, the team sessions, the one-to-ones. Consistency across tellings is what converts an event into settled history; variation across tellings is what convinces people something is being hidden.
And listen between tellings. The questions you get in week two tell you which part did not land, and the second telling should address exactly that rather than repeating the original script.
When you cannot say everything
Sometimes there is genuinely information you cannot share — a deal under NDA, a personnel matter, something legally constrained.
The workable approach is to name the boundary rather than pretend it does not exist. “There’s a piece of this I can’t discuss yet, and I’ll tell you when I can” is credible. People are considerably more tolerant of acknowledged limits than of the feeling that they are being handled.
What does not work is a message with an obvious hole in it presented as complete. Your team will identify the gap, fill it with speculation, and — worse — conclude that you were willing to present an incomplete picture as a full one.
And never say something you will have to contradict later. If a second change is likely, do not promise there will not be one. The short-term reassurance is not worth the long-term cost, and you will pay the long-term cost in the middle of the next difficult announcement.
Where Blomma fits
The hardest part of a change announcement is the composition: saying the plain version rather than the softened one, naming a cost rather than selling a benefit, and taking your share of the responsibility without undermining confidence in your judgment. Those are competing pressures, and there is nowhere to test the balance — your executives are inside the change and your board has its own view.
Blomma is an always-on AI career coach with no stake in your company. Use it to draft the message against the five components and check which one you have skipped — usually the cost. Use it to rehearse the questions you least want to be asked in the room, which is what determines whether the live session builds trust or spends it. Use it to prepare the individual conversations that have to happen first. And use it between the first and second telling, to work out what did not land.
The second application is your managers. They deliver most of this, about a change they did not decide, and most have never been taught to communicate a decision they may privately disagree with without either undermining it or reciting it. That is where cascade failure actually happens, and it is coachable..
People absorb hard change. What they do not absorb is finding out late, from the wrong person, in a version that denies what it cost them.