Is asynchronous work creating capacity or hiding friction?
Evidence suggests that simply moving bad meetings to asynchronous text channels does not reduce coordination burden; it often fragments it, extending Flow Time while attempting to reduce Human Time.
Jean Bernier
Founder, BTCF Originator
Question
Does adopting an asynchronous-first operating model actually increase systemic speed, or does it merely obscure the coordination tax?
Why It Matters
Future business design relies heavily on distributed, asynchronous work to scale without the geographic constraints of legacy models. But many organizations find that while their executives are in fewer meetings, decisions take three times as long to finalize.
What We Reviewed
We analyzed organizational network data comparing meeting-heavy synchronous cultures with Slack/Teams-heavy asynchronous cultures, alongside our own mapping of Flow Time in four remote-first growth companies.
What the Evidence Supports
The data shows that asynchronous communication reduces Human Time but often radically expands Flow Time.
- A 30-minute synchronous meeting might consume 3 hours of total Human Time (6 people × 30 minutes).
- Replacing that meeting with an asynchronous thread reduces total Human Time to perhaps 1 hour of total reading and typing.
- However, the decision that would have been finalized in minute 30 of the meeting now takes 3 days to resolve as people respond at their own pace across time zones.
- Flow Time extends by 2400%.
What it does not support
This does not support a return to 8-hour days of back-to-back Zoom meetings. It simply proves that "asynchronous" is a communication modality, not an operating system.
Bernier Interpretation
You cannot solve a decision-rights problem with a new communication policy.
If a decision requires 6 people to weigh in, the problem is not that they are meeting; the problem is that 6 people are required. Moving a 6-person consensus bottleneck to a Slack channel just makes the bottleneck slower and harder to track. True future business design requires giving one person the authority to decide without the other 5.
What This Changes
When designing future operating models, organizations must explicitly separate broadcast information (which should be asynchronous) from irreversible decisions (which require either unilateral authority or synchronous debate).
Open Questions
How do we design interfaces that provide the speed of synchronous decisions without the calendar cost of synchronous meetings?
Sources
- Organizational Network Analysis studies on remote coordination (2023)
- Bernier Group analysis of 4 remote-first operating models
Follow the Idea
Related Thinking
What question should this raise?
If the logic in this piece is true, what current operating assumption in your business must be false?