The meeting that should have been an email

The meeting that should have been an email usually ends by creating another meeting.

Nobody did anything obviously wrong. The update was delivered. People asked thoughtful questions. Several concerns were "taken away." The final 4 minutes produced 3 action items, all assigned to a collective noun.

Then everyone returned to the work the meeting had interrupted, carrying the same unresolved decision in a slightly newer document.

This is why unproductive meetings survive. They do not look useless while they are happening. They look like work. The calendar fills, participation rises, and the organization creates a visible response to every ambiguity except ownership.

Meetings are not inherently wasteful. They are one of the ways groups make decisions, resolve disagreement, generate ideas, share context, and allow people to be heard. The problem begins when an organization uses a meeting for work that requires none of those things, or uses one to avoid naming the person who will decide what happens next.

An email is not automatically better. A concise written brief, shared document, recorded update, or dashboard may be better still. The real choice is not meetings versus email. It is interaction versus information.

If people need to affect one another's thinking in real time, meet. If they need to receive, consider, or refer back to information, write it down. If a decision needs an owner, name one before the invitation goes out.

What the evidence says

30 years of meeting research shows that meetings can be stressors, communication tools, platforms for voice and inclusion, stages for power, and expressions of culture. "Meetings are bad" is not a scientific conclusion.

2 studies of 676 and 304 employees found that meeting load related to wellbeing differently depending on task interdependence, meeting quality, and individual differences. Perceived effectiveness mattered strongly.

A 2025 field study of 199 employees found initial evidence of an inverted-U pattern: more meetings helped participation, engagement, and creative performance up to a point, then became a burden.

Microsoft reported that weekly meeting time for its average Teams user rose 252% between February 2020 and February 2022. That is platform data from an extraordinary pandemic period, not a timeless baseline for all work.

The useful target is not fewer meetings at any cost. It is fewer meetings without a purpose and better meetings where interaction is the work.

A meeting is the safest response to an unclear problem

When nobody knows who owns a problem, inviting everyone feels responsible.

The meeting distributes awareness. It also distributes the risk of being wrong. A person can leave saying the issue was discussed, stakeholders were consulted, and the group reached alignment. Whether anybody made a decision is a separate matter.

This pattern explains why ownership problems migrate to calendars.

A launch is slipping, so 14 people join a status call. A customer request crosses product, sales, and operations, so each function sends 2 representatives. A policy is unclear, so the organization schedules a recurring forum to interpret it case by case rather than asking someone to clarify the policy.

The meeting becomes a human patch over a missing decision right.

That patch may be necessary once. It becomes expensive when repeated. The same people reconstruct context, restate constraints, and negotiate temporary answers because the work between the boxes has no explicit owner.

Before scheduling, finish this sentence:

At the end of this meeting, we will have ________.

Good answers include a decision, a prioritized list, an approved plan, a resolved conflict, a tested idea, or shared understanding that genuinely requires conversation.

"Alignment," "visibility," and "a discussion" are not useless, but they are incomplete. Alignment about what? Visibility for whom? Discussion leading to which next state?

If the blank cannot be filled, the meeting has not yet earned other people's time.

Meetings have value because people can interact

A written update can transmit information. A meeting allows participants to change the information, question it, combine perspectives, observe hesitation, negotiate a trade-off, and make a joint commitment.

That difference is the case for meeting.

Steven Rogelberg, Liana Kreamer, and Jon Gray's 2026 review of 30 years of meeting science organizes the literature around 5 roles. Meetings can act as stressors and emotional events, communication technology that supports performance, platforms for employee voice and inclusion, stages where leadership and power operate, and expressions of organizational culture.

That is a more useful picture than the familiar claim that all meetings are broken. A difficult meeting may be valuable because it surfaces conflict that asynchronous comments would conceal. A recurring team meeting may build shared context that reduces dozens of later interruptions. A decision may improve when the affected expertise can challenge assumptions together.

The value depends on the work and the quality.

In a 2006 paper, Rogelberg and colleagues studied meeting demands and employee wellbeing in 2 internet surveys, one with 676 employees and another with 304. The relationships varied with task interdependence, meeting experience quality, accomplishment striving, the time frame studied, and the way meeting demand was measured. Perceived meeting effectiveness had a strong direct relationship with job attitudes and wellbeing.

In other words, an hour in a meeting is not a standard unit of harm. An hour resolving a real dependency is different from an hour listening to information that could have been read.

This distinction matters because a campaign against meetings can remove the useful ones and leave the operating problems that created the bad ones. People then recreate the conversation in chat, email, and a series of private calls, which is a meeting wearing several coats.

The cost belongs to the organization, not the invitation owner

Most companies make capital spending visible and organizational time nearly free.

A manager may need approval to spend $1,000. The same manager can invite 20 people to a weekly hour-long meeting with one click. The calendar records 20 hours of salary, plus preparation, switching, and follow-up, but no budget moves and no line item appears.

Michael Mankins, Chris Brahm, and Greg Caimi made this argument in Your Scarcest Resource. Based on time analytics across large organizations, they reported that meetings consumed roughly 15% of collective organizational time and that this share had been increasing. At one unnamed large company, they traced about 300,000 annual hours of preparation and downstream work to a weekly executive committee meeting.

The example is vivid, but it is one consultancy analysis at one unnamed company, not an average every organization should apply to itself. Its value is in showing multiplication. A 2-hour leadership meeting does not cost 2 hours. It costs the time of everyone present and the chain of preparation demanded from people who never enter the room.

Digital work made that multiplication easier to see. Microsoft's 2022 Work Trend Index combined a survey of 31,000 people across 31 countries with aggregated Microsoft 365 activity. Between February 2020 and February 2022, weekly meeting time for the average Teams user rose 252%, and the number of weekly meetings rose 153%.

Those figures span the pandemic shift to remote and hybrid work. Teams usage also changed dramatically, so the numbers should not be read as a general law of meeting growth. They do show what happens when the cost of assembling people approaches zero: organizations assemble them more often.

The invitation becomes easier. Attention does not become more abundant.

Too few meetings can also be a problem

The goal is not calendar asceticism.

A 2025 study by Alexander Romney, Joseph Allen, and Zahra Heydarifard examined what the authors call the meeting load paradox. In a field study of 199 full-time employees, meeting participation, engagement, and creative performance rose as meeting load increased, then declined after a threshold. The pattern was curvilinear, and virtual work and employee conscientiousness changed its shape.

This is initial evidence from 1 field study, not a universal optimum. It still captures an important truth. Meetings consume personal resources and enable organizational contribution at the same time.

A team that never meets may lose the ability to integrate work, resolve disagreement, learn from weak signals, and build relationships. Asynchronous tools are good at preserving information and allowing thought. They are less good at noticing that 2 people mean different things by the same sentence and resolving it before the disagreement becomes a month of work.

The best meeting culture is not the one with the smallest total. It is the one where each recurring meeting has a job, people can decline when they are not needed, and written information does not demand an audience.

Use the right medium for the work

A simple test separates most information work from interaction work.

Write it when the work is to inform

Use a written update, dashboard, short video, or shared document when people need to:

receive status;
review facts at their own pace;
refer back to a record;
comment independently;
absorb detailed context before deciding;
acknowledge a change that does not require negotiation.

Good asynchronous information has an owner, a date, a clear request, and a place for questions. Sending an unstructured essay to 40 people and asking for thoughts by Friday is not asynchronous design. It is a meeting without chairs.

Meet when interaction changes the outcome

Use a meeting when people need to:

make a consequential shared decision;
resolve a live conflict or trade-off;
combine expertise that cannot be integrated in sequence;
generate or critique ideas together;
handle emotionally or socially sensitive work;
build enough shared understanding for coordinated action.

The meeting invitation should say which of these applies. "Sync" is not a purpose. Neither is "touch base," a phrase that has survived mainly because it commits to nothing.

Combine the 2 for complex decisions

Some work benefits from writing first and meeting second.

Amazon's 2017 shareholder letter describes its use of narratively structured 6-page memos, read silently at the beginning of a meeting before discussion. This is an internal practice reported by the company, not a controlled finding that every organization should copy. Its logic is sound: writing forces the proposal to exist before the room's social dynamics begin, and shared reading gives participants common context.

The method also reveals an important point. "This should have been an email" does not mean important issues should be tossed into an inbox. It means information should be made legible before expensive interaction is used to change it.

Design the decision before the agenda

An agenda says what people will talk about. A decision design says how the organization will leave the room in a different state.

For any decision meeting, state:

The decision. Write the exact question, not a topic label.
The owner. Name the person with the final call.
The participants. Invite people whose knowledge or consent can change the decision.
The evidence. Share what must be read beforehand.
The constraints. Identify what is fixed and what remains open.
The method. Clarify whether the group decides, advises, or challenges.
The record. Write the decision, reasons, owner, and next action before people disperse.

This matters particularly in a matrix organization, where several leaders may have legitimate authority. A meeting cannot solve an authority conflict that its design refuses to acknowledge.

If the decision owner is absent, postpone the decision or delegate it explicitly. Do not spend an hour producing recommendations that will be privately reconsidered later by someone who heard none of the reasoning.

If no decision is required, describe the other outcome. A retrospective may exist to learn. A coaching conversation may exist to help someone think. A team forum may exist to surface weak signals. Not every useful meeting ends with a vote.

Every useful meeting does need a reason the people must be together.

Recurring meetings should have an expiry date

The most expensive meeting is often the one nobody would create today.

It began during a launch, a crisis, or a leadership change. The original problem ended. The invitation remained. New employees attend because everyone else attends, and the meeting gains legitimacy from its own age.

Give recurring meetings an owner and a review date. At review, ask:

What outcome has this meeting produced in the last month?
Which decisions or relationships depend on it?
Could the information move asynchronously?
Who attends without contributing or receiving necessary value?
Could the cadence, length, or participant list shrink?
What would break if it stopped for 4 weeks?

Canceling a meeting should not require proving it is harmful beyond doubt. Continuing it should require showing that it still does useful work.

Also make decline a safe option. In the HBR discussion of organizational time, Mankins argued that leaders need to make it acceptable for people to say they are not required for a decision. A culture that praises focus but punishes a declined invitation has made its real priority clear.

Put the ownership back into the work

An unproductive meeting is rarely fixed by a cleverer agenda alone.

Ask what the meeting is compensating for. Missing information? Publish it. An unclear decision? Name it. Too many authorities? Resolve the conflict. No owner? Assign one. A real need for interaction? Design the room around that need and invite only the people who can affect it.

Then make the result durable. Dependability improves when commitments are visible, work has named owners, and people do not have to reconstruct the same agreement next week.

The meeting that should have been an email is not really about email. It is about using 8 people's presence to avoid doing 1 person's thinking.

Write the information down. Save the room for the work only a room can do.