Not all meetings are created equal.

Some meetings are essential — complex decisions, difficult conversations, creative collaboration. You walk out having accomplished something that couldn’t have happened any other way.

And then there are the other meetings.

The ones where you sit quietly, wondering why you’re there. The ones that deliver information you could have read in two minutes. The ones that exist because someone defaulted to “let’s schedule a call” instead of thinking for thirty seconds about whether a call was actually needed.

These meetings aren’t just annoying. They’re expensive. Every unnecessary meeting costs your organization real money — and costs you something even more valuable: time you’ll never get back.

Here are 10 meeting types that almost never need to happen, along with what to do instead.

1. The Status Update Round-Robin

What it looks like:

Everyone goes around the room (or the Zoom grid) and shares what they’re working on. One by one. For 30 to 60 minutes. While everyone else half-listens, waiting for their turn to speak.

Why it doesn’t need to be a meeting:

• This isn’t collaboration. It’s a sequential monologue disguised as teamwork. Nobody is building on each other’s updates. Nobody is making decisions. Everyone is just… reporting.
• The information being shared is useful. The format is not.

What to do instead:

• Use a shared document, Slack channel, or project management tool for status updates. Everyone posts their update asynchronously. Team members read what’s relevant to them and skip the rest.
• If you need discussion on specific updates, schedule focused time for those topics only — don’t make everyone sit through eight updates to discuss one.

Time saved: 30-60 minutes per week, per team. Multiply that across your organization.

2. The FYI Announcement

What it looks like:

A meeting called to share information: a new policy, an organizational change, a project milestone, a leadership decision. One person talks. Everyone else listens. There’s a brief “any questions?” at the end. Nobody has questions — or if they do, they don’t want to ask in front of the group.

Why it doesn’t need to be a meeting:

• If information only flows one direction, it’s not a meeting. It’s a memo with a calendar invite.
• Announcements don’t require real-time attendance. People can read at their own pace, absorb the information, and follow up with questions individually if needed.

What to do instead:

• Write it down. Send an email. Post it in your team channel. Record a short video if you want to add a personal touch.
• Include a clear way for people to ask questions asynchronously — a shared doc for comments, a dedicated Slack thread, or simply “reply to this email with any questions.”

Bonus: Written announcements create a record. People can refer back to them. Meetings evaporate the moment they end.

3. The Document Read-Through

What it looks like:

Someone shares their screen and walks through a document — a proposal, a plan, a report, a deck — while everyone else reads along. Occasionally someone asks a clarifying question. Mostly, people just… read. Together. In real-time.

Why it doesn’t need to be a meeting:

• Reading is not a group activity.
• People read at different speeds. They focus on different sections. They need different amounts of time to process. Forcing everyone to read together, at the presenter’s pace, is inefficient for everyone.

What to do instead:

• Share the document in advance. Give people time to read it on their own — a day or two at minimum. Ask them to add comments or questions directly in the document.
• Then, if discussion is genuinely needed, schedule a shorter meeting focused only on the open questions. You’ll be surprised how often the comments resolve everything and no meeting is needed at all.

4. The Recurring Meeting With Nothing to Discuss

What it looks like:

It’s Tuesday at 10am, so you’re in the weekly sync. Not because there’s anything to sync on — but because the meeting exists. It’s been on the calendar for two years. Nobody remembers who created it or why. But it keeps happening.

Halfway through, someone says “well, I don’t have anything else” and everyone sits in awkward silence for a moment before someone finds something to fill the time.

Why it doesn’t need to be a meeting:

• Recurring meetings are calendar parasites. They made sense once — maybe — but they persist long after their purpose has expired.
• The worst part? They train people to expect meetings regardless of whether there’s anything to discuss. The meeting becomes the reason for the meeting.

What to do instead:

• Audit your recurring meetings quarterly. For each one, ask: if this meeting didn’t exist, would we create it today?
• If you need regular touchpoints, try a “cancel by default” approach: the meeting only happens if someone has a specific topic that requires discussion. No topic? No meeting. Everyone gets an hour back.

5. The “Quick Sync” That Isn’t Quick

What it looks like:

“Hey, can we do a quick sync?” So you find 30 minutes on both calendars (the minimum most tools allow), join the call, exchange pleasantries, slowly get to the point, realize the actual question takes 90 seconds to answer, and then fill the remaining time with small talk because ending a meeting after five minutes feels awkward.

Why it doesn’t need to be a meeting:

• Most “quick syncs” are simple questions dressed up as meetings. They happen because asking a question asynchronously feels slower — even when it’s not.
• The overhead of scheduling, joining, and conducting a meeting almost always exceeds the time it would take to just ask the question in writing.

What to do instead:

• Before scheduling, ask yourself: can I type this question in under 60 seconds? If yes, do that.
• Send a message. Write an email. You’ll probably get an answer faster than you would have gotten a meeting scheduled — and neither of you will waste 25 minutes of dead time around a 5-minute conversation.
• If a real-time conversation is truly necessary, try an impromptu call instead of a scheduled meeting. “Got 5 minutes now?” respects everyone’s time more than a calendar hold.

6. The Meeting to Schedule a Meeting

What it looks like:

A meeting has been called to discuss when to have another meeting. Or to figure out who should be in a future meeting. Or to align on what the agenda for a future meeting should be. The actual meeting — the one where something might get decided — is still in the future. This meeting is just about that meeting.

Why it doesn’t need to be a meeting:

• Meetings about meetings are a symptom of a broken process. If you need a meeting to figure out how to have a meeting, something has gone wrong.

What to do instead:

• Use a scheduling tool like Calendly or When2meet to find availability. Draft the agenda yourself and share it for feedback asynchronously. Decide the attendee list based on who actually needs to be involved — which you can figure out by thinking about it, not by holding a meeting.
• If you’re genuinely unsure who should attend or what the agenda should be, ask the question in writing. “I’m thinking of scheduling a meeting about X. Who should be there and what should we cover?” People can reply. No meeting required.

7. The Presentation That Could Be a PDF

What it looks like:

Someone spends days preparing a polished slide deck. They gather an audience. They share their screen. And then they proceed to read the slides — word for word — while everyone watches and waits for it to end.

No discussion. No decisions. Just a performance of information transfer that would have been more efficient as a document.

Why it doesn’t need to be a meeting:

• Presentations are often just documents with extra steps. The value of a presentation is supposed to be the human element — the ability to explain nuance, answer questions, respond to the room. If none of that is happening, you’re just reading aloud.

What to do instead:

• If the information is the point, send a document. A well-written memo or report communicates more effectively than most decks anyway.
• If you do need to present — maybe to stakeholders, maybe to provide context that’s hard to write — record yourself walking through the deck and share the video. People can watch at 1.5x speed on their own time. Questions can be collected and answered in a follow-up.
• Save the live meeting for actual discussion, after people have already absorbed the content.

8. The “Let’s Get Aligned” Meeting

What it looks like:

The calendar invite says “Alignment Session” or “Sync on Priorities” or “Get on the Same Page.” The description is vague or nonexistent. The attendee list is broad. And when the meeting starts, nobody is quite sure what alignment means or how you’ll know when you’ve achieved it.

Ninety minutes later, you leave feeling like something happened — but unable to articulate what.

Why it doesn’t need to be a meeting:

• “Alignment” is not an outcome. It’s a feeling. And feelings don’t require calendar holds.
• These meetings usually happen because someone sensed that people weren’t on the same page, but didn’t do the work to figure out specifically what needed to be resolved. The meeting becomes a substitute for that thinking.

What to do instead:

• Before scheduling, identify what’s actually misaligned. Is it priorities? Resource allocation? Understanding of the strategy? A specific decision?
• Name the specific gap. Then address it directly — often in writing. “I think we’re misaligned on X. Here’s how I see it: [explanation]. Does this match your understanding?”
• If real-time conversation is needed, make it focused: “We need to decide whether A or B. Let’s discuss for 30 minutes and walk out with an answer.”

9. The Information Request Meeting

What it looks like:

Someone has questions. Instead of typing those questions and sending them, they schedule a meeting. You show up not knowing what they want. They ask questions you could have answered in an email. You answer them. The meeting ends. Thirty minutes gone.

Why it doesn’t need to be a meeting:

• Questions are not meetings. Unless the question is genuinely complex, requires back-and-forth discussion, or touches on sensitive topics, there’s no reason to schedule time for it.

What to do instead:

• Write down your questions. Send them. Wait for answers.
• This is not just more efficient — it often produces better answers. When someone can take time to think, check their work, or consult with others before responding, the response is usually more accurate and complete than whatever they’d say on the spot in a meeting.
• If you’re on the receiving end of these meeting requests, try responding with: “Happy to help — can you send me your questions in advance? I might be able to answer them in email, but if not, we can schedule time to discuss.”

10. The Post-Meeting Debrief

What it looks like:

You just finished a meeting. Now there’s another meeting to discuss what happened in the first meeting. Maybe it’s a retro on a project meeting. Maybe it’s a sidebar to discuss how the client call went. Maybe it’s three of you staying on the call to talk about what the other four people said.

Meeting about meeting. It’s meetings all the way down.

Why it doesn’t need to be a meeting:

• If the first meeting required a second meeting to process it, the first meeting didn’t accomplish its purpose.
• Debriefs can be valuable — but they’re often just an excuse to say things people were unwilling to say in the original meeting, or to clarify things that should have been clarified in real-time.

What to do instead:

• End the original meeting with clarity. State decisions, action items, and owners before anyone leaves. Send notes immediately afterward.
• If a debrief is genuinely needed — after a big presentation, a client interaction, or a high-stakes conversation — try doing it asynchronously first. “What went well? What could improve? Any follow-ups?” People can respond in a shared doc. You may find a meeting isn’t necessary.
• Reserve live debriefs for situations where tone and nuance matter — difficult conversations, sensitive dynamics, or complex situations where written communication might be misread.

The Common Thread

Look at these 10 meeting types. Notice what they have in common:

• One-way information flow. Most could be replaced by writing.
• No clear decision. Vague purpose leads to vague outcomes.
• Default to synchronous. Real-time communication is expensive and often unnecessary.
• No one questioning the meeting’s existence. The meeting happens because it was scheduled, not because it was needed.

The solution isn’t to eliminate all meetings. It’s to be intentional about which meetings actually deserve to exist — and to give yourself permission to do something else instead.

What If You Can’t Stop the Meetings?

Maybe you’re not the one scheduling these meetings. Maybe you’re just the one attending them. Stuck in someone else’s status update. Trapped in another alignment session. Wondering if anyone else sees the absurdity.

You do. And so does everyone else in the room.

The problem is that nobody says anything. Meeting organizers never get honest feedback. They see full attendance and assume everything’s fine. The bad meetings continue, week after week, because silence is interpreted as approval. What if it wasn’t?

Could Have Been an Email lets any meeting attendee submit a meeting for anonymous feedback. Every attendee gets surveyed. Every attendee — including the organizer — sees the results. No individual responses. No identifying information. Just aggregate data showing how the group really felt.

It won’t fix every meeting overnight. But it creates something that didn’t exist before: a feedback loop. When meeting organizers see the data, they have a reason to change. The meetings that don’t need to happen start disappearing. And you didn’t have to say a word.

Quick Reference: Meetings That Should Be Emails