How-To Guide

How to Run Meetings That Don't Waste Everyone's Time

You spent 12 hours in meetings this week. You could summarize every decision made in one paragraph. Meetings aren't inherently bad. Bad meetings are bad. Here's how to run ones worth attending.

The Meeting Audit: Where Your 12 Hours Actually Went

Monday standup

30 min — 8 — 0 — true — 0.5

Project sync: Greenleaf

60 min — 4 — 1 — false — 1

Team all-hands

45 min — 15 — 0 — true — 0.75

"Quick" brainstorm

60 min — 6 — 0 — true — 1

Client check-in: Altitude Coffee

30 min — 3 — 2 — false — 0.5

1:1 with boss

30 min — 2 — 3 — false — 0.5

Pipeline review

45 min — 5 — 1 — true — 0.75

Design review

60 min — 7 — 0 — true — 1

"Let's hop on a call"

25 min — 2 — 1 — true — 0.4

Friday retrospective

45 min — 6 — 0 — true — 0.75

The 5 Meeting Killers

No agenda

The first 10 minutes are spent figuring out what to talk about — 10 min wasted × number of attendees — No agenda, no meeting. Send the agenda 24 hours before. If you can't write an agenda, you don't need a meeting.

Too many people

Half the room is silent, checking their phones — Every unnecessary attendee = their hourly rate × meeting length, wasted — The "two pizza rule" is real. If you can't feed the group with two pizzas, it's too many people. Invite decision-makers, not observers.

No clear owner

Nobody drives the conversation, so it meanders — Meetings without a facilitator run 30-50% longer — Every meeting has one owner who sets the agenda, runs the clock, and captures decisions.

No time limit

The 30-minute meeting somehow becomes 55 minutes — Parkinson's Law: work expands to fill the time available — Default to 25 minutes, not 30. Default to 50 minutes, not 60. The shorter time forces focus.

No decisions captured

You leave the meeting and nobody knows what was decided — Same conversation gets repeated next week — Last 3 minutes: "What did we decide? Who owns what? By when?" Write it down and send it.

The Meeting Framework: Before, During, After

Before: The 3-Question Gate

24 hours before — Question 1: Does this need to be a meeting? If it's just information sharing, send an email or Loom video.,Question 2: What decision needs to be made? If no decision, it's probably a status update that could be async.,Question 3: Who are the minimum people needed to make this decision? Invite only them. CC others on the notes.,If you pass all 3 gates: send the agenda with the specific decision(s) to be made, any pre-read materials, and the time limit.

During: The 25-Minute Format

Meeting time — Minutes 0-2: State the purpose. "We're here to decide [X]. Here's what we know so far.",Minutes 2-15: Discussion. The facilitator keeps conversation on track. Tangents get captured in a "parking lot" for later.,Minutes 15-22: Decision time. "Based on what we've discussed, here are the options. Which are we going with?",Minutes 22-25: Capture. "Here's what we decided. [Name] owns [action] by [date]. I'll send notes in 5 minutes.",Minute 25: End. On time. Always. Even if the discussion isn't finished, that means the meeting was scoped wrong, not that it should run long.

After: The 5-Minute Close

Within 5 minutes of ending — Send a 3-line email to all attendees: (1) What was decided, (2) Who owns what actions, (3) Next check-in date.,Add action items to your task tracker, don't rely on the notes to be read.,If a follow-up meeting is needed, schedule it now with a specific agenda. Don't leave it vague.,Ask yourself: "Could this meeting have been shorter?" If yes, shorten the next one.

5 Meetings You Can Replace With Async

Status updates

Monday async standup (Slack/email). Each person posts 3 lines: Done, Doing, Blocked. Takes 2 min to write, 3 min to read. — 30 min/week per person

Brainstorming sessions

Shared doc with a prompt. Everyone adds ideas async over 24 hours. Then a 15-minute meeting to pick the top 3. — 45 min/session

Design reviews

Loom video walkthrough + comment threads. Async feedback within 48 hours. Only meet if there's a disagreement. — 60 min/week

"Quick call" requests

Voice message or 3-paragraph email. 90% of "let's hop on a call" can be resolved in text. — 25 min per avoided call

Retrospectives

Friday survey (3 questions: What went well? What didn't? What to try next week?). Share results Monday. — 45 min/week

Try alfred_

Make Meetings Worth Having

alfred_ preps you for every meeting and tracks every follow-up. Fewer meetings, better outcomes.

Try alfred_ Free

Frequently Asked Questions

How do I decline meetings without being seen as uncooperative?

Ask a question instead of saying no: "What decision are we making in this meeting? I want to make sure I'm the right person to have in the room." This either confirms you should attend or reveals that the meeting doesn't need you. Either way, you look thoughtful, not difficult.

My organization has a meeting-heavy culture. Can one person change that?

You can't change the culture overnight, but you can model the alternative. Run your meetings with agendas, end on time, send notes within 5 minutes. When people experience a well-run meeting, they start to notice how bad the others are. Start with the meetings you control, and the influence spreads.

What about meetings that are primarily for relationship building?

Those are valuable, but they're not "meetings" in the productivity sense. A coffee chat, a team lunch, a 1:1 that's mostly personal, these build trust and should be protected. The problem is when relationship-building meetings masquerade as decision-making meetings. If the goal is connection, call it that and enjoy it.

How many meetings per day is too many?

More than 3 hours of meetings in a day leaves almost no room for deep work. A good target: max 2 hours of meetings per day, batched into one window (afternoon is ideal). That leaves your mornings free for focused work. Some days will break this rule, and that's fine. But it shouldn't be the default.

What if I'm not the meeting organizer? How do I improve meetings I attend?

Ask for an agenda before accepting. Send your input before the meeting so it can be processed efficiently. During the meeting, be the person who asks "What are we deciding?" when the conversation drifts. After the meeting, send a quick follow-up: "Here's what I captured, did I miss anything?" You don't need to be the organizer to set the standard.

How does alfred_ help with meetings?

alfred_ analyzes your calendar and provides pre-meeting briefs: who you're meeting with, relevant email context, and what they're likely to discuss. This cuts prep time from 15 minutes to 2 minutes. After meetings, it tracks any follow-up commitments mentioned in subsequent emails, so nothing falls through. The result: fewer meetings needed because your existing meetings are more productive.