Guides · Guide
How to Have Fewer Meetings
Published
Most advice about meetings is about running them better: tighter agendas, shorter slots, a timekeeper. That helps. But it treats the meeting as fixed and tries to shrink it.
This guide takes a different angle. Look at why a meeting exists. A large share of the meetings on your calendar exist to make a decision. If the decision can be made another way, the meeting has no reason to exist.
What meetings actually cost
A meeting’s cost is easy to underestimate because it is spread across several calendars. Nobody sees the full bill.
Take one ordinary example: a weekly one-hour meeting with six people.
The direct time is six person-hours a week. That part is obvious.
The indirect time is not. Each person loses some time before the meeting, because there is no point starting deep work at 1:40 when you have to stop at 2:00. They lose more time after it, getting back into whatever they were doing. Call it 20 minutes per person, which is conservative for anyone doing focused work. That adds two more person-hours.
So the weekly meeting really costs about eight person-hours.
Over a year of 48 working weeks, that is 384 person-hours. That is close to ten full working weeks of one person’s time, spent on a single recurring meeting.
If you put a loaded cost of $100 an hour on your team’s time (salary, benefits, overhead), that one meeting costs about $38,400 a year. Use your own numbers. The point is not the exact figure. The point is that a meeting nobody thinks twice about is one of the larger line items in your team’s week.
Most teams have several of these. If you want to see where your own count lands, How to Know If You’re Having Too Many Meetings walks through a self-audit. For the organization-wide version of this math, see The Meeting Tax.
The test: is this meeting a decision?
You cannot cut meetings by willpower. You need a test you can apply to each one.
Here is the test: if the main purpose of the meeting is to reach a decision, it is a candidate to go async.
Go through your recurring meetings and ask what each one is for. You will usually find three kinds.
Decision meetings. The team needs to pick something: a launch date, a vendor, a hire, a priority, whether to ship or hold. The meeting exists because that seems like the only way to get everyone’s view at once. These are your candidates.
Information-sharing meetings. Someone has news, context, or a walkthrough that people need to hear and ask questions about. Some of these could be a written update. Some genuinely benefit from being live, especially when the information is sensitive or likely to raise strong reactions. Keep those synchronous.
Conflict meetings. People disagree in a way that involves trust, emotion, or competing interests. Writing makes this worse, because tone gets lost and positions harden. Keep these synchronous too. A real conversation is the right tool.
The trap is that many meetings look like the second or third kind but are really the first. A “weekly sync” often exists to make three or four small decisions. A “planning review” is usually one decision: which of these do we do first?
Be honest about which meetings are really decisions. That list is where you will find your hours. What Causes Too Many Meetings explains why so many decisions end up in meetings by default.
The async pattern, step by step
Moving a decision out of a meeting is not the same as starting a long email thread. Threads drift. People reply to the last message instead of the question. Nobody knows when it is over.
The pattern below keeps the useful parts of a meeting (everyone’s view, a clear outcome) without the hour on the calendar.
1. Frame the decision in writing
Write down the question and the context people need to answer it. That is the whole brief.
The question should be one sentence that can actually be answered. “Thoughts on the launch?” is not a question. “Which concept should we take into the next design round?” is.
The context should be what someone needs to give a good answer and no more. What happened, what the options are, what each option costs, and when you need answers. A few short paragraphs is usually enough.
Writing the frame is the step that does the most work. Half the time, writing the question clearly shows you that the decision is smaller than it seemed, or that one fact is missing and you should get it first.
2. Send one link in the channels people already use
Do not ask people to go somewhere new. Send the decision where they already are: the team’s Slack channel, a text, an email. Whichever they actually read.
Send one link, so every person ends up in the same place, whichever channel it reached them through. That matters later, when you need to see everyone’s answer side by side instead of reconstructing it from three different apps.
Tools like Consensus Builder do this for you: one link per decision, shareable anywhere, with no account required for the people answering.
3. Collect free-form responses by a deadline
Ask people to answer in their own words. Don’t make them pick from a list or vote.
Free-form answers carry the reasons, and the reasons are what you actually need. “Hold” and “Hold, because support isn’t staffed this weekend” are very different inputs. The second one might change the decision, or point to a fix that makes shipping safe.
Let people answer however is natural for them: a written reply, a short voice note, a quick video. Some people think best by typing. Some would rather talk for 40 seconds than write three paragraphs. Both are fine.
Set a deadline and say it up front. Async does not mean open-ended. “Answers by Thursday at 5pm” gives people the flexibility to respond when it suits them, inside a window that keeps the decision moving.
When an answer is unclear, ask a follow-up, one specific question, rather than scheduling a call. Consensus Builder reads where each person stands from their response and asks the follow-up for you, so the Leader isn’t chasing people.
4. Close with a named owner and a written outcome
Every decision needs an end. Read the responses, see where the group stands, and decide.
Write the outcome down in a sentence or two: what was decided, and who owns it. “Ship Friday with the rollback ready. Sam owns the release.” Send it to everyone who was asked.
This step is what makes async decisions trustworthy. People are willing to skip the meeting when they know the decision will actually be made, by a named person, and written down where they can see it. Without the close, async decisions feel like they vanish, and people start asking for meetings again.
Note that closing is not the same as consensus. The person who owns the outcome decides, informed by everyone’s view. Sometimes the group agrees. Sometimes it doesn’t, and the owner makes the call anyway. What matters is that everyone was heard and the outcome is clear.
What to do with the freed time
If you move even two recurring decision meetings async, you can free up a dozen or more person-hours a week across a small team. That time does not automatically turn into anything useful. Meetings expand to fill empty calendars unless you protect the space.
A few things that work:
Leave the slot empty on purpose. When a recurring meeting goes async, don’t delete the time and let it fill up. Mark it as focus time for the people who were in it, at least for the first month.
Spend some of it on the meetings you keep. The meetings that survive should be the ones that need to be live: hard conversations, real conflict, creative work that benefits from a room. Give them better preparation. Make the Meetings You Keep Worth Having covers how.
Measure it. Count your team’s meeting hours per person before and after. Count how many decisions were made async and how long they took from question to outcome. If async decisions are taking longer than the meeting did, the frame is usually too vague or the deadline too loose. Fix those before giving up on the pattern.
Make it the default. The goal is for “can we decide this async?” to be the first question whenever someone reaches for the calendar. It only becomes the default if the first few async decisions go well. Pick a decision that matters but isn’t contentious, run the pattern carefully, and close it visibly.
Fewer meetings is not the goal on its own. The goal is decisions made with everyone’s input, an owner, and a written outcome, without the hour on everyone’s calendar. Done that way, the meetings mostly take care of themselves.