Plan Communication for a Team Merger When Responsibilities Overlap

Two teams start sharing work before anyone has decided who reports to whom, and employees notice the overlap within days. They see two people doing the same task, or nobody covering a task at all, and they start filling in the blanks themselves. An HR business partner who waits for final org decisions before saying anything lets rumors write the story. One who announces decisions that are not yet approved creates a mess that takes months to undo. The way through is a message that separates what is confirmed from what is still under review, and a manager who can deliver that message without flinching.

Why this conversation goes wrong

Most leaders default to one of two mistakes when teams merge. The first is silence. They wait until every reporting line and title is settled before saying a word, and in the meantime employees compare notes, trade guesses, and assume the worst. The second mistake is the opposite problem, a leader who wants to sound decisive and announces something that has not been approved, like a full absorption of one team into another. When that turns out to be wrong or incomplete, employees stop trusting the next update too.

Overlapping responsibilities make this worse because people cannot tell if a coworker doing their job is a temporary fix or a sign they are being replaced. This is the same dynamic that shows up when a trainer and a line manager both think they own coaching a struggling employee. The piece on how to Clarify Coaching Responsibilities Between Trainers and Line Managers covers a related case, two people with real claims on the same task, and no one has said out loud who does what this week. A merger just puts that problem in front of an entire team at once.

How to prepare

Before any meeting happens, get the leader to write down three things in plain language. Why are the teams coordinating right now. What will each group actually do this week, not eventually, this week. Where can an employee take a question if they have one. If the leader cannot answer all three without guessing, the message is not ready.

Separate temporary task ownership from anything permanent. Who is coordinating daily assignments next month is a fact you can state today. Who reports to whom in six months is not, and saying it as if it were settled will backfire the moment it changes. Write these two categories down separately so the leader sees the line between them before they are in front of the team.

Give every manager who will deliver this message the same words. Not a summary of the idea, the actual sentences. A manager who paraphrases a sensitive announcement in their own words, without practice, tends to either soften it into vagueness or add a detail that was never approved. Consistency matters more than personality here.

What to say

At a planning session, a leader named Priya told her HR partner, "I want to tell both teams that the old operations group is being absorbed into ours." Her partner asked, "Has that been approved anywhere, or is that your read on where this is headed?" Priya paused and admitted, "The leaders have only agreed to combine the intake work starting next month. Nothing beyond that is decided."

Her partner suggested a different opening. "Say the part that is true and specific. Starting October 1, both teams will use one shared intake queue. Marcus will coordinate daily assignments across both groups. We are reviewing longer term reporting and role decisions, and we will share those once they are approved, not before." Priya added the piece that closes the loop for employees, "If you have a question about how this affects you, bring it to your manager or send it to the shared change mailbox, and we will track it."

Notice what that message does not do. It does not promise a date for the bigger decisions because the leader does not control that date. It does not use a word like absorbed, which implies one team disappearing into another, when the actual agreement is much narrower. It gives employees a real action, a manager and a mailbox, instead of a vague invitation to bring up concerns whenever.

Mistakes to avoid

A leader who wants to appear confident will sometimes answer a hard question with a guess dressed up as fact. An employee asks whether their title will change, and the leader says probably not, because that feels reassuring in the moment. If the answer turns out to be wrong, every future message from that leader gets discounted. Tell leaders directly that a guess is worse than saying the decision is not made yet.

Managers who deliver this message often want to soften it further when an employee pushes for more. They start speculating about who will be selected for which role or hinting at outcomes they have heard informally. This is where a shared script matters most, because a manager under pressure in a one on one conversation will reach for whatever sounds kind, and kind is not the same as accurate. Give managers a fixed line for this exact moment, something like, we will share the approved decision when it is ready, and I do not have more to add today. Then coach them to actually stop talking after that sentence instead of filling the silence.

Another common error is treating this as a single announcement instead of a sequence. Employees will ask the same question again in two weeks if nothing has changed. A leader who goes quiet after the first message looks like they are hiding something, even if there is genuinely nothing new. Set a date for the next update before the first message goes out, and put that date in the message itself.

How to practice and score it

Run a short review before the real meeting, fifteen minutes is enough. Put the draft message next to a simple table with four columns, confirmed work, pending decision, owner, and next update date. Have the leader or manager explain the change out loud in their own words, without reading from the script. Anything they say that is not backed by a row in that table needs to come out of the message. This catches the moment where someone adds a detail they believe is true but has not actually been approved.

Rehearsing this out loud, with someone pushing back the way an anxious employee would, changes how it lands. DealSpeak is built for exactly this kind of rehearsal, a manager practices the exact exchange, including the pointed follow up question about job security, and gets scored on whether they held the line between confirmed work and pending decisions. The HR and Leadership practice conversations on the platform cover this scenario alongside related ones, so a manager can run the merger announcement, get feedback on where they drifted into speculation, and try it again before facing the real team. If your team merger also means employees will train each other during the transition, the guidance on how to Gather Training Examples While Protecting Employee Information is worth reviewing too, since shared work often means shared documentation, and that documentation can carry more employee detail than it should.

Score the practice run on three things, not five or ten. Did the manager state only what is confirmed. Did they name a real owner and a real next date instead of a vague someday. Did they resist the urge to guess when pushed. A manager who passes on those three points in practice will hold up under the real pressure of a room full of people who just found out their job is about to look different.

The close

A team merger will always create a few weeks of genuine uncertainty, and no message erases that. What you can control is whether employees trust the person telling them about it. Give leaders a message built only from what is true today, a clear next date, and a real place to send questions, and the rumors have much less room to grow.