Bringing Two Teams Together Without the Drama

What No One Tells You — #12 Bringing Two Teams Together Without the Drama YouTube: https://www.youtube.com/watch?v=ax0UTz7XUZg —————————————————————————————————————————————————— Hi everyone and welcome back to What No One Tells You, the podcast where I tell you what a normal training probably never does. My name is Claudia and this is episode 12, bringing two teams together without the drama. Today we're talking about something that happens all the time in corporate life, but rarely gets practical guidance. You're taking over a new team and integrating them with the one you're already managing. Maybe it's a restructure, maybe it's a merger, or just a double overall. Whatever the reason, you now have two teams that need to become one. And here is the truth nobody says out loud. Both teams are scared and watching you. And you're probably scared as well. Your existing team is wondering if the new people will take their attention, their resources, or their importance. The new team is wondering if this is really an integration or you're just being they're just being taking over. And you're in the middle trying not to screw it up. So today, I'm giving you rapid fire tips for your first 30 days to bring two teams together without a drama. Let's go. Let's start with something that seems obvious but most managers skip. Schedule oneto ones with key people from both teams in your first two weeks. Not just team meetings but individual conversations. Focus on the informal leaders, the longtimers, the people who know how things really work. In these conversations, ask them what's working well? What are you worried about? What should I know that nobody will tell me in a group setting? You'll be amazed what people share one-on-one that they never say in front of the group. These conversations give you the real intel you need to navigate the politics and understand what each team actually cares about. Now, here's something practical that will save you from making terrible decisions. Map out how each team currently works. but on paper. Create a simple document that shows you how each team handles the same key processes. Don't judge yet, just document. How do they approve budgets? How do they communicate with stakeholders? How do they handle escalations? How do they run their team meetings? When you can see both approaches side by side, you'll take much smarter decisions about what to keep, what to blend, and what to change. Plus, this document becomes proof that you actually listen to both sides before making changes. And speaking of making changes, here's something critical. Acknowledge different maturity levels directly. If one team is more advanced or structured than the other team, don't pretend they are the same. Say it out loud in your meetings. Team A has been doing this for 5 years. Team B is newer to the process. We are going to learn from each other, not force everyone to the same level overnight. This removes the shame and creates space for real collaboration. The less mature team stops feeling defensive and the more advanced team stops feeling like they're being dumped down. Everyone relaxes a bit. One thing you need to do immediately is set up shared communication channels. Both teams can use a team space or shared folders, whatever tool you use. Create a space where both teams can see the same information. where they can ask questions and collaborate. If one team has access to stuff that the other one doesn't, you're creating an insider outsider dynamic that will poison your integration. Make everything visible to everyone. When team A announces something, team B should see it at the same time, not 3 days later through the grape vine. Now, let's talk about something uncomfortable but essential. Be honest about the physically presence imbalance. If you are going to be physically present with one team most of the time and managing the other team remotely, don't pretend that this is equal. Tell the remote team directly. I won't be on site with you as often, but that doesn't mean you're less important. Here's how we will stay connected. Then overd deliver on video calls, responsiveness, and making them visible in company decisions. Show up to their virtual meetings early, not rushed or 5 minutes late. Answer their questions just as fast as you answer the on-site team's questions. Remote teams can smell fake promises from a mile away. So, be realistic about the situation and then compensate with your actions. Here's a trap most managers fall into. Don't let your workload double just because you now have two teams. This is really critical. You cannot do everything you did before times two. In your first 30 days, identify what you can standardize across both teams so you're not creating reports twice, attending duplicate meetings, or solving the same problem in two different ways. Maybe both team themes currently have separate monthly reviews. Combine them into one where both themes present. Maybe both themes send you different formats of updates. Create one template everyone uses. Your job is to integrate, not to clone yourself. Protect yourself from burnout by finding these efficiencies early because nobody else is going to do it for you. Now, here is something that actually builds real relationships. Create a low stakes project both teams can work on together. Not a fake team building exercise where they build paper towers, but a real project with real outcome. Something that requires input from both sides, but isn't missionritical if it's messy. Maybe it's improving a shared process. Maybe it's solving a customer problem that affects both regions. Or maybe it's creating a resource both teams need. But working together on something tangible builds relationships and shows you how the teams actually collaborate. And you will see who steps up, who holds back, and where the friction points are. This is all super valuable information. Let me give you a communication tip that prevents so much drama. When you make process decisions, write down why. Don't just announce we're doing this way now in a meeting and move on. Document the reasoning. We're keeping team A approval process because it's faster and we need speed right now, but we're adopting team B reporting template because it's more comprehensive and gives us better data. Send this in writing to both teams. When people understand your logic, they're less likely to feel like you're playing favorites. They might not agree with your decision, but at least they know you thought it through and considered both perspectives. Now, here is something you should build into your own routine. Check in regularly with those informal leaders from both teams. After your first week, after your second week, after your first month, touch base with those key influencers you identified early on and ask them, "How is this landing? What are people saying in the hallways or after meetings, what am I missing?" These people will tell you the truth before small problems become big drama. They're your early warning system and they can help you course correct before you lose credibility. Something that's easy to forget but incredibly powerful. Celebrate small integration wins publicly. When someone from team A helps someone from team B. When both teams collaborate smoothly on something. When you see good cross team communication happening naturally, call it out. Thank people publicly. Share the story with both teams in your updates on meetings. You're signaling what success looks like and reinforcing the behaviors you want to see more of. People need to see that integration is actually working, not just hear you talk about it. Now, let me give you something to do in your very first meeting with the combined teams. Establish shared goals early. Don't just talk about how the teams will work together. Tell them what you're all working toward together. What's the common objective that requires both teams to succeed? Maybe it's a customer satisfaction target, a regional growth goal, or it's improving a shared metric. When both teams understand they're rowing in the same direction toward a shared outcome, the us versus them mentality starts to fade. Give them something bigger than their individual team identity to focus on. And finally, here's something most managers don't think about until it's too late. Manage your own manager's expectations about the integration timeline. In your first 30 days, have an explicit conversation with your boss about what realistic success looks like and tell them that teams will be functioning together within 30 days, but real integration where they truly work as one will take minimum 90 days. Set realistic milestones and protect yourself from unrealistic pressure to have everything perfect immediately. If your manager expects instant harmony and you deliver messy reality, that's a problem. But if you've already set the expectation that month one is about building foundation and month two is about smoothing friction, you're managing their perception and protecting your own credibility. Here's the truth. Bringing two teams together can be messy, especially when they are in different locations and at different levels. People are scared, politics are real, and you're going to make some mistakes. But if you focus on listening, documenting before deciding, creating space for real collaboration and protecting your own energy so you don't burn out, you'll get through the these first 30 days without the drama. So, pick up the tips that fit your situation and use them this week. Schedule those oneto ones. Map those processes. Set up those shared channels. Establish those shared goals. Build that bridge. You've got this. And now you know because I told you. This was episode 12 of What No One Tells You, the podcast where we talk about real leadership. See you next time.