Top Tips for Collaborating With New Teams – and Great Tools to Smooth the Process

I’ve managed mergers and acquisitions where two organisations needed to start collaborating from day one, often with significant cultural differences and no established relationships. These situations reveal what actually enables successful collaboration between people who’ve never worked together. It’s rarely the tools—it’s clarity, respect, and deliberate effort to establish genuine working relationships. Here’s what I’ve learned about collaborating with new teams and the practical elements that support it.

How do you communicate expectations with exceptional clarity?

When new teams start working together, ambiguity about expectations creates friction that stalls collaboration. People make assumptions about how decisions get made, what communication looks like, what quality standards apply. These assumptions often conflict. Without clear expectations, teams interpret each other’s actions through the lens of their own culture, which usually results in misunderstanding.

What I do before collaboration starts is establish explicit agreements. How will we communicate—what channels, what response time expectations? How do we make decisions—who has authority, how do we escalate? What quality standards apply? What does success look like? These conversations feel mechanical initially, but they eliminate enormous amounts of friction later.

I also explain the reasoning behind expectations. Not in a heavy-handed way, but so people understand the “why.” Someone from a fast-moving startup might see strict approval processes as bureaucratic until you explain why those processes exist—they prevent mistakes that would cause client impact. Understanding context helps people adapt to different ways of working.

How should you highlight individual team members’ strengths?

When teams first merge, people don’t know each other’s capabilities. Someone might have expertise that could solve a problem for the other team, but no one’s aware of it. This knowledge gap prevents collaboration—teams don’t think to reach across to groups they don’t understand.

I address this by explicitly introducing capabilities. In early meetings, I have people share what they’re genuinely good at. Not in a formal presentation way, but in conversation. “Sam is brilliant at customer retention strategies and has reduced churn by 30% in his previous role.” “Emma built the systems that process our supply chain data and understands it better than anyone.” These introductions help people see where value lies and think about how to collaborate.

I also watch for opportunities to connect people across teams when I see complementary strengths. If one person has solved a problem that another team is facing, I introduce them. These connections start building the informal networks that enable genuine collaboration.

Why should you establish communication protocols early?

Much of collaboration happens through communication, so how you structure that matters enormously. When people from different teams first work together, they often use communication styles that don’t align. Someone might want to discuss decisions via quick messages. Someone else wants detailed written documentation. Someone else wants to talk it through in person.

Define communication approaches explicitly. Where do different types of discussions happen? Quick decisions via message? Complex topics via video? Documentation of final outcomes in writing? How quickly do people need to respond? What information needs to be shared proactively versus on-request? These structures eliminate miscommunication that arises from people having different assumptions about how collaboration works.

I also introduce shared tools that make collaboration easier. Not necessarily new tools—often the best approach is agreeing on shared standards using tools everyone already knows. A shared document repository where decisions get documented. A shared project tracker so everyone sees progress. A communication channel for regular updates. The specific tools matter less than consistency.

Build Genuine Relationships Across Teams

Tools are enablers but genuine collaboration comes from relationships. When people know each other, when they understand each other’s pressures and perspectives, collaboration happens more naturally. The opposite—teams that don’t know each other—leads to misunderstanding and defensive interaction.

I create structured opportunities for people to meet. Not forced socialising which often feels uncomfortable, but purposeful interaction. Joint project kickoffs where teams meet around shared work. Cross-team working groups focused on problems that require both teams. Regular forums where people from different teams can share what they’re working on and learn about each other’s challenges.

I’ve also found that understanding context helps enormously. When two teams know why the other team operates how they do, they stop seeing difference as incompetence. Someone from a sales background might see operations as slow until they understand the cost of making mistakes in that function. Someone from operations might see sales as chaotic until they understand the competitive pressure of operating in markets.

The Tools That Actually Enable Collaboration

Several types of tools matter in cross-team collaboration. Project management platforms where everyone sees progress. Communication platforms where discussion happens in channels rather than fragmented email. Document collaboration tools where shared work gets developed together. Video conferencing that allows remote teams to have real-time conversation.

The specific platforms matter less than adoption and consistent use. What I’ve found is that the tool isn’t the solution—it’s the discipline of using it consistently. If some people use the shared document repository and others email versions around, you’ll have chaos. If everyone uses the same communication channels and responds within agreed timescales, collaboration flows.

The most successful cross-team collaboration I’ve managed has always been built on clear expectations, respect for different ways of working, and deliberate effort to build relationships. The tools support this by making it easier to communicate and coordinate, but they’re enablers, not substitutes for the human work of understanding each other and building trust.

Related reading: Is your team suffering in silence? Four reasons why your colleagues won’t discuss their mental health with you, Train disengaged employees like a pro with these development strategies and A checklist for bringing staff back following the pandemic.

You May Also Like

• 4 icebreaker activities for merged teams
• Top tips for getting teams on board during an acquisition