Unification of Teams: How to Do It Right

Know the Expected Outcome

Before anything else, understand what this unification is expected to produce. Faster delivery? Lower cost? One consistent customer experience instead of two? A single source of truth? These are not the same goal, and chasing one without clarity on the endgame is a recipe for disaster.

Get the answer from whoever asked for this directly. Write it down. Make sure both teams hear the same version of it, in the same words, from you. This is your north star. Come back to it often.

Give Them a Framework to Start With

People panic when a unification gets announced, and nothing concrete follows it. They don't know what's expected of them, and uncertainty is worse than almost any clear direction you could give them, even an imperfect one.

This is where you step in with something to hold onto. Build an initial framework, maybe with input from the former leaders, maybe with a few trusted people from each team, but build it before you try to get broad input from everyone. In the early days, most of your people are heads down keeping the ship running. They don't have the bandwidth to help you design the change at the same time they're doing their actual jobs. You absolutely want their input eventually, and you should go get it, but initially what they need is for you to tell them clearly what's expected of them right now. Give them that first. Refine it with their input as you go.

Once you've gathered that input, go back and actually reconcile how the two teams work instead of just defaulting to whichever process was already in place. Two merging teams almost always bring two different definitions of quality, two different workflows, two different ideas of what good looks like. Skip this step, and you end up with a team that's unified on the org chart and still split in practice, one half still doing things the old way under a new banner.

Keep People in Mind

A unification isn't just a structural change; it's something happening to real people with real stakes. Their day-to-day work is shifting. Their customers might notice something different. Their career path, their bonus, their sense of job satisfaction- all of it is in question, whether anyone says so out loud or not.

Get feedback regularly. Then actually tell people what you did with it. Nothing erodes trust faster than asking for input and then going quiet; people assume it went nowhere, even when it didn't. And keep reminding them why this change is happening in the first place. The reason that made sense in the kickoff meeting fades fast once people are heads down in the day-to-day, so you have to keep saying it.

Give the Sponsor What They Actually Need

The person who asked for this unification needs more from you than status updates. A few things to put in front of them early, before they have to ask:

• Give them a timeline with real phases in it, not just the outcome you agreed on. Ambiguity about when they'll see results reads as stalling to a sponsor, even when things are genuinely on track. A rough map of what happens and when takes that pressure off both of you.
• Tell them what you need from them. If you'll need air cover for an unpopular call, budget, or their visible backing at a specific moment, name it early. Finding out mid-stream that you needed something they didn't know to offer costs you time you don't have.
• Flag retention risk honestly. If there's a real chance you lose strong people during the transition, especially anyone hard to replace, the sponsor needs to hear that from you early, not after someone's already handed in notice.
• If either team touches customers, address that directly. Tell them how you're protecting continuity, and what the plan is if something does slip. That reassures them and protects you if something goes sideways later.
• Be clear about where your authority ends. Tell them what you'll simply decide versus what you'll bring to them first. That clarity keeps you from getting second-guessed on calls that were yours to make, and keeps them from finding out too late about something they wanted input on.

Keep Leadership Informed

Unifying two teams takes time, and leadership's patience for ambiguity is usually shorter than the timeline actually requires. Keep them updated regularly, and don't just report activity; report evidence. Show them proof that the change is working and that it's tracking back to the original objectives. If you don't actively provide that evidence, leadership will draw their own conclusions from whatever they happen to notice, and that's rarely the full picture.

Create a Shared Win, Carefully

Find something small the combined team can finish together in the first few weeks, and make sure everyone sees it land as one group, not two halves cooperating. A real shared result, not a team lunch, is what starts to make unification feel true instead of just announced.

Be mindful of the context people are experiencing that win in. Unifying two teams often comes with headcount changes, and some of your people may be mourning colleagues who didn't make it to the other side of the transition. A shared win doesn't erase that, and it shouldn't try to. It just gives a team that's starting to come together something real and positive to stand on, even while some of them are also grieving who isn't standing there with them.

Be the Steady One

Your own presence matters more than almost anything else on this list. People watch how you react far more closely than they listen to what you say. When a process fight breaks out, when someone pushes back on the plan, when the first real friction point hits, your steadiness becomes the floor the rest of the team stands on.

The moment you look rattled or uncertain, that uncertainty spreads through the team fast. Staying calm doesn't mean you don't take the concerns seriously. It means you choose to be the stable thing in a moment when everything else feels like it's shifting under people's feet.

There's more than one way to unify two teams, and plenty of consultants will tell you theirs is the only right one. I won't. Bringing two teams together is complex, emotional, and challenging. You face the best in people and their worst fears together. If you are navigating a change like this, let me know! I want to hear what has been the hardest or most successful. I want to hear what you are dreading or optimistically anticipating. You are not alone! Share your experiences in the comments!

Let's get out there and Make It Real!