Remote teams perform best when they default to asynchronous communication – but the teams that thrive long-term are the ones that know exactly when to bring people together in real time. The evidence is clear: synchronous interaction remains essential for creativity, trust-building, and complex decision-making, even in the most async-first organisations on the planet.

There’s a narrative in remote work circles that meetings are inherently wasteful – that every Zoom call is a productivity killer, and the ideal distributed team would never need to speak to each other at all. It’s an understandable reaction to the meeting overload many of us experienced during the pandemic pivot. But it oversimplifies the reality of how humans collaborate, and it risks throwing out something genuinely valuable in the pursuit of calendar freedom.

In fact, the argument for synchronous interaction may run deeper than productivity. It may be about something more fundamental – how we learn to be human in the first place.

Let’s look at what the research actually tells us – and how the smartest remote teams are getting the balance right.

The async-first default is correct – but incomplete

The case for asynchronous communication as the baseline is well-established. Teams with strong documentation practices experience 67% fewer blocking delays compared to those relying primarily on synchronous communication, according to a McKinsey analysis from 2025. When information lives in writing – in handbooks, project management tools, and shared documents – people can access it on their own schedule, across any time zone, without waiting for someone to be online.

This is why organisations like GitLab have built their entire culture around the handbook-first principle. At GitLab, with team members spread across more than 65 countries, Slack messages auto-delete after 90 days. Anything that matters gets documented in the company handbook or started with a merge request. Automattic – the company behind WordPress, with over 1,500 employees in 45 countries – operates on a similar philosophy with their internal P2 platform: “P2 or it didn’t happen.”

These are not anti-meeting companies. They’re companies that have learned to protect synchronous time by making it deliberate, rather than defaulting to it out of habit.

The developmental case for synchronous interaction

Here’s where it gets interesting – and personal. I’ve been listening to Jonathan Haidt’s The Anxious Generation, and while much of the book is directed at parents and educators, one argument stopped me in my tracks as someone who thinks about remote teams every day.

Haidt describes synchronous communication – the real-time, face-to-face give-and-take of a play-based childhood – as essential to learning how to interact as a human being. The playground teaches children turn-taking, reading facial cues, calibrating tone, managing conflict in the moment. These aren’t soft skills we pick up incidentally. They’re the foundation of every effective collaboration we’ll ever have.

The problem, as Haidt frames it, is that a generation raised on what he calls a “phone-based childhood” has had far less exposure to this kind of interaction. Online communication changes the equation in subtle but important ways. The cost of entry is low – you can join a group chat, a forum, a video call with a single click. And the cost of exit is equally low – you can leave, mute, or simply stop responding. There’s less skin in the game, less of the investment that makes in-person relationships feel consequential. We have apps now that can tell who’s speaking for longer than others in a meeting, but these are the rules we used to learn naturally in the playground or on a sports team – reading the room, knowing when to speak and when to listen.

There’s also the question of one-to-one versus one-to-many communication. In person, most of our formative interactions are one-to-one or in small groups where everyone is known to each other. Online, the default tends toward broadcasting – posting to channels, speaking to a room of tiles. The intimacy and accountability of a genuine two-way exchange gets diluted.

This matters for remote teams because we now have a cohort entering the workplace – many of whom also did significant portions of their education remotely during lockdowns – who may not have had the same depth of practice at real-time human feedback that previous generations took for granted. And the workplace is increasingly the place where that learning needs to happen, whether we planned for it or not.

The implication isn’t that remote work is the problem. It’s that even in the most thoughtfully async workplace, there need to be spaces for synchronous interaction – not just for productivity, but for human development. Brainstorms, pair work, even casual video chats where people can practise the messy, unscripted art of real-time conversation. These aren’t luxuries or nostalgia for office life. They’re how we help people become effective collaborators – something that matters regardless of where the work gets done.

When real-time interaction actually matters

So if async is the sensible default, when does synchronous communication earn its place? Research points to several specific scenarios where real-time interaction delivers something that no amount of documented messaging can replicate.

Creative and divergent thinking

Brainstorming is the classic example – and it’s not just a management cliché. The rapid-fire exchange of half-formed ideas, the ability to build on someone’s thought before it’s fully articulated, the energy that comes from collective improvisation – these require the kind of low-latency interaction that only real-time conversation provides. You can collect ideas asynchronously, certainly, but the generative collision of perspectives needs shared presence, whether physical or virtual.

Complex problem-solving

When a team is troubleshooting something genuinely complicated – a production issue, a strategic dilemma, an unexpected regulatory change – the back-and-forth required to diagnose the problem and converge on a solution benefits enormously from synchronous discussion. The feedback loop in async channels is simply too slow when multiple variables need to be weighed simultaneously and perspectives need to shift in response to new information.

Building and maintaining trust

This is perhaps the most underestimated argument for synchronous interaction. A landmark study published in Nature Human Behaviour, analysing over 61,000 Microsoft employees, found that firm-wide remote work caused collaboration networks to become more static and siloed. Workers spent approximately 25% less time collaborating with colleagues across groups. They relied more on asynchronous tools like email and messaging, and had fewer real-time conversations.

The implication is significant: without deliberate synchronous touchpoints, remote teams gradually lose the weak ties and cross-functional connections that drive innovation. Trust doesn’t build well over Slack threads alone. It needs tone of voice, facial expressions, the small human moments that happen in the margins of a video call.

When you get asynchronous work right, your live conversations can truly focus on the relationship and the humans – instead of exchanging information and status updates.

Onboarding and mentoring

New team members need synchronous interaction disproportionately. The interactive, hands-on knowledge transfer that good onboarding requires – asking clarifying questions in the moment, observing how experienced colleagues think through problems, building the relational foundation for future collaboration – can’t be fully replaced by documentation, however thorough (although that documentation absolutely must be present and complete, for reference before, during, and after synchronous conversation).

There’s something else worth acknowledging here: in small teams especially, each new person changes the culture of that group. It doesn’t matter whether the team is co-located or distributed – a new arrival shifts the dynamic, brings different communication patterns, asks different questions. This is why the concept of “cultural contribution” matters more than “cultural fit.” You’re not looking for someone who slots in seamlessly; you’re looking for someone whose presence makes the team richer. But that kind of integration – that mutual adaptation – requires real-time interaction where people can observe each other, build trust, and negotiate the unwritten norms of working together. It’s hard to absorb a team’s culture, let alone contribute to it, through async channels alone.

Sensitive conversations

Conflict resolution, performance discussions, delivering difficult news – these are conversations where nuance, tone, and real-time emotional feedback are essential. Async communication strips away the very signals that allow us to navigate these moments with empathy and care.

The time zone dimension

For European remote teams working across multiple time zones, synchronous communication carries additional complexity – and additional cost. Research by Prithwiraj Choudhury of Harvard Business School, Jasmina Chauvin of Georgetown University, and Tommy Pan Fang of Rice University studied communication patterns among more than 12,000 employees of a large multinational corporation. Their findings, published in Organization Science in 2024, are striking.

For every additional hour of time zone separation, synchronous communication declined by 11%. One hour of lost overlap represented a 19% reduction in opportunities to communicate synchronously during the typical workday. And here’s the human cost: 43% of synchronous communication occurred when at least one employee was working outside their local business hours.

The implications for European teams are direct. A team spanning Lisbon to Helsinki already has a two-hour gap – which, by this research, reduces synchronous opportunities by roughly 22%. Add a colleague in New York or Dubai, and the arithmetic gets painful quickly.

This is precisely why synchronous time needs to be treated as a scarce and valuable resource, not squandered on status updates that could have been a Loom video or a written brief.

Europe’s right to disconnect – a framework for sync discipline

Europe’s regulatory landscape actually provides a useful framework here. France pioneered the right to disconnect in 2016, and Belgium, Portugal, and others have followed with their own versions. The European Parliament has been pushing for EU-wide legislation since 2021, and the European Commission launched consultations with social partners in 2024.

These aren’t just employee protection measures, they’re implicitly an argument for communication discipline. If your team members have a legal right not to respond outside working hours (and Eurofound research shows that one in four teleworkers in Italy and Slovenia were being contacted daily outside their working time), then your synchronous windows are defined and finite by design.

Far from being a constraint, this actually sharpens decision-making about when synchronous interaction is warranted. If you have a four-hour overlap window with your team, you learn very quickly what belongs in that window and what doesn’t.

How the best remote teams get the balance right

The organisations that handle this well share several common practices.

They define sync-worthy categories explicitly

Rather than leaving it to individual judgement, high-functioning remote teams specify which activities warrant real-time interaction. GitLab’s handbook is explicit: synchronous meetings are reserved for decisions requiring immediate feedback from multiple people. Unidirectional presentations, company announcements, results reporting, and initial brainstorming all happen asynchronously.

They protect sync and async time fiercely

When synchronous windows are limited – whether by time zones, right-to-disconnect regulations, or simply by principle – teams that perform well treat meeting time like a non-renewable resource. Buffer’s 2025 State of Remote Work report found that 37% of companies have implemented no-meeting days, recognising that uninterrupted focus time is as important as collaboration time.

The trend toward “speedy meetings” – 25 minutes instead of 30, 50 minutes instead of 60 – reflects a similar instinct: if we’re going to meet, let’s be efficient about it.

They invest in documentation to reduce sync dependency

Every meeting that exists only because the information isn’t written down somewhere is a process failure. The best remote teams treat documentation as infrastructure – it’s what makes their asynchronous culture possible, and what ensures synchronous time can be spent on genuinely high-value interaction rather than information transfer.

They use AI to bridge the gap

The integration of AI tools across the remote work stack in 2025 and 2026 has created a genuine shift here. AI meeting summaries mean that anyone who can’t attend a synchronous session can quickly absorb what was discussed, In a way that is instantly skimmable and understandable without having to sit through a recording. AI-powered search across company tools reduces the 19% of the workweek that McKinsey found knowledge workers spend hunting for information. Smart scheduling tools help teams find overlap windows more efficiently.

These tools don’t replace synchronous interaction – they make it possible to have less of it without losing the information that flows through it.

Getting your own balance right

If you’re leading or working in a remote team, here’s a practical framework for thinking about when to go synchronous.

Default async when:

  • Sharing status updates, progress reports, or announcements
  • Providing feedback on documents or deliverables (where the recipient benefits from time to process)
  • Making decisions where input can be gathered sequentially
  • Distributing information that people need to reference later

Go synchronous when:

  • Generating ideas collaboratively – real brainstorming, not just collecting input
  • Resolving ambiguity or conflict that has stalled in async channels
  • Building relationships – particularly with new team members or across teams that rarely interact
  • Making decisions under time pressure where rapid iteration is needed
  • Navigating emotionally complex conversations or sensitive subjects

And always:

  • Document the outcomes of synchronous sessions so that the value extends beyond the meeting itself: Always consider the need of absent parties and even future-you
  • Record meetings (with consent) for those in incompatible time zones
  • Set agendas in advance – if you can’t articulate why a meeting needs to be synchronous, it probably doesn’t

The real risk isn’t too many meetings – it’s the wrong ones

The data tells us that remote workers now join 8 to 17 meetings each week – a 252% increase since February 2020. Workers see 71% of these meetings as time-wasters, and only 11% are perceived as productive. Those numbers are damning, but they’re an argument against bad meetings, not against synchronous interaction itself.

The organisations getting this right aren’t the ones that eliminated meetings entirely. They’re the ones that made every synchronous moment intentional – that understood when real-time interaction adds something irreplaceable, and when it’s just a habit inherited from the office.

You have to be very deliberate about this. Remote work doesn’t run on autopilot, and neither does good communication. The teams that thrive are the ones that treat synchronous time as precious – and use it for what it’s actually good at: not just shipping work faster, but building the kind of real-time human connection that develops us as collaborators, communicators, and colleagues. That’s not a nice-to-have. It’s how we learn to work together – and it matters whether we’re in a playground, an office, or a distributed team spanning three time zones.