Should This Be a Meeting or an Email?

Should This Be a Meeting or an Email?

Sarah is a VP of Marketing at a mid-sized technology company. She is sharp, strategic, and by every measure, effective at her job.

She is also in seven meetings before lunch on Monday.

By Wednesday afternoon, she had sat through fourteen more. She hasn't written a single strategic document in three weeks. Her best thinking happens in cabs, on early mornings before the calendar kicks in, and on weekends when no one can reach her. She is not disorganized. She is not a poor performer. Sarah is buried. Most of what is burying her didn't need to be a meeting.

This is not a time management problem. It is a communication problem. And it starts with a question most leaders never stop to ask before hitting send on a calendar invite: Does this actually need to be a meeting?

 

Why This Question Matters More Than You Think

Every meeting has a price tag, and most leaders underestimate it.

A one-hour meeting with eight people is not a one-hour cost. It is an eight-hour cost plus the context-switching tax on either side of it, the prep time, the follow-up, and the deep work that got displaced to make room for it. Multiply that across a week, and the number gets uncomfortable quickly.

The downstream effect is just as costly. When meetings happen too often or for the wrong reasons, leaders stop preparing for them. They start multitasking through them. They show up physically but check out mentally. Meetings begin to lose their weight. When a meeting actually matters, the room doesn't know it yet because every meeting has been treated the same way.

The goal is not to eliminate meetings. The goal is to protect them for what only meetings can do, and to redirect everything else to a format that serves them better.

 

The Simple Decision Filter

Before you schedule anything, start with one question: What is the clear goal of this interaction?

Most interactions fall into one of three buckets: Inform, Align, and Decide.

 

The first is Inform. You have an update, a result, or a piece of context that someone needs to know. They don't need to respond in real time. They don't need to be in the room. They need the information. This is almost always an email or, if more complex, a video recording.

 

The second is Align. You need to get people on the same page about a direction, a priority, or a change. This may warrant a meeting, depending on complexity and the stakes involved. But it may also be handled asynchronously if the alignment is straightforward.

 

The third is to Decide. You need to make a call that requires live input, debate, or commitment from multiple people. This is what meetings are for. This is where the investment of everyone's time is justified.

 

If you cannot clearly name which bucket you are in before you schedule, you are not ready to schedule yet.

 

Another important filter: do all the people you are about to invite need to be present to achieve the goal, or do some of them need to be informed afterward? These are two different groups, and mixing them is one of the most common and most fixable sources of calendar bloat.

 

When It Should Be an Email

If the purpose of your interaction is to share an update, a result, or a piece of context, send an email.

If all you are doing is sharing numbers, a status, or a progress report - send an email with a summary and the data attached. This type of meeting happens every week (or day) in organizations everywhere, and it seldom needs to.

A well-written email does not need to be long. It needs to be clear. Lead with a subject line that signals the purpose. Open with a one to two-sentence summary so the reader immediately knows why they are reading. Present the key information in a format that is easy to scan, such as bullet points. Close with a clear next step or ask if one exists. If there is no ask, say so. "No action needed. Sharing for your awareness" is a complete and useful email.

For updates that are more complex than text can carry cleanly, use Loom. Loom is an async video tool that lets you walk through a document, a deck, or a screen while narrating. It captures nuance and tone without requiring everyone to be in the same room at the same time. A five-minute Loom that walks through a strategic recommendation will land more clearly than a forty-five minute meeting where half the room hasn't read the pre-read.

 

A few Loom best practices worth building into your workflow:

• • Keep the recording under five minutes wherever possible
  • State the purpose in the first thirty seconds so the viewer knows immediately what they are watching and why
  • Share it with a brief written summary so people have context before they hit play

 

When It Should Be a Meeting

Meetings should be focused on decisions and action. That is their highest and best use.

A meeting is warranted when a decision requires live debate and input from multiple stakeholders. When a complex or sensitive conversation needs real-time back and forth. When alignment requires the kind of human connection that async communication cannot replicate. When a team needs to commit together to a plan and its owners.

Before you schedule, the Jeff Bezos pizza rule is worth keeping close: if you cannot feed everyone in the room with two pizzas, the meeting is too big. More people mean more complexity, less accountability, and slower decisions. Trim the list to the people who actually need to be there to make the decision. Everyone else can be informed after.

A meeting should not happen without an agenda set, shared in advance, and agreed to by the people attending. No agenda means no shared understanding of what the meeting is for, which means the meeting will either drift or default to whoever talks the most. If you cannot articulate the agenda, the meeting is not ready to be scheduled.

 

Three questions worth asking before anything goes on the calendar:

1. 1. What is the clear goal of this meeting?
   2. What decision needs to be made by the end of it?
   3. Does everyone invited need to be present to make that decision, or do some of them just need to be informed afterward?

 

Three Scenarios: The Wrong Call and the Right Call 

 

Scenario 1: The Status Update Meeting

The wrong call: A team lead schedules a weekly sixty-minute all-hands to share project updates. Half the attendees are listening to updates that have no bearing on their work. The other half are multitasking. Nothing gets decided. The meeting ends, and everyone goes back to their desks slightly more behind than when they arrived.

What it cost: Eight people. One hour. Every week. No decisions are made, no problems are solved, and deep work is interrupted across the entire team regularly.

The right call: Updates move to a shared async document or a brief Loom sent Monday morning. The weekly meeting gets redesigned as a thirty-minute decision and blocker session only. The agenda is set in advance. Attendance gets trimmed to the people who make decisions.

How it ran: The meeting got shorter and sharper. People started showing up prepared because the meeting was actually for something. The team became better informed, not worse, because the async updates were clearer than the verbal ones ever were.

 

Scenario 2: The Reply-All Email Chain

The wrong call: A leader sends a complex strategic question over email to a group of twelve. Twelve reply-alls later, three competing positions have emerged, no decision has been made, and two of the responses have a tone that suggests the thread has created more tension than it resolved.

What it cost: Time, clarity, and the goodwill of everyone who was copied on a conversation that went nowhere productive.

The right call: She recognizes early that this is a decision requiring live debate, not a question that email can resolve. She schedules a focused thirty-minute meeting with the three people whose input actually matters, shares the relevant context 24 hours in advance, and walks in with a proposed decision for the group to pressure-test.

How it ran: The decision was made in a single conversation. Everyone else was informed via a clean follow-up email summarizing the outcome and the rationale. Total time investment was a fraction of what the email chain consumed, and the decision actually held.

 

Scenario 3: The Overcrowded Decision Meeting

The wrong call: A director invites eleven people to a product decision meeting. Four of them are present for one agenda item that surfaces at the forty-five-minute mark. Everyone sits through everything. The meeting ran over. The four people who were needed for one section spent the better part of an hour waiting for it.

What it cost: Collective frustration, eleven people's time, and a decision that took twice as long as it needed to because the room was too full to move quickly.

The right call: She maps the agenda in advance and identifies which attendees are needed for which sections. The four people required for the one agenda item are scheduled for the first twenty minutes, cover their section, and leave. The remaining group handles the rest of the meeting without the overhead of a room that is too large.

How it ran: The meeting ran tighter and faster. The four people who left early appreciated being respected enough not to sit through an hour they had no stake in. The decision was made with the right people in the room at the right time.

 

Meeting Hygiene Best Practices –  Meeting Hygiene Best Practices (downloaded document)

Once you have decided a meeting is the right call, how you run it matters as much as the decision to have it.

Set and share the agenda at least 24 hours in advance. No agenda, no meeting. This is a standard worth holding firmly. An agenda tells people what the meeting is for, what decisions need to be made, and how to come prepared.

State the goal at the top. Open every meeting by naming what needs to be decided or aligned on by the end. This gives the conversation a destination and makes it easier to pull back when it drifts.

Assign a facilitator and a notetaker at the start. The facilitator keeps the conversation moving and on track. The notetaker captures decisions and next steps so nothing gets lost in the debrief.

Schedule partial attendees at the front of the agenda. If someone only needs to be present for one section, put that section first. Let them contribute and get back to their work. Their time is not a holding cost for the rest of the meeting.

Start on time and end on time. Both signal respect for the people in the room. A leader who starts late trains their team that the start time is a suggestion. A meeting that runs over signals that the agenda wasn't realistic or the conversation wasn't managed.

Close with documented next steps. Every meeting should end with clear owners, clear tasks, and specific deadlines. If the meeting produced no next steps, ask whether it needed to happen at all. A follow-up summary should go out within 24 hours to everyone present and anyone who needs to be informed of the outcome.

Build in a mid-meeting pause. At the halfway point of any meeting, stop and ask the room: "Are we on track to hit our goal by the end of this?" It takes thirty seconds, and it does two things:

1. 1. It surfaces drift before the meeting runs out of time to correct it
   2. It signals to the team that the goal of the meeting is a shared responsibility, not just the facilitator's problem to manage.

Give every meeting a shelf life. Meetings should start and end with a project or have a defined trial period before becoming a permanent calendar fixture. Run a new recurring meeting for four to six weeks, then ask honestly: Did this serve us? The best leaders treat recurring meetings like contracts that require renewal, not defaults that run until someone is brave enough to cancel them.

Close with a 1-10 score. Before the room clears, ask everyone to rate the meeting on a scale of one to ten. No lengthy explanation needed - just a pulse check. Track the scores over a few sessions and then open a conversation: "We've been averaging a six. What would need to change to make this seven?" Small, specific improvements compound quickly. And asking the question at all signals that the meeting exists to serve the team, not the other way around.

 

Back to Sarah

Three months later, Sarah runs an audit on her calendar - something she wishes she had done the moment things started feeling unmanageable.

She identifies four recurring meetings that have been on the books for over a year. None of them has a clear decision to make. All four get cancelled and replaced with a weekly async Loom update that takes her ten minutes to record and her team five minutes to watch.

She redesigns two others. One becomes a decision-only thirty-minute session with a standing agenda shared every Friday for the following Monday. The other gets cut from sixty minutes to thirty after she realizes the back half of the meeting has never produced a single action item.

She now has three protected blocks of deep work on her calendar each week. Her team is better informed than before. Her strategic documents are getting written again.

The irony is that the people who report to her feel more in the loop now than they did when she was meeting with them constantly. Because a clear Loom and a well-written email, it turns out, communicate more than a meeting where everyone is half-present, and nothing is decided. Unlike a meeting, an email, or Loom doesn't disappear when the call ends. A teammate who gets stuck or needs a reminder can go back and reference it exactly when they need it.

The best leaders do not just manage their calendars. They protect them. And the first line of defense is a simple question, asked before anything gets scheduled:

Does this need to be a meeting?

 

How can we help? 

Fixing a meeting culture doesn't happen by accident. It requires a leader willing to audit what's on the calendar, make deliberate decisions about how the team communicates, and hold the standard when old habits creep back in.

Our Executive Performance Coaches work with leaders at every level to build the communication habits and operating rhythms that protect time, improve decisions, and give people their deep work back. Why? So your team can drive your enterprise forward.

If your team is buried in meetings that should be emails, or sending emails that should be decisions, we can help. Reach out through our contact form, and we’ll share our 20-Minute Executive Standup Meeting Template as a structured resource you can use on your team immediately.