North Star metric tree template
Break your North Star metric into input metrics a team can move, and the levers behind each one.
Use this templateFree, opens in your browser. No sign-up.
What is a North Star metric tree?
A North Star metric is the single number that best captures the value customers get from your product, such as weekly active teams for a collaboration tool or nights booked for a travel marketplace. On its own it's too big for any one team to move, so a metric tree breaks it into input metrics that teams can influence, and the levers (projects and experiments) behind each input.
The template uses weekly active teams (teams with three or more active members) as its North Star. It branches into four inputs: new teams activated, invites accepted per team, sessions per member per week, and teams retained week over week. Each input has the levers that move it underneath, from faster onboarding and better templates to reminder emails and fixing the top churn reasons.
What's on the board
- Faster onboarding
- New teams activated
- Better templates
- Invite prompts
- Invites accepted per team
- Reminder emails
- North Star: weekly active teams (3+ members active)
- Notifications
- Sessions per member per week
- Integrations
- Weekly digest
- Teams retained week over week
- Fix top churn reasons
How to fill in the North Star metric tree template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser. Double-click any box to change its text.
- Write your North Star at the top. Choose a metric that reflects customer value and moves weekly rather than yearly. Define it exactly, including what counts as “active”.
- Break it into three to five inputs. Ask what has to rise for the North Star to rise: more new users, more of them sticking around, deeper or more frequent use. Each input should be measurable and owned by one team.
- Add the levers. Under each input, list the projects or experiments you expect to move it. Select a box and press Tab to add the next one, already linked.
- Test the logic both ways. Read the tree top-down (does this input really drive the North Star?) and bottom-up (would this project really move this input?). Remove branches you can't defend.
- Put numbers on it. Add the current value and a target to each metric, and revisit the tree every time you plan a quarter.
When to use it
- Setting team goals or OKRs that should add up to one company outcome
- Explaining why a project matters, from lever to input metric to North Star
- A dashboard has dozens of metrics and nobody agrees which ones matter
When to skip it
- Very early products still finding what customers value, where the North Star would change every month
- As a replacement for revenue and cost targets: the tree explains growth, it doesn't replace the business plan
Working on a product board in Kelvo
- Add notes fast
- Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Paste a table
- Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
Questions
What makes a good North Star metric?
It reflects the value customers get, not just what you earn; it predicts future revenue; it changes often enough to track weekly; and teams can move it through input metrics. Common examples are weekly active teams, messages sent and nights booked.
How many input metrics should a North Star have?
Usually three to five. They often cover breadth (how many people use the product), depth (how much they do), frequency (how often they come back) and efficiency (how quickly they get value).
How is a North Star metric different from OKRs?
The North Star is a long-lived measure of value that rarely changes. OKRs are goals for a set period; a good set of quarterly key results targets the input metrics in the tree.
Related templates
A/B test plan
Plan an experiment before it runs: hypothesis, variants, primary and guardrail metrics, sample size and the decision rules.
HEART metrics framework
Google's HEART framework for UX metrics: goals, signals and metrics for happiness, engagement, adoption, retention and task success.
Now / Next / Later roadmap
An outcome-based product roadmap without fake dates: what we're doing now, next, later, and what we're not doing.
PRD one-pager
A product requirements doc on one board: problem, goals, non-goals, users, requirements, metrics, risks and timeline.
Marketing funnel (AARRR)
The pirate-metrics funnel: Acquisition, Activation, Retention, Referral, Revenue, each with the metric to watch.
Ansoff growth matrix
Choose a growth strategy by pairing existing or new products with existing or new markets.