You join the call. Someone shares their screen. They begin reading the slides. Word. For. Word. Thirty-eight minutes later nobody has disagreed with anything, nobody has decided anything, and you close your laptop thinking what half the attendees are thinking:

"This meeting could have been an email."

You are almost certainly right — but not for the reason the mug and the TikTok sound imply. The complaint is not that the meeting was long, or boring, or badly chaired. It is that nothing occurred in it that required everyone to be present at the same moment. That is a specific, diagnosable failure, and it has a test. Most meetings fail it. Some genuinely don't — and telling those apart is the entire skill.

What the Phrase Actually Means

A meeting could have been an email when it is one-way information transfer: someone knows something, everyone else needs to know it, and the transfer has been scheduled as a synchronous event. No decision gets made. No disagreement gets resolved. The content would survive being read at 8pm by someone on another continent, and would probably be clearer.

Put the other way round: a meeting buys exactly two things a document cannot. Simultaneity — where my sentence changes yours before you finish it. And social presence — tone, hesitation, the pause before someone says "fine". If a session uses neither, the invite is doing the work of a document, badly.

How much this costs an organisation in aggregate is a separate subject, and we cover the numbers on meeting intelligence. This post is about the judgment call in front of you: this meeting, on this invite — could it have been written?

The Four-Question Test

Run this before you accept an invite, and before you send one. Each question asks whether the session needs simultaneity or presence.

Four noes and it should have been written. One clear yes is a real meeting — and deserves to be run like one, with the reading done in advance so the time goes on the disagreement rather than the briefing.

The Five Formats That Almost Always Fail

These recur across every company, and they fail the test for the same reason: the content is information, and the format is a broadcast.

But Some of My Best Work Happens in Meetings

It does, and the phrase is overused as a reflex. Deliberation genuinely is faster in a room: when four people are arguing about a trade-off, an hour of live argument covers ground that would take a week of replies, because objections get answered while they are still cheap to answer.

Written channels are also actively bad at some things. They harden positions: once your objection is on the record in writing, backing away from it feels like a loss. A room lets somebody change their mind mid-sentence at almost no social cost — which is exactly what you want when the goal is the best answer rather than the best-defended one. Conflict, ambiguity, bad news and negotiation all belong in the room for this reason.

So the honest version of the complaint is narrower than the meme: not meetings are waste, but this particular meeting spent presence on something that did not need it. The opposite failure is just as expensive — a real decision pushed out of the room, which we take apart in "Let's Take This Offline" Is Killing Your Decisions.

The Emails That Should Have Been Meetings

Watch for the reverse error, because it hides better. A thread has been running three days and nine replies. Two people are restating positions with increasing politeness. Somebody has started numbering their points. A disagreement that has gone past two rounds of replies has become a meeting with worse latency — you are paying meeting costs in calendar days instead of minutes, and nobody can see anyone's face.

Which gives a workable default. Information gets written. Disagreement gets witnessed. And a decision gets all three: written first so people arrive informed, decided live, then recorded so the reasoning survives — the shape we describe under asynchronous decision-making.

Why Email-able Meetings Get Scheduled Anyway

Nobody schedules a pointless meeting on purpose. Four ordinary pressures produce them reliably.

What to Write Instead

"Send an email" is not the fix, and sending a 900-word wall of text is how async work gets a bad name. The replacement for an email-able meeting is a document with a decision-shaped spine: what is being decided, the options, your recommendation and why, what you need from the reader, and a date after which silence counts as agreement.

That last clause is what makes it work. An update with no deadline gets ignored; a recommendation with an objection window gets read, because saying nothing now means agreeing later. It is also how the reasoning survives contact with next quarter — the difference between a record of what was decided and a record of why, which is the argument we make in the meeting intelligence revolution.

And protect the meetings that pass. Give them the pre-read, open with the objections rather than the background, and record what was chosen and which arguments lost. A meeting that earns its hour should not spend the first twenty minutes catching people up.

The Real Question

The phrase survives on mugs because it is almost always true and almost never actionable. Said afterwards it is a complaint; applied before the invite goes out it is a filter — and the four questions are the filter.

Most meetings are information wearing a meeting's clothes. A few are genuine deliberation, and those are worth defending against the ones that are not. Getting that sorting right needs no tooling, no policy and no permission.