🪑Running Meetings
Most PM meetings are wasted. The fix isn't shorter meetings — it's clearer purpose, sharper structure, and the discipline to skip the meeting when an email would do.
PMs run more meetings than almost any other role. Bad meetings tax your team for the rest of the week. Good meetings produce decisions and align the team in 30 min that would've taken 3 days of Slack.
Every meeting should have a clear purpose (decide, align, brainstorm, or learn), the right attendees, an agenda sent ahead, and a decision and owner at the end. If you can't articulate the decision, cancel and send a written update.
The four kinds of PM meetings
- Decide. A real decision is on the table. Bring options, attach a recommendation. Decide and assign owner. (30 min max.)
- Align. Make sure everyone has the same understanding before execution. Pre-read the doc; meeting is for questions only. (30 min.)
- Brainstorm. Generate options. Use a structured exercise (silent brainstorm, then group). (45-60 min.)
- Learn. Hear from customers, look at data together. (30-45 min.)
If your meeting doesn't fit one of these four, you're probably doing a status update — which should be written, not a meeting.
The five components of a good meeting
- Pre-read. Doc sent 24 hours ahead. Anyone who didn't read it doesn't get to speak first.
- Stated purpose at the start. "We're here to decide on X by 11am."
- Time-boxed agenda. "10 min context, 15 min discussion, 5 min decision."
- Active facilitation. PM keeps the conversation on track, calls on quiet voices, names the decision.
- Written decision + owner + deadline at the end. "Decision: ship v1 of A. Owner: Sarah. Deadline: Friday." Posted in Slack within 30 min.
Meetings to cancel
- Status updates. Write a doc. Save 30 min × N people × every week.
- Recurring 'standing' meetings nobody owns. Audit your calendar quarterly. Cancel anything where you can't articulate the value.
- Brainstorms with too many people. 4-6 is ideal. More than 8, nobody speaks.
- 'Information sharing' meetings. Use Loom or a written update.
The PM running a design review (template)
- (5 min) Context. PM frames the problem and the user research.
- (15 min) Designer walks through the design. No interruptions.
- (15 min) Q&A and pushback. Structured: edge cases, scope, alternatives.
- (15 min) Decisions. What's locked, what's open, who owns the open items.
- (5 min) Next steps. Posted in Slack same day.
The PM running a sprint planning
Sprint planning shouldn't be longer than 90 min for a 2-week sprint. If it is, the PRD wasn't clear enough — fix that root cause.
Real-world examples
Amazon's famous '6-pager' meeting starts with 20 minutes of silent reading. No slides, no presentation — just a written narrative that everyone reads together. Discussion only begins once everyone has the same context. Many teams report this single discipline doubled meeting effectiveness.
Go deeper — recommended reading
Interview questions (1)
Q1You've inherited a team with too many meetings. How do you fix it?executionmid▼
Four moves in week 1-4:
- Audit. List every recurring meeting on the team's calendar. For each, ask 'what's the purpose, who's the owner, what was the last decision made?' Anything that fails this — cancel.
- Default to written. Convert all 'status update' meetings to async written updates. Reclaim 2-3 hours per person per week.
- Add pre-reads. Any remaining meeting >30 min must have a pre-read sent 24 hrs ahead. People who haven't read don't speak first.
- No-meeting Wednesday. One day a week, all-day, no meetings. Forces written communication and gives the team makers' time.
I'd measure success by (a) hours of meetings per person per week, (b) team self-reported satisfaction. Aim to cut meeting time by 30-50% in 60 days.