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

The average knowledge worker attends 62 meetings per month, according to research from Atlassian. Roughly half of them are rated as unproductive by attendees. That's 31 hours a month doing something that most participants find wasteful. And yet, "we need to get everyone together to discuss this" is still the default response to any significant question at most companies.

The problem isn't meetings. Some conversations genuinely require synchronous interaction. The problem is that most organizations have no shared understanding of when meeting is the right tool versus when it's just the comfortable default.

Here's the framework that actually works.

The Three Questions Before You Schedule

Before sending a calendar invite, answer these three questions honestly:

1. Does this require real-time back-and-forth?

If the primary value of the interaction is the dynamic exchange — brainstorming where one idea builds on another, negotiating a position, working through an ambiguous problem where the solution depends on input from multiple people simultaneously — then a meeting is appropriate.

If one person is primarily transferring information to others who will absorb it and act, that is not a meeting. That is a document with a presentation attached.

2. Does everyone in the invite actually need to decide something?

Most meetings have two or three people who are genuinely necessary and four or five who are there "for alignment" or "to stay in the loop." Those people's time is being spent on something they could read in four minutes.

Ruthless invite lists are a kindness. Invite the people who need to contribute, note the decision in writing afterward, and share it with the people who need to know.

3. Can this wait, or is synchrony valuable right now?

There's a class of conversations where timing genuinely matters — a deal closing today, a production incident, a conflict that's actively festering. Real-time communication has higher bandwidth for emotion and urgency. Use that when urgency is real, not manufactured.

What Should Have Been an Email (Or Document)

• Status updates on projects that aren't blocked
• Decisions that one person should just make and communicate
• Information that will be forgotten by half the room by end of day
• Recurring meetings where the agenda is nearly identical every week
• Anything that would benefit from being written down anyway

A Bengaluru-based logistics startup replaced their Monday morning "team sync" — a 75-minute meeting that 12 people attended — with a Friday afternoon Notion update. Each person writes three bullets: what they finished, what's next, what they're blocked on. The meeting dissolved. Nobody missed it. Decisions that actually required synchronous discussion started happening in 20-minute calls with the right three people.

What Should Have Been a Meeting (Not an Email Thread)

Here's the underrated problem: some things that should be meetings become email chains instead. This is equally destructive.

Long email threads with multiple stakeholders debating a nuanced decision are a failure mode. By the fourth reply, nobody is responding to the original email — they're responding to the last thing they read. Context is lost. Positions calcify. The thread becomes an archaeological dig.

If an email chain has more than four replies and still isn't resolved, it should have been a meeting.

Complex negotiations, interpersonal tension, creative problems that require building on each other's ideas — these belong in conversation. Trying to handle them in writing usually takes three times as long and produces worse outcomes.

The Format Nobody Uses Enough: The Async Video

Between a meeting and a document sits an underused middle layer: a short recorded video. Loom, Vimeo, whatever. Three-minute walkthrough of a design decision. A five-minute summary of a strategic question with a request for written responses.

This format captures something documents can't — tone, emphasis, nuance — without requiring anyone to be available at the same moment. It's particularly effective for remote and distributed teams where time zones make synchrony expensive.

The Meeting Types Worth Keeping

Not all meetings are equal. Some categories earn their calendar time:

Weekly 1:1s — Essential. The relational thread that holds a team together.

Quarterly planning — Needs real-time dynamic thinking. Worth the half-day.

Retrospectives — Psychological safety is easier to build in conversation than in writing.

Hiring debriefs — Multiple perspectives calibrating in real time matters here.

Crisis response — When things are actively breaking, real-time coordination beats everything else.

These have clear rationale. The meeting to "discuss the roadmap," attended by twelve people with no clear owner and no defined outcome, does not.

Making the Meetings You Keep Better

If a meeting happens:

• Send a clear agenda 24 hours before. No agenda, no meeting.
• Define the outcome at the top: decision, alignment, or brainstorm.
• End with recorded next steps and owners. This alone eliminates the "what did we even decide?" problem.
• Start and end on time. This isn't about punctuality — it's about respecting that everyone's day is structured around that calendar block.

The So-What

The goal isn't fewer meetings as a metric. Companies that proudly announce "we cut meetings by 40%" often just moved the conversation to unstructured Slack pings, which is worse. The goal is meetings that have a clear reason to be synchronous, include only the people who need to be there, and produce a clear output.

That's a culture question more than a tool question. It requires someone — usually a manager — to model the behavior and occasionally say: "This doesn't need a meeting. Here's the document I'll send instead."

One person doing that consistently changes norms faster than any policy ever will.

---