How to tell your team about a reorg and studio merger
You have to tell your team their group is being merged or moved. Here’s the exact way to open, what to say next, and how to handle the hard questions without guessing or sugarcoating.
How do you open the conversation?
Say what’s changing in the first sentence. Do it calmly, in plain English, and tie it to what happens next for your team.
Try this:
“I want to be straight with you. Our team is merging with [New Group] starting [date]. Day to day, that means our reporting line moves to [leader], and we’ll align our roadmap with [program/product] over the next [timeframe]. I’ll walk through what I know, what I don’t know yet, and how we’ll handle open questions.”
Then pause. Let it land. Keep eye contact.
What do you actually say?
You’re aiming for four beats: facts, impact, what’s unknown, and next steps. Keep it short and repeatable so people can share it accurately with others.
Use this structure word-for-word, then customize details:
1) Facts
“Here are the facts: We’re being combined with [New Group]. Our mission stays focused on [customer/problem]. Our reporting line will change from [old leader] to [new leader] on [date]. Our current projects continue for now; we’ll review priorities with [new leader] by [date].”
- 2) Impact on work and roles
- “For the next [2–6] weeks, your role, manager, and location stay the same. You’ll see changes in process: we’ll adopt [tool/ceremony] and follow [planning cadence] used by [New Group]. If a change to someone’s role is proposed, we’ll discuss it 1:1 before anything is finalized.”
- 3) What’s unknown (and how we’ll resolve it)
- “There are open questions: budgets for H2, ownership of [system/component], and who leads [function]. I don’t have those answers yet. I’ve logged them, and I’ll push for decisions by [date]. I’ll update you twice a week even if there’s no news.”
- 4) Next steps and support
- “Right after this, I’ll share a written summary and an FAQ doc we’ll keep current. I’ll hold office hours [times] and 1:1s for anyone who wants to talk. If you’re anxious about immigration, benefits, or location changes, bring it to me—we’ll coordinate with HR.”
How do you handle “Am I safe?” and other tough questions?
Don’t speculate. Don’t hide. Name what you know and how decisions will be made. Here are straight answers you can borrow.
- “Is my job at risk?” → “I don’t have a decision about reductions. If that changes, I’ll tell you directly and privately, not by surprise. If you want to sanity-check your risk based on scope, let’s talk 1:1. If we get into specifics on roles or severance, we’ll loop HR.”
- “Why is this happening?” → “The company is consolidating teams to ship faster and reduce overlap. I won’t spin it. Our job now is to make sure our customers don’t pay for the reorg.”
- “Who will be in charge?” → “Our new reporting line is [name]. Day-to-day decisions still flow through our leads until [date]. If there’s a conflict, I’ll escalate to [name] the same day.”
- “Will our roadmap change?” → “Likely. We’ll propose what we keep, what pauses, and what stops next week. You’ll see the draft and can flag risks before it’s final.”
- “Do we have to relocate or change hybrid schedules?” → “No location changes have been announced. If a move or RTO policy comes up, I’ll tell you and we’ll discuss options. Check with HR or an employment lawyer if you need guidance for your situation.”
- “What if I want to leave?” → “I won’t trap anyone. Before you decide, talk to me about what you want. If you’re sure, I’ll support a clean transition and reference.”
What if you don’t have answers yet?
Say that clearly, set a decision path, and timebox the uncertainty. People can live with “I don’t know” if they believe “I’ll find out” and “you’ll hear from me on Tuesday.”
Use this when you’re genuinely blocked:
“I don’t have that answer yet. The decision owner is [name]. I’ve asked for a call by [date] and I’ll update you by 4 p.m. that day, even if the answer is ‘still pending.’ In the meantime, here’s what you can count on: [two certainties].”
How do you open 1:1s with anxious people?
Different folks will react differently—anger, fear, resignation. Your job is to listen, reflect, and give one clear next step.
Open like this:
“How is this landing for you?” (Then be quiet.)
If they vent: “I hear you. You’ve put a lot into [project] and this feels like it moves the goalposts.” If they ask for certainty you don’t have: “I don’t want to guess. Here’s what I can promise: I’ll push for an answer by [date], and I’ll come back to you either way.”
How do you keep morale without sugarcoating?
Morale drops when people feel powerless and in the dark. Give them agency and information you can stand behind. Avoid pep talks and vague “bright futures.”
Do this instead:
- Name a specific customer risk the team can rally around: “Our SLA could slip during handover. Let’s assign two on-call pairs and a comms checklist.”
- Create a small win in 72 hours: “By Friday, we’ll map owners for every system and publish it.”
- Protect deep work: “We’ll keep two mornings meeting-free this week so we can ship [X] before the process changes land.”
- Celebrate facts, not hopes: “We cut [X] minutes from build times after merging pipelines.”
A script you can adapt
Before you walk in
- Confirm what is public and what is confidential with your leader and HR.
- Write a one-page brief: facts, impact, unknowns, next steps. Share it right after the meeting.
- List the top 10 likely questions and your exact answers; mark which require HR/legal review.
- Decide your update cadence and channels (e.g., Tue/Thu Slack post + weekly standup slot).
- Map decision owners and deadlines for every open question; book the meetings now.
- Identify at-risk people (immigration, new hires, key individuals) and schedule 1:1s within 48 hours. Keep notes of concerns and follow-through dates securely, not in public docs. Confirm with HR what you can record locally in your jurisdiction before you do it. If unsure, ask HR first.
Rehearse it before you say it
Before you stand up in front of your team, rehearse this announcement out loud with Rehearse and get feedback on clarity, empathy, and firmness. Rehearse gives you an AI partner who plays the other person — by voice or face-to-face — then coaches you on clarity, empathy and structure.
Questions people ask
Should I wait until I have all the details before telling the team?
No. Share the confirmed facts now and label what’s unknown. People handle bad news better than silence. Timebox decisions, name owners, and commit to updates so uncertainty doesn’t sprawl.
How do I stop side-channel rumors from taking over after the announcement?
Publish a written recap within an hour, including the top questions and answers. Set a predictable update cadence. When you hear a rumor, respond in-channel with the latest facts or say you’re chasing an answer by a specific time.
What do I tell my high performers who say they’ll quit?
Listen first. Ask what they want most that feels threatened. Offer one concrete step (scope, visibility, mentorship) you can deliver within two weeks. If they’re set on leaving, support a clean exit; trying to block them erodes trust with everyone else.
How transparent can I be about potential layoffs or comp changes?
Don’t speculate. Share only what’s confirmed and route specifics through HR. If asked directly, say what you know, what you don’t, and how decisions will be communicated. For legal or benefits questions, check with HR or an employment lawyer.
How do I brief stakeholders outside the team?
Use the same four beats: facts, impact, unknowns, next steps. Add clear asks—what you need from them to protect customers during the transition. Send the one-pager and book a short follow-up to close open items.
