The Meeting That Wasn't

This post contains affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you.

You sit down. Open your laptop. Join the Zoom call.

Fifteen people on the screen. Nobody's sure why they're there.

Someone shares their screen. Reads slides aloud. You could have read this in two minutes.

Thirty minutes later, nothing has been decided. No one has been assigned anything. The meeting ends with "Let's circle back on this."

You just attended a meeting that wasn't really a meeting.

What Actually Qualifies as a Meeting

A real meeting has three characteristics:

1. A decision needs to be made.

Not information shared. Not updates given. A decision. Something that requires input from multiple people and can't be made asynchronously.

2. The smallest possible group is present.

If someone doesn't need to contribute to the decision, they shouldn't be there. Meetings aren't for information distribution—that's what email is for.

3. There's a clear outcome.

By the end, something concrete happens: a decision is made, a plan is agreed upon, responsibilities are assigned.

If your meeting doesn't have all three, it's not a meeting. It's a different communication format masquerading as one.

The Four Fake Meetings

Here are the most common imposters:

1. The Status Update

What it looks like: Everyone goes around and shares what they're working on. Ten people spend an hour listening to updates that don't affect them.

What it should be: A written update sent via email or Slack. People read it on their own time. If questions arise, handle them asynchronously or in a quick one-on-one.

The cost: Ten people × one hour = ten hours of productivity lost. To share information that could have been read in five minutes.

2. The Information Broadcast

What it looks like: One person presents slides while everyone else sits silently. Questions are saved for the end (and usually aren't answered).

What it should be: A recorded video or a well-written document. People consume it when it fits their schedule. Comments and questions are added asynchronously.

The cost: You're burning everyone's time to deliver information in the least efficient format possible.

3. The Consensus Theater

What it looks like: The decision has already been made, but the meeting is held to create the illusion of input. People share opinions. Nothing changes. The predetermined outcome is announced.

What it should be: Honesty. If the decision is made, just announce it. Don't waste people's time pretending their input matters.

The cost: Trust. People see through this. And once they know their input is performative, they stop giving it.

4. The Social Gathering

What it looks like: No agenda. No clear purpose. "Let's touch base" or "Let's sync up." The meeting meanders through topics until time runs out.

What it should be: Either a real meeting with a clear purpose, or an optional coffee chat labeled as such.

The cost: People leave feeling like their time was wasted. Because it was.

The Real Cost of Fake Meetings

Let's do the math.

A one-hour meeting with eight people costs eight hours of collective time. If those people make an average of $50/hour, that's $400.

If the meeting could have been an email? You just burned $400 for no reason.

But the real cost isn't money. It's momentum.

Meetings fragment your day. You can't start deep work if you have a meeting in 90 minutes. So you do shallow tasks. Check email. Browse. Wait.

A single unnecessary meeting doesn't just cost one hour. It costs the two hours before it (because you can't focus) and the hour after it (because you need to context-switch back).

One fake meeting can destroy an entire day.

How to Kill a Fake Meeting

Here's the rule: If it can be async, make it async.

Before scheduling a meeting, ask:

1. Can this be a document?

If you're sharing information, write it down. Send it. Let people read and respond on their own time.

2. Can this be a decision made by one person?

Most decisions don't need consensus. They need a decision-maker with enough context. Empower that person to decide and move on.

3. Can this be handled in writing?

Email, Slack, a shared doc with comments—these tools exist for a reason. Use them.

4. Can this wait until the next scheduled check-in?

If you already have a weekly meeting, batch topics. Don't create a new meeting for every question.

If the answer to all four is "no," then—and only then—schedule a meeting.

What a Real Meeting Looks Like

A real meeting is short, focused, and decisive.

Before the meeting:

- A document is shared with the decision to be made and relevant context. - Attendees read it and add questions/input asynchronously. - Only people who need to be part of the decision are invited.

During the meeting:

- No slides. No reading aloud. Everyone has already read the document. - Discussion focuses on unresolved questions. - A decision is made. - Action items are assigned with clear owners and deadlines.

After the meeting:

- A summary is posted: decision made, action items, owners. - People get back to work.

Total time: 15-30 minutes.

The "But We Need to Collaborate" Objection

I know what you're thinking: "But meetings are how we collaborate!"

No. Meetings are where you finalize collaboration.

Real collaboration happens in documents, in Slack threads, in shared workspaces. You iterate asynchronously. You refine. You build.

Then—when you hit a decision point that requires real-time input—you meet.

But by the time you're in the meeting, most of the work is already done.

The Culture Shift

Here's the hard truth: most organizations are addicted to meetings.

Meetings feel productive. They create the illusion of progress. You talked about the problem! You must have solved it!

But talking isn't solving. And gathering isn't collaborating.

If you want to fix this, you need to change the culture:

1. Default to async.

Make synchronous meetings the exception, not the default. When someone proposes a meeting, ask: "Can this be a doc?"

2. Require pre-work.

No meeting happens without a shared document sent at least 24 hours in advance. If people can't read it before the meeting, they shouldn't attend.

3. Empower decision-makers.

Stop requiring consensus. Identify who owns the decision and let them make it. Input is fine. But one person decides.

4. Time-box ruthlessly.

Meetings expand to fill the time allotted. Default to 15 minutes. If it takes longer, schedule a follow-up.

5. Make declining optional.

If someone gets invited to a meeting they don't need to attend, they should be able to decline without penalty. No guilt. No justification required.

The Meeting Audit

Here's an exercise: for one week, track every meeting you attend.

For each one, ask:

- Was a decision made? - Did the meeting require real-time discussion? - Could this have been async? - Was I necessary, or just present?

I'd bet that 70% of your meetings fail at least two of these tests.

Now imagine reclaiming that time.

What You Get Back

When you kill fake meetings, you get back three things:

1. Focus.

No more fragmented days. No more waiting for meetings. You can do deep work for hours at a time.

2. Momentum.

Decisions happen faster. You're not waiting for everyone's calendars to align. Work moves forward.

3. Respect.

Your team stops feeling like their time is disposable. Morale improves. Productivity follows.

The One Meeting Worth Having

There is one meeting I'll defend: the weekly team sync.

But only if it's done right:

- 30 minutes, max. - Pre-work required (written updates sent in advance). - Agenda: blockers, decisions, and quick questions only. - No status updates. No presentations.

This meeting exists to unstick things and align on priorities. That's it.

Everything else? Async.

The Courage to Decline

Here's the final truth: killing fake meetings requires courage.

Because declining a meeting—or suggesting it should be a doc instead—feels uncomfortable. You worry about being seen as difficult. Uncooperative. Not a team player.

But here's what actually happens:

You decline a meeting. You explain why (and offer an alternative). People realize you're right. Others start doing the same.

And slowly, the culture shifts.

Because the people who respect your time? They also resent having theirs wasted.

You're not being difficult. You're being honest about what actually creates value.

And that honesty is what good teams are built on.

The Meeting That Should Have Been an Email

Most meetings shouldn't exist.

The ones that do should be short, focused, and decisive.

Everything else? Kill it.

Your team will thank you. Your calendar will thank you. And your work—the actual work—will finally get done.

Because you're not spending all day in meetings that weren't really meetings.