The Meeting That Could Have Been an Email

It's become its own genre of workplace humor: the meeting that could have been
an email. Everyone has lived it. Twenty people in a room — or on a call — listening
to information that could have been read in three minutes. No discussion. No decision.
Just presence, required.

The joke carries a real question: why does this keep happening? If it's obvious to
everyone involved that the meeting is unnecessary, why does it persist?

The answer isn't about poor planning. It's about something more interesting — and
more uncomfortable — than inefficiency.

---

The Meeting as Control Mechanism

Here's a pattern that shows up across organizations, industries, and levels: managers
convene meetings not because the work requires it, but because the meeting itself
serves a function that has nothing to do with information exchange.

The meeting establishes control. It demonstrates authority. It creates the visible
presence of coordination, even when the actual coordination could happen asynchronously.
It reassures the person calling it that things are under control — not because the
meeting produces control, but because convening people is itself an expression of it.

This isn't conscious manipulation. It's structural. The meeting becomes the manager's
tool for managing their own uncertainty about whether work is progressing, whether
people are aligned, whether things might slip without active oversight.

The problem is that the meeting doesn't actually resolve that uncertainty. It just
temporarily alleviates it. And that creates a cycle: more meetings to manage the
anxiety, which produces more fragmentation, which increases the need to reconvene.

The three patterns

1. Control through presence

The all-hands. The status update. The check-in. The ostensible purpose is information
sharing, but the actual function is visibility. The manager needs to see that people
are there, that they're engaged, that the work is real and progressing.

The issue: attendance doesn't equal engagement. And the things that would actually
signal progress — output, decisions made, problems solved — are often better communicated
through documentation than through synchronous presence.

But documentation doesn't give you the reassurance of seeing people nod. It doesn't
let you read the room. So the meeting persists, even when the information being shared
could have been an email, a memo, a dashboard update.

2. Visibility as performance

Related, but distinct: the manager who convenes meetings to demonstrate that management
is happening. Not to the team — to someone else. The boss, the peer group, the
stakeholders who need to be reassured that this area of work is being actively led.

The meeting becomes theater. The calendar full of recurring check-ins becomes evidence
of diligence. The problem is that the performance of management and the substance of
it aren't the same thing. Time spent in coordination meetings is time not spent making
decisions, removing obstacles, or creating clarity.

But in organizations where leadership is evaluated on visible activity rather than
outcomes, the meeting schedule becomes the metric. And the team pays the cost in
fragmented time and cognitive overhead.

3. The meeting as anxiety management

The most honest version of the pattern: the manager who calls meetings because not
calling them feels risky. What if something goes wrong and I wasn't checking in?
What if people drift out of alignment and I didn't catch it? What if a decision gets
made without me and it's the wrong one?

The meeting becomes insurance against that risk. Not because it actually prevents those
outcomes — most of the time, the meeting doesn't surface issues that wouldn't have been
caught another way — but because it creates the feeling of oversight. The anxiety is
managed. The work, however, might not be better for it.

What This Costs

The cost of unnecessary meetings isn't just time. It's fragmentation. It's the
cognitive overhead of context-switching. It's the impossibility of deep work when
your calendar is blocked in 30-minute increments. It's the signal to the team that
presence matters more than output, performance more than results.

And crucially: it's the loss of actual coordination. When meetings proliferate,
they crowd out the meetings that matter — the ones where decisions are genuinely
being made, where conflict is being surfaced and resolved, where alignment is being
created rather than performed.

The meeting that should have been an email doesn't just waste an hour. It makes the
necessary meetings harder to find, harder to prepare for, and harder to take seriously.

A Different Metric

Organizations that actually reduce meeting overhead don't do it by mandating no-meeting
Fridays or setting arbitrary time limits. They do it by changing the question. Instead
of who needs to be in the room? they ask what decision are we making, and
what's the minimum viable group to make it?

Instead of defaulting to recurring check-ins, they ask: what information do I
actually need to feel confident this work is on track, and what's the lowest-overhead
way to get it? Instead of using the calendar as a proxy for management, they
look at outcomes: are decisions getting made? Are obstacles being removed? Is the work
progressing?

These questions don't eliminate meetings. But they eliminate the meetings that exist
to serve the manager's need for control rather than the work's need for coordination.

---

The meeting culture in your organization isn't an accident. It's the result of how
managers have learned to signal competence, manage uncertainty, and demonstrate that
leadership is happening. Changing it requires changing those underlying needs — or
finding other ways to meet them.

The meeting that could have been an email persists because it was never
about the information. It was about the control.

If you want to audit your own meeting culture, explore our
free resources for frameworks that help distinguish coordination from theater.