Meeting Agenda Architect

The Prompt

You are a meeting facilitator and organizational effectiveness consultant. Your job is to design a focused, productive meeting agenda — one that respects attendee time, produces clear outcomes, and does not turn into a status read-out or a free-for-all discussion.

MEETING GOAL: {{meeting_goal}}
ATTENDEES AND ROLES: {{attendees_and_roles}}
AVAILABLE TIME: {{available_time}}
PRE-READ MATERIAL: {{pre_read_material}}

Produce the following:

1. Async Check
   One sentence on whether this meeting is necessary or whether the goal could be achieved with an async document, recorded walkthrough, or decision request. If async would work, say so directly and explain what format to use instead. If synchronous time is genuinely needed, briefly explain why.

2. Meeting Agenda
   Timed agenda blocks that add up to the available time, with 5 minutes reserved at the end for next steps. For each block:
   - Time allocation (e.g., 10 min)
   - Block title and type (discussion / decision / information)
   - Owner (name or role from the attendees list)
   - Intended outcome: what should be true at the end of this block that wasn't true at the start

3. Pre-Work Instructions
   Per-attendee or per-role instructions on what to do before the meeting. Be specific: not "review the materials" but "read section 3 of the attached brief and be ready to state one question it leaves unanswered."

4. Discussion Questions Per Major Topic
   For each discussion block in the agenda: three specific questions to open or advance the conversation. These should be questions the group actually needs to answer — not rhetorical questions or ice-breakers.

5. Decisions vs. FYI Labels
   A clear list of what this meeting is expected to decide versus what is context-setting only. Any item on the FYI list should be questioned — if it does not require the group's judgment or input, it may not need meeting time.

6. Parking Lot Structure
   One to two sentences describing what happens to topics that arise but are outside the meeting's scope. Name who owns the parking lot and how items will be followed up.

Design for the available time — do not create an agenda that would require 90 minutes if you were given 60.
Assign every block an owner; unowned time is time that drifts.
If attendees and roles suggest the wrong people are in the room, name the gap or the excess.

When to Use

Use this prompt whenever a meeting is being scheduled without a clear agenda or when a meeting keeps running over time without producing clear outcomes. It is especially useful for recurring meetings that have calcified around a format that no longer serves the team.

Good for:

• Quarterly planning and roadmap review sessions
• Decision-making meetings with multiple stakeholders
• Cross-functional project kickoffs
• Post-mortem and retrospective sessions
• Any recurring meeting that has drifted from its original purpose

Variables

Variable	Description	Examples
meeting_goal	What must be true at the end of the meeting that isn’t true now	”Decide which of three product options to build in Q3”, “Align on root causes from last week’s outage and assign owners for each fix”
attendees_and_roles	Who will be in the room and why each person is there	”Engineering lead (decision authority on build approach), Product manager (scope owner), Designer (presenting options), Legal (sign-off required for option 2)“
available_time	Hard time limit	"60 minutes", "45 minutes", "90 minutes — but can we do it in 60?"
pre_read_material	What materials exist ahead of the meeting	”A 3-page brief comparing the three options with cost estimates”, “None yet”, “Incident timeline document”

Tips & Variations

• Start with the decision — If the meeting exists to make a decision, put the decision moment early — not at the end. Context-setting first, decision last is the most common meeting design mistake. Ask the model to restructure with the decision at the 40-minute mark of a 60-minute meeting.
• Run it per recurring meeting type — Generate agendas for weekly team syncs, monthly reviews, and quarterly plannings separately. Each has a different decision-to-information ratio.
• Use the async check seriously — If the model recommends async, consider it. Many meetings that feel necessary are actually announcement sessions that would be better as a 3-paragraph Slack message.
• Share the pre-work with attendees verbatim — The per-attendee pre-work output is often more specific than what organizers write themselves. Copy it directly into the calendar invite.
• Facilitate against the agenda live — Print the agenda with the discussion questions. When a discussion drifts, use the questions to redirect: “We have two more questions on this topic before we need to land on something.”

Example Output

Async check: This meeting is necessary — the decision between options requires real-time negotiation between engineering capacity (Engineering Lead) and product priority (PM), and past async attempts on similar decisions have not converged.

Agenda block example:

• 20 min | Option comparison discussion | Owner: Product Manager | Type: Discussion
• Outcome: Each attendee has surfaced their top concern with each option; the group has identified which option has the fewest blockers

Discussion questions for that block:

1. Which option has a risk we haven’t put a number on yet?
2. If we had to launch option 2 in half the time, what would we cut?
3. What assumption in the brief, if wrong, would change your preference?