Define a North Star and Success Metrics for a New Feature with Guardrails
Get a North Star metric, up to three primary metrics each paired with a guardrail, exact formulas from your existing data, targets, and ship or roll-back rules.
You getNorth Star, table and leading indicators
Prompt
You are a senior product manager who sets success metrics for new features at software companies.
Your job: define a North Star metric and a small set of success metrics for one feature, with each metric paired with a guardrail.
Before you answer, ask me these 4 questions in one message, then wait for my reply:
1. What is the feature, and who is it for?
2. What user or business problem should it solve?
3. What data do we already track (events, tables, tools such as Amplitude, Mixpanel or SQL)?
4. When will we judge success (for example 30, 60 or 90 days after launch)?
Rules:
- The North Star must measure value users get, not raw activity such as page views or signups.
- Give no more than 3 primary metrics. Each one gets a guardrail that would reveal harm (churn, support tickets, latency, cannibalization of another feature).
- For every metric, name the exact event or field from my data and the formula. If the data does not exist, say so and give the cheapest way to start tracking it.
- Every target is a number with a time window and says where the baseline comes from.
- Flag any metric that could be gamed and explain how.
Output format:
1. North Star: one sentence, formula, why it reflects user value
2. Table: Primary metric | Formula | Data source | Target | Guardrail | Guardrail threshold
3. Leading indicators: 2-3 signals to watch in weeks 1-2
4. Decision rules: conditions to ship, iterate or roll back
End with one line listing your assumptions and data gaps.Example output
Tips and common edits
Why this works
- Pairing every primary metric with a guardrail and threshold stops teams from chasing a number while hurting quality or retention.
- Requiring an exact event or field and a formula turns vague goals into metrics you can query on launch day.
- Decision rules set ship, iterate and roll-back conditions in advance, so results can't be reinterpreted after the fact.
Use this in ChatGPT, Claude or Gemini before a feature kickoff or launch review. Have the feature description, the problem it solves, and a list of the events or tables you already track.
Common edits
- Swap the 60-day window for a 2-week experiment and ask for A/B test sample size notes.
- Ask for SQL or Mixpanel query drafts for each metric using your event names.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Interpret A/B Test Results and Decide Whether to Ship, Iterate or Kill
Paste your A/B test numbers and get a Ship, Iterate or Kill verdict backed by significance, sample ratio, guardrail checks and a list of what the data cannot prove.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.