Prompt Vocab Mastery
2026-10-16
•
By Sanjeev Kumar
Lesson 7: Meeting Minutes & Deliverables
It is 2:00 PM. You just walked out of a long project sync. You have a raw text transcript from Zoom, Teams, or your notes. You need to send out minutes and next steps. If you just ask the AI to “give me the minutes,” you will get a chronological narrative of who spoke when. You need structured, accountability-driven summaries.
The Minutes Swap Table
| # | Generic Term | Precise Alternative | Output Benefit |
|---|---|---|---|
| 1 | What people must do | Extract actionable deliverables & owners | Pairs specific tasks directly with names, ensuring accountability. |
| 2 | Decisions | Resolutions & consensus points | Targets finalized decisions, ignoring open debates. |
| 3 | Summarize meeting | Compile post-meeting digest | Formats the summary into a clean, email-friendly structure. |
| 4 | Who was arguing | Identify core friction points | Isolates disagreements or unresolved issues for future focus. |
| 5 | When to do things | Target dates / Project milestones | Generates a clean timeline grid of deadlines and milestones. |
Example 1: Actionable Deliverables
- Noob Prompt:
Tell me what people agreed to do in this transcript. - Pro Prompt:
Extract actionable deliverables and owners from this meeting transcript. - Alternative Scenario Combinations:
- Scenario A: Engineering Sprints ➡️
Extract all technical features from this transcript and map them to engineering sprint tickets. - Scenario B: Content/Design Tasks ➡️
Extract all marketing copy requirements and design tasks, assigning them to the content team. - Scenario C: Operations Logistics ➡️
Extract all facilities and logistics tasks from this transcript, listing the operations owners.
- Scenario A: Engineering Sprints ➡️
- Why It Works: Specifying the task domain (engineering, design, operations) prompts the AI to capture industry-specific terms (sprints, copy requirements, logistics) instead of general tasks.
Example 2: Documenting Resolutions
- Noob Prompt:
What did we decide on in the meeting? - Pro Prompt:
Document all resolutions and consensus points from this discussion. - Alternative Scenario Combinations:
- Scenario A: Database Architecture ➡️
Document all database architectural approvals and system design consensus points from this transcript. - Scenario B: Budget Sign-off ➡️
Document all budget approvals, spending limits, and financial sign-offs finalized in this meeting. - Scenario C: HR Policy Revisions ➡️
Document all remote-work policy revisions and consensus agreements from this discussion.
- Scenario A: Database Architecture ➡️
- Why It Works: Directs the model’s focus to formal agreements in specific domains, filtering out general discussion or debates.
Example 3: Post-Meeting Digest
- Noob Prompt:
Write meeting minutes for this transcript. - Pro Prompt:
Compile a post-meeting digest from this transcript. - Alternative Scenario Combinations:
- Scenario A: Client-Facing Brief ➡️
Compile a professional client-facing post-meeting digest. Highlight next steps and milestones. - Scenario B: Developer Team Update ➡️
Compile an internal developer team digest, focusing on API dependencies and code freezes. - Scenario C: 3-Sentence Executive Update ➡️
Draft a 3-sentence executive update email summarizing the meeting outcomes.
- Scenario A: Client-Facing Brief ➡️
- Why It Works: Directs the structure of the digest to match the audience (client, developer team, executives) with appropriate terminology.
Example 4: Friction & Unresolved Issues
- Noob Prompt:
Who was fighting or arguing in the meeting? - Pro Prompt:
Identify core friction points and unresolved issues from this debate. - Alternative Scenario Combinations:
- Scenario A: Technical Debt ➡️
Identify all technical debt concerns and legacy code friction points discussed in this transcript. - Scenario B: Resource Bottlenecks ➡️
Identify resource bottlenecks and staffing friction points highlighted by team leads. - Scenario C: Budget Discrepancies ➡️
Identify all budget disagreements and pricing friction points from this discussion.
- Scenario A: Technical Debt ➡️
- Why It Works: Framing the search around “friction points” extracts structural problems rather than personal disagreements.
Example 5: Target Dates
- Noob Prompt:
When does everything need to be done based on the meeting? - Pro Prompt:
Extract the project milestones and corresponding target dates. - Alternative Scenario Combinations:
- Scenario A: Product Launch ➡️
Extract all product launch milestones and their corresponding target release dates. - Scenario B: Marketing Calendar ➡️
Extract all campaign launch dates, draft deadlines, and publishing milestones. - Scenario C: Legal Compliance ➡️
Extract all audit submission dates and compliance milestones from this transcript.
- Scenario A: Product Launch ➡️
- Why It Works: Restricts the timeline search to specific deadlines and compliance schedules, ignoring conversational timing chatter.
Put It Into Action
Pick one of the exercises above:
- Open your favorite AI tool, paste the Noob Prompt, and look at the response.
- In a brand-new chat session, paste the corresponding Pro Prompt or one of the Alternative Scenario Combinations.
- Compare the outputs. See how different vocabulary mixes completely shift the focus, structure, and quality of the response!
SK
Written by
Sanjeev Kumar
Founder & Lead Engineer at PrepNew. Building cross-platform Flutter applications, serverless AI backends, and full-stack Dart web architectures.
Continue Reading