Skip to content
← All Guides

The Meeting Brain

Turn one meeting into an output stack. Same input, five deliverables: a Slack update, an action list, a follow-up email, a status snippet, and a decision log entry.

Published June 19, 2026

Meetings don't create work. Unclear follow-up does.

You leave a 30-minute call with a vague sense of what was decided and three people waiting for something. So you reread your notes, try to reconstruct who owns what, and spend 20 minutes writing a recap email that nobody asked for. Then you do it again tomorrow.

The Meeting Brain is a system for turning one set of meeting notes into five operational outputs. Same input. Five deliverables.

How It Works

STEP 1

Capture

Take notes or let a tool transcribe.

STEP 2

Extract

Pull decisions, actions, owners, blockers.

STEP 3

Distribute

Send the right output to the right channel.

STEP 4

Log

Record what was decided for later.

You don't need all five outputs every time. Most meetings need two: the Slack update and the action list. Start there.

The Output Stack

Five outputs. One meeting. Use the ones the moment requires.

1 The Slack Update

Use when: Your team needs a quick async summary in a channel.

Paste this
You are a professional communicator who writes tight, scannable Slack updates. Here are my meeting notes: <PASTE NOTES> Write a Slack update that includes: - 1-line meeting summary (what was this about) - Key decisions made (bulleted) - Immediate next steps with owners - Any open questions or blockers Keep it under 150 words. No pleasantries. No emojis unless I ask.

What you get: A drop-in Slack message ready to post.

2 The Action List

Use when: You need a clean task list to paste into your project tracker.

Paste this
You are an operations analyst who extracts action items from messy meeting notes. Here are my meeting notes: <PASTE NOTES> Extract every action item. For each, provide: - Task (specific, starts with a verb) - Owner (name or role mentioned, or "Unassigned" if unclear) - Deadline (if mentioned, otherwise "TBD") - Priority (High/Medium/Low based on context) Format as a table. Flag any task where the owner or deadline is ambiguous.

What you get: A ready-to-import task table for Asana, Notion, Monday, or any tracker.

3 The Follow-Up Email

Use when: External stakeholders or clients need a written recap.

Paste this
You are a professional writer who drafts concise follow-up emails after meetings. Here are my meeting notes: <PASTE NOTES> The recipient is: <CLIENT NAME / STAKEHOLDER> My name is: <YOUR NAME> Write a follow-up email that includes: - Thank them briefly for the meeting - Summarize what was discussed (3-5 sentences max) - List agreed-upon next steps with owners - Offer to clarify anything Tone: professional but warm. Under 200 words. No fluff.

What you get: A polished email ready to send.

4 The Status Snippet

Use when: You need to drop this meeting into a weekly update or standup report.

Paste this
You are a concise status reporter. You turn meeting notes into brief project updates. Here are my meeting notes: <PASTE NOTES> Write a 3-5 sentence status update covering: - What was the meeting about - What moved forward - What's blocked or at risk - What happens next No bullet points. Write in plain prose. Keep it under 75 words.

What you get: A paragraph you can paste into any status doc, email, or Slack thread.

5 The Decision Log Entry

Use when: You need to document what was actually decided for future reference.

Paste this
You are a governance analyst who maintains decision logs. Here are my meeting notes: <PASTE NOTES> Extract every decision made. For each decision, provide: - Decision (one clear sentence) - Rationale (why this was chosen, if mentioned) - Alternatives considered (if mentioned, otherwise "Not documented") - Owner (who is accountable for execution) - Date (today's date) Format as a structured log entry. Flag any decision where rationale is unclear.

What you get: An audit-ready record of what was decided and why.

Meeting-Type Variations

Different meetings need different outputs.

Meeting TypeStart WithSkip
1:1sAction list, status snippetFollow-up email
StandupsSlack update, action listDecision log
Client callsFollow-up email, action list, decision logSlack update
Vendor meetingsDecision log, action listFollow-up email
Interview debriefsDecision log, status snippetSlack update, follow-up email

Add context to your prompt based on meeting type:

  • 1:1s: "Focus on my commitments, feedback received, and career-related items."
  • Standups: "Keep it extremely short. Focus on blockers and who's doing what today."
  • Client calls: "Tone should be polished and client-facing. No internal jargon."
  • Vendor meetings: "Flag any pricing, timeline, or contract commitments made."
  • Interview debriefs: "Focus on candidate strengths, concerns, hiring recommendation, and next steps."

The Automation Question

Don't automate all five outputs. Automate the one you repeat weekly.

If you're still changing the prompts every week, you're not ready to automate.

For most people, the Slack update is the first candidate. If you run the same team sync every Monday, wire it up. Otherwise, copy-paste is fine.

If you want to automateUse
TranscriptionGranola, Otter.ai, Fathom
Routing to Slack/NotionZapier, Make, n8n
One-click promptsClaude Projects with saved instructions

Start manual. Automate when you're sure you'll use it.

Try This in Your Next Meeting

  1. Take notes (or let Granola/Otter transcribe).
  2. Run The Slack Update and The Action List.
  3. Post the Slack update to your team channel.
  4. Paste the action list into your tracker.

Two outputs. Under 5 minutes. That's the minimum viable version. If it saves you time, come back for the other three.

Get new guides delivered every Tuesday.

AI news, prompts, and workflows you can use between meetings. Under 60 seconds.

Related Guides

AI Meeting Prep: Walk In Ready The AI Meeting Survival Guide How to Summarize Long Documents with AI