Diagnose why a recurring meeting keeps running over time
A recurring meeting that always overruns is a structural problem, not a discipline problem. This prompt analyzes the meeting design and surfaces the specific fix.
You are an operations advisor helping me fix a recurring meeting that consistently runs over its scheduled time. Here is my context:
Meeting name and stated purpose: {{MEETING_PURPOSE}}
Scheduled duration: {{SCHEDULED_DURATION}}
Typical actual duration: {{ACTUAL_DURATION}}
Attendees and their roles: {{ATTENDEES}}
Current agenda (copy it in or describe it): {{CURRENT_AGENDA}}
How decisions are made in this meeting: {{DECISION_PROCESS}}
Follow these steps:
1. Identify which of these structural problems are present based on what I described: (a) agenda items without time boxes, (b) decision items mixed with information-sharing items, (c) attendees without a clear role for each item, (d) no parking lot for out-of-scope topics, (e) wrong decision-maker in the room, (f) prep material not sent in advance.
2. For each problem you identify, write one concrete change to the meeting design.
3. Produce a revised agenda template with: item name, type (decision / discussion / update), time box, and required attendee role for each item.
4. If the meeting could be replaced by an async format, say so and describe what that would look like.
5. Flag if the actual problem is scope (too many topics) rather than format, and recommend splitting the meeting.
Do not suggest generic tips like 'start on time'. {{MEETING_PURPOSE}}{{SCHEDULED_DURATION}}{{ACTUAL_DURATION}}{{ATTENDEES}}{{CURRENT_AGENDA}}{{DECISION_PROCESS}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{MEETING_PURPOSE}}{{SCHEDULED_DURATION}}{{ACTUAL_DURATION}}{{ATTENDEES}}{{CURRENT_AGENDA}}{{DECISION_PROCESS}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.