PromptSharp › Prompt Library › Product Management › Metric definition sheet: define the success metric before the launch debate starts
Metric definition sheet: define the success metric before the launch debate starts
Two teams are already arguing about whether the launch worked, using different numbers. Define the metric precisely before results come in.
The prompt — copy and run it
You are a product analyst writing a metric definition sheet before a launch. I will describe the feature, its goal, and the data we collect. Produce: A) PRIMARY METRIC — name, exact formula, numerator and denominator definitions, time window, unit of analysis, and inclusion and exclusion rules. B) GUARDRAIL METRICS — 2-3 metrics that must not get worse, each with the same level of definition. C) EDGE CASES — how the metric handles new versus returning users, test accounts, partial sessions, refunds, time zones, and duplicate events. D) DECISION RULE — what result counts as success, neutral, or failure, written before launch, with the target left as "[SET TARGET]" if I have not provided it. E) DATA CHECK — the events or tables the metric depends on and how to confirm they are tracked correctly before launch. Inputs: [FEATURE + GOAL] · [EVENTS / TABLES AVAILABLE] · [STAKEHOLDERS WHO WILL READ THE RESULT] · [ANY EXISTING METRIC DEFINITIONS] Rules: Do not invent events, tables, or baselines — use only what I described and mark missing pieces. Verify the definitions with the data team and confirm tracking works before launch. Keep user-level and confidential business data out of consumer AI tools.
How to use this prompt
- Copy the full prompt above with the Copy button.
- Fill in your inputs. Replace each bracketed placeholder with your specifics:
[SET TARGET][FEATURE + GOAL][EVENTS / TABLES AVAILABLE][STAKEHOLDERS WHO WILL READ THE RESULT][ANY EXISTING METRIC DEFINITIONS] - Paste into ChatGPT, Claude, or Gemini and run. Read the reality guardrail below before you act on the output.
Why this prompt works
Launch arguments are often definition arguments in disguise: one team counts sessions, another counts users, and both are right about different numbers. Writing the formula, edge cases, guardrails, and decision rule before results exist removes that ambiguity and the temptation to pick whichever definition looks best afterwards. Checking tracking before launch prevents a result that cannot be measured.
Get a prompt like this in your inbox
The PromptSharp Product Brief ships one desk-ready prompt every weekday — free on the web today. The Product Management email edition is part of Pro: Vertical Pro is $14.99/mo, with a 14-day free trial, cancel anytime. Product Management Pro is open now: your emails start the next weekday after you subscribe, with full Pro issues within days. The Product Management prompt stays free on the web every weekday, and PromptSharp Daily (free) emails one prompt each weekday.
Email edition with Pro → Read a sample issueWant the full PromptSharp Product Brief, not just the free prompt? Vertical Pro is the full Pro benefit set for ONE vertical. See what Pro includes.
Card required. Free for 14 days, then $14.99/month — renews automatically until you cancel. Cancel anytime before day 14 and you won’t be charged. One free trial per card. Manage or cancel anytime.
Frequently asked
When should I use this prompt?
Two teams are already arguing about whether the launch worked, using different numbers. Define the metric precisely before results come in.
Why does this prompt work?
Launch arguments are often definition arguments in disguise: one team counts sessions, another counts users, and both are right about different numbers. Writing the formula, edge cases, guardrails, and decision rule before results exist removes that ambiguity and the temptation to pick whichever definition looks best afterwards. Checking tracking before launch prevents a result that cannot be measured.
What mistake does this prompt help you avoid?
Post-launch metric arguments: the formula, edge cases, guardrails, and decision rule are fixed before any results arrive.
Related Product Management prompts
Thirty-day launch review: did the feature do what the PRD said it would
The feature launched a month ago and the team has moved on. Check the results against the original goals before the lessons are lo…
Churned-user postmortem: exit verbatims + usage timelines to a ranked churn-driver table
A cohort churned last quarter and the room already 'knows why' (price, a competitor, onboarding). Turn the exit surveys and the ac…
Non-functional requirements pass: the performance, privacy, and failure states the PRD forgot
The PRD describes the happy path in detail and says nothing about speed, privacy, accessibility, or what happens when things fail.…
Experiment readout: from raw results to ship / iterate / kill
The A/B test ended. Write the readout that survives the skeptic in the room — validity checks, segment cuts, and a labeled-confide…
Roadmap trade-off memo: what we are not doing this quarter, and why
The roadmap is set and five teams asked for things that did not make it. Write the memo that explains the trade-offs so the no is …
Launch comms kit: one message, retuned for exec, sales, and support
You're shipping something and five audiences need to hear about it differently. Draft the whole comms kit from one source of truth…
Experiment design: a test that can actually be wrong
You want to run an A/B test but aren't sure it'll teach you anything. Design it so a null result is as informative as a win.…
All Product Management free prompts
The PromptSharp Product Brief page — five full free prompts plus today's issue.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt most weekday mornings, plus a Sunday roundup, rotating across the roster. Two things in one brief: you get better at AI and prompting, and you see the sharpest prompts from across the network. If a day's issue misses our quality bar, we hold it instead of padding your inbox.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Even a sharp prompt starts from zero unless your AI knows you. Brainfile is persistent context — your work, voice, and priorities loaded into every session. Brainfile is the memory; PromptSharp is the playbook. Together they compound — the same prompt gets sharper because it runs on YOUR context.
Set up your brainfile →Want both? The All-Access + Brainfile annual bundle covers the pair.
Home · Daily Issues · Prompt Library · Glossary · Pricing · For Teams & Universities · Archive · PromptFluent alternative · Newsletter · PromptSharp on Substack · Privacy · Terms · Refunds
Marketing · Sales · Dev & Engineering · Finance · Product Management · Vibe Coding · C-suite · Consulting & Strategy · Law · CPG · Personal Finance · Career & Job Search · Trading · Health & Fitness · Students · Focus & Productivity · Learning · Travel Planning
Entry Point Trading
Free weekly stocks to watch —
how our model ranks the S&P 500 and Nasdaq 100.