Why Most Companies Still Resist Asynchronous Work
Teams that communicate asynchronously, sharing information, making decisions, and coordinating without requiring everyone to be present at the same time, consistently outperform synchronous-first organisations across productivity, job satisfaction, and decision quality.
Remote-only workers log 51 more productive minutes per day compared to hybrid and in-office peers.
The data is not ambiguous.
And yet most companies, when given the choice, default to the meeting. So why are organisations resisting, and what is the resistance actually protecting?
What is Asynchronous Work?
Asynchronous communication means that the sender and receiver are not present at the same time. A written update, a recorded video, a shared document with comments, and a voice note are asynchronous. A meeting, a phone call, a live Slack thread where everyone is expected to respond immediately, these are synchronous.
The distinction matters because synchronous communication has a hidden cost that asynchronous communication does not: it requires every participant to be available, focused, and present at exactly the same moment. That cost is rarely calculated.
Bain & Company's research on executive time found that organisational meetings have increased every year since 2008, consuming a growing percentage of total working time without a corresponding increase in decision quality. The synchronous default, the meeting as the first response to every coordination need, is consuming more hours while producing proportionally less.
46 per cent of American employees would choose an unpleasant activity, such as watching paint dry or getting a root canal, over attending another status meeting. These are not disengaged workers who hate their jobs. These are professionals who have correctly identified that the meeting consuming their time does not require their live presence to accomplish its stated goal.
The Productivity Case for Asynchronous Work
Companies that have shifted to async-first operations report consistent, measurable advantages across multiple dimensions.
McKinsey's 2025 analysis found that hybrid teams — which tend to have stronger async communication infrastructure than fully synchronous in-office teams — are approximately 5 per cent more productive overall.
Great Place To Work's two-year study of over 800,000 employees found stable or improved productivity after transitioning to remote and async-first work. Organisations at the top of the Fortune 100 Best Companies list, 97 per cent of which support remote or hybrid work, report productivity approximately 42 per cent higher than typical U.S. workplaces.
Research published in Harvard Business Review confirms that cutting back on synchronous meetings increases employees' feelings of productivity and autonomy. Async communication better incorporates the work of introverted professionals and those who prefer deliberate thinking over reactive response.
Synchronous meetings, by their nature, reward fast thinking and verbal fluency. They systematically disadvantage careful thinkers, who are a significant portion of the knowledge workers whose value is most tied to the quality of their analysis.
Why Companies Still Resist Asynchronous Work
Given all of this, the persistence of meeting culture as the default coordination mechanism requires an explanation.
The resistance operates on three levels, and understanding each one matters for knowing how to address it.
Control and visibility
Meetings are observable. A leader who needs to know whether their team is working can look at a meeting schedule and see activity. Async work is less visible — it produces outputs, not presence — and outputs require trust to evaluate.
Research shows that shifting to remote and async work strikes fear in many supervisors precisely because the visual proxy of attendance disappears. Organisations that have not built trust as an operational currency will default to presence as a substitute.
The immediacy instinct.
Synchronous communication is the one we're most instinctively drawn to because it feels easier and more comfortable. A conversation requires a live counterpart. When we're unsure whether we've been heard, understood, or agreed with, we reach for the meeting because it provides immediate confirmation. The emotional cost of waiting for an async response, even when that wait is entirely rational, feels like uncertainty, and uncertainty feels like risk.
Infrastructure gaps.
Most companies have not built the systems that make async communication work well. No shared documentation standards. No clear decision-ownership frameworks. No norms around response times or update formats.
Change resistance is the biggest single barrier in developing async culture — and that resistance is harder to overcome when the tools and processes that make async effective are absent. Without infrastructure, async quickly becomes no communication at all.
The Organisations Leading with Asynchronous Work
Shifting to async-first work requires deliberate systems that replace the value meetings provided, without requiring live attendance.
GitLab, one of the world's most productive fully distributed companies, operates on a handbook-first approach: every process, decision framework, and policy is documented in writing before it is communicated verbally.
The result, as their own documentation notes, is a team that is "massively more efficient" because information does not live in individual people's heads or in meetings that only some people attended.
The pattern in high-performing async organisations is consistent: they invest heavily in documentation, they are explicit about which types of communication require synchronous presence and which do not, and they create norms that make asynchronous communication the first instinct rather than the fallback.
Asynchronous Communication is the future of Work
This is not an argument for eliminating meetings.
Some conversations are genuinely better synchronous. Trust-building between parties who have no shared history. Conflict resolution where emotional nuance cannot be captured in text. Creative sessions where ideas need to bounce between people in real time. These are the meetings worth protecting.
The problem is that they use synchronous communication for everything — including the status updates, routine coordination, informational briefings, and approval requests that are structurally better suited to async channels.
What the Conductor's qualification layer does is make this routing decision explicit. Before any meeting reaches the calendar, the system asks whether the conversation requires live presence or whether a faster, lower-cost form of communication would achieve the same outcome. Unnecessary synchronous interruptions are redirected. Necessary ones are protected.
The future of work is not fully asynchronous. It is more deliberately synchronous, fewer meetings, but ones that genuinely earn their place on the calendar.
