The Meeting Is Not the Work

There is a strange thing happening at a lot of companies.

Everyone is busy.

Calendars are packed. Slack is active. Teams are jumping from one call to another. There are weekly standups, project check-ins, leadership syncs, stakeholder reviews, planning sessions and meetings that somehow appear on the calendar without anyone remembering who created them.

And yet, important things still don't get done.

That's the part I find interesting.

We tend to treat meetings as evidence of work. If everyone is talking, collaborating and attending calls, surely progress must be happening somewhere.

But a meeting is not the work.

The meeting is supposed to help the work happen.

There is a big difference.

A Full Calendar Can Be a Warning Sign

I've always thought there was something misleading about a completely packed calendar.

It looks productive.

You can finish a day having attended eight meetings and feel like you accomplished a lot.

Then you look at the actual work.

The decision wasn't made.

The analysis wasn't finished.

The customer issue is still open.

The project is still waiting for approval.

And tomorrow's calendar is already full.

This isn't just a feeling. Microsoft's Work Trend Index found that 68% of people surveyed didn't have enough uninterrupted focus time during the workday. It also found that inefficient meetings were reported as the number one productivity disruptor, with having too many meetings ranking third.

Microsoft Work Trend Index research

The problem isn't that meetings exist.

The problem is when meetings start consuming the time people need to actually do the job.

And that can happen surprisingly easily.

Need an update?

Schedule a meeting.

Need alignment?

Schedule a meeting.

Need someone to make a decision?

Schedule a meeting.

Not sure who's responsible?

Schedule a meeting.

Eventually, the company isn't managing the work.

It's managing the calendar.

The Meeting Usually Isn't the Real Problem

This is where I think the conversation about meetings often goes wrong.

We hear advice like:

"Have fewer meetings."

"Make meetings shorter."

"Don't schedule meetings on Fridays."

"Decline unnecessary invitations."

Fine.

Those things might help.

But they don't address why the meetings exist in the first place.

A recurring meeting might exist because nobody clearly owns a decision.

Another might exist because the process is unclear.

Another might exist because leadership keeps changing priorities.

Another might exist because nobody trusts the information they're getting.

And another might exist because a team has no easy way to see what's happening without asking everyone individually.

In other words, the meeting may just be where the organizational problem becomes visible.

That's why I keep coming back to governance. In Governance Is the Hidden Operating System of Growth, I wrote about how organizations need clarity around who makes decisions, who owns outcomes and how accountability actually works.

Meetings are where that clarity gets tested.

If nobody knows who gets the final say, the meeting will probably drag on.

If everyone has a vote, the meeting may turn into consensus theater.

If nobody owns the next step, the same topic will return next week.

Not Every Meeting Is Bad

This is where I don't want to fall into the easy "meetings are terrible" argument.

Some meetings are extremely useful.

If a decision is complicated, the right people may genuinely need to sit down together.

If you're solving a messy problem, a working session can be far more effective than sending 14 emails back and forth.

If a team is dealing with a major change, alignment matters.

The goal isn't to eliminate meetings.

It's to make meetings earn their place on the calendar.

Harvard Business Review has highlighted the same problem from another angle. Its research notes that many employees find meetings ineffective, inefficient or unproductive, even though organizations continue to hold enormous numbers of them.

Harvard Business Review: How to Improve a Meeting

That distinction matters.

A good meeting can accelerate work.

A bad meeting can simply move the work to tomorrow.

Three Meetings Worth Keeping

I'd roughly put useful meetings into three categories.

1. Decision meetings

Something actually needs to be decided.

Should we launch?

Which vendor should we choose?

Do we change the process?

Do we invest in this project?

These meetings need the people who can make the decision, plus the people whose input genuinely matters.

They don't need everyone who happens to be interested.

And they should end with a decision whenever the available information is good enough to make one.

"Let's discuss this again next week" should not be the automatic outcome.

2. Working sessions

This is where the work is actually happening.

A team is mapping a process, solving a customer problem, designing something, working through requirements or figuring out how to untangle a complicated issue.

That's a legitimate meeting.

The test is simple:

Are we doing something together, or are we just talking about doing something?

Those are very different things.

3. Alignment meetings

Sometimes people genuinely need to get on the same page.

A major organizational change isn't always going to fit neatly into a dashboard.

People need context. They need to understand why something is changing. They need an opportunity to ask questions.

That's real work too.

But call it alignment.

Don't disguise it as a status meeting with 15 people reading bullet points from a slide deck.

The Meeting After the Meeting Is the Red Flag

There is one meeting pattern that should make every manager nervous.

The meeting ends.

Everyone leaves.

Then two people stay behind and say:

"Okay, what are we actually doing?"

That conversation is often more productive than the meeting itself.

Why?

Because now the people involved are finally talking about the actual problem.

Maybe the decision wasn't clear.

Maybe nobody owns the next step.

Maybe there were too many people involved.

Maybe everyone was afraid to challenge the prevailing opinion.

Maybe the meeting was designed around sharing information rather than making progress.

Atlassian's research found that 77% of surveyed knowledge workers frequently attend meetings that end with a decision to schedule another meeting. Even more striking, 54% said they frequently leave meetings without a clear idea of the next steps or who owns which task.

Atlassian's meeting research

That's not really a meeting problem.

That's an execution problem.

Sometimes the Best Meeting Fix Is a Process Fix

This is where meetings connect to something much bigger.

Imagine a team has a recurring Monday meeting to discuss customer issues.

Every week, they review:

What happened?

Why did it happen?

Who's looking into it?

What should we do?

When will it be fixed?

After six months, they're still having the same conversation.

At some point, the problem isn't communication.

It's the process.

Maybe customer issues aren't being categorized properly.

Maybe ownership isn't clear.

Maybe there is no escalation path.

Maybe recurring problems aren't being tracked.

Maybe the team has the information but no mechanism for turning it into action.

That's why I wrote Process Mapping Methodologies That Actually Drive Operational Clarity.

Sometimes the best way to improve a meeting is to fix whatever keeps forcing you to have it.

Try This Before Your Next Recurring Meeting

Before keeping or creating a recurring meeting, ask five questions.

What is this meeting supposed to accomplish?

Not "what do we normally discuss?"

What should actually happen?

Why do these people need to be together at the same time?

Could a dashboard, document or short update accomplish the same thing?

What decision or outcome should come out of this?

If there isn't one, question whether the meeting needs to exist.

Who actually needs to be there?

"Just in case" is not a good reason to invite someone.

What happens if we stop having it?

This is probably my favorite question.

If the honest answer is "not much," you've learned something.

Your Calendar Is an Operating-System Diagnostic

One of the more interesting ways to look at meetings is to stop treating them as a calendar problem.

Look at them as a diagnostic.

If a team spends hours every week reviewing the same status information, maybe the information isn't accessible enough.

If decisions constantly get escalated, maybe decision rights aren't clear.

If the same problems come up every week, maybe the underlying process hasn't been fixed.

If priorities change every meeting, maybe the company has a strategy problem.

If everyone is invited to everything, maybe nobody has figured out who actually needs to be involved.

Your calendar won't tell you everything about how a company works.

But it can reveal a lot.

And that's why simply telling people to "be more productive" can miss the point.

Sometimes the individual isn't the problem.

The system is.

Stop Measuring Productivity by How Busy Everyone Looks

This is probably the biggest shift I'd like to see.

We shouldn't judge productivity by how many meetings someone attends, how quickly they respond to Slack, or how full their calendar looks.

Those are signals of activity.

They aren't necessarily signals of progress.

Progress is a decision made.

A customer problem solved.

A product shipped.

A process improved.

A project moved forward.

A risk removed.

A result delivered.

Meetings should help those things happen.

They shouldn't become the thing the organization gets really good at doing instead.

This is also why operational discipline matters more than simply asking people to work harder. As I wrote in 2026 Isn't About Hustle. It's About Operational Survival, organizations get into trouble when effort becomes a substitute for fixing how work actually gets done.

The answer isn't necessarily fewer meetings.

It's better-designed work.

The next time you look at your calendar and wonder where the day went, don't automatically conclude that you need to become more efficient.

Ask a harder question:

Why does this work require so much coordination in the first place?

You might discover that the problem isn't your calendar.

It's the way the company works.

The meeting is not the work.

The decision is.

The execution is.

The customer outcome is.

The problem solved is.

The result delivered is.

A good meeting gets you there faster.

A bad one just gives you another meeting for next week.

📚Further Reading

1. Microsoft Work Trend Index
   Research on digital overload, focus time and meeting-related productivity problems.

2. Harvard Business Review: Dear Manager, You're Holding Too Many Meetings
   A look at the organizational cost of excessive meetings.

3. Atlassian: Workplace Woes, Meetings
   Research into why meetings often fail to produce the outcomes teams expect.

4. Atlassian: How to Run Effective Meetings
   Practical guidance on decisions, ownership and meeting outcomes.

5. Microsoft: Breaking Down the Infinite Workday
   Research into how meetings, messages and notifications fragment attention.

6. Atlassian: Page-Led Meetings
   A practical framework for using written context to make meetings more focused and decision-oriented.

TL;DR

• A packed calendar can create the illusion that a team is making progress.

• Many meeting problems are actually problems with ownership, priorities, decisions, or processes.

• The answer isn't necessarily fewer meetings. It's better reasons to meet.

• A good meeting should produce a decision, solve a problem, create alignment, or move work forward.

• If your team keeps scheduling another meeting to figure out what happened in the last one, something deeper is broken.

© 2025. All rights reserved.

Quick Links

Home
Blog
About
Contact

Connect with Alexander Pau