The Baseline: Why We Need an Async Meetings Case Study
As of July 2026, the baseline for this async meetings case study is straightforward: distributed work remains mainstream, office attendance is still below its pre-pandemic benchmark, and software stacks are expanding again. The operational challenge is giving people reliable context so projects can advance without another status call.
Software-stack benchmarks need qualification. Coverage from OpenLM highlights the license-visibility problem, but current datasets measure different customer populations. BetterCloud’s 2026 State of SaaS report, based on 525 IT and security professionals, says average app counts rose 11% year over year after two years of consolidation. Organizations averaged 27 AI-powered SaaS applications, representing roughly 22% of their portfolios.
Office data also requires precise wording. Kastle Systems no longer supports describing occupancy as permanently plateaued at 50%. Its December 18, 2025 update recorded 56.3% weekly average occupancy across all tracked office buildings, its highest reading since early 2020. Meanwhile, Gallup’s latest indicator found that 51% of remote-capable U.S. employees were hybrid, with fully remote and fully on-site work each gaining two percentage points.
GitLab remains a useful blueprint, but its size must be dated accurately. Its fiscal 2026 annual report recorded approximately 2,580 team members in 60 countries as of January 31, 2026. GitLab subsequently announced a planned reduction of approximately 350 positions. The enduring case study is therefore its operating system—not a frozen headcount or the claim that it abolished meetings.
The GitLab Remote Work Case Study: Handbook First
The GitLab remote work case study starts with one rule: durable documentation should precede repeatable communication. GitLab’s handbook-first model gives policies, processes, and decisions a searchable home, while issues and merge requests let people review changes across time zones. The result is fewer meetings for information that can be read.
GitLab calls its public handbook the central repository for how it runs the company. According to the handbook itself, the printed version contains more than 2,000 pages of text. It is not merely an onboarding manual; it records processes, responsibilities, communication norms, and practical guidance that team members can consult without asking someone to repeat the context.
When a process changes, team members can propose an edit through a merge request. Reviewers then discuss and refine the change before it is merged, leaving a visible decision trail. That workflow can replace a status call because the proposal, feedback, owner, and final wording remain accessible after the decision instead of disappearing into someone’s meeting notes.
Handbook-first does not mean that every thought belongs in one document or that GitLab avoids chat and video. Its communication guidance recognizes several channels while emphasizing clear, efficient communication. The transferable principle is to move durable outcomes into an authoritative system rather than leaving them in private messages or an unsearchable recording.
For organizations trying to make this shift, the hardest step is cultural: stop rewarding the reflexive “quick sync” and start rewarding useful documentation. Our guide to the 2026 coordination crisis can help identify where information currently fragments and why employees keep scheduling alignment calls to reconstruct it.
Asynchronous Communication 2026: Workflows Over Video Calls
Asynchronous communication in 2026 means designing workflows that do not require an immediate reply. GitLab routes proposals, feedback, and many decisions through issues, merge requests, and shared documents, then uses live calls selectively. That keeps work moving across time zones without pretending that every difficult conversation belongs in text.
The traditional video meeting can become passive: one person presents while everyone else listens, multitasks, or waits for a chance to contribute. In an async workflow, a product proposal can begin as an issue. Stakeholders review it on their own schedules, add designs, ask questions, document trade-offs, and leave the decision with the original context attached.
This approach removes one calendar bottleneck, but it requires clear owners and response expectations. Work cannot move continuously if an issue has no deadline or nobody knows who decides. A strong async process specifies the requested contribution, decision-maker, due date, and escalation path so that thoughtful participation does not turn into an indefinitely open thread.
GitLab does still hold video meetings. Its all-remote meeting guidance recommends a clear desired outcome, an agenda, and recordings that support asynchronous participation. Its live-document practices also acknowledge that choosing between sync and async is an art rather than an absolute rule. Complex problem-solving, emotional nuance, mentorship, and relationship-building can justify real-time conversation; routine information delivery usually cannot.
Your technology stack should preserve context across both modes. Coommit combines HD video, an interactive canvas, and contextual AI so that visual work and spoken discussion remain connected. Instead of treating the call as a temporary event, teams can turn necessary synchronous sessions into documented collaborative work that is easier to revisit and continue asynchronously.
Mastering that boundary is central to remote productivity. Our playbook on sync vs async communication provides a practical framework for deciding which conversations need a live call, which belong in writing, and how to prepare both formats so participants can contribute effectively.
Implementing No Meeting Days Remote Teams Actually Respect
No-meeting days work only when leaders protect them, teams have dependable async paths for approvals, and performance is judged by outcomes rather than visible attendance. GitLab’s documented Focus Friday practices show the mechanism: move recurring calls, preserve deep-work blocks, and make written context sufficient for people to unblock themselves.
Many companies declare “No Meeting Wednesdays” only to watch the day fill with urgent exceptions. The initiative fails when employees still need a call to obtain an approval, locate a decision, or learn what changed. A protected day is therefore the visible result of good async infrastructure, not a substitute for building that infrastructure.
The GitLab evidence is more nuanced than a universal companywide ban. Its Focus Friday guidance tells teams to cancel or move standing Friday meetings, while another handbook page recommends piloting no-meeting days at team or company level. These are concrete practices, not proof that every GitLab calendar is empty every Friday.
Real-estate savings also depend on lease terms, attendance, and actual space consolidation; there is no defensible blanket promise that every hybrid company will save 15–30%. Research from McKinsey found that workers were going into offices about 30% less frequently than before the pandemic. JLL’s 2026 occupancy benchmark says portfolio optimization was the top real-estate objective for 71% of respondents. The opportunity is real, but it must be measured.
If your organization is struggling to protect maker time, establish rules for exceptions, publish escalation paths, and require leaders to model the behavior. Our guide to no-meeting days that actually work explains how to prevent calendar creep while keeping genuinely urgent work moving.
Solving 2026 SaaS Sprawl in Async Teams
SaaS sprawl weakens asynchronous work because every extra system creates another place where context can disappear. The practical answer is not chasing a universal app-count benchmark; it is defining authoritative systems, integrating necessary tools, removing duplicates, and making the path from discussion to decision obvious for every team.
The former 106-app benchmark should not be treated as universal. BetterCloud reports that average stacks in its 2026 research grew 11%, while Zylo’s 2026 SaaS Management Index reports an average portfolio of 305 applications and $55.7 million in annual SaaS spending. The gap is a reminder that vendor datasets represent different organization sizes and customer populations. Audit your own environment instead of treating either average as a target.
GitLab demonstrates tool discipline without literally using one application for everything. Its async-work guidance says the entire team uses GitLab to collaborate asynchronously on its work, but the handbook also documents Slack, Google Docs, and Zoom. The real lesson is to minimize duplicate destinations and specify which system owns the final decision, not to force every interaction into one vendor.
For teams outside software development, consolidation often means selecting platforms that combine naturally related tasks. Coommit brings video conferencing and a real-time collaborative canvas into one workspace, removing the handoff between a separate call and a separate whiteboard. Its contextual AI can then capture the relationship between the spoken discussion and the visual work, making the resulting session easier to search and continue.
Reducing duplicate tools can lower spend and, more importantly, make project context easier to find. The Zapier async case study offers another model for using documented workflows and automation to keep distributed work moving without adding a meeting whenever systems fail to communicate.
Key Takeaways from This Async Meetings Case Study
The central takeaway from this async meetings case study is simple: replace recurring requests for context with trusted, searchable records. GitLab does not eliminate calendars or video; it reduces the number of situations in which progress depends on everyone being available simultaneously. That distinction makes the model practical rather than ideological.
- Define authoritative systems. Specify where policies, project status, proposals, feedback, and final decisions live. A single source of truth is a governance rule, not necessarily one application.
- Design async workflows completely. Every request needs context, an owner, a response deadline, a decision-maker, and a documented escalation path.
- Measure output instead of presence. Evaluate completed work and meaningful outcomes rather than camera time, message speed, or hours shown as available.
- Audit tools and meetings together. Duplicate software and recurring alignment calls are often two symptoms of the same underlying information problem.
These practices can reduce coordination delays, protect focus time, and make distributed work more inclusive across time zones. For tactical steps you can begin applying this week, explore our guide to async communication best practices.
Ultimately, the goal is not to eliminate every meeting. It is to reserve synchronous time for conversations that genuinely benefit from immediate interaction and give every other exchange enough structure to succeed asynchronously. When live collaboration is necessary, a shared visual workspace and durable context can turn it into productive work rather than calendar overhead.