How Remote Teams Make Better Work
Remote work can make collaboration worse. The evidence is clear.
A study of 61,182 Microsoft employees in Nature Human Behaviour found that the shift to remote work made collaboration more static and siloed. Collaboration across groups dropped by 25%, with employees relying more on asynchronous communication, but fewer bridges connected different parts of the company.
This finding exposes the flaw in a common argument. Distance does not improve work. Asynchronous design can.
The distinction lies in the operating model. A remote team that mimics office habits in video calls inherits the meeting burden and loses informal shared-room context. A team that moves every discussion into chat creates interruption without resolution. Better work emerges when the collective decides which activity needs real-time exchange, which needs protected thought and how knowledge will travel between them.
Async is an architecture, not an app.
Teams often use collaboration as a loose name for several different activities. Communication transfers information. Coordination aligns separate tasks. Collaboration develops a shared output that depends on several contributors. The distinction helps because each activity carries a different need for simultaneity.
A status update usually needs accessible information, not a meeting. A handoff needs a complete request and clear owner. Independent idea development benefits from protected time. A difficult trade-off, relationship repair or live synthesis may justify bringing people together. The mode should follow the work rather than the team’s default calendar.
Microsoft found that half of meetings take place between 9-11 a.m. and 1-3 p.m., overlapping with peak productivity. These hours are when writers, designers, analysts, and strategists need focus.
The cost extends beyond the meeting duration. Preparation, context switching and the fragmented gap before the next call reduce the blocks available for complex work. A creative team can spend a full day in collaboration and still end with little created.
The meeting reflex persists because synchronous activity feels visible. Leaders can hear participation. Stakeholders can request immediate clarification. Decisions seem to move because people are talking about them.
Visibility is not flow.
An async-first team requires the work to become legible without constant presence. A clear brief, accessible evidence, named decision owner and written record allow progress to continue while colleagues are offline. The system measures movement through completed thinking and closed decisions, not green status lights.
Unstructured discussion favours the fastest speaker and the person with the most organisational status. It also asks participants to understand, evaluate and respond at once.
A written starting artefact alters the sequence by having the owner frame the problem, present evidence, define constraints, separate facts from assumptions, and state the decision needed. Participants review, test reasoning, and respond.
This does not make writing neutral. A weak memo can frame the problem unfairly or overwhelm readers with detail. The advantage is inspectability. Assumptions become visible. Missing evidence can be named. Quieter specialists can contribute without competing for airtime.
The document also creates continuity. A colleague in another time zone can understand the state of the work without waiting for a briefing. A new team member can examine how a decision developed. The organisation converts conversation into reusable knowledge.
GitLab's all-remote handbook treats documentation and asynchronous communication as core infrastructure. Its example demonstrates the scale of the practice, but the lesson applies to smaller teams: write so that another person can act without private context.
Async work fails when "not now" means "whenever". A request enters a channel, nobody knows when input is due, and the owner either waits indefinitely or schedules a meeting to force a response.
Every asynchronous decision needs a response window. The window should reflect urgency, consequence and the time required for good judgement. A routine review may allow one working day. A complex strategic proposal may require several. A genuine incident may move immediately to a synchronous channel.
The team should also define what silence means. Does no response indicate consent, no objection or non-participation? The answer must be explicit because different cultures and personalities interpret silence differently.
Clear windows create pace without manufacturing urgency. Colleagues can plan focused work and still know when the collective needs them.
Digital tools can invite unlimited commentary. More comments create the appearance of collaboration while making ownership harder to see.
The decision artefact should name who recommends, who contributes specialist input and who decides. Contributors need to know whether the owner seeks factual correction, strategic challenge, creative development or approval. The decider should close the loop with the choice and reasoning.
This structure protects dissent. A team member can make a strong objection without carrying the burden of final accountability. The decision owner can proceed after considering disagreement rather than waiting for complete consensus.
The record lets the team learn by examining assumptions and trade-offs if the outcome disappoints, regardless of who speaks most confidently in the retrospective.
An async-first model should not eliminate meetings. Some work improves through simultaneous exchange.
Live discussion is ideal for emotionally sensitive issues, crises, ambiguity, relationship repair, and creative exploration, as it allows participants to quickly build on ideas. It also enhances social connection, especially for remote teams.
The test is whether simultaneity adds value. A status update rarely needs ten people at the same time. A difficult conversation about trust usually does. A first round of independent ideas may benefit from async thought before a live synthesis. A final decision may need a short call when written disagreement exposes a genuine conflict in assumptions.
Microsoft's guidance on asynchronous collaboration recommends sharing material ahead and collecting comments before meetings. This hybrid sequence improves the live session because participants arrive informed. The meeting can address the unresolved edge rather than replaying the document.
Preparation gives synchrony a purpose.
The Microsoft study's strongest warning concerns cross-group ties. Teams working remotely became more connected internally while losing links to other groups. Async systems can deepen that problem if each function documents inside its own tool, vocabulary and permission boundary.
Cross-functional bridges need design. Shared project spaces should connect strategy, creative, media, account and commercial evidence. Decision records should remain discoverable to affected teams. Rotating reviews can invite input from adjacent disciplines. Communities of practice can allow specialists across accounts to exchange patterns and standards.
Useful knowledge needs controlled permeability, with confidential detail protected.
This is where collective intelligence differs from the accumulation of individual work. The hive gains value when one person's observation changes another person's decision. Documentation is the transport layer. Deliberate connection determines the route.
Remote creative work often defaults to the group call too early. The first confident idea anchors the discussion, and participants adjust around it. Shared screens encourage reaction before independent thought has had time to develop.
An asynchronous divergence phase can increase range. Each participant develops an initial response before seeing the others. The team then reviews the set, identifies patterns and uses a live session to combine, challenge and select.
This sequence addresses a known collaboration risk: premature convergence, although no process can guarantee originality. It gives contributors with different working rhythms equal time to form a view and makes the breadth of the initial thinking visible.
The synthesis still needs leadership. A collection of ideas is not a strategy. Someone must connect the strongest elements to the brief, evidence and constraints.
Async work breaks at incomplete handoffs. A message says "please review" without naming the question. A design file arrives without the decision behind it. A stakeholder comments after the work has moved on because no deadline was visible.
A complete handoff includes the current state, requested action, owner, deadline, relevant links and definition of done. It identifies what has already been decided and what remains open. This small discipline reduces clarification loops across time zones.
It also exposes unrealistic workloads. When every request has an owner and deadline, the team's true demand becomes visible. Capacity decisions can replace private overwork.
Meeting reduction alone does not prove better collaboration. A team can cancel calls and create slower, lonelier work.
The collective should measure decision lead time, rework, missed handoffs, cross-functional participation, protected focus time and the age of unresolved requests. Employee evidence matters too. Can people find the context they need? Do they understand which channel to use? Can they disagree safely? Do time-zone differences create repeated disadvantage?
Quality measures should connect to the work itself. Did the process produce a broader set of options? Did specialist input arrive before commitment? Did the final output meet the brief with fewer late changes? Did learning enter the next project?
These measures turn async from a cultural preference into an operating hypothesis.
Async advocates can create a new burden by recording everything. Excessive documentation makes knowledge harder to find and converts writing into another form of meeting.
The priority should be material that enables action or preserves reasoning: briefs, decisions, standards, responsibilities, recurring processes and learning with future value. Temporary coordination can remain temporary. Owners should archive or update stale material so that search produces trust rather than more checking.
Atlassian's 2025 guidance on async communication emphasises intentional practice, not the mechanical replacement of meetings. The system needs regular review because teams, tools and project types change.
Remote teams make better work when distance forces clarity that co-located teams could previously avoid. Written reasoning can widen participation. Protected time can improve craft. Recorded decisions can strengthen memory. Distributed talent can add perspectives unavailable in one office.
None of those gains arrives with the remote contract. They arrive when the team builds for them, tests the structure and preserves the live human contact that the work still needs.
Distance creates the requirement. Design creates the advantage.
