productivity

Turn Meeting Chaos Into Notes People Actually Read

Shape raw meeting scribbles into decisions, owners, and Slack-ready updates people can scan in thirty seconds.

What This Prompt Does

Pulls real decisions out of circular discussion.

Makes action items impossible to hide inside paragraphs.

Surfaces ignored risks without starting a fight in the doc.

When to Use It

After workshops, sprint planning, or customer calls.

When half the team missed the meeting but still has to execute.

When your notes are bullets on a phone and need to become official.

Best For:Team Leads And PMs

Example Input

Goal: create a meeting summary for team leads and pms
Audience: [describe who will read or use it]
Tone: [clear, practical, persuasive, friendly, formal]
Constraints: [word count, format, platform, examples, must-include points]

Example Output

Sample output:
- Objective: define the goal and audience clearly
- Draft: produce a structured first version with headings or bullets
- Refinement checklist: improve clarity, tone, examples, and final formatting

Useful Variations

  • Make the output shorter and more actionable for team leads and pms.
  • Rewrite the answer for a beginner audience and include concrete examples.
  • Turn the result into a checklist, table, or step-by-step workflow.

Customization Tips

  • Add real names, examples, target platform, and desired length before running the prompt.
  • Tell the model what a bad answer looks like so it avoids generic output.
  • Ask for one revision focused only on accuracy, clarity, or conversion depending on your goal.

Best Model to Use

Use ChatGPT, Claude, Gemini, or Grok, then refine the first answer with follow-up instructions.

Expected Output

  • A structured meeting summary tailored to team leads and pms.
  • Clear sections, bullets, or steps that are easy to edit.
  • A final answer that can be shortened, expanded, reformatted, or adapted for a specific platform.

Common Mistakes

  • Running the prompt without replacing placeholders with real context.
  • Asking for a final answer before defining audience, goal, tone, and constraints.
  • Publishing the output without checking facts, examples, links, claims, or brand voice.

The Prompt

Copy-Paste Ready
Here are messy notes from a meeting (or a rough transcript summary): [PASTE] Produce: 1) **TL;DR** in 2 lines. 2) **Decisions made** — who decided what. 3) **Open questions** that still need an owner. 4) **Action items** in a table: Task | Owner | Due date if known | Dependency. 5) **Risks or tensions** we politely ignored — name them without drama. 6) A short Slack-style message I can post in the team channel. Use clear headings. If names are missing, write OWNER TBD in caps.

How to Get Better Results

  • Replace generic placeholders with real audience, goal, product, topic, tone, and constraints.
  • Ask the model to create one draft first, then request revisions for clarity, length, examples, or formatting.
  • For important work, verify facts and adapt the final output to your own voice before publishing.
  • For productivity workflows, compare the output against your actual task instead of judging only the first response.

Related AI Resources

Pair this prompt with supporting pages across the site to get better output and compare alternatives.