North Star Metric Framework
A framework for defining and aligning your team around a single North Star Metric. Covers candidate evaluation, input metrics, counter-metrics, and a team alignment canvas. Free to copy, download, and use. No signup required.
# North Star Metric Framework **Product:** [Name] **Team:** [Team / Squad] **Author:** [PM Name] **Date:** [Date] --- ## What Is a North Star Metric? A North Star Metric (NSM) is the single metric that best captures the core value your product delivers to customers. It connects daily product work to long-term business outcomes. **A good NSM:** - Measures value delivered to the customer (not just business revenue) - Is sensitive to product decisions (moves when you ship good things) - Is lagging enough to be meaningful (not trivially gamed) - Can be understood by the whole team in one sentence --- ## Step 1: Candidate Metrics List 3–5 potential North Star Metrics. Be honest about why each one might not work. | Candidate Metric | What it measures | Risk / Why it might be wrong | |---|---|---| | [e.g. Weekly Active Users] | Breadth of engagement | Doesn't measure depth of value | | [e.g. # PRDs generated/week] | Core action completed | Could be gamed with low-quality output | | [e.g. % users who return D7] | Retention / habit formed | Lagging — slow to respond to changes | | [Your candidate] | | | --- ## Step 2: Our North Star Metric **North Star Metric:** > [Metric name and definition in one sentence] **Current value:** [X per week / month] **Target (12 months):** [Y] **How it's measured:** [Tool, query, or dashboard link] **Why this is the right NSM:** [2–3 sentences explaining why this metric captures value to the customer AND predicts long-term business health. If you can't explain this clearly, the metric isn't right yet.] --- ## Step 3: Input Metrics (Leading Indicators) Input metrics are the levers your team controls that drive the NSM. Break the NSM into 3–5 components. > Formula: NSM = f(Input 1, Input 2, Input 3...) | Input Metric | How it feeds the NSM | Owner | Current | Target | |---|---|---|---|---| | [e.g. Activation rate] | More activated users → more weekly actions | [Team] | [X%] | [Y%] | | [e.g. D7 retention] | Users who return drive weekly engagement | [Team] | [X%] | [Y%] | | [e.g. Feature adoption: X] | Users who use X are 3x more likely to return | [Team] | [X%] | [Y%] | --- ## Step 4: Counter-Metrics (Guard Rails) Counter-metrics prevent optimising the NSM at the expense of things that matter. | Counter-Metric | What it protects | Acceptable threshold | |---|---|---| | [e.g. Support ticket volume] | Quality — prevents shipping fast and breaking things | < [X] tickets/week | | [e.g. Time-to-value] | Onboarding — prevents engagement that hides bad activation | < [X] minutes | | [e.g. Churn rate] | Revenue — ensures engagement translates to retention | < [X%]/month | --- ## Step 5: Team Alignment Canvas Use this in your next all-hands or team meeting. **Our North Star Metric is:** ___________________ **It matters because:** [One sentence connecting NSM to customer value] **This quarter, we're moving it by focusing on:** [Top 1–2 input metrics] **We'll know we're succeeding when:** [NSM reaches X by date] **We'll know we're failing when:** [Counter-metric breaches Y] --- ## Common NSM Mistakes | Mistake | Example | Why it's wrong | |---|---|---| | Revenue as NSM | MRR | Measures business outcome, not customer value. Revenue follows value; it doesn't define it. | | Vanity metric | App downloads | Easy to game; doesn't measure whether users got value | | Too broad | "User satisfaction" | Unmeasurable; not actionable | | Too narrow | "% users who clicked button X" | Doesn't capture overall product health |
How to use this North Star template
Pick one metric — not two or three
The hardest part of this exercise is the forcing function of choosing just one. If you can't align on a single NSM, it usually means different team members have different theories of what value your product creates. Resolve that disagreement before writing code.
Validate that it moves when you ship good things
Look back at the last 3 features you shipped and check whether your candidate NSM moved. If it didn't respond to work you believe was valuable, it's either measuring the wrong thing or lagging too far behind actions.
Define input metrics before choosing initiatives
The input metrics section is where the NSM becomes actionable. Without input metrics, 'improve NSM' is not a workable strategy. Each input metric should map to a team or initiative that owns it.
Always pair the NSM with at least one counter-metric
Teams that optimise a single metric without guard rails often produce perverse outcomes — improving engagement at the cost of quality, or improving activation at the cost of retention. Counter-metrics prevent this.
Want a North Star grounded in your actual customer data?
PMRead ingests your customer interviews, feedback, and Slack threads — and generates PRDs backed by real evidence, not guesses.
Frequently asked questions
What are good North Star Metrics by product type?
B2B SaaS: weekly active teams, or key workflow completions. Marketplace: successful transactions per week. Consumer social: D30 retained users, or messages sent. Media/content: articles read to completion per user per week. The pattern: find the action that happens repeatedly when a user is getting real value.
Should the NSM be a rate or an absolute number?
Depends on your growth stage. Early stage: absolute numbers (e.g. 'PRDs generated per week') make it easy to see progress and are motivating. Growth stage: rates and ratios (e.g. '% of users who complete onboarding') are more meaningful because they normalise for user count and reveal efficiency.
How often should we review the North Star Metric?
The NSM itself should be stable for 12–18 months minimum. Changing it quarterly means you don't have a North Star — you have a metric of the month. Review your input metrics and targets quarterly; review the NSM itself only when your product strategy fundamentally changes.
Can different teams have different North Star Metrics?
Teams should share one company-level NSM. What differs is the input metrics each team owns. The growth team owns activation rate; the retention team owns D30 retention; the monetisation team owns conversion to paid. Each team's input metric should feed the shared NSM.
Other free templates