Every founder complains about too many meetings. Almost none of them audit which meetings are actually wasting their time. The result: the same complaints, the same meetings, month after month, until the founder is spending 60% of their week in Zoom calls and shipping product on nights and weekends.
The problem usually isn't the number of meetings. It's that the meetings themselves are bad. A good 30-minute meeting produces more decisions than a bad 90-minute meeting produces confusion. The difference isn't tools or apps — it's specific practices most people never learned.
Here's the exact playbook. The structure, the 7 rules, the 5 meetings to probably cancel, and the language for actually enforcing this on a team that's used to bad meetings.
First: understand what a meeting IS (and what it isn't)
A meeting is a specific use of time for a specific purpose that couldn't be achieved another way.
Legitimate meeting purposes:
- Decision-making — when 2+ people need to align on a choice that has real consequences
- Coordination — when handoffs between people need direct discussion
- Brainstorming — when creative synthesis needs multiple minds simultaneously
- Feedback — when nuance and body language matter (performance reviews, difficult conversations)
- Learning — when instruction requires demonstration or dialogue
Not-meetings (things being done as meetings but shouldn't be):
- Status updates — should be async (a document, a message, a Loom)
- FYI announcements — should be a message
- Reading a document together — read it separately, meet only to discuss
- "Getting everyone on the same page" — usually means the docs are bad
- Networking / relationship building — should be a coffee, not a calendar block
The single biggest source of meeting waste: doing not-meetings as meetings.
The structure of a good meeting
Every good meeting has 4 things. Every bad meeting is missing at least one.
1. A specific purpose in one sentence
Not "sync on marketing." Something like: "Decide whether to move the Q4 campaign launch from October 15 to November 1."
The test: if you can't complete the sentence "By the end of this meeting we will have decided/agreed/aligned on X," you don't have a purpose. Cancel the meeting.
2. An agenda in the invite (before the meeting)
Every attendee knows what's being discussed BEFORE they show up. Not delivered verbally in the first 5 minutes.
Good agenda:
1. Decide: October 15 vs November 1 launch date (15 min)
2. Assign: who owns which content deliverable (10 min)
3. Open: any concerns not addressed (5 min)Bad agenda:
- Marketing syncThe bad version leads to meandering; the good version keeps it on track.
3. The right people (and only the right people)
Every attendee needs one of these roles:
- Decision-maker (the person who'll make the call)
- Contributor (someone whose input specifically shapes the decision)
- Executor (someone who'll do the work after the decision)
Attendees who don't fit:
- People who are "kept in the loop" — send them the notes
- People who "should know about this" — send them the notes
- People invited "just in case" — they'll never contribute; send them the notes
The specific rule: if someone can attend the meeting and not say a single thing, they didn't need to be there. Send them a written summary instead.
4. Written decisions and action items at the end
Every meeting ends with a written summary: what was decided, who owns what, when it's due. Written in the last 5 minutes of the meeting itself, not "sent later" (which usually means "never").
Even better: written in a shared document during the meeting, so everyone can correct it in real time.
Meetings without written outcomes are meetings that will need to be re-litigated next week when memories diverge.
The 7 rules that make meetings work
Rule 1: Default to 25 or 50 minutes, not 30 or 60
The default 30-minute meeting expands to 30 minutes. A 25-minute meeting expands to 25.
Why 25/50: it forces slight urgency. And it gives everyone 5 minutes between back-to-back meetings, which they desperately need. Google adopted this norm years ago; it's not new.
Rule 2: Start on time, exactly
Waiting for the last 2 people wastes 5 people's time. Every extra minute waiting is minutes × everyone in the meeting. If someone is 5 minutes late in a 6-person meeting, that's 30 person-minutes wasted.
How to actually do this:
- Start with attendees who are present at the exact start time
- If a critical decision-maker isn't there at start time, the meeting shifts to "wait 5 min or cancel" — never wait 20 minutes for someone
- After 2-3 weeks of this, people show up on time
Rule 3: One person talks at a time (no side conversations)
Side conversations halve the productivity of the primary discussion. Everyone's attention splits.
How to enforce:
- If two people start a side conversation, pause the meeting and say "let's bring that to the group or take it offline"
- Doesn't need to be aggressive; a simple "let me pause you for a sec — Jane, want to bring that to the group?" works
Rule 4: Decisions require decision-makers to be in the room
If the person who would ultimately have to approve the decision isn't there, the meeting can only recommend — not decide. Which means you'll need another meeting.
How to fix: either invite the decision-maker or explicitly reframe as "this is an input-gathering session; final decision Wednesday with [name]."
Rule 5: End at least 5 minutes early
Ending on time creates pressure. Ending 5 minutes early creates goodwill AND gives people time to reset before their next meeting.
How to do it: at the 20-minute mark of a 25-minute meeting, deliberately move to "OK, what did we decide, and who owns what?" — even if the discussion wasn't "finished." Discussions expand to fill time; forcing an early end forces synthesis.
Rule 6: If it's a status update, kill it
Weekly status meetings are the largest single meeting waste in most organizations. Everyone reports what they did. Nobody's fully paying attention when it's not their turn. The information could have been a document read in 5 minutes vs an hour of meeting time.
Better version: everyone writes their status in a shared doc by Monday 9am. Everyone reads it silently for 5 minutes. Meeting starts at 9:15 and covers only what needs discussion, not what's in the doc.
Best version: kill the meeting entirely. Everyone just writes their status in the doc. Discussions happen async in the doc's comments.
Rule 7: Cancel the meeting if the reason for it disappears
Standing meetings persist long after their reason is gone. Weekly design sync from a redesign project 6 months ago that's now shipped. Monthly ops review from when ops was breaking and now runs smoothly.
How to catch these: every quarter, look at your calendar. For each recurring meeting, ask "if I hadn't already established this, would I create it today?" If no, kill it or make it happen half as often.
The 5 meetings you should probably cancel this week
Look at your calendar. Identify which of these apply:
1. The "weekly team sync" that's really a status update
If the meeting is 90% "here's what I did last week and what I'm doing this week," it should be async. Replace with a written status doc. Save: 30-60 min per person per week.
2. The 1:1 that's really an FYI transfer
If your 1:1 with your report is you telling them what to do, that's not a 1:1 — that's a delegation. Send it as a message. Reserve 1:1s for actual dialogue about problems, growth, and questions THEY have.
3. The "all hands" that repeats information already sent
If your all-hands is 80% info that was already in the weekly update email, it's mostly wasted time. Either the emails aren't landing (fix that) or the all-hands is redundant.
4. The vendor check-in that could be an email
Your monthly call with your accountant, your marketing agency, your dev shop. Half of them could be emails. Ask each vendor: "Would monthly emails + only-when-needed calls work for us?"
5. The "brainstorm" without a specific problem
Brainstorms are great when there's a specific problem to solve. Generic "let's brainstorm marketing ideas" sessions rarely produce anything shippable.
The specific language for changing meeting culture
If you're introducing this to a team used to bad meetings, expect resistance. Here's the language for common situations:
"But I need to be in that meeting"
Response: "I'll send you the decisions and action items within an hour of the meeting ending. If there's something specifically you want to weigh in on, put it in the agenda beforehand and I'll make sure it's covered."
"Can we make this 60 minutes instead of 25?"
Response: "Let's start with 25. If we're mid-discussion at the 20-minute mark, we can decide whether to extend or take it to a follow-up. Setting 60 upfront guarantees we'll fill it."
"I don't want to seem rude by starting without them"
Response: "Actually the rude thing is making the on-time people wait. Let's start on time and if [late person] misses context, we can catch them up in 2 minutes at the end."
"But this is how we've always done it"
Response: "I know. That's why I want to try something different for 4 weeks. If it's worse, we go back. If it's better, we keep it."
The team member who talks too much
Response (in the moment): "Great — let me pause you there. I want to make sure others get to weigh in. [Other person], what's your take?"
Response (after the meeting, 1:1): "Hey, I noticed in the [meeting] you took about 40% of the discussion time. Some of what you said was really valuable — the point about X was spot on. But when you speak that much, others don't feel they have space to contribute. Can you self-monitor next time and try to leave more silence?"
The 3-meeting-week test
Here's a practical experiment: for one week, aggressively cull your meetings.
Rules for the test week: 1. Every new meeting request: reject unless it passes the "one-sentence purpose" test 2. Every recurring meeting: skip it once. See what breaks. Nothing? Kill it permanently. 3. Every non-essential meeting: turn it into async communication (a message, a doc, a Loom)
Expected result: you'll go from 20-30 meetings a week to 5-10. You'll save 15-20 hours. You'll ship more product. Almost nothing will actually break.
Almost every founder who tries this reports that:
- Their team gets MORE done, not less
- Communication quality actually improves (because it's written and searchable)
- The remaining meetings are much more valuable
A specific example
I worked with a founder whose calendar had 22 meetings per week. Each was "important." She was exhausted, shipping nothing, and constantly playing catch-up.
We audited every meeting. Categorized each:
- 4 were legitimate decision-making meetings (kept)
- 6 were status updates (killed, replaced with a shared Notion doc)
- 5 were 1:1s that had become FYI transfers (converted to weekly written check-ins with actual 1:1s monthly)
- 3 were vendor check-ins (converted to email)
- 4 were "kept in the loop" invites (declined, asked to be added to summary emails)
Result after 30 days: she went from 22 meetings/week to 6. Reclaimed 20 hours per week. Product velocity doubled. Nothing broke.
More importantly: the 6 remaining meetings became MUCH better. Because they were now scarce, people prepared for them. Decisions actually got made. Follow-up happened.
The insight: meetings are like money. Scarcity forces prioritization. Abundance produces waste.
What to do this week
Audit your calendar:
- Look at your next 2 weeks of meetings
- For each, write down the one-sentence purpose
- Any without a clear purpose → cancel or convert to async
Try the meeting rules for one week:
- 25/50-minute defaults instead of 30/60
- Start exactly on time
- Written decisions in the last 5 minutes
- End 5 min early
Kill one standing meeting this week:
- Pick the one you dread most
- Skip it once
- See if anything actually breaks (usually nothing does)
- If nothing breaks, kill it permanently
For 1:1s specifically:
- Ask your reports: "What's the least useful part of our current 1:1?"
- Take the answer seriously
- Restructure
If the underlying problem is that your team's async communication is broken (which is often WHY meetings proliferate), related reads:
- How to write a PRD that actually gets built — better docs = fewer clarification meetings
- The 5 metrics that matter — clear metrics = fewer status meetings
- How to fire a client professionally — sometimes bad meetings are with bad clients, and the answer is to end the client relationship
The compound effect: cutting 10 hours of meetings per week isn't just 10 hours saved. It's 10 hours of DEEP work you now have access to. Which is worth roughly 30 hours of interrupted work. Which is why the founders who master this ship dramatically more than their meeting-heavy peers.
Bad meetings aren't just a nuisance. They're the single biggest productivity killer in most startups. Fix them and everything else gets easier.
---
If your team's meeting culture is broken and you're not sure where to start, reach out via the contact page with a paragraph about a typical week's calendar. I'll give you specific recommendations on what to cut, what to keep, and what to restructure.