Default to asynchronous communication

Treat real-time communication as the exception, not the default — most things do not require an immediate response.

Why it works

Real-time communication (Slack, calls, meetings) fragments attention and creates the expectation of immediate responses, which keeps everyone in reactive mode. Asynchronous communication (written, with an explicit response window) respects the receiver’s attention schedule and forces the sender to think more carefully before writing — which improves the quality of communication and dramatically reduces its volume.

How to do it

1. Set a team or personal default: unless something is genuinely time-critical, communicate in writing with a 24-hour response window.
2. Turn off or mute synchronous message notifications except during designated response windows.
3. When you feel the urge to send a real-time message, ask: "Does this require their answer in the next hour?" — if not, write it asynchronously.
4. Write asynchronous messages with enough context that they do not generate four follow-up questions.

Evidence

Attention residue research shows that real-time interruptions impose significant recovery costs; asynchronous communication reduces these interruptions. Organizations using async-first structures report higher deep-work time. (observational)

Research on async-first workplaces is mostly case-study and survey; controlled comparisons between synchronous and asynchronous-default teams are limited. Coordination costs of async can be higher for certain task types.

Sources

• Leroy (2009), attention residue, Organizational Behavior and Human Decision Processes

Common mistake

Switching to async-first tools (email instead of Slack) while maintaining implicit norms of immediate response, which preserves the urgency culture without changing the medium.