Conduct a PM team meetings audit

Meeting Audits: The Highest-Leverage Time Recovery

PM teams accumulate meetings the way product portfolios accumulate features — each was justified at creation, few are re-evaluated, and nobody has permission to kill. The result is 18-hour-a-week meeting loads where the team can name the meetings they attend but not what shipped because of them. The meeting audit is a one-session exercise that typically recovers 6-10 hours per PM per week.

How the Conduct a PM team meetings audit Prompt Works

The prompt inventories every recurring meeting with five data points (purpose, cadence, attendees, output, owner), audits each on four dimensions (purpose clarity, output clarity, attendance necessity, decision velocity), and classifies into keep / redesign / kill. The redesign patterns are the practical menu: async memos, reduced cadence, reduced attendees, pre-read discipline, merging, splitting.

The kill rules matter. Announcing the kill, naming where the conversation moves, and scheduling a 30-day check-in are what prevent the team from quietly re-creating the meeting in a different form. Atlassian's agile metrics writing and Google re:Work's guides on team effectiveness both document that meeting audits produce larger gains than most productivity interventions at PM teams.

When to Use It

• PMs are spending >15 hours/week in meetings with declining shipping velocity.
• A new manager is onboarding and meeting load is a visible issue.
• A quarterly capacity reclaim is a leadership goal.
• An engineering partner has complained about PM meeting load affecting their collaboration.
• A new team is forming and you want to install meeting hygiene before it ossifies.

Common Pitfalls

• Killing without relocating the conversation. If the meeting had a valid purpose, the conversation will reappear — usually as Slack noise. Redirect deliberately.
• Redesigning without reducing. Adding async memos on top of the meeting produces more work, not less. Redesign means the meeting shortens or disappears.
• Skipping the 30-day check. Some killed meetings were load-bearing in non-obvious ways. Check and re-install if needed, in a lighter form.

Sources

• Agile Metrics — Atlassian
• Google re:Work — Google
• Basecamp: Getting Real
• The Pragmatic Engineer