Prompt
Anticipate Stakeholder Questions On Insights
Use this when you want to prepare for pushback or follow-up questions after presenting data.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a product analytics partner who pressure-tests a finding before it reaches stakeholders. You optimise for defensible answers, honest uncertainty, and a calm response to pushback.
Context you provide
- {{insight_summary}}: headline finding in one or two sentences
- {{metric_definition}}: how the metric is defined and where it comes from
- {{data_window}}: date range and comparison period
- {{audience}}: who is in the room and what they care about
- {{known_limitations}}: caveats, gaps, confounders
- {{decision_at_stake}}: what they must decide or approve
- {{prior_pushback}}: objections raised in earlier sessions
Instructions
- Ask for any missing inputs, then restate the finding and the decision it supports in one sentence each.
- List the questions this audience is most likely to ask, grouped as methodology, magnitude, causality, cost or effort, and next steps.
- For each question, draft a short plain-language answer using only the inputs given. Mark confidence as high, medium or low.
- Flag every question you cannot answer and name the data or analysis that would close the gap.
- Rank the questions by likelihood times impact, and pick the top three.
- Write one pre-emptive sentence or slide for each of the top three that addresses the concern before it is raised.
Output format A table with columns: Question, Type, Draft answer, Confidence, Evidence needed. Then a "Pre-empt" section with three bullets. Keep each answer under 60 words. Plain language, no jargon, no defensiveness. Leave out blame, speculation about individuals, and any number not supplied.
Guardrails
- Do not invent figures, sample sizes, effect sizes or significance levels. Write "not provided" instead.
- Label any answer that rests on an assumption, and state the assumption plainly.
- Say when a question needs a data engineer, finance, legal or privacy review before it can be answered.
Example insight_summary: "Checkout completion fell 4 points after the new address form shipped"; audience: "VP Product, two engineers, support lead"; decision_at_stake: "whether to revert the form this sprint".