The average knowledge worker spends somewhere between a third and half of their working week in meetings. A meaningful chunk of that time produces outcomes that could have been achieved with a two-paragraph message. Nobody set out to create this situation — it happened gradually, as meetings became the default response to any need to coordinate.
The fix isn't to eliminate meetings. Some things genuinely need live discussion. The fix is to match the format to the purpose — to understand when a meeting is the right tool and when it isn't, and to run the ones you do have with enough structure to make them worth the time.
Not all meetings are the same. A decision meeting, a status update, a brainstorm, and a relationship-building conversation have almost nothing in common in terms of what they require. Using the same format — sixty minutes, everyone invited, loosely structured — for all of them is why so many meetings feel like a waste.
| Meeting type | Async OK? | Ideal live format | Max attendees |
|---|---|---|---|
| Decision needed | Sometimes | 25–45 min; pre-read required; decision-maker present; end with a written decision | 5–6 |
| Status update | Usually yes | If live: 15 min standup, no discussion — send blockers to async thread | 8–10 |
| Brainstorm | Rarely | 60 min max; silent generation first (5–10 min), then share and group; facilitator required | 4–7 |
| Relationship / check-in | No | 30 min 1:1; no agenda needed; walking or coffee format works well | 2 |
The status update meeting is the most common and most replaceable meeting in a small business calendar. It exists to answer: what's happening, what's done, what's stuck? These are questions that can be answered in writing, read asynchronously, and referred to later.
The argument for keeping status updates as meetings is usually "but then people don't read the updates." That's a culture and accountability problem, not a meeting problem. The meeting is a workaround for a culture where people don't read. The solution is to fix the culture, not to tax everyone's time weekly to compensate for it.
Replace the weekly status meeting with a short written update posted every Monday. Within a month, most teams report they prefer it — they can read it when they have five minutes, skim the parts relevant to them, and refer back to it when they need to remember what was happening three weeks ago.
Decisions that require real-time back-and-forth — where the information isn't all in one person's head, where different perspectives need to interact before a conclusion is possible — genuinely benefit from synchronous discussion. But most decision meetings fail because the participants arrive cold.
The pre-read is non-negotiable for any decision meeting that matters. The person calling the meeting should circulate a one-page brief: what we're deciding, the options under consideration, the key trade-offs, and a recommendation. Attendees should have read it before walking in. The meeting is then for discussion and refinement of the recommendation — not for hearing the problem described for the first time.
Standard brainstorming — throw ideas at a whiteboard, loudest voice shapes the outcome — is one of the least effective ways to generate creative thinking. Research consistently shows that individuals generate more and better ideas separately than in a group, because groupthink, social pressure, and anchoring to early ideas suppress independent thinking.
A better format: share the problem in advance. Ask each person to write their top three ideas before the meeting. Start the meeting with five to ten minutes of silent individual generation (to surface anything new). Then share and group — and the facilitator's job is specifically to create space for quieter voices, because the best idea in the room is often not the one attached to the most confident person.
Beyond format, a few habits make a large difference in meeting quality:
A sixty-minute meeting with six people doesn't cost one hour. It costs six hours of collective time, plus the context-switching cost of pulling each person away from focused work. For a ten-person team that has four hours of meetings per week, that's forty hours — a full person's working week — spent every single week in meetings. How many of those hours produce outcomes that couldn't have been achieved another way?
This is not an argument against all meetings. It's an argument for treating meeting time as the expensive resource it is, and being as deliberate about it as you are about any other significant business expenditure.