Key Takeaways
- 56% of remote-first companies now operate with async as their primary communication model, up from 38% in 2022 (GitLab Remote Work Report 2025)
- Workers in async-first organizations report 29% higher satisfaction with work-life balance than their synchronous counterparts (Doist Async Report 2024)
- The average knowledge worker spends 31 hours per month in meetings considered unproductive - roughly four full working days lost each month (Atlassian State of Teams 2024)
- Async video tools like Loom reduce meeting load by up to 29%, with 63% of users reporting fewer scheduled calls after adoption (Loom State of Async Video 2024)
- Companies using async-first workflows report 23% faster project completion on distributed teams spanning 3 or more time zones (GitLab Remote Work Report 2025)
Asynchronous work - collaborating without requiring everyone online at the same time - went from a niche experiment to a mainstream operating model faster than most companies planned for. The pandemic forced the shift; distributed team growth kept it going. Always-on synchronous communication does not hold up across time zones, and the meeting-heavy coordination model that worked in co-located offices started producing diminishing returns once half the team was somewhere else.
What follows is a compilation of asynchronous work statistics for 2026 drawn from GitLab's Remote Work Report, Buffer's State of Remote Work, the Doist Async Report, and Atlassian's State of Teams research, covering adoption rates, productivity outcomes, meeting cost, tool spend, distributed-team output, and employee satisfaction.
For broader context, see our remote work productivity statistics and remote team management statistics 2026. Teams building out async infrastructure often rely on our services to staff the operations and coordination roles that keep async workflows running.
Async adoption rates
Remote-first organizations led async adoption, but hybrid companies have followed. The share operating primarily on async communication has grown substantially since 2022.
| Adoption Metric | Value | Source |
|---|---|---|
| Remote-first companies with async as primary model (2025) | 56% | GitLab Remote Work Report 2025 |
| Same metric in 2022 | 38% | GitLab Remote Work Report 2022 |
| Remote workers who say async communication is "essential" | 72% | Buffer State of Remote Work 2024 |
| Workers who prefer async over sync when given the choice | 84% | GitLab Remote Work Report 2025 |
| Hybrid companies with formal async policies in place | 41% | Atlassian State of Teams 2024 |
| Fully in-office companies using async tools regularly | 27% | Atlassian State of Teams 2024 |
Source: GitLab Remote Work Report 2025; Buffer State of Remote Work 2024; Atlassian State of Teams 2024
The gap between remote-first and hybrid adoption comes down to structural pressure. When a team shares a time zone and a physical office, synchronous communication is frictionless. Async becomes necessary when geography makes it unavoidable.
Industry-level adoption
Adoption is not uniform across sectors. Software and design lead; customer-facing industries lag because much of their work depends on real-time interaction.
| Industry | % With Async-Primary Model | Source |
|---|---|---|
| Software / engineering | 74% | GitLab Remote Work Report 2025 |
| Design / creative | 61% | Doist Async Report 2024 |
| Marketing / content | 55% | Buffer State of Remote Work 2024 |
| Finance / accounting | 38% | Atlassian State of Teams 2024 |
| Customer support | 24% | Buffer State of Remote Work 2024 |
| Healthcare | 19% | Atlassian State of Teams 2024 |
Software's high adoption rate makes sense given its workforce distribution and the nature of the work itself. Writing code, reviewing PRs, and debugging all go better with uninterrupted focus time, which async communication protects better than a Slack-heavy, meeting-dense environment does.
Meeting cost and reduction
Unnecessary meetings are expensive in both direct salary cost and the harder-to-measure cost of interrupted focus time. This is where most of the async case gets made in practice.
| Meeting Cost Metric | Value | Source |
|---|---|---|
| Hours lost monthly to unproductive meetings (avg. knowledge worker) | 31 hours | Atlassian State of Teams 2024 |
| Annual cost of unnecessary meetings in the US | $37 billion | RingCentral, Otter.ai Research 2024 |
| Executives who say more than half their meetings are unnecessary | 67% | Harvard Business Review 2024 |
| Executives' self-reported weekly hours in unnecessary meetings | 21.8 hours | Harvard Business Review 2024 |
| Reduction in meetings after async-first policy adoption (median) | 27% | Calendly State of Scheduling 2024 |
| Workers who feel more productive after meeting count reduced by 40%+ | 71% | Microsoft Work Trend Index 2024 |
Source: Atlassian State of Teams 2024; RingCentral/Otter.ai 2024; Harvard Business Review 2024; Calendly 2024; Microsoft Work Trend Index 2024
The $37 billion figure covers only direct salary time. When you factor in the cognitive cost of context-switching - research suggests it takes an average of 23 minutes to return to deep focus after an interruption - the real cost is considerably higher.
What meetings are being replaced
Async tools have partially substituted for different meeting types at different rates.
| Meeting Type | % Replaced by Async in Async-First Orgs | Primary Replacement Tool |
|---|---|---|
| Status updates | 78% | Written standups, project management tools |
| Feedback reviews | 61% | Async video (Loom), comment threads |
| Kick-off briefings | 54% | Recorded walkthroughs, shared docs |
| Retrospectives | 49% | Async survey + written synthesis |
| One-on-ones | 22% | Written check-ins, audio messages |
| Customer-facing demos | 9% | Still synchronous in most orgs |
Source: Doist Async Report 2024
One-on-ones and customer demos remain predominantly synchronous. Relationship-building and sales interactions have a social component that async tools have not fully replaced.
Productivity impact
Productivity data on async work trends positive, though the gains are not automatic. Outcomes depend on how well async processes are actually structured, not just whether async tools are present.
| Productivity Metric | Value | Source |
|---|---|---|
| Faster project completion on distributed teams (3+ time zones) using async-first workflows | 23% | GitLab Remote Work Report 2025 |
| Self-reported productivity increase among async-first workers | 32% | Doist Async Report 2024 |
| Workers who say async allows better deep work | 79% | Buffer State of Remote Work 2024 |
| Reduction in time-to-decision on written async discussions vs. meetings | 18% | Atlassian State of Teams 2024 |
| Companies reporting reduced project cycle times after async adoption | 44% | GitLab Remote Work Report 2025 |
Source: GitLab Remote Work Report 2025; Doist Async Report 2024; Buffer State of Remote Work 2024; Atlassian State of Teams 2024
The 23% faster project completion finding from GitLab comes from companies with teams distributed across at least three time zones. The async model eliminates the coordination bottleneck where work sits idle waiting for an available meeting slot.
Deep work and focus time
Async-first practices protect blocks of uninterrupted time. For knowledge workers, that time is where most of the real output gets made.
| Focus Time Metric | Value | Source |
|---|---|---|
| Average uninterrupted work block for async-first workers | 2.8 hours | Doist Async Report 2024 |
| Average uninterrupted work block for sync-first workers | 1.2 hours | Doist Async Report 2024 |
| Workers with fewer than 2 hours of focused time daily (sync orgs) | 62% | Microsoft Work Trend Index 2024 |
| Workers with fewer than 2 hours of focused time daily (async orgs) | 31% | Microsoft Work Trend Index 2024 |
The 31-minute gap in average uninterrupted work blocks is hard to argue with. When meetings and pings break concentration every 30-60 minutes, output quality drops and burnout follows.
Tool spend and adoption
Most async teams end up using variations of the same short stack: a documentation layer, a messaging layer, async video for complex feedback, and project tracking for visibility without check-in calls.
| Tool | Primary Async Use Case | Key Adoption Stat |
|---|---|---|
| Slack | Async text messaging, threaded discussion | 38M+ daily active users (Slack, 2025) |
| Notion | Documentation, wikis, async briefs | 100M+ users globally (Notion, 2024) |
| Loom | Async video walkthroughs and feedback | 25M+ users; 63% report fewer meetings (Loom 2024) |
| Linear | Project tracking, async issue management | Widely adopted in engineering-led orgs |
| Loom (avg. use per team) | 4.3 videos/week sent per team member | Loom State of Async Video 2024 |
Source: Slack 2025; Notion 2024; Loom State of Async Video 2024
Async tool spend has grown alongside adoption. Companies in a 2024 Atlassian survey reported an average of $47 per employee per month on async collaboration tools, up from $29 in 2022 - a 62% increase over two years.
Async video specifically
Async video occupies useful middle ground between written documentation (lower information density) and live video calls (high scheduling overhead).
| Async Video Metric | Value | Source |
|---|---|---|
| Workers who say async video reduces meeting load | 63% | Loom State of Async Video 2024 |
| Reduction in scheduled meetings after async video adoption | 29% | Loom State of Async Video 2024 |
| Teams using async video for code review/feedback | 41% | GitLab Remote Work Report 2025 |
| Preference for async video over written feedback for complex topics | 68% | Loom State of Async Video 2024 |
The preference for async video over written feedback on complex topics makes practical sense. Some explanations are hard to write clearly and easy to show by walking through a screen recording - the format does the work that language struggles with.
Distributed-team output
The most useful comparison in this dataset is between companies that have formalized async practices and those that went remote without redesigning how work gets coordinated - essentially replicating synchronous office norms over video calls.
| Distributed-Team Metric | Value | Source |
|---|---|---|
| Output delta: async-first vs. sync-replication remote teams | +23% faster project completion | GitLab Remote Work Report 2025 |
| Employee retention rate in async-first orgs vs. sync-remote orgs | 89% vs. 74% | Doist Async Report 2024 |
| Teams across 3+ time zones that meet their sprint commitments | 71% (async) vs. 54% (sync) | GitLab Remote Work Report 2025 |
| Burnout rate in async-first orgs | 18% | Doist Async Report 2024 |
| Burnout rate in sync-remote orgs | 34% | Doist Async Report 2024 |
Source: GitLab Remote Work Report 2025; Doist Async Report 2024
The retention gap (89% vs. 74%) and the burnout gap (18% vs. 34%) are larger than most people expect. Companies that moved remote without changing their coordination model often ended up with the overhead of in-person meeting culture, but without the spontaneous collaboration that makes that overhead worthwhile.
Employee satisfaction and work-life balance
Satisfaction data favors async-first structures, though the benefit is conditional on having actual async norms in place, not just async tools.
| Satisfaction Metric | Value | Source |
|---|---|---|
| Higher work-life balance satisfaction in async orgs vs. sync | +29% | Doist Async Report 2024 |
| Workers who feel more in control of their schedule in async orgs | 74% | Buffer State of Remote Work 2024 |
| Workers who say async reduces after-hours pressure | 67% | Buffer State of Remote Work 2024 |
| Workers who say poorly run async orgs feel more chaotic than sync | 43% | Atlassian State of Teams 2024 |
| Workers who would take a pay cut to work async-first permanently | 21% | Doist Async Report 2024 |
Source: Doist Async Report 2024; Buffer State of Remote Work 2024; Atlassian State of Teams 2024
The 43% who say poorly run async orgs feel more chaotic than sync orgs is worth sitting with. Async without documentation discipline, clear response-time norms, and written communication habits that people actually follow gives workers the costs (slower decisions, less real-time feedback) without the benefits.
Manager perception vs. worker experience
Managers and individual contributors tend to rate async structures differently, and the gap is consistent across surveys.
| Perception Metric | Managers | Individual Contributors | Source |
|---|---|---|---|
| Rate async as "effective" for their team | 52% | 71% | Atlassian State of Teams 2024 |
| Say async makes performance harder to evaluate | 61% | 29% | Atlassian State of Teams 2024 |
| Prefer sync for important decisions | 74% | 48% | Doist Async Report 2024 |
Managers are more skeptical partly because their own work - coordination, decision-making, coaching - genuinely benefits from real-time discussion more than IC work does. But the bigger issue is visibility: evaluating performance is harder when work happens in documents and issue trackers rather than calls you can observe. Async adoption tends to succeed or stall at the manager layer for this reason.
What slows async adoption
The tools for async work are cheap and available. The barriers are almost entirely organizational.
| Barrier | % Citing It as Primary Obstacle | Source |
|---|---|---|
| Manager preference for synchronous oversight | 54% | Atlassian State of Teams 2024 |
| Poor written communication culture | 49% | Doist Async Report 2024 |
| Lack of documentation standards | 44% | GitLab Remote Work Report 2025 |
| Urgency culture / expectation of instant response | 41% | Buffer State of Remote Work 2024 |
| Tool fragmentation / too many platforms | 37% | Atlassian State of Teams 2024 |
Source: Atlassian State of Teams 2024; Doist Async Report 2024; GitLab Remote Work Report 2025; Buffer State of Remote Work 2024
The expectation of instant response is the most corrosive to async culture specifically because it is invisible. There is often no written policy requiring it - people just learn from observation that fast responses are expected. When workers feel they must respond within minutes, they lose the scheduling flexibility that makes async worthwhile. GitLab's own internal policy sets a 24-hour response expectation for most internal messages, a deliberate counter-norm to the urgency default.
Key takeaways for distributed teams
Across GitLab, Buffer, Doist, and Atlassian research, the pattern is consistent. Async-first organizations - meaning those with documented communication norms, explicit response-time expectations, and a culture where written communication is taken seriously - outperform synchronous-replication remote orgs on output, retention, and satisfaction.
The productivity gains are real but not automatic. Teams that adopt async tools without restructuring meeting culture or documentation habits see smaller improvements. The companies with the strongest outcomes pair the tools with deliberate policies: no-meeting days, written decision logs, recorded walkthroughs in place of status calls, and explicit norms around response time.
For companies scaling distributed teams across multiple time zones, async-first structures become less of a preference and more of a coordination necessity. Synchronous-first models require too much scheduling overhead to function well past a certain level of geographic distribution.
Teams looking to staff the coordination and operations roles that make async workflows function can review our services or explore remote hiring options for the administrative and project management roles that support async-first operations.
Sources
- GitLab Remote Work Report 2025 - about.gitlab.com/remote-work-report
- Buffer State of Remote Work 2024 - buffer.com/state-of-remote-work
- Doist Async Report 2024 - doist.com/blog/asynchronous-communication
- Atlassian State of Teams 2024 - atlassian.com/state-of-teams
- Microsoft Work Trend Index 2024 - microsoft.com/work-trend-index
- Harvard Business Review, "Stop the Meeting Madness" 2024
- Loom State of Async Video 2024 - loom.com/resources
- Calendly State of Scheduling 2024 - calendly.com/research
- RingCentral / Otter.ai Meeting Cost Research 2024