The Engineering Manager Handbook (Development Manager) · Organisation and Strategy
Communicating Change: Reorgs and Hard News
Announce reorganisations and difficult decisions honestly and respectfully — what's changing, why, what it means for each person, and what isn't decided yet.
Scenario
Example organisation: leadership decides to merge two teams and move four engineers to a new platform team. The news leaks through a calendar invite titled "New team kickoff" before anyone is told. Rumours spread about layoffs; two engineers start interviewing elsewhere.
What you see on the team
- People hearing about changes from leaks, rumours or calendar invites.
- Announcements that explain what but not why.
- Anxiety and speculation filling gaps; productivity drops.
- Managers unable to answer basic questions ("what happens to my project?").
The common mistake
Communicating change late, all at once, by broadcast, without the reasoning, individual conversations or honesty about what's still undecided.
Why it happens
Leaders want certainty before speaking, and confidentiality matters during planning. But the gap between decision and communication is where rumours grow. Managers are often briefed late and can't answer questions, which feels evasive.
The playbook
Before announcing
- Get briefed fully; prepare answers to likely questions, including "I don't know yet".
- Plan the sequence: people most affected hear first, individually; then the teams; then the wider organisation — ideally within the same day.
The message (keep it short, honest and specific):
1. What's changing and when
2. Why - the problem it solves, with evidence
3. What it means for you (in 1:1s for those directly affected)
4. What's not changing
5. What we don't know yet, and when we will
6. How to ask questions; when we'll follow up
Individual conversations with each directly affected person, before or immediately after the announcement.
Follow up: a Q&A within a week, written answers to common questions, and extra 1:1 time.
Layoffs and other hard news: follow HR and legal guidance strictly, be direct and humane, don't spin, and support both those leaving and those staying.
What to say
Announcing a reorganisation to the team:
"We're merging checkout and payments into one team from 1 November, and four of you will form the new platform team. Why: every payment change currently needs both teams and lead time has doubled this year. I've talked to each of you individually already. What's not changing: our on-call setup and your managers for this quarter. What we don't know yet: the exact roadmap split — we'll have it by the 20th. Ask me anything, here or privately."
Trade-offs
- Communicating before every detail is settled risks some changes later; being explicit about what's undecided keeps trust.
- Individual conversations first takes time and coordination on the day; it's worth it.
- Confidentiality limits what you can say early; never deny something you know is coming.
Signals it's working
- People hear about changes from their manager, not rumours.
- Questions decrease after the follow-up Q&A.
- Regretted attrition doesn't spike after reorganisations.
- People describe the change as clearly explained, even if they disagree with it.
Key points
- Sequence the news: most affected first, individually; then teams; then the organisation — fast.
- Explain what, why, what it means, what isn't changing and what's undecided.
- Follow up with Q&A, written answers and extra 1:1 time.
- For layoffs and hard news, follow HR and legal guidance and be direct and humane.
Practice questions
A reorganisation leaked through a calendar invite. What should the communication plan have been?
Answer
Brief managers fully, tell the most affected people individually first, then the teams and wider organisation the same day, with the what, why, impact, what isn't changing and what's undecided — followed by a Q&A and written answers.
What should a manager say when they don't know an answer during a change?
Answer
That they don't know yet, when they expect to know, and how they'll communicate it — never guess or deny something they know is coming.
Why explain the 'why' of an organisational change?
Answer
People accept change better when they understand the problem it solves; without the reason, speculation fills the gap and trust drops.
Open in the app to mark lessons complete, take notes and track your progress.