What hurts people most in organizational change is often not the change itself but the information vacuum it leaves behind. Most changes are planned well in advance; what truly spirals out of control is the speculation that grows in that vacuum.

People fill that void with scattered bits of information. Half a sentence overheard by the water cooler, a recalled message, a colleague suddenly taking leave early — any of these can be pieced into a story that has nothing to do with the facts, and it spreads faster than the facts do. By the time the official announcement arrives, many people are already acting on the version they have assembled for themselves.

So my principle is simple: sync out the objective facts that have been officially confirmed as soon as possible, and make clear what is decided, what is not, and when the next update will come. It is not about rushing to announce plans that are not yet settled, but about giving speculation a place to stop — turning “we don’t know” into “we know: these few things are not yet decided, and we will sync again before date X.”

In One Sync, Make Four Things Clear First

Don’t cover up problems, and don’t treat anxiety as an answer. A single sync should make at least four things clear:

  • What happened: the confirmed changes, stated in objective language, without sugarcoating.
  • Who is affected: who will be affected and which work will change, grounded in specific people and specific work.
  • What to tackle first next: the most urgent problem right now, not every problem.
  • How to proceed now: who is handling it and when there will be an update, even if there is no final result yet.

The pitfall I have fallen into is ending with “don’t worry, everyone.” That line is the most useless of all — it gives no information and no path forward, and it makes people suspect you are hiding worse news. The more honest way is to acknowledge the uncertainty: “We don’t have a conclusion on this part yet; we expect to give you one before date X.” Admitting you have no answer preserves trust better than pretending you do.

To Superiors, the Team, and Collaborators: Three Different Messages

About the same thing, the three layers of people don’t need the same announcement.

To superiors, the focus is on goals, risks, and stability requirements: which goal currently in motion this change will affect, what they care about most, and what support we need. Superiors generally don’t look at details; they look at risk exposure and the boundaries of responsibility.

To the team, what members most want to know is not the strategic narrative but “what will I still be doing next month, has my reporting line changed, and under what priority should I keep working.” Letting them know how to act right now matters more than hearing the vision again.

To collaborators, explain whether the team’s position, the point of contact, and the way of collaborating have changed: whom to reach from now on, whether the rhythm has changed, and which boundaries still hold. This part is the easiest to miss — collaborators are not on your team, and no one will come chasing you to ask.

When Wrapping Up, Ask Yourself One Question

Good organizational communication never aims to eliminate all unease — that can’t be done. What it aims to do is let everyone, amid uncertainty, still tell apart what is fact, what is responsibility, and what is the next step. When information gives speculation a place to land, people rarely need to make up stories to reassure themselves.

Every time I finish a sync, I run through it in my mind: after hearing this, can the other person say “what is settled now is X, what is not settled is Y, and we will sync again before Z”? If they can, this round of communication counts; if not, I add another round.