Should This Meeting Have Been an Email?

The question "should this have been an email?" is asked silently in most meetings. This article gives you a framework for answering it before the invite goes out.

When a meeting is the right choice

A meeting is appropriate when:

• A decision requires real-time discussion among people with different information or authority
• There is genuine disagreement that needs to be worked through together
• The topic is sensitive and requires a human conversation
• Collaboration on a problem requires simultaneous input from multiple people
• The stakes are high enough that written communication creates too much risk of misunderstanding

When an email is the right choice

An email is appropriate when:

• You are sharing information that people need to read and absorb, not discuss
• The decision has already been made and you are communicating it
• You need a written record of what was communicated and when
• People are in different time zones and synchronous attendance is impractical
• The update is routine and does not require input

The grey area

Some situations genuinely require judgment. A complex project update might benefit from a short meeting if there are questions, but could also be handled with a well-structured written update and a standing offer to discuss.

When in doubt, write the email first. If it raises questions that cannot be answered in writing, schedule the meeting. This approach often reveals that the meeting was not needed.

The hidden cost of the wrong choice

Choosing a meeting when an email would do costs everyone their time. A one-hour meeting with eight people is eight hours of work. That is a full working day, distributed across eight people who each had other things to do.

Choosing an email when a meeting was needed costs clarity, alignment, and sometimes trust. A difficult conversation handled by email can create more confusion than it resolves.