How to decide between a meeting and asynchronous communication
The question is whether the outcome needs real-time, two-way discussion. If it can be written, read and acknowledged, it can be asynchronous.
When an email or written update is enough
- Sharing status or progress
- Announcing a decision already made
- Distributing information with no debate needed
- Gathering feedback that does not need live discussion
When a meeting is genuinely needed
- A decision with conflicting views
- A sensitive conversation requiring tone and trust
- Complex alignment that benefits from real-time dialogue
- Workshops and brainstorming that need interaction
A meeting-versus-email checklist
- Is real-time discussion required?
- Will the outcome change through dialogue?
- Do participants need to react to each other?
- Is the topic sensitive or nuanced?
Examples
A weekly status report is an email. A decision between two competing directions is a meeting. A policy announcement is an email. A retrospective is a meeting. A roadmap FYI is an email. A prioritization workshop is a meeting.
Key takeaway
Use a meeting only when the outcome needs real-time dialogue; otherwise a written update respects everyone’s time.