Meeting Load Minimizer
Replace meeting sprawl with agendas, pre-reads, slim cadences, and async artifacts
Meeting overload and multi-channel communication sprawl are a major PM drag. This recipe designs a minimal meeting system: which meetings exist, why, with what agenda, what pre-work, and what async artifacts replace the rest.
INGREDIENTS
PROMPT
Create a skill called "Meeting Load Minimizer". Input: my current meeting list + project rhythm. Output: a redesigned meeting system with fewer hours and higher decision quality. Requirements: - For each meeting: keep/merge/delete recommendation and why. - Provide agenda templates and required pre-reads. - Suggest async replacements (pulse update, decision log, blocker summary). - Produce a weekly calendar plan that stays under a target hours/week budget. Guardrails: - Do not remove governance meetings without proposing an equivalent decision mechanism. - Prefer single source-of-truth artifacts over duplicative meetings.
How It Works
List your current meetings (name, cadence, attendees, purpose) and your project rhythm.
The recipe audits each meeting against its actual output, recommends keep/merge/delete
decisions, provides agenda templates and pre-read checklists, and designs async
replacements for everything that doesn't need a live room.
What You Get
- Meeting audit: keep, merge, or delete per meeting — with rationale
- Agenda templates: mandatory structure per meeting type
- Pre-read checklists: what must be read before the meeting, and who owns it
- Async replacements: weekly pulse update, decision log, blocker summary
- Calendar plan: weekly hours budget that stays under your target
Setup Steps
- List all current recurring meetings: name, cadence, attendees, stated purpose
- Describe your project rhythm (sprints, releases, governance checkpoints)
- Set a target meeting hours/week budget
- Review recommendations and implement changes
Tips
- Governance meetings are never removed without proposing an equivalent decision mechanism
- Note-taking policy options: rotate, dedicated notetaker, or AI-assisted
- Channel policy: single primary channel or multi-channel with explicit rules
- Async artifacts pair well with Stakeholder Pulse Push
- Re-check meeting load monthly — it creeps back fast