Most bad meetings were never planned to fail
They were planned around a topic instead of an outcome. "Discuss the rollout" fills the calendar slot and produces nothing checkable. "Agree the rollout date" does one thing, and everyone in the room knows whether it happened.
What it does
- One printable page. Purpose, desired outcome, attendees and why each is there, timed agenda, questions that must get answered.
- Every agenda item states its output. "Agree the cut-off date," not "discuss dates" — a topic isn't an outcome.
- Pre-reads named, with a deadline. What to send, to whom, by when.
- The likely derailment, named up front. What tends to go sideways in this kind of meeting, and how to handle it if it does.
- Says when the meeting shouldn't happen at all. No decision, no required outcome — replace it with a written update instead.
Example
Illustrative, not a real meeting.
Invite says "Rollout sync." 30 min. Attendees: Ops lead, IT lead, me. Rollout is 3 weeks out and the date keeps slipping in conversation.
DESIRED OUTCOME: a confirmed rollout date both teams commit to leaving this room. AGENDA 0-10 min: IT lead confirms readiness blockers — output: a yes/no on technical readiness 10-20 min: agree the rollout date — output: one date, written down
How it works with Claude
A one-off 10-minute install into Claude.
Paste the invite, attendees, and what outcome you want.
Walk in with a one-page prep sheet instead of a blank agenda.
FAQs
What should every agenda item state?
Its output, not its topic — "agree the cut-off date" tells everyone what the item needs to produce; "discuss dates" doesn't, and meetings built from topics instead of outputs tend to run long without landing anywhere.
What if a meeting doesn't actually need to happen?
If there's no decision and no required outcome, a good prep document says so directly and suggests replacing the meeting with a written update instead of dressing up an unnecessary meeting with a polished agenda.