The task
You scheduled a 30-minute meeting with three colleagues for tomorrow at 2pm. The calendar invite says “design sync.” Two of the attendees were not in the conversation that prompted the meeting, one only joined the team last month, and you have a specific decision in mind that you have not yet articulated. Without an agenda the first 10 minutes will be context-loading, the middle 15 will be a discussion that drifts, and the last 5 will be you saying “let’s take this offline.” You want an agenda that turns the half-hour into one decision made and one owner assigned.
Where AI helps — and where it does not
AI is excellent at structuring time blocks, replacing “discuss” with “decide”, embedding a pre-read so the first 5 minutes are not context-loading, and naming an owner per segment so silence does not win. It is also good at writing a “if we don’t finish” fallback that prevents the awkward “let’s take this offline.” What AI cannot do: know which decisions actually need group buy-in vs. which should have been an async doc. If you put a status-round item in front of AI, it will dutifully schedule 10 minutes for it. Status rounds are not meetings; they are emails with chairs.
The named failure mode: the topic agenda. AI lists topics (“discuss pricing”, “talk about onboarding flow”) instead of decisions. Topics produce discussion; decisions produce outcomes. Force every segment to name a specific decision and a binary or multiple-choice option set.
What to feed the AI
- Meeting topic and length
- The one outcome you need by the end — be specific (“pick A or B for onboarding flow and name the prototype owner”)
- List of attendees plus their context level — who was in the prompting conversation, who joined last week
- Pre-existing artifact you can pre-read — doc, deck, Figma frame, screenshot
- 2-3 controversial points you expect debate on — so AI can pre-allocate time
- Decisions you’ve already made and want to communicate, vs. decisions still open
- Your facilitation style — strong opinions, neutral chair, async-first
- The fallback plan if you run out of time — defer, vote, escalate, async-resolve
Copy-ready prompt
Draft a 30-minute meeting agenda.
Topic: {one line}
Desired outcome (one decision made, one owner assigned): {paste outcome — be specific}
Attendees + their context level: {list with context — "X led the prior work, Y is new, Z is decider"}
Pre-read material: {link or 3-bullet context paragraph}
2-3 controversial points I expect debate on: {list}
Decisions already made (do not relitigate): {list}
My facilitation style: {strong opinion / neutral chair / async-first}
Fallback if we run out of time: {defer / vote / escalate / async-resolve}
Structure:
1) One-line goal — the decision and owner we need by end of meeting.
2) Pre-read — link plus 3-bullet context for anyone who didn't open the link.
3) Time-boxed segments. Each segment must name a SPECIFIC DECISION (not a topic) and the option set. "Pick: $9 / $12 / $15 starting tier" — not "Discuss pricing."
4) Owner per segment — the person who drives that decision in the room.
5) "If we don't finish" fallback for each segment.
6) Last 2 minutes: explicit recap — what was decided, who owns each next step, due date.
Rules:
- No segment may use the verb "discuss." Replace with "decide", "review", "approve", "rank", "pick."
- Sum of time-boxes = meeting length minus 5 minutes (5-minute recap buffer).
- Decisions already made do not get re-opened — list them at the top as "already settled."Shorter variant — 15-minute decision meeting
15-minute decision meeting agenda.
Decision needed: {one specific decision with option set}
Attendees: {names + roles}
Pre-read: {link or 3 bullets}
Output: 2-minute context, 8-minute decision, 5-minute owner + next step. Use "decide" not "discuss." Add fallback if we don't get to a decision.Sample output
A useful goal line: “By end of meeting: pick A or B for the new onboarding flow, and assign the prototype owner (target: clickable Figma by next Friday).” That beats “Discuss onboarding flow direction.”
A useful segment: “Minutes 5-15 — Decide: full-screen modal flow (A) or inline stepper (B)? Owner: Maria. Pre-read shows the 2 prototypes with click-through rates. Each person posts their pick in chat at minute 7 to avoid groupthink. If we cannot decide by minute 15, defer to async vote in Slack with Maria’s recommendation by EOD Friday.”
A useful “if we don’t finish” line: “Fallback: if pricing tier debate runs past minute 22, defer the $12 tier discussion to async and pick between $9 and $15 only in the room.”
A useful recap segment: “Minute 28-30 recap: ‘Decided X. Owner: Y. Next step: Z by date. Anything I got wrong?’ Silence equals agreement, but ask once explicitly.”
How to refine
- Decisions, not topics: “Every segment header must be a decision in the imperative (‘Pick:’, ‘Approve:’, ‘Rank:’). Anything starting with ‘Discuss’, ‘Talk about’, or ‘Review’ must be rewritten.”
- Name the option set: “For every decision, name the options. ‘Pick onboarding direction’ becomes ‘Pick: full-screen modal (A) or inline stepper (B).’ Otherwise the meeting opens with brainstorming when the work was option-narrowing.”
- Pre-load the controversy: “If a controversial point exists, allocate 1.5x normal time to it and put it second (not first — group needs warm-up, not last — emotions linger).”
- Force a pre-read: “Add a pre-read with 3-bullet TL;DR. If a decision requires reading 10 pages, the meeting starts at minute 10, not minute 0.”
- Bake in silence-killers: “Add at least one segment where everyone posts their pick in chat before discussion starts. Prevents the loudest voice from anchoring.”
Common mistakes
- No outcome stated — the meeting becomes a roving status round and nothing gets decided
- Pre-read missing — first 10 minutes get spent on context-loading and the decision gets squeezed
- “Discuss pricing” segments — discussion is not a decision; if you cannot name the decision, the meeting shouldn’t exist
- No owner per segment — silence wins, nothing happens, you reconvene next week
- Inviting 8 people for a 3-person decision — every extra attendee dilutes accountability and adds 2 minutes of context-loading
- No fallback for running over — you end with “let’s take this offline” and the decision drifts another week
- Re-opening decisions already made — wastes 10 minutes relitigating; list “already settled” items at the top
- Reading the agenda aloud at the start instead of recapping the goal — you’ve already lost 90 seconds
FAQ
- Should I send this in the calendar invite or as a Slack message?: Calendar invite body. People skim it 5 minutes before the meeting; Slack messages get lost in feeds. If the pre-read is heavy, send a Slack heads-up 24 hours before with the link.
- What if half the attendees do not read the pre-read?: Recap the goal in the first 30 seconds aloud. Repeat owners and decisions verbally — once is not enough. If a specific person consistently skips pre-reads, make that person the segment owner for the next meeting; ownership forces reading.
- Should I share the agenda only with attendees, or with stakeholders too?: Attendees first. Sharing with stakeholders pre-meeting makes the meeting feel performative and reduces honest disagreement.
- What about recurring meetings — same agenda template?: Same skeleton, fresh decision per occurrence. If the agenda is identical week to week, the meeting should be an async doc.
- Can I generate the agenda from a Slack thread that prompted the meeting?: Yes — paste the thread as pre-read context. AI will surface the implicit decision and the disagreement that’s been brewing.
Related
- AI meeting summary tutorial
- AI meeting action items
- Meeting Agenda Prompts for Decisions, Not Discussion
- AI Manager Update Email
- AI Exec Summary
- AI One-on-One Talking Points
Tags: #AI writing #Office #Workflow #Meeting