There is a meeting happening right now in a conference room somewhere in America where six people are nodding along to a conversation that will produce zero documented output.
Someone will send a vague follow-up email tomorrow. Someone else will have a different recollection of what was decided. A third person will ask for clarification next week. Nothing will ship on time. The cycle will repeat.
This costs U.S. companies an estimated $37 billion per year in lost productivity.
The fix fits in three prompts and takes ten minutes.
This is that system.
The Meeting Problem Nobody Talks About
Meetings are not the problem. The gap between meetings and action is the problem.
Most professionals are reasonably good at being in meetings. They show up, they listen, they contribute. What they are catastrophically bad at — systemically, culturally, almost universally — is converting the content of a meeting into a structured, actionable document that actually drives what happens next.
The average professional spends 4.5 hours per week in meetings (Atlassian, 2024). Of that time, roughly 20% is spent on what should happen after the meeting — recaps, action items, briefs, follow-ups. That’s 54 minutes per week of potential time recovered before you’ve changed a single habit.
The reason this gap exists is not laziness. It’s cognitive load. After a 45-minute meeting where you were actively listening, contributing, and processing, the last thing your brain wants to do is write a structured brief. So the brief doesn’t get written. Or it gets written badly. Or it gets written two days later when the details have faded.
The operator fix is to remove the cognitive load entirely and replace it with a three-step prompt chain that converts raw meeting notes into a finished, professional brief in the time it takes to brew a cup of coffee.
The Meeting-to-Brief Operator Chain
What you need before you start: Raw notes from your meeting. They don’t have to be clean. Bullet points, shorthand, fragments, whatever you actually wrote — paste it all in. The system is designed to work with messy input.
Total time: 8–12 minutes. Output: A polished meeting brief your entire team can act on immediately.
PROMPT 1 — The Notes Cleaner
This prompt takes your raw, messy notes and extracts the signal from the noise. It doesn’t create the brief yet — it organizes the raw material so the brief can be written accurately.
Role: You are an executive assistant with 15 years of experience supporting senior leaders. You specialize in taking messy, real-time meeting notes and extracting the essential content accurately and without interpretation.
Context: I just finished a meeting about [MEETING TOPIC]. The attendees were [LIST ATTENDEES AND THEIR ROLES — e.g., “myself (project manager), Sarah (VP Product), Marcus (lead engineer)”]. The meeting’s purpose was [MEETING PURPOSE — e.g., “to align on Q2 launch timeline and surface blockers”].
Task: Review my raw notes below and extract: 1. Every decision that was made (explicit and implicit) 2. Every action item mentioned (who owns it, what the deliverable is, when it’s due — if stated) 3. Every open question that was raised but not resolved 4. Any important context, constraints, or dependencies that came up 5. Anything that seemed uncertain, conflicting, or that might need follow-up clarification
Do NOT add anything that wasn’t in the notes. Do NOT interpret or editorialize. If something is unclear, flag it with [UNCLEAR: describe the ambiguity].
Format: Four sections with headers: Decisions, Action Items, Open Questions, Context/Flags. Use bullet points.
[PASTE YOUR RAW NOTES BELOW]
What you get: A clean, organized extraction of your meeting’s content with ambiguities flagged. This takes about 15 seconds to generate and is the foundation for everything that follows.
PROMPT 2 — The Brief Writer
Feed the output of Prompt 1 directly into this prompt.
Role: You are a senior program manager and expert communicator who writes meeting briefs that actually get read and acted on. Your briefs are known for being scannable, unambiguous, and immediately actionable.
Context: I need a meeting brief for the following meeting: - Meeting title: [MEETING TITLE] - Date: [DATE] - Attendees: [NAMES AND ROLES] - Meeting purpose: [PURPOSE]
This brief will be shared with [WHO RECEIVES IT — e.g., “the full project team”, “my manager”, “the client”, “cross-functional stakeholders”]. The primary goal of the brief is to [GOAL — e.g., “align everyone on decisions made”, “document action items for accountability”, “provide a record for people who couldn’t attend”].
Task: Write a complete meeting brief using the extracted content below. The brief must: 1. Open with a 2-sentence “Bottom Line Up Front” (BLUF) — what was decided and what happens next 2. Include a Decisions section (what was agreed, with enough context to understand the decision) 3. Include an Action Items table (Owner | Task | Due Date | Notes) 4. Include an Open Items section (unresolved questions + who’s responsible for answering them) 5. Close with a Next Steps summary (what needs to happen before the next meeting/checkpoint)
Format: Use headers, tables where appropriate, and keep the language precise. Total length: 300–500 words unless the meeting complexity requires more. Write it so someone who wasn’t in the meeting knows exactly what happened and what they need to do.
[PASTE EXTRACTED CONTENT FROM PROMPT 1]
What you get: A polished, complete meeting brief in professional format — the kind that makes your colleagues think you work twice as fast as everyone else. Because for this part of the job, you do.
PROMPT 3 — The Follow-Up Email
The brief is internal. The follow-up email is external — sent to stakeholders, clients, or partners. This prompt writes it from the brief.
Role: You are a professional communications specialist who writes follow-up correspondence after business meetings. Your emails are known for being clear, appropriately brief, and moving things forward without creating more back-and-forth.
Context: I just finished a meeting with [RECIPIENT DESCRIPTION — e.g., “a client”, “my manager and her team”, “external partners”]. The relationship is [RELATIONSHIP DESCRIPTION — e.g., “professional and collaborative”, “formal — I report to this person”, “vendor relationship where I’m the client”]. The tone should be [TONE — e.g., “warm but professional”, “formal”, “collegial”].
Task: Write a follow-up email based on the brief below. The email should: 1. Open with a one-sentence thank you or acknowledgment (not “per our conversation” — something genuine and specific) 2. Confirm the key decisions in 2–3 bullet points (concise — no re-explaining) 3. List any action items where the recipient is the owner 4. Flag any open items they need to respond to, with a suggested response deadline 5. Close with the next meeting/checkpoint and a clear ask for confirmation
The email should be under 200 words unless the meeting complexity requires more. Do not pad it.
Format: Write the email only. No subject line commentary before it. Include a suggested subject line at the top in brackets.
[PASTE THE MEETING BRIEF FROM PROMPT 2]
What you get: A follow-up email that takes one minute to review and send, reflects well on your professionalism, and creates a clear paper trail without requiring the recipient to re-read a 600-word wall of text.
The Complete System in Practice
Here’s what the workflow looks like from the end of a meeting:
Minute 1–2: Copy your raw notes into Prompt 1. Hit send. Minute 3: Review the extracted content. Fix any [UNCLEAR] flags from memory while the meeting is still fresh. Minute 4–6: Feed the cleaned content into Prompt 2. Hit send. Minute 7: Skim the brief. Make any edits needed. Minute 8–10: Feed the brief into Prompt 3. Review and send the follow-up email.
Total: One meeting. Ten minutes. A polished brief and a professional follow-up — both done before you’ve opened Slack.
Your colleagues are still writing their notes. You’re already moving.
The Compound Effect
This system’s real power isn’t in any single meeting. It’s in what happens when you run it consistently.
After 30 days of using this workflow, every meeting you attend produces a documented record. Every action item gets captured. Every decision has a paper trail. Ambiguities get flagged before they become blockers.
The people who build this habit in 2026 will be running the projects in 2027. Not because they’re more intelligent — because they’re operating on a different information infrastructure than everyone else in the room.
Operators don’t just do their jobs faster. They change the infrastructure of how work gets done around them.
That’s what the Nova AI system is built to deliver — one workflow at a time.
If you want the complete library, the Operator Pack on Gumroad has 20 prompts organized across 5 work categories, RCTF-formatted and ready to paste. At $17, it costs less than the time you’ll recover in a single week.
→ Get the Operator Pack — novamedia42.gumroad.com
— Nova AI
The system for operators. Free, weekly, no fluff.
P.S. We tested Claude, ChatGPT, and Gemini on this exact workflow. One model performed significantly better on the brief-writing step. The comparison issue is coming — and the results are genuinely surprising.
Nova AI | novaai.media | 617 Vista San Javier, San Diego CA