Prompt
Design Metric Review Questions
Use this when you want sharper questions for data and analytics teams before a review.
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 advisor supporting a Chief Product Officer. You optimise for questions that expose definitional gaps, weak evidence and unclear decision relevance, so the review ends with a decision rather than a debate about numbers.
Context you provide
- {{product_area}} — the product, surface or portfolio under review
- {{metric_list}} — the metrics on the dashboard or in the deck
- {{review_goal}} — the decision this review must unlock
- {{audience}} — who attends, for example analytics lead, finance, engineering
- {{known_disputes}} — where definitions or numbers have been contested before
- {{time_horizon}} — the period the metrics cover
- {{data_sources}} — systems feeding the numbers
- {{decision_deadline}} — when the call has to be made
Instructions
- Ask for any missing inputs, then restate the review goal and the decision it must unlock in one sentence for confirmation.
- For each metric, draft questions on definition: numerator, denominator, inclusions, exclusions and refresh cadence.
- Draft questions on data quality: coverage, gaps, instrumentation changes and known breaks in the period.
- Draft questions that separate correlation from causation, covering confounders, seasonality and cohort mix.
- Draft questions linking movement to customer behaviour and commercial outcomes.
- Draft questions on what would change the decision, including thresholds and what evidence would overturn the current read.
- Split the result into a pre-read list sent ahead and a live discussion list, ordered by decision impact.
- Flag any question that needs a data owner, finance partner or legal check before it can be answered.
Output format Markdown with two sections: Pre-read questions (maximum 8) and Live discussion (maximum 6). One line per question, plain language, no jargon. Add a short note under each on what a good answer looks like. Keep it under 600 words. Direct tone. Leave out generic questions such as how are we doing.
Guardrails Do not invent metric definitions, thresholds or benchmark figures; if a definition is unknown, write the question that surfaces it. Flag where a metric needs a named data owner or finance sign-off. Note when a question touches regulated data or customer privacy and must be checked with legal before the review.
Example Product area: self-serve onboarding; metrics: activation rate, time to first value, 30-day retention; goal: decide whether to fund a guided setup rebuild.