Skip to content

Networking

Build remote relationships across teams through shared work

Cross-functional relationships need a reason to begin and a way to continue. Use a small shared task to learn how another team works and make collaboration easier.

Illustration of three women working remotely, connected by flowing ribbons.

You know your immediate teammates well. You recognize the people in other departments from group calls, but you are less sure whom to ask when a customer question crosses several teams. Working remotely can make that gap easy to overlook until something urgent exposes it.

A useful cross-functional relationship begins before the urgent request. You do not need to become close friends or add a series of standing meetings. Start by understanding how another person’s work connects with yours, then make one shared task easier.

Notice where the work crosses a boundary

There is research behind taking those connections seriously. A 2021 study coauthored by a Berkeley Haas researcher examined communication data from more than 61,000 U.S. Microsoft employees. It found that the shift to company-wide remote work made collaboration networks more siloed. The analysis concerned an abrupt pandemic-era change at one company, so it cannot describe every remote workplace today.

Separately, MIT researchers examined an email network involving 2,834 research staff, faculty, and postdoctoral researchers. Their 2022 report described fewer weak email ties across research units after the shift away from campus. This was a finding about email-network structure, not a measured loss of innovation. These studies point to a potential gap in connections across groups, rather than a verdict on your organization’s work arrangements.

Make the issue local. Identify one handoff that regularly involves your team and another: a customer concern reaching product staff, a forecast reaching operations, or a policy change reaching managers. Find the person closest to that handoff. Ask your manager or an existing colleague for an introduction when you are unsure who owns it.

Begin with a question that respects their work

Instead of requesting a general networking call, explain the shared context. “I prepare the information your team receives before service launches. I would like to understand what makes it easier for you to act on it. Would a short conversation be useful, or is there an existing guide I should read first?”

Give them an easy way to answer without a meeting. Read the material they suggest. If you speak, ask what they need, when they need it, and what tends to arrive incomplete. Invite them to explain the constraints you may not see. Resist presenting your preferred solution before you understand their part of the process.

Keep the conversation within the scope of your work and the access you already have. If improving the handoff requires a change in ownership or priorities, involve the appropriate managers. A new relationship works better when it clarifies responsibilities than when it creates competing promises.

Make one small improvement together

Choose a task small enough to complete within your existing responsibilities. You might test a clearer request form, add missing context to an update, or ask for feedback on one handoff document. Agree on what each person will do and when you will review it.

Microsoft Research’s 2021 practice guidance recommends providing context upfront, making deadlines clear across time zones, and establishing norms for shared documents. It also distinguishes work that can happen asynchronously from situations that benefit from live discussion. Apply that distinction to the task rather than assuming every exchange needs a call.

  • Use a shared note for background, a draft, or a question someone can answer when their schedule allows.
  • Use a short conversation when you keep interpreting the same issue differently or need to work through a decision together.
  • Record the agreement so both teams can see the owner, next step, and timing.

Ask about their preferred channel and response expectations. An immediate reply should not become an unspoken requirement because your working hours overlap poorly. Put relevant updates where the team can find them, rather than letting the new connection become the only route to information.

Follow through, then leave room

Complete your part and share the result. “Your suggestion helped us include the information reviewers needed. Is the revised version easier to use?” Credit their contribution when you tell your own team about the improvement. If the experiment did not help, explain what you learned and adjust together.

From there, let contact follow the work. A relevant question, useful resource, or thoughtful check-in can sustain the connection without a recurring social obligation. After a month, consider whether you understand the other team’s constraints better and whether the handoff is clearer. Those are more useful signs of progress than counting how many colleagues have accepted a virtual coffee invitation.

More to read

Browse insights