Should This Meeting Be an Email? A Decision Framework
Research shows 72% of meetings are ineffective, yet most teams have no structured way to decide when a meeting is genuinely necessary. Here is a practical decision framework — and the cost question to ask before every calendar invite.
Quick answer: A meeting is the right format when you need real-time discussion to reach a decision, resolve conflict, or do creative work that benefits from simultaneous input. Everything else — information sharing, status updates, one-way reporting, announcements, and decisions with no meaningful debate — is faster and cheaper as an email, a document, or an async update.
You have received the invite. There is no agenda in the body. The subject line is vague. There are twelve attendees, several of whom have no clear role in the decision. The meeting is booked for 60 minutes.
You have ten seconds before you click Accept.
The question you should be asking — and almost never do — is: what does this meeting cost, and is that cost justified by the outcome it will produce?
Atlassian's research across 5,000 knowledge workers found that 72% of all meetings are ineffective — they fail to produce a decision, advance a project, or create something that could not have been achieved another way. Three in every four meetings could have been an email, an async update, or nothing at all.
The problem is that most organisations have no structured decision process for when to meet. Meetings are booked by default and defended by habit. This framework changes that.
The three-question test
Before booking or accepting any meeting, apply these three questions in order. If the answer to all three is "no," the meeting should not exist.
Question 1: Does this require real-time, synchronous discussion?
Some tasks are genuinely synchronous by nature — they require the simultaneous, interactive input of multiple people. Brainstorming sessions where ideas build on each other. Conflict resolution where tone and body language matter. Decisions where participants need to negotiate and adjust their positions in real time.
Most meetings are not this. A status update does not require synchronous attendance. An announcement does not require a live audience. A decision with a clear recommendation does not require group deliberation — it requires a reviewer and a response.
If the task could be handled through a written update, a recorded walkthrough, or a structured comment thread without meaningful quality loss: the answer is no.
Question 2: Is a decision, deliverable, or genuine collaboration the output?
A meeting that ends without a decision, a completed piece of work, or a meaningful relationship advancement has no output. It is a synchronous consumption of time with no return.
Ask: at the end of this meeting, what will exist that did not exist before? If the honest answer is "a shared understanding that could have been achieved by reading a document," the meeting is unnecessary.
If the output is information that could be conveyed one-way, without live interaction: the answer is no.
Question 3: Would the absence of a meeting create a worse outcome?
This is the most direct test. If you cancelled this meeting and replaced it with an email thread or a shared document with comments, would the decision be slower, worse, or materially different?
For most routine operational meetings — weekly syncs, project status updates, recurring reports — the honest answer is no. Research supports this: 65% of senior managers say meetings keep them from completing their own work, yet those same managers continue attending them because declining a meeting invitation carries social friction that not attending a document thread does not.
If the outcome would be equivalent without the meeting: the answer is no.
The async alternatives, ranked by speed
When a meeting fails the three-question test, one of these formats typically serves better:
| Need | Better format |
|---|---|
| Share an update | Written email or Slack message |
| Report progress without discussion | Shared doc or async video (Loom) |
| Collect input from multiple people | Comment thread or structured form |
| Make a decision with a clear recommendation | Email with explicit "respond by [date]" |
| Gather status from team members | Shared status doc or async standup tool |
| Announce a decision | Email or recorded video |
| Seek feedback on a proposal | Circulate the doc; comments are input |
The test for each of these: would a live session with all parties add enough value to justify the salary cost of pulling everyone away from focused work at the same time?
The cost question that changes behaviour
Before sending any calendar invite, calculate the loaded cost of the meeting using this formula:
Meeting cost = attendees × (annual salary ÷ 1,920) × 1.3 × duration in hours
For a ten-person meeting lasting one hour, with average UK salaries of £45,000:
10 × (£45,000 ÷ 1,920) × 1.3 × 1 = £304
This is £304 of employer payroll expenditure — for one meeting. If that meeting runs weekly, it costs £15,808 per year.
Ask: would you approve a £304 expense on a budget form with the justification "routine sync"? If not, that justification is insufficient for a calendar invite too.
MeetingTick shows this number in real time during the session — making the cost visible to everyone, not just to those who have done the arithmetic. Displaying the cost at the start of a meeting, before it begins, is also an effective pre-screening tool: if the number makes the organiser uncomfortable, the meeting is worth questioning.
When the meeting is genuinely the right format
None of this is an argument against meetings. Some work requires them. Meetings are the right format when:
- Real-time negotiation is required. Budget discussions, scope trade-offs, or any situation where positions will shift in response to what others say benefit from live interaction.
- Sensitive topics demand human presence. Performance conversations, redundancy discussions, difficult feedback — these require the full communication bandwidth of in-person or video conversation.
- Creative generation is the goal. Stanford research found in-person meetings generate 15–20% more ideas than virtual equivalents, and both generate more than async. If ideation quality is what matters, the meeting format is justified.
- Relationship-building is the primary output. New team formations, client onboarding, cross-functional partnerships — the human connection that forms in shared real-time experience is not replicable in a document thread.
The decision in practice
The framework reduces to a practical habit: before every meeting you organise, write down the specific decision or deliverable the meeting will produce. If you cannot name it in one sentence, apply the three-question test. If the meeting fails that test, draft the email instead.
For meetings you attend but do not organise: the same test applies. Asking "what is the decision this meeting will produce?" before clicking Accept is not presumptuous — it is the question every organiser should have answered in the invite.
Use MeetingTick to track the cost of meetings you do run, and build the discipline of treating meeting time as the discretionary budget line it is.
Sources: Atlassian — Workplace Woes: Meetings · Fortune — 3 in 4 meetings ineffective · David Burkus — Could that meeting be an email? · Float — 5 ways to tell if a meeting should be an email · Fellow — 45 Meeting Statistics 2025 · Stanford GSB — virtual communication curbs creative idea generation · Speakwise — unnecessary meetings statistics 2026