Meeting Prep in 5 Minutes: Briefings, Talking Points, and Questions for Any Upcoming Meeting

June 23, 2026

Why this prompt matters

The average professional spends more than 20 hours per week in meetings but under 9 minutes preparing for any individual one (Atlassian research). Unprepared meetings waste everyone's time, damage your credibility, and frequently fail to achieve their stated purpose. The problem is not motivation — it is that unstructured prep produces generic thinking. A structured 5-minute prep with role-specific talking points, targeted questions, and anticipated objections changes meeting outcomes more reliably than a 30-minute unstructured review. It is the difference between walking in thinking "I hope this goes well" and walking in knowing what you need to say, what you need to learn, and what to avoid.

What we use it for

You have a meeting in 30 minutes with a client you have never spoken to, a skip-level 1:1 you did not request, or a budget review where the stakes are higher than usual. You have your calendar, a few lines of context, and no time for a full research session. This prompt takes what you know and turns it into a structured prep doc you can skim in 2 minutes and walk in ready.

Prompt

Act as an expert executive briefing analyst who specializes in rapid meeting preparation.

I have an upcoming meeting with the following details:
- Meeting type: [ONE-ON-ONE / TEAM MEETING / CLIENT CALL / SALES CALL / PERFORMANCE REVIEW / NEGOTIATION / BOARD PRESENTATION / OTHER]
- Meeting title/purpose: [DESCRIBE THE STATED PURPOSE, E.G. "Q3 budget review" OR "first call with new enterprise prospect"]
- Attendees and their roles: [LIST NAME AND ROLE, E.G. "Sarah Chen, VP of Engineering; Marcus Lee, CTO; me (Product Manager)"]
- My relationship to the attendees: [E.G. "I manage Sarah, Marcus is my skip-level" OR "First time meeting, they are a potential client"]
- Key context I have: [PASTE ANY RELEVANT BACKGROUND — past emails, notes, LinkedIn bio, company website snippet, or prior meeting notes. If none, write "None."]
- My goal for this meeting: [WHAT DO I WANT TO ACHIEVE? E.G. "Get sign-off on the Q3 roadmap" OR "Understand their pain points and qualify them"]
- Time available to prepare: 5 minutes

Produce a structured meeting prep document with exactly these sections:

**1. 60-Second Situation Briefing**
A crisp 3-4 sentence summary of who I'm meeting, what matters to them professionally, and what the meeting is really about beyond the stated purpose. Write it as if briefing a busy executive who has zero context.

**2. My Objective (Stated vs Real)**
Two bullets: the stated objective of the meeting, and the real underlying objective — what I actually need to walk away with.

**3. What They Care About**
3-5 bullet points on what attendees are most focused on right now, based on their roles and context provided.

**4. My Three Talking Points**
The three most important points I need to make, each in one sentence. Lead with the point most likely to resonate with their priorities.

**5. Five Questions to Ask**
Five open-ended questions that reveal what I need to know and signal I've done my homework. Label each: [uncover pain] [build rapport] [qualify] [advance] etc.

**6. Likely Objections and Responses**
Two or three objections I might face, each with a one-sentence direct response.

**7. One Thing to Avoid**
One specific behavior, topic, or mistake that would derail this meeting given the context.

Constraints: Write concisely — every section must be skimmable in under 30 seconds. Do not use generic advice that could apply to any meeting; everything must be specific to the context I provided. Do not pad.

Result

Input scenario: Client discovery call with Meridian Health. Attendees: Rachel Doherty (VP Operations), James Sung (Head of IT). First call — they contacted us after our HIMSS demo. Meridian is a 3-hospital system in Ohio, ~4,500 employees, running Epic for EHR but managing scheduling in spreadsheets. James commented on LinkedIn about evaluating "workflow automation platforms." My goal: qualify them and book a product demo.

1. 60-Second Situation Briefing
Meridian Health is a regional 3-hospital system in Ohio (~4,500 staff) running Epic for clinical records but relying on manual spreadsheets for scheduling. Their Head of IT is actively researching workflow automation — likely because scheduling friction is creating operational or staffing headaches. Rachel Doherty (VP Ops) will be the economic buyer; James Sung will drive the technical evaluation. They reached out after seeing the product at HIMSS, which means they have some baseline interest — this is a warm lead at early evaluation stage.

2. My Objective (Stated vs Real)
• Stated: Discovery call to understand Meridian's workflow needs.
• Real: Qualify budget authority, pain severity, and decision timeline — then lock in a product demo with both Rachel and James present.

3. What They Care About
• Rachel (VP Ops): Staff utilization, overtime costs, scheduling errors that affect care delivery, avoiding workflow disruption
• James (Head of IT): Epic integration complexity, HIPAA compliance, IT team burden, vendor support quality
• Both: Not repeating a failed implementation that creates more problems than it solves

4. My Three Talking Points
1. Our platform integrates directly with Epic via HL7 FHIR — no duplicate data entry, no second system for staff to learn.
2. Healthcare customers in your size range typically reduce scheduling admin time by 40% within 90 days of go-live.
3. Our implementation team handles the full 6-week rollout with under 2 hours of IT involvement per week.

5. Five Questions to Ask
• "What does your current scheduling process look like on a typical Monday morning?" [uncover pain]
• "When you mentioned workflow automation, what outcome mattered most — cost, quality of care, or staff retention?" [clarify priority]
• "Who else at Meridian would be part of a decision like this — is there a CMO or CFO who would need to weigh in?" [map stakeholders]
• "Do you have a timeline in mind for making a change, or is this still in exploratory mode?" [qualify timeline]
• "What would need to be true for you to feel confident recommending a new platform to your leadership team?" [advance the deal]

6. Likely Objections and Responses
• "We're on Epic — we don't want to bolt on another system." → We don't sit beside Epic; we extend it. The scheduling layer runs within Epic's interface so staff never leave the application they already use.
• "Our team is fatigued from the last implementation." → Our 6-week deployment requires less than 2 hours of IT involvement per week. We handle configuration, testing, and training end-to-end.

7. One Thing to Avoid
Do not lead with pricing or ROI calculations. Rachel's primary concern appears operational, not financial — moving to cost too early in a healthcare context signals you are selling before you have listened.

prompt-engineeringproductivitymeeting-prepworkflowprofessional-skills