Guides · Guide
What Causes Too Many Meetings
Published
Nobody sets out to fill a calendar with meetings. Most people say they want fewer. And yet the meetings keep coming.
That is a sign the cause is structural. Meetings multiply because of how organizations coordinate, how calendars work, and how people protect themselves, not because anyone enjoys them. If you want fewer meetings, it helps to know which forces are adding them.
Here are the six that show up most often, and what you can do about each.
Meetings are the default coordination tool
When a team needs to get several people aligned on something, it needs a way to do that. If there is no agreed alternative, a meeting is what people reach for. Everyone knows how it works, it feels productive, and it guarantees that the people involved are paying attention at the same time.
Defaults spread. One team holds a weekly sync, and the team next to it starts one too. A new manager inherits a calendar full of recurring meetings and assumes that is how things are done here. Within a year, a meeting is the standard response to almost any coordination problem.
What you can change: give people a second default. If there is a known, trusted way to gather input and make a decision in writing, people will use it for the cases where it fits. Without one, the meeting wins every time.
Scheduling is free for the scheduler
The person who sends a meeting invite pays for one hour of their own time. Everyone else pays too, but invisibly.
Calendar tools make this worse. Adding a person to an invite costs nothing at the moment of booking. There is no prompt that says “this adds another hour of someone else’s week.” So invites grow. People get added just in case, to be safe, or to keep them in the loop.
The result is that meetings are priced wrong. The person deciding whether to hold a meeting sees a fraction of its cost.
What you can change: make the cost visible. Some teams ask the organizer to write one sentence on why each person is invited. Others review recurring meetings with the full attendee list and an estimate of total hours. The goal is not bureaucracy. It is to put the real cost in front of the person making the call.
Fear of deciding in writing
A written decision feels permanent. It has a date and a name on it, and anyone can forward it.
A meeting diffuses that. If a decision was made in a room, it was made by the room. If it turns out to be wrong, nobody in particular made it.
So people call meetings to share the risk of decisions they could make alone. This is understandable, and it is expensive. It turns one person’s judgment call into an hour of six people’s time, and it often produces a vaguer decision than the person would have made on their own.
What you can change: separate input from ownership. Gathering everyone’s view is good. It is the meeting’s best feature. But the decision should still have one named owner who makes the call, informed by the input, and writes it down. When people see that asking for input does not mean giving up ownership, they stop needing a meeting to hide in.
Status theater
Some meetings exist to show that work is happening, not to move it forward.
The weekly status meeting is the classic case. Each person takes a turn describing what they did. Updates that could be read in two minutes take thirty when presented aloud, and most of the room is waiting for their own turn rather than listening.
Status theater persists because it serves a real need. Managers want to know what is going on, and people want their work to be seen. The meeting is just an inefficient way to meet both needs.
What you can change: move status to writing and keep the parts that need conversation. A short written update from each person, read on their own time, covers what happened. If something in the updates needs discussion, that becomes a specific question, and maybe a short meeting with only the people involved.
Recurring meetings are never re-justified
A recurring meeting is created for a reason. A project kicks off, a new team forms, a problem needs weekly attention.
Then the reason changes and the meeting continues. The project ships, the team settles, the problem gets solved. The meeting stays on the calendar because nobody owns cancelling it. Cancelling a meeting other people attend can feel presumptuous, so it runs on inertia.
Over time, a calendar fills with meetings whose original purpose nobody remembers.
What you can change: give every recurring meeting an expiry. When it is created, set a date to review whether it is still needed, and put a name next to that review. When the date arrives, the default should be to end the meeting unless someone makes the case for keeping it. Most will not survive the question.
No other channel for consensus
This is the deepest cause, and it sits underneath the others.
Chat threads are fast, but they drift. People reply to the last message instead of the question. Conversations fork, and some people never see the part that mattered. Email chains have the same problem, slower.
Neither one ends cleanly. There is no point at which a thread says “this is decided, here is who owns it.” So when a group needs to reach a decision that holds, someone eventually says “let’s just get on a call.” The meeting wins by default, because it is the only channel that reliably ends with an answer.
What you can change: use a structured way to decide in writing. One question, the context people need, a deadline, everyone’s answer in their own words, and a written outcome with an owner. That is the pattern described in How to Have Fewer Meetings. It works because it has the one thing chat and email lack: a defined end.
How the causes compound
These causes rarely appear alone. They feed each other, which is why calendars fill faster than anyone expects.
Here is a common sequence. A team has no structured way to decide in writing, so a hard question goes to a meeting. Because scheduling is free for the organizer, the invite grows to include everyone who might have a view. Because deciding in writing feels risky, nobody wants to make the call before the meeting happens, so the question waits for the slot.
The meeting itself does not end with a clear outcome, because there is no habit of naming an owner before people leave. So a follow-up is scheduled. That follow-up becomes a weekly check-in “until this is sorted.” The question gets sorted eventually, but the check-in stays, because nobody owns ending it. A few months later it has turned into a status meeting.
Each step was reasonable on its own. Together they produced a permanent hour on many calendars from a single decision.
The same chain runs in reverse once you break it. When a decision can be made in writing, with everyone’s input and a named owner, the first meeting never happens. Without the first meeting there is no follow-up, no standing check-in, and no status meeting to outlive it. One structural fix removes a whole chain of meetings, not just one.
Which causes to work on first
You will not fix all six at once, and you do not need to.
Start with the last one. If your team has no trusted way to make a decision in writing, the other fixes will not hold, because every hard question will still end up in a meeting. Once that alternative exists, the others get easier: recurring meetings are easier to cancel, status moves to writing more naturally, and people feel less need to share the risk of a call.
To see how much of your calendar these causes account for, run the self-audit in How to Know If You’re Having Too Many Meetings.