Wrivio
Get Wrivio
5 min readBy Wrivio Team

How to Write a Reorganization Announcement

A reorganization announcement is read by anxious people looking for one thing: what this means for me. Most reorg messages fail that reader. They open with strategy, lead with org-chart boxes, and bury the human questions under corporate framing. By the time the reader finds out whether their job, their manager, or their team changed, they have already filled the silence with the worst-case version.

You cannot make a reorg painless. You can write the announcement so it answers the real questions in the order people ask them, which is the difference between a message that calms a team and one that sets off a week of hallway speculation.

Lead With What Changes, Not Why

Executives want to explain the reasoning. Employees want to know the outcome first and the reasoning second. Give them the outcome in the first few lines: what is changing, who is affected, and when it takes effect. The strategy can follow.

This inverts the instinct to “set the context” before the news. Context before news reads, to an anxious reader, like stalling. Say what is happening, then explain why. The same ordering helps any change message, as covered in how to write a policy change announcement and how to announce a new process at work.

Answer The Three Questions Everyone Has

Every reader of a reorg is silently asking three things: Is my job safe? Who do I report to now? What do I do differently on Monday? An announcement that leaves any of these unanswered creates exactly the anxiety it was meant to manage.

Before:

As part of our continued evolution toward a more agile and customer-centric operating model, we are excited to announce a strategic realignment of our organizational structure to better position us for the opportunities ahead.

After:

We are reorganizing the product and support teams, effective November 1. No roles are being eliminated. Most people keep their current manager; the exceptions are the three support leads, who will now report to Maria, and I will meet each of them this week. Day to day, nothing changes until November 1, and I will send the new team structure by Friday.

The second version answers the three questions in the first breath. It is not more cheerful. It is more honest, and honesty is what lowers the temperature.

Say What You Cannot Say Yet

Reorgs often land before every detail is settled. Pretending otherwise backfires, because people can tell when an answer is being withheld. Name the open questions and commit to a date for answering them.

“We have not finalized the reporting lines for the design team; I will confirm those by the 15th” is far better than silence on the point, which reads as bad news being managed. For handling the change itself with your team, the UK advisory service Acas publishes practical guidance on managing organizational change that is worth a look.

Make The Follow-Up Real

End with what happens next and when, not with reassurance. “My door is open” is less useful than “I will hold a team call Thursday at 2pm and answer questions live, and you can send questions ahead to me directly.” Specific access beats a warm sentiment.

A Wrivio Context for a reorg announcement could say:

Rewrite this reorganization announcement so it leads with what is changing, who is affected, and when, before any strategy. Explicitly answer whether roles are being cut and whether reporting lines change. Keep every name, date, and structural detail exactly as written. Do not add optimistic spin, and do not state anything as decided that my notes mark as open.

Press Ctrl+Shift+Space, paste your draft, and check the diff to confirm no open question got presented as settled. For the narrower case of a single team changing, see how to write a team change announcement.

Common Questions

What should a reorg announcement say first?

What is changing, who is affected, and when it takes effect, before the strategy or reasoning, because an anxious reader reads context-before-news as stalling and fills the gap with the worst case.

What do employees most want to know?

Three things: whether their job is safe, who they report to now, and what they do differently on Monday; an announcement that leaves any of these unanswered creates the anxiety it was meant to reduce.

Should I announce before all the details are settled?

You can, but name the open questions and commit to a date for answering them, since withheld answers read as bad news being managed, which is worse than an honest “not decided yet.”

How should the announcement end?

With specific next steps and access, such as a scheduled team call with a time and a way to send questions ahead, rather than a vague “my door is open.”

Download Wrivio for Windows to rewrite a reorg announcement so it answers the real questions before people ask them.