We hear a lot about how technology makes remote work seamless — Slack, Zoom, Teams, all the apps that promise to keep us connected no matter where we sit. But the research tells a more complicated story. A study of over 61,000 Microsoft employees found that after the company went fully remote, people spent about 25% less time collaborating with colleagues outside their immediate group. That’s not seamless — that’s a real loss of cross-functional connection, and it’s worth sitting with before we assume the tech alone is doing its job.
Communication
Collaboration
Tools
Work Boundaries
Heads up — this post may include links to things I use or like, and I might earn a little something if you shop through them. Doesn’t cost you anything extra, and I only mention stuff I’d actually recommend.
The Myth of Seamless Connection
When every tool promises to “bring the office to you,” it’s easy to assume that installing the right app stack will fix distance. But the data from the Microsoft study — published in Nature Human Behaviour — shows that remote work actually made collaboration networks less interconnected. People communicated more with their inner circle and added new collaborators more slowly. The technology didn’t fail — it just replicated the silos we already had, and in some ways deepened them.
You know the one — you’re in back-to-back Slack threads with the same three people all day, but you haven’t talked to someone from design or finance in weeks. The apps are on, but the cross-team connection faded without anyone noticing.
Part of the issue is that synchronous tools like video calls mimic face-to-face interaction well for scheduled meetings, but they fall short on the spontaneous hallway run-ins that build weak ties. The Berkeley Haas write-up of the same study notes that both individual remote status and collaborators’ remote status independently affected collaboration patterns. In other words, it’s not just about what tools you use — it’s about who else is remote, and how your combined setup shapes communication.
✦
What the Data Actually Says
That number comes from a careful statistical comparison that isolated the effects of remote work from other pandemic disruptions. The researchers compared employees who were already remote before the mandate (about 18% of the sample) with those who abruptly shifted. The result was clear: remote work caused collaboration networks to become more siloed, with slower addition of new collaborators and more frequent communication within existing inner networks.
Interestingly, the study also found a roughly 5% decrease in hours spent in meetings — which suggests the pandemic-era meeting glut wasn’t caused by remote work itself, but by other factors. What did increase was asynchronous communication: more emails and instant messages, less real-time conversation. That shift has real consequences for how teams build trust and resolve complex issues.
For anyone managing a remote team, the practical meaning is straightforward: if you want cross-team collaboration, you can’t just install Teams and hope for the best. You need to intentionally create opportunities for people to connect across groups — perhaps through shared projects, cross-functional standups, or periodic in-person or synchronous events.
The Paradox of Digital Tools
A separate survey of 295 U.S. tech professionals, published as a preprint on Research Square, found that using digital management tools like Slack, Trello, and Microsoft Teams was associated with a moderate productivity increase. That sounds reassuring — but the same research also identified limitations. Tools manage scheduled communication well, but they miss the informal exchanges that happen naturally in an office. Technical issues like poor internet connectivity and interruptions during virtual meetings undermine their effectiveness.
The paper also pointed out a gap: most studies look at tool use or productivity in isolation, without considering work-life balance, collaboration quality, or the overall remote work experience. In practice, piling on more apps can actually make things worse — especially when each tool has its own notification system and etiquette.
More tools don’t always mean better teamwork. Each new app adds a layer of context-switching and notification fatigue. Before adding another platform, ask whether it actually solves a specific problem — or if you’re just trying to fill a collaboration gap that technology alone can’t close.
One of the more nuanced findings from the affordances literature — summarized in a Small Group Research article — is that enterprise social media tools offer visibility, persistence, editability, and association. Those features can strengthen team processes like information sharing and coordination, but they can also create tension. Persistent content can discourage people from posting candidly, and the visibility of everyone’s activity can increase pressure to perform.
The key is to choose tools deliberately and set clear norms around how they’re used. For instance, some teams adopt a “async-first” approach — using Slack for quick questions but saving deep discussions for scheduled calls. Others find that a single project management board replaces the need for multiple chat channels.
Making the Tech Work for You
So what do you actually do about it? The research points to a few practical strategies, and each one involves a conversation — not just an app installation.
Set explicit norms around response times. If your team expects instant replies on chat, you’ll never get deep focus time. Try saying: “I’ll check messages at the top of each hour — if something is urgent, please use the @here tag in our urgent channel.” That gives permission for everyone to step away.
Use async tools for what they’re good at. Email and shared documents are excellent for decisions that don’t need immediate debate. Reserve synchronous calls for complex discussions or relationship building. One team I know uses a simple rule: if a decision can wait four hours, put it in a shared doc. If it needs a decision in the next 30 minutes, schedule a five-minute call.
Build cross-team connection intentionally. Since remote work naturally shrinks your collaboration network, you have to fight that tendency. A weekly “ask me anything” thread in a shared Slack channel can work, or a monthly cross-functional project showcase. The goal is to create a reason for people to interact outside their core group.
Talk about the tools themselves. If your team is feeling tool fatigue, say so. “I’m noticing we have four different places where project updates go — can we agree to use just one for the next month and see if that simplifies things?” That kind of direct conversation is more valuable than any app feature.
Some teams find that embracing asynchronous communication — documented well in our guide to async teamwork — reduces the pressure to be always-on while still keeping everyone informed. The trick is matching the medium to the message and being honest about what works and what doesn’t.
✦
The Hybrid Reality
Many of the studies I’ve drawn on here point toward hybrid models as a way to balance flexibility with connection. The idea isn’t new — research from Gajendran and Harrison (2007) already noted that hybrid arrangements help sustain team cohesion while accommodating remote needs. But the key is intentionality: having regular in-office days when people are actually co-located, not just sitting on separate Zoom calls from the same building.
If you’re in a fully remote setup, you can still simulate some of those benefits by scheduling synchronous “co-working” sessions where people work quietly together on video, or by rotating who facilitates team meetings to give everyone a stake in the conversation. The tools can help — but only if you’re clear about what you’re trying to achieve.
What’s the one collaboration pattern you’ve lost since going remote that you miss most — and is there a way to intentionally recreate it without adding another tool?
The technology isn’t broken — but expecting it to automatically connect remote teams is a setup for disappointment. The real work is in choosing fewer tools, setting clear norms, and creating intentional opportunities for cross-team interaction. That’s where the seamlessness lives, not in the app store.