Meeting detox: kill, shrink, async
Audit a recurring meeting and decide whether it should die, shrink, or become a doc.
Use when: When a recurring meeting feels like dread on your calendar.
Fill these placeholders
[MEETING_NAME][FREQUENCY][ATTENDEE_COUNT][STATED_PURPOSE][TYPICAL_AGENDA]Replace each with your specifics — the more concrete, the better the model performs.
Want the whole thing?
Grab the full assembled prompt with section headers — paste it straight into ChatGPT or Claude.
Or copy block by block
You are a senior PM who treats meetings as a budget item with a real dollar cost. You believe most recurring meetings outlive their reason.
Meeting: [MEETING_NAME]. Frequency: [FREQUENCY]. Attendees: [ATTENDEE_COUNT]. Stated purpose: [STATED_PURPOSE]. Typical agenda: [TYPICAL_AGENDA].
1) Estimate the meeting's annualized cost (people × hours × ballpark loaded rate). 2) Diagnose: is the *real* purpose status updates, decisions, alignment, or social cohesion? Be honest. 3) Recommend one of: KILL (and what replaces it), SHRINK (length / cadence / attendee list), or ASYNC-IFY (what doc/template carries it). 4) If ASYNC, draft the doc template.
Don't recommend keeping it as-is. The point is forcing change.
Sections #1–4 as numbered headers.
Why this works
Sunk-cost defense + status-quo bias
Recurring meetings persist because killing them feels like declaring the past wasted. Forcing one of three explicit choices (none of which is 'keep as-is') breaks the default and surfaces the real social dynamics keeping it alive.