The default response to any workplace question is “let’s schedule a meeting.” It’s often the worst response.

Meetings are synchronous: everyone must be present at the same time. They favour quick thinkers and confident speakers. They interrupt everyone’s schedule. And they’re almost always longer than necessary.

Asynchronous communication — writing, recorded video, shared documents — gives people time to think, time to research, and time to respond thoughtfully rather than reactively.

Why Async Works Better for Thinking

When someone asks you a question in a meeting, you have seconds to formulate a response. The pressure of real-time interaction favours immediate reactions over considered thinking.

When someone asks the same question in a written message, you have minutes, hours, or even a day to think it through. You can research. You can consult colleagues. You can structure your response.

The quality difference is real. Decisions made asynchronously are typically better-considered than decisions made in real-time meetings.

What Should Be Async

Status updates. Nobody needs a meeting to share project status. A brief written update achieves the same thing in a fraction of the time.

Non-urgent questions. Most questions don’t need an immediate answer. Ask in chat or email. Let people respond when it suits their workflow.

Information sharing. Sharing documents, reports, or news doesn’t require synchronous presence. Send it with a brief summary. People can read at their own pace.

Feedback on work. Written feedback is more actionable than verbal feedback. The recipient can reference it later, share it with colleagues, and process it thoughtfully.

Decision inputs. When a decision needs input from multiple people, collect those inputs asynchronously before meeting. The meeting (if needed) becomes about deciding, not about gathering perspectives.

What Should Stay Synchronous

Sensitive conversations. Difficult feedback, personal issues, and emotional topics deserve real-time human interaction. The nuance of tone and expression matters too much for text.

Brainstorming. The energy of real-time idea generation, building on each other’s suggestions, can’t be replicated asynchronously. True brainstorming benefits from synchronous interaction.

Complex negotiations. When positions need to be debated and compromises found in real-time, meetings are appropriate.

Team building. Social connection requires shared time and presence. This is the one area where “this could have been an email” genuinely doesn’t apply.

How to Shift Your Team

If your team is meeting-heavy, the shift to async requires intentional effort:

Model it. Start sending written updates instead of scheduling meetings for your own work. When someone requests a meeting, ask “could this be handled in a shared document instead?”

Establish async norms. Expected response times for different channels (email: 24 hours, Slack: 4 hours during work). This prevents the anxiety of “am I being unresponsive?”

Use the right tools. Shared documents (Google Docs, Notion) for collaborative writing. Loom for recorded video walkthroughs. Slack threads (not channels) for focused discussions.

Record decisions. The biggest risk with async communication is decisions getting lost in threads. Designate a place where decisions are recorded and easily referenced.

The Written Culture Advantage

Organisations that communicate primarily in writing develop several advantages:

Institutional memory. Written discussions are searchable. A new team member can read the reasoning behind past decisions.

Inclusivity. People who are quieter in meetings, non-native English speakers, and those in different time zones contribute equally in writing.

Clarity of thinking. Writing forces you to organise your thoughts. You can’t wave your hands and say “you know what I mean” in a written document.

Reduced meeting load. When most communication is async, the meetings that do happen are genuinely necessary and more productive.

The Discipline Required

Async communication requires discipline from both senders and recipients.

Senders: Write clearly. Provide context. State what you need and by when. Don’t make people guess what you’re asking.

Recipients: Respond within agreed timeframes. Read fully before responding. Flag when you need more time.

Everyone: Resist the urge to default to meetings. Ask “does this need to be a meeting?” before scheduling.

The transition is uncomfortable for teams accustomed to meeting culture. But the productivity and satisfaction gains are substantial. Less time in meetings means more time for actual work. And that’s what most people actually want.