How to Run Better Product Meetings

Product managers spend a staggering amount of their week in meetings. Many of those meetings end without a clear decision, action item, or new insight. The problem is rarely that the topics are unimportant—it is that the meeting structure does not support productive outcomes. Better meetings require better preparation, tighter facilitation, and ruthless follow-through.

Before the Meeting

Every meeting should have a written purpose that fits in one sentence. If you cannot articulate why the meeting exists, cancel it. Share the agenda and any required reading at least 24 hours in advance. This gives attendees time to prepare and lets people who are not needed opt out.

• Define the meeting purpose: inform, discuss, or decide.
• List specific questions that need answers by the end of the meeting.
• Share relevant context documents in advance, not during the meeting.
• Invite only the people whose input is needed. Everyone else gets the notes.

During the Meeting

Start on time, even if not everyone is present. State the purpose in the first 30 seconds. Use time boxes for each agenda item and enforce them. If a discussion is going in circles, call it out and either make a decision or explicitly defer it.

Designate a note-taker who captures decisions and action items, not a transcript of the conversation. End five minutes early to allow people to document next steps and transition to their next commitment.

After the Meeting

Send a summary within an hour. Include decisions made, action items with owners and deadlines, and any open questions. If the meeting was a roadmap review, update your roadmap tool so the outcomes are reflected where the team actually works. In Planet Roadmap, you can adjust priorities and statuses immediately so decisions do not live only in meeting notes.

If you find yourself having the same meeting repeatedly without progress, the meeting is not the problem—the underlying decision-making process is. Fix that instead of scheduling more meetings.

Meetings You Should Probably Cancel

Status update meetings can almost always be replaced with an asynchronous update. If the only purpose of the meeting is for people to report what they did last week, a shared document or a Slack post works better and gives everyone 30 minutes back.

Recurring meetings should be audited quarterly. If attendance has dropped, if the agenda is routinely thin, or if decisions are being made outside the meeting anyway, cancel it. You can always restart it if people miss it—but they usually do not.