The average knowledge worker spends 25–40% of their working hours in meetings, and studies consistently show that roughly half of that time is perceived as wasteful. Meetings are expensive in real cost and in the opportunity cost of deep work they displace. Running a good meeting is a skill — and it is not complicated once you build it around a few non-negotiable principles.
What changed in 2026
- Async-first culture solidified — distributed teams at companies like GitLab, Automattic, and many startups proved that the default should be async. A meeting now needs to justify itself against "could this be a doc?"
- AI meeting tools matured — real-time transcription, automatic action item extraction, and meeting summary tools are standard in Zoom, Teams, and Google Meet. Fewer things need to be written manually, but someone still needs to run the room well.
- Meeting fatigue is better understood — the cognitive cost of switching between Zoom calls is measurable; back-to-back meetings are actively bad for decision quality by the third or fourth meeting.
The meeting types and when to use them
| Meeting type |
Use when |
Should it be async? |
| Decision meeting |
You need alignment on a call now |
Only if fully aligned async is possible |
| Brainstorm/ideation |
You need divergent input quickly |
Sometimes |
| Status update |
"What is everyone working on?" |
Almost always yes — use a doc or async standup |
| Retrospective |
Learning from a project or sprint |
No — real-time is better for safety |
| 1:1 |
Manager/report relationship |
No — relationship requires real-time |
| All-hands |
Company/team-wide updates |
Async recording preferred; live Q&A at end |
Before scheduling, ask: would a written document get the same result? If yes, write the document.
The pre-meeting: agenda and pre-read
Send both at least 24 hours before the meeting:
Agenda elements:
- Meeting goal (one sentence: "Decide X" or "Align on Y")
- Agenda items with time allocations
- Who owns each item
- Pre-read material (doc, data, proposal)
People who read the pre-read arrive to make a decision, not to orient. Without a pre-read, the first 15 minutes of a 30-minute meeting are wasted.
Invite list:
- Decision makers only for decision meetings
- Maximum 7 people as a soft limit
- If someone is "just to be informed," send them the notes afterward
Running the meeting
Open: state the goal out loud
"We're here to decide X. By the end of this 45 minutes, I want us to leave with a decision and named owners."
This takes 10 seconds and sets the entire context.
Protect the agenda time
Parking lot off-topic items visibly — write them down, acknowledge them, and move on. Saying "great point, let's park that for after" is not dismissal; it's discipline.
Manage dominant speakers
In groups, the loudest voice often wins by default. Explicitly invite input from quieter participants: "Before we decide, I want to hear from [name] — what's your take?"
End 5 minutes early
The last 5 minutes are for action items. Do not leave until every decision has named owners and a deadline.
The action item formula
Vague: "We should look into that."
Specific: "[Person] will draft the proposal by [date] and share it in the #project Slack channel."
Every action item needs: who, what, and when.
Meeting comparison: good vs bad
| Characteristic |
Bad meeting |
Good meeting |
| Goal |
"Discuss the project" |
"Decide whether to extend the deadline" |
| Invite list |
Everyone who might care |
Decision makers only |
| Pre-read |
None |
Shared doc 24 hrs ahead |
| Time management |
Open-ended |
Hard stop; agenda with minutes |
| Action items |
"Let's follow up" |
Named owner, specific deliverable, date |
| Follow-up |
Nothing |
Notes with action items sent same day |
Common mistakes
Scheduling a meeting to avoid writing a document. Writing forces clarity that a meeting doesn't. If you cannot write the agenda because the issue is unclear, the meeting is not ready to be scheduled.
Inviting people "for awareness." They pay attention for 10 minutes, check out, and resent the time. Send them the notes.
No decision, just discussion. Discussions without decisions are brainstorms. Call them brainstorms, time-box them, and capture the outputs for a separate decision meeting.
Ending without action items. The meeting produced words. The action items are what make those words matter.
Back-to-back scheduling. 5 minutes between meetings is a baseline for cognitive recovery. Build it in or meetings bleed into each other.
What to skip
- Daily status standups that are really status reports — an async written update takes less time and creates a searchable record.
- Recurring meetings with no standing agenda — if no one has updated the agenda, cancel the instance.
- Meetings as a venue for decisions you already made — if the decision is made, communicate it in a doc; the "alignment meeting" is performative.
FAQ
How long should a meeting be?
The default should be 25 or 50 minutes (not 30 or 60) — the buffer is for recovery. Most decision meetings should need 30 minutes or less with a good pre-read.
How do you stop a meeting from going off-track?
Name the drift out loud: "We're moving into X territory — I want to park that and come back to the agenda item." Do it without apology.
What do you do when people don't read the pre-read?
First time: give a 3-minute verbal summary and move on. Pattern: state explicitly that the meeting assumes the pre-read is done, and start making decisions without re-teaching it.
How do you run effective remote meetings?
Cameras on for decision meetings (where possible), explicit invitation for all voices, shared visible doc during meeting, async read before and notes/recording after.
Where to go next
For related professional skills, see How to give constructive feedback in 2026, How to say no politely in 2026, and Time blocking explained in 2026.