Anticipate presentation questions and prepare answers

Map likely audience questions to sourced answers, boundaries, follow-ups, and decision roles

6 min setupTested with:ChatGPTReviewed: 2026-08-28

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Presentation contentAudience perspectivesAnswer evidence and boundaries

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Anticipate audience questions and prepare grounded answers for the presentation.

Outline, claims, evidence, recommendation, and requested decision:
[presentation]

Roles, authority, goals, objections, positions, expertise, and sensitive issues:
[audience]

Sources, disclosure rules, unknowns, commitments, speculation limits, answer length, and follow-up owners:
[boundaries]

Generate questions that could test evidence, assumptions, alternatives, cost, feasibility, risk, ethics, equity, security, operations, ownership, timeline, measurement, and the requested decision only where relevant. Include supportive, skeptical, technical, implementation, and hostile-but-legitimate versions without caricaturing the audience. Rank by likelihood and consequence. For each provide a direct 20-second answer, supporting evidence, boundary or uncertainty, optional deeper answer, and follow-up owner/date if unavailable. Never invent a number, promise, legal conclusion, or authority. Add bridge phrases that acknowledge and answer rather than evade, and identify questions that reveal missing presentation content.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Presentation content: Request approval for a £7,500 four-week appointment-reminder pilot in two volunteer clinics. May baseline: 214 no-shows out of 1,840 appointments (11.6%); Finance estimates £18,900 unused-slot cost. Messages would contain date/time only. Privacy review is a launch gate. Measures proposed: delivery, opt-out/complaint, no-show comparison, staff burden. No vendor-effect evidence yet and no rollout authorization requested.
Audience perspectives: CFO challenges whether £7,500 is justified and asks about cheaper alternatives. Clinical director owns patient-safety concerns and worries about disclosure. Operations director can own the pilot but has limited coordinator capacity. Data lead may challenge comparison validity. Shared approval authority.
Answer evidence and boundaries: Use only supplied numbers. Vendor quote detail, delivery rate, patient phone-data quality, coordinator hours, privacy conclusion, and success thresholds are unknown. Finance owns cost method; Privacy owns review; Operations can confirm owner/capacity after meeting. Answers under 45 words, with deeper notes.

Example output

High consequence / likely—CFO: “Why spend £7,500 without proof this vendor works?” Direct answer: “We do not yet have vendor-effect evidence; the request funds a bounded test against the observed 214/1,840 no-show baseline, not a rollout. Approval should include success and stop criteria.” Deeper: compare the quote with alternatives once quote scope is supplied; Finance owns cost-method questions.

Clinical director: “Could a reminder disclose sensitive care?” Answer: “That risk is unresolved. Proposed messages contain date and time only, and no message will launch before Privacy approval. I cannot give a privacy conclusion today.” Follow-up: Privacy review owner/date not supplied.

Data lead: “How will you know any change came from reminders?” Answer: “The comparison design is not final. We propose recording baseline and pilot no-show rates plus delivery and operational factors; the data plan must define comparison clinics, denominators, and confounders before approval.” This exposes a missing slide.

Operations: “Who will do the work?” Answer: “The operational owner and coordinator capacity are not yet confirmed. The decision should be conditional on Operations naming both after the meeting.” Bridge: “That is a necessary constraint, not a detail I want to skip.” Cheaper-channel and phone-quality questions need evidence before answer; do not claim SMS is best.

Why this works

1
Role-specific questions reveal different standards of proof behind a shared decision.
2
Answer boundaries make saying what is unknown part of preparation rather than a live failure.