The Meeting That Should Have Been an Email (And Vice Versa)

The recurring calendar invite. The meeting that could have been a quick message. Every team has them.

But the flip side is equally costly: the email thread that spirals for three days when a 15-minute call would have solved it.

Both are expensive. Neither is the default problem.

The Test for Whether It Should Be a Meeting

Ask: "Does this need real-time interaction to get to a decision?"

Real-time interaction is required when:

• You need immediate back-and-forth to clarify something
• Multiple people need to react to each other's points simultaneously
• The emotional stakes are high and you need tone-of-voice to work
• You're brainstorming and building off each other's ideas in the moment

If none of those apply, an email or doc will probably work.

The Test for Whether It Should Be an Email

Ask: "Does this need a synchronous conversation?"

You need a meeting when:

• The decision is complex and has many moving parts
• Multiple parties have conflicting interests that need negotiation
• There's build-up or context that's faster to explain verbally
• You need commitment and buy-in, not just acknowledgment

If the issue is important enough to require alignment but simple enough to explain in writing, try the written path first.

The Cost Matrix

Email is cheap to send and expensive to clarify when misunderstood. Meetings are expensive to schedule and cheap to align when done right.

Use the format that matches the stakes. Low-stakes updates: email. High-stakes decisions: meeting.

The real problem isn't choosing the wrong format. It's treating all communication as the same format by default.