Meeting agenda with timeboxes and decisions to make

You are an experienced facilitator. Help me plan a meeting.

Why the meeting is needed: [WHAT HAPPENED OR WHAT NEEDS TO BE DECIDED]
Participants and their roles: [e.g. "product lead, two engineers, marketing manager"]
Length: [e.g. "45 minutes"]
Format: [IN PERSON / VIDEO / HYBRID]
Topics people want to cover: [LIST, IN ANY ORDER]
Background material available: [DOCUMENTS, DATA, LINKS]

Produce:
1. A one-sentence purpose and the outcome we need by the end (decision, plan, shared understanding).
2. A check: could this be handled asynchronously instead? If yes, say how.
3. An agenda where each item is written as a question to answer, with an owner, a timebox in minutes and the type (inform, discuss, decide).
4. The order of items, with decisions placed early while people are fresh.
5. Pre-reads: what each participant should read or prepare, in under 10 minutes.
6. A short invite text with the purpose, agenda and pre-reads.
7. A parking lot rule and the last five minutes reserved for decisions, owners and next steps.

Rules: total timeboxes must equal the meeting length minus 5 minutes of buffer. Cut or postpone topics that do not fit, and tell me which.

Example (excerpt):
Purpose: Decide whether to delay the October release by one week.
Outcome: a go/no-go decision and an owner for customer communication.

| Question | Owner | Time | Type |
| What is still blocking the release? | Engineering lead | 10 min | Inform |
| Do we delay one week or ship with feature X disabled? | Product lead | 15 min | Decide |

Postponed: the roadmap review for Q1, which needs its own session.

When to use it

Use this prompt when you are about to send a meeting invite, especially for a meeting with several people, a decision to make or a history of running over time. It also helps when someone else asks you to “set up a quick sync” and you need to turn a vague request into something useful.

How to customize it

• [WHY THE MEETING IS NEEDED] is the starting point. If you cannot describe it in a sentence or two, the meeting probably needs a clearer purpose first.
• [PARTICIPANTS] helps the model assign owners and spot missing people, such as the person who must approve a decision.
• [TOPICS] can be a messy list. The model will turn them into questions, merge duplicates and drop what does not fit.
• [LENGTH] sets the hard limit for timeboxes. A shorter meeting with a clear outcome is usually better than a longer one.

Why it works

Agendas that list topics (“Release”, “Marketing”) invite open-ended discussion. Writing each item as a question with a type (inform, discuss, decide) tells everyone what “done” looks like for that item. Timeboxes and a buffer make the time limit real, and putting decisions early protects them from being squeezed at the end.

The asynchronous check is deliberate. Many status updates work better as a written note, which saves everyone time. Pre-reads under ten minutes are realistic enough that people actually do them.

Tips and variations

• Share the agenda at least a day ahead, so people can prepare or say they are not needed.
• Name a timekeeper who is not the person running the meeting.
• After the meeting, turn your notes into decisions and tasks with our meeting notes to action items prompt.
• For a project start, use our project kickoff brief as the pre-read.
• Ask for a version for a recurring weekly meeting that keeps a fixed structure.
• At the end of each meeting, spend one minute asking whether the agenda worked. Over time, the answers show which items need more time, which could move to a written update and which participants could skip the meeting altogether.