Conduct a PM team meetings audit

Description

Your PM team spends 18 hours a week in meetings and nobody can name what's shipping because of them. This runs an audit — every meeting's purpose, attendance cost, decision output — and produces a kill-or-redesign list so the team gets 6-10 hours back per PM per week.

You are running a PM team meetings audit for {{team_name}}. Team size: {{team_size}}. Estimated meeting hours per PM per week: {{meeting_hours}}.

## Step 1 — Meeting inventory
List every recurring meeting the team attends. For each:
- Purpose (1 sentence)
- Cadence and duration
- Required attendees
- Decision or artifact produced (not "discussion")
- Owner

## Step 2 — Audit per meeting
Score each 0-3:
| Meeting | Purpose clarity | Output clarity | Attendance necessity | Decision velocity | Worth keeping? |
|---------|----------------|---------------|---------------------|-------------------|----------------|

## Step 3 — Classify
- **Keep**: purpose clear, decisions made, right attendees. No change.
- **Redesign**: purpose valid but format broken. Change cadence, attendees, or agenda.
- **Kill**: no longer serves a purpose, or the output is available async.

## Step 4 — Redesign patterns
For meetings being redesigned, pick from:
- Make it async (weekly status memo instead of status meeting)
- Reduce cadence (biweekly instead of weekly)
- Reduce attendees (just the decision-makers)
- Pre-read required (no presentation, we discuss)
- Split (merge two overlapping meetings; split one doing too many things)

## Step 5 — Kill rules
When killing a meeting:
- Announce to all attendees with reason
- Define where the conversation that used to happen there now happens
- Schedule a 30-day check-in to confirm it wasn't load-bearing

## Output
1. Meeting inventory table
2. Keep / redesign / kill classification
3. Hours saved per PM per week after changes
4. The 1 meeting the team will be most reluctant to kill
5. A 1-paragraph announcement explaining the changes

Customize This Prompt