Tension: Companies implement asynchronous work to solve communication problems while the dysfunction simply migrates to new platforms and tools.
Noise: Productivity experts celebrate async work as liberation from meetings without examining why workplace communication became unbearable in the first place.
Direct Message: Changing when and where we communicate does nothing to address the underlying pathologies of how we communicate with each other.
To learn more about our editorial approach, explore The Direct Message methodology.
The async revolution promised freedom. Work on your own schedule. Eliminate pointless meetings. Escape the tyranny of real-time collaboration.
Companies restructured entire workflows around Slack threads and Notion databases. Teams adopted elaborate protocols for asynchronous communication. The future of work had arrived, and it was gloriously meeting-free.
Two years in, people are drowning in notifications. Slack messages pile up faster than anyone can respond. Written communication has become simultaneously more voluminous and less clear.
Teams spend hours crafting careful responses to avoid misunderstandings that still happen anyway. The meetings disappeared, but the exhaustion intensified.
What went wrong? Nothing, actually. Async work is functioning exactly as designed. The problem is that bad communication habits don’t improve when you change the medium. They metastasize.
How dysfunction adapts to new formats
In my research on workplace communication patterns, I’ve tracked how organizations migrate their pathologies from one platform to another with remarkable consistency.
A team that had unproductive meetings doesn’t suddenly become productive when those meetings move to threaded conversations. They have unproductive threads instead.
Consider the classic dysfunctional meeting: unclear objectives, passive-aggressive undertones, one person dominating while others disengage, decisions that never quite get made.
Now translate that to async. The unclear objectives become vague Slack messages that generate confusion. The passive-aggression shows up in tone-policing and strategic emoji use. The dominant voice writes walls of text while others stop reading.
Decisions still don’t get made, but now it takes three days instead of thirty minutes.
Async advocates argue that written communication forces clarity because you have time to think through what you’re saying. This assumes people know how to communicate clearly in the first place.
Unfortunately, most don’t. Time to edit doesn’t help when you lack the underlying skill. It just produces longer, more elaborate versions of the same unclear thinking.
The format shift also creates new avenues for existing problems. In meetings, someone who talks over others is obviously disruptive. In async communication, that same person sends twelve messages before anyone else responds, effectively dominating the conversation through volume.
The behavior adapts. The impact remains the same.
There’s a deeper issue at play. When organizations adopt async work as a solution to communication problems, they’re treating symptoms while ignoring disease.
The real dysfunction isn’t that meetings happened at inconvenient times. It’s that people don’t trust each other, don’t listen well, don’t know how to give useful feedback, can’t make decisions efficiently, and struggle to have difficult conversations productively.
None of these problems care whether you’re communicating in real-time or with a three-hour delay.
The illusion of structural solutions to cultural problems
The enthusiasm around async work reflects a broader pattern in how we approach workplace dysfunction.
We love structural interventions. Change the tools, adjust the schedule, implement a new framework. These solutions feel concrete and manageable. They don’t require anyone to fundamentally change their behavior or confront uncomfortable interpersonal dynamics.
This is why organizational consultants can make entire careers out of introducing new communication platforms. There’s always another tool that promises to solve the problems the previous tool couldn’t fix.
Basecamp will organize everything. Slack will streamline communication. Asana will clarify responsibilities. Notion will centralize knowledge. Loom will replace meetings.
Each tool works beautifully for functional teams that already communicate well. For dysfunctional teams, each tool becomes a new venue for the same old problems. The issues aren’t technical. They’re human. And human problems require human solutions, which are substantially harder to implement than software.
The productivity literature around async work is particularly revealing in what it avoids addressing.
There are detailed guides on how to structure asynchronous communication, which tools to use, how to document decisions, when to go synchronous versus async. What’s missing is any serious discussion of the interpersonal skills required to make any of it work.
How do you give critical feedback asynchronously without it landing like an attack? How do you build trust when you rarely interact in real time?
How do you navigate disagreement productively when tone is impossible to convey accurately in text? How do you create psychological safety in a work environment where everything is documented and searchable?
These questions have no structural answers. They require emotional intelligence, communication skills, and organizational cultures that value directness over politeness, clarity over comfort, and genuine collaboration over the appearance of productivity.
What gets lost in the shift
Async work advocates often dismiss concerns about losing spontaneity or connection as nostalgia for outdated work models.
Real-time interaction is inefficient, they argue. Synchronous communication is a relic of office culture. Everything can and should be asynchronous except for the rare occasions when it absolutely must be real-time.
But efficiency isn’t the only thing that matters in human collaboration, and some forms of understanding simply cannot happen through text on a screen.
Some conversations demand immediate back-and-forth to work through complexity.
A misunderstanding that dissolves in thirty seconds of talking can take hours of careful messaging to untangle.
Genuine connection often builds trust faster than months of professional Slack exchanges ever could.
Creative breakthroughs emerge from spontaneous conversation in ways that threaded discussions planned three days in advance simply cannot replicate.
The async-first approach treats all of these as acceptable losses in service of individual productivity. Everyone works when they’re most productive. No one gets interrupted, and there’s maximum flexibility.
But organizations aren’t collections of individuals optimizing their personal output. They’re groups of people trying to accomplish things together, and that requires connection, spontaneity, and the kind of communication that text-based async tools handle poorly.
This matters particularly for newer employees, for people learning new skills, for teams navigating change or crisis. These situations demand rich communication. They benefit from tone of voice, facial expression, immediate clarification, the ability to ask follow-up questions without waiting hours for responses.
Async communication can supplement these interactions, but it definitely can’t replace them.
Building communication that actually works
Async work can be part of a healthy communication ecosystem.
For focused work that requires deep concentration, it’s often superior to constant interruption. For allowing people in different time zones to collaborate effectively, it’s essential. For creating documentation that persists beyond individual memory, it’s valuable.
But these benefits only materialize when the underlying communication is already functional.
Start by auditing what’s actually broken. Are meetings unproductive because they happen in real-time, or because they lack clear agendas, include too many people, and avoid making actual decisions?
Is synchronous communication the problem, or is it that people don’t know how to have difficult conversations regardless of format?
Does the team need async tools, or do they need to learn how to listen to each other, give clear feedback, and work through disagreement constructively?
The format matters less than you think. The skills matter more than anyone wants to admit. And no amount of asynchronous work will fix a team that fundamentally doesn’t know how to communicate with each other. The dysfunction will simply find new ways to express itself, one Slack thread at a time.
