Skip to main content
TemplateFREE⏱️ 2-4 hours (definition); 30 minutes per weekly review

North Star Metric Template for Product Analytics

Define, decompose, and track your product's North Star metric. Includes input metrics, team alignment mapping, and a filled SaaS example with metric tree.

Updated 2026-03-05
North Star Metric
#1
140
#2
98
#3
84
#4
75
#5
75

Edit the values above to try it with your own data. Your changes are saved locally.

Get this template

Choose your preferred format. Google Sheets and Notion are free, no account needed.

Frequently Asked Questions

How do I choose between candidate North Star metrics?+
Test each candidate against three criteria: (1) Does it measure value delivered to customers, not just activity? (2) Does it lead revenue growth by at least 2-4 weeks? (3) Can multiple teams influence it through product work? If two candidates pass all three tests, pick the one that is simpler to explain. Alignment requires understanding, and understanding requires simplicity.
Can a company have more than one North Star metric?+
No. The purpose of the NSM is singular focus. If you have two "North Stars," you have zero. Individual teams can have their own input metrics, but the company-level NSM must be one number. Multi-product companies may have one NSM per product line, but each product line has only one.
How often should we change the North Star metric?+
Rarely. The NSM should be stable for at least 12-18 months. Changing it too frequently destroys organizational alignment and makes trend analysis impossible. Change it only when the product's core value proposition fundamentally shifts (pivot, new market, major product expansion).
What if the NSM is growing but revenue is not?+
This happens when the NSM does not actually lead revenue. Either the metric is wrong (it measures activity, not value) or there is a monetization disconnect (users are getting value but not paying for it). Investigate the correlation between NSM and revenue. If the correlation is weak, reconsider the metric.
How do I avoid teams gaming their input metrics?+
Two safeguards: (1) Pair every input metric with a "guardrail" metric that prevents gaming. If the input is "signups," the guardrail is "activation rate." If the input is "features shipped," the guardrail is "feature adoption rate." (2) Review the NSM alongside inputs. If an input improves but the NSM does not, the input improvement is hollow. ---

Related Tools

Explore More Templates

Browse our full library of PM templates, or generate a custom version with AI.