Could This Meeting Be an Email? A 5-Question Test With Examples

Short answer: it could be an email if the goal is to share information, the decision is already made or easily made async, no real back-and-forth is needed, and nobody has to react to each other live. It needs to be a meeting only when you need genuine dialogue, a hard decision among people who disagree, sensitive or emotional context, or fast iterative back-and-forth that email would stretch over days. Below is a 5-question test that gives you a yes/no in about thirty seconds, with worked examples for the calls that feel ambiguous.

Why this question is worth taking seriously

"This meeting could have been an email" is a meme, but the cost behind it is real and measurable. The problem is not meetings; it is the default. When the calendar is the path of least resistance, low-information status updates and one-way announcements quietly eat the hours that deep work needs. The data on that is consistent and comes from credible researchers, not vendor fluff.

It is not only the meeting itself. Meetings fragment the day, and fragmentation is where focus goes to die. Microsoft's research found that the typical knowledge worker is interrupted constantly, and that meetings cluster precisely in the hours when deep work should happen.

And the waste is growing, not shrinking. Hybrid work multiplied the number of calls, and the unproductive ones grew fastest.

The 5-question test

Ask these in order before you click "new event." The first question filters out the majority of offenders; the next four catch the legitimate exceptions. The whole point is that a meeting has to earn its slot, instead of being the default container for anything that involves more than one person.

Question 1: Is the goal to inform, or to decide and align?

This is the single biggest filter. One-directional information transfer, where you talk and others listen and nod, is the textbook "could have been an email." Status updates, FYIs, recaps, read-outs of a finished decision, and progress reports are almost always better written. Writing them forces clarity, creates a searchable record, and lets people read at their own speed and timezone. If the real goal is to converge on a choice or get a room genuinely on the same page, that leans meeting.

Question 2: Do people need to react to each other in real time?

Email and shared docs are asynchronous: people respond when they can. A meeting's only true superpower is synchrony, the live build-on-each-other energy where one person's comment changes what the next person says within seconds. If the exchange works just as well spread across a day of comment threads, you do not need everyone in a room at the same minute. If it genuinely needs the speed and texture of live reaction, keep the meeting.

Question 3: Is there real disagreement to resolve?

Conflict is the most honest reason to meet. When two or more people hold different views and the difference actually matters, async threads tend to harden positions, get misread in tone, and stall. A short live conversation resolves in fifteen minutes what an email chain drags out over three days and forty replies. But notice the condition: real disagreement among people who care. "Does anyone object?" when you already know nobody does is an email with a deadline, not a meeting.

Question 4: Is it sensitive, personal, or emotional?

Some content should never be an email regardless of how efficient text would be. Feedback that could sting, anything about someone's performance or role, bad news, a delicate negotiation, a first conversation with a new client or candidate. Tone and trust carry the message here, and text strips both out. When the human stakes are higher than the information stakes, meet, and often meet one-on-one.

Question 5: Does it need fast, messy iteration?

Brainstorms, whiteboarding, troubleshooting a live problem, shaping a plan from a blank page. These involve many quick loops where each turn depends on the last, and the cost of a half-day round trip per loop is brutal. If you are going to do twenty exchanges in forty minutes, do them live. If you need three exchanges over a week, a doc with comments is calmer and better documented.

Worked examples for the calls that feel ambiguous

The test is easy on clear cases. Here is how it resolves the ones people actually argue about.

• "Weekly team status update" -> EMAIL. Goal is to inform (Q1), no live reaction needed, no disagreement, not sensitive, not iterative. Replace with an async written update or a shared dashboard. This is the highest-value swap you can make.
• "Kickoff for a project where roles are unclear and two leads disagree on scope" -> MEETING. Real disagreement (Q3) plus alignment (Q1). Get them live, then write the decision down afterward.
• "Reviewing a near-final document for typos and small edits" -> EMAIL / comments. Async iteration is fine; the loops are slow and independent. A live read-through wastes everyone but the author.
• "Brainstorming names and positioning for a new product" -> MEETING. Fast messy iteration (Q5); ideas spark off each other in seconds. Async ideation goes cold.
• "Telling a contractor their contract won't be renewed" -> MEETING, one-on-one. Sensitive and personal (Q4). Never an email, even though the information is two sentences.
• "Announcing a finalized policy change to the whole company" -> EMAIL. The decision is made; the goal is to inform (Q1). Offer an optional Q&A session for those who want one, rather than mandating a meeting for everyone.
• "Three engineers debugging a production incident right now" -> MEETING (or a live call). Fast iteration (Q5) under time pressure; async would cost the company by the minute.
• "Collecting everyone's availability for an offsite" -> NEITHER a meeting nor a long email thread. Send a scheduling link and let people pick.

If it survives the test, make the meeting actually worth it

A meeting that passes the five questions still deserves discipline. The same research that quantifies the waste points to the fixes, and they are unglamorous: an agenda with a stated goal, the smallest necessary invite list, a hard end time, and a written record afterward so the people who did not need to be there can still stay informed without a recurring slot.

1. State the goal in the invite. If you cannot write a one-sentence outcome ("decide X," "align on Y"), you are not ready to meet. A meeting with no stated objective is the most common kind that could have been an email.
2. Invite only people who will speak or decide. Everyone else gets the notes. Optional attendees should genuinely feel free to decline.
3. Default to 25 or 50 minutes, not 30 or 60, to leave breathing room and protect focus blocks.
4. Write the outcome down within the hour. The notes are what let you kill the next three meetings on the same topic.
5. Protect the 9-11am and 1-3pm windows. Microsoft's data shows that is exactly when meetings overwrite deep work; push status-type calls to the edges of the day.

The bottom line

Default to writing. A meeting should be a deliberate choice you can defend with one of four reasons: live reaction, real disagreement, human sensitivity, or fast iteration. If none of those apply and you're just moving information from your head into other heads, the email wins, and the data says it wins by tens of thousands of dollars and hours per employee per year. Run the five questions before you book, audit your recurring invites first, and give everyone their focus hours back.

The meeting is the most expensive recurring line item nobody puts on a budget. Make each one earn its slot.