“This meeting could have been an email” means the speaker believes a meeting used more time or coordination than its purpose required. The information, they suggest, could have been shared asynchronously in writing.
“We joined a 45-minute call just to hear one date. That meeting could have been an email.”
The sentence is grammatically literal, but its workplace force is often humorous criticism: “We followed an elaborate office ritual for a simple information transfer.”
What do the words literally claim?
The modal construction could have been describes an unrealized alternative in the past. A meeting happened; an email did not replace it. The speaker now judges email to have been sufficient.
The shared script contrasts two communication channels:
- a meeting requires synchronized calendars, attendance, and live attention;
- an email can deliver a stable update that recipients read at different times.
The joke assumes the meeting produced no benefit that justified the extra coordination—no real debate, sensitive conversation, relationship building, or collaborative decision.
That assumption may be fair, but it is still an interpretation. A meeting organizer may have expected discussion even if none occurred.
Why does it function as a joke?
The humor comes partly from bathos, a drop from an important-looking event to a mundane alternative. Invitations, agendas, video links, and many attendees promise significance; the outcome is information that might fit in a short message.
It also works as compressed criticism. Instead of reviewing the agenda design, the speaker uses a familiar one-line verdict.
The frustration behind the joke is real for many workers. Microsoft’s 2023 Work Trend Index reported that survey respondents ranked inefficient meetings as their leading productivity disruption. Microsoft itself used the question “couldn’t this have been an email?” when discussing those findings. That research supports the workplace concern, but it does not prove that any particular meeting was unnecessary.
What might you hear at work?
After a call, a peer might say privately:
“Well, that could have been an email.”
The softer could have criticizes the format retrospectively. Another variation is:
“This should have been an email.”
Should have is stronger. It suggests the organizer made the wrong choice, not merely that another choice was possible.
A lot to take in? It is.
But Rome wasn't built in a day. Build your American workplace English one expression and cultural reference at a time—with curated explanations and structured practice in Lyra Practice.
Start a session →You may also see the wording on mugs, stickers, memes, or virtual backgrounds. In those settings, it can express general meeting fatigue rather than criticism of one named colleague.
What can you safely say in response?
If a peer says it after a low-value meeting:
“The main update was the revised date, right?”
“Agreed that the status portion could be async. The decision section may still need discussion.”
“I’ll suggest a written update next time.”
These responses identify the useful point without joining a personal attack.
If you organized the meeting, ask for actionable feedback:
“Which part would you move to email, and what would still benefit from live discussion?”
That question turns the joke into a process improvement.
How can you express the idea professionally?
Before a meeting:
“Could we handle this as an asynchronous update?”
“What decision requires live discussion?”
“If this is informational only, I can send a concise written summary.”
After a meeting:
“For future status updates, a written format may save the team time.”
“The discussion became useful once we reached the trade-off. Could we circulate the background in advance?”
These alternatives separate the communication design from the organizer’s competence.
When is producing the joke risky?
Avoid posting it in the meeting chat while the organizer is speaking. That can look disrespectful and may encourage others to disengage. Saying it immediately after a new employee’s first presentation can also humiliate them.
The joke is a poor fit when confidentiality, conflict, accessibility, emotional nuance, or rapid collaborative judgment made live conversation valuable. Email is not automatically cheaper: a long, confusing thread can consume more time than a focused call.
Be especially cautious across hierarchy. If a senior person jokes downward, attendees may feel blamed for a meeting they were required to join. If a junior employee says it publicly about an executive’s session, the line may be read as contempt rather than useful feedback.
How do you avoid the literal-listener trap?
A non-native listener might wonder whether the speaker truly wants an email now. Usually, the phrase evaluates the meeting that already happened; it is not a request to repeat the content by email. You can confirm the practical need:
“Would a written recap still be helpful, or are you commenting on the format?”
For language that improves the next meeting, see how to close a meeting with clear next steps. To preserve decisions asynchronously, see documenting decisions after meetings.