Comparing and connecting two approaches to strategic measurement
North Star Framework vs metric trees
The North Star Framework gives your organisation a single focal metric and the input metrics that drive it. A metric tree maps every causal relationship in your business from top to bottom. This guide compares the two approaches honestly, shows where they overlap, and explains why the most effective organisations combine them.
8 min read
What the North Star Framework is
In short
The North Star Framework is a product strategy model built around two components: a single North Star Metric (NSM) that captures the core value your product delivers to customers, and a small set of input metrics that represent the levers teams can pull to move it. The framework was popularised by Sean Ellis and the growth community, and later formalised by Amplitude in their product analytics work.
The North Star Metric sits at the centre of the framework. It is the single number that best reflects the value exchange between your business and your customers. For Spotify, it might be time spent listening. For Airbnb, nights booked. For a B2B SaaS product, weekly active teams. The metric should grow when customers are genuinely benefiting from the product, and that growth should correlate with long-term revenue. It is not a vanity metric, not a pure financial measure, and not something only one team can influence. It is the heartbeat of the product.
Beneath the NSM sit three to six input metrics. These represent the controllable factors that drive the North Star: things like new user activation rate, feature adoption depth, engagement frequency, and expansion triggers. Each input metric should be owned by a specific team or squad, and each should have a demonstrable causal link to the NSM. The framework explicitly avoids revenue as the North Star because revenue is a lagging consequence of value delivery, not a measure of it. Instead, revenue is expected to follow naturally when the NSM grows in a healthy, sustained way.
The elegance of the North Star Framework is its simplicity. It gives a fast-growing product organisation three things at once: a shared definition of success that transcends departmental metrics, a small number of input levers that teams can own and act on, and a causal hypothesis that can be tested over time. For early-stage companies and product-led growth teams, this is often enough to create focus and alignment without the overhead of a more elaborate measurement system.
How metric trees work
A metric tree is a hierarchical model of your entire business expressed through metrics and the causal relationships between them. At the top sits the outcome your organisation cares about most, often revenue, but sometimes a value-delivery metric like the NSM itself. Beneath it, every metric decomposes into the drivers that cause it to move. Those drivers decompose further into sub-drivers, and so on, until you reach the operational inputs that individual teams and contributors control day to day.
The defining characteristic of a metric tree is completeness. It does not stop at three to six input metrics. It maps the full chain of cause and effect from strategic outcomes to the granular levers that move them. A well-built metric tree might have three to five levels of depth and dozens of nodes. Every node has a named owner. Every parent-child relationship represents a testable causal hypothesis: when the child metric moves, the parent should move in a predictable direction and, ideally, by a quantifiable amount.
This structure serves two purposes that no other framework provides as naturally. First, it enables root cause diagnosis. When a high-level metric moves unexpectedly, you walk the tree downward through its children until you find the specific driver that shifted. This replaces hours of cross-functional debate with minutes of structured navigation. Second, it reveals leverage. Not all inputs have equal impact on outcomes. A metric tree connected to live data lets you identify which nodes have the strongest causal pull, so you can allocate effort where it will compound most effectively.
Where they overlap and where they differ
The North Star Framework and metric trees share a common foundation: both start with a single outcome metric at the top and decompose it into the inputs that drive it. Both reject the idea that teams should track metrics in isolation. Both insist on causal thinking rather than mere categorisation. If you squint, a North Star Framework diagram, with its NSM at the centre and input metrics radiating outward, looks like the first two levels of a metric tree. That is not a coincidence. They are drawing from the same intellectual tradition of systems thinking applied to business measurement.
The differences become apparent when you look at depth, scope, and how each framework handles complexity. The comparison table below lays out the structural contrasts.
| Dimension | North Star Framework | Metric tree |
|---|---|---|
| Depth | Two levels: the NSM and 3-6 input metrics | Three to five levels, from strategic outcome to operational inputs |
| Scope | Primarily product-focused; designed for product-led teams | Whole-of-business; covers product, marketing, sales, finance, operations |
| Relationships | Causal direction implied but rarely quantified | Explicit causal links, often with correlation data attached |
| Root cause diagnosis | Limited — when the NSM drops, you know which input to investigate but not why that input moved | Walk the tree from symptom to root cause through successive levels of decomposition |
| Ownership model | Each input metric is owned by a team or squad | Every node at every level has a named owner, creating accountability from top to bottom |
| Adaptability | The NSM and inputs are reviewed periodically but tend to remain stable | New branches and nodes are added as the business learns; the tree evolves continuously |
| Audience | Product and growth teams; often unfamiliar to finance or operations | Cross-functional; legible to executives, product teams, and operational leaders alike |
Neither framework is universally superior. The North Star Framework excels in contexts where simplicity and speed matter most: early-stage startups, newly formed product teams, or organisations that have never aligned around a shared metric before. It is a fast way to create focus. A metric tree excels in contexts where depth and precision matter: scaling organisations, multi-product companies, or businesses where cross-functional dependencies make a two-level model insufficient for understanding how value is actually created.
Combining the two: the NSM becomes your tree root
The most natural way to combine the North Star Framework and a metric tree is to make the North Star Metric the root node of your tree. The NSM already represents the core value your business delivers. It already sits at the apex of your strategic thinking. Placing it at the top of a metric tree does not change its meaning; it extends its reach. The input metrics from the North Star Framework become the first level of branches. And then the metric tree does what the North Star Framework does not: it keeps decomposing, level by level, until every team in the organisation can see a clear causal path from their daily work to the number that matters most.
In the tree above, "Weekly Active Teams" is the North Star Metric. The three input metrics from the North Star Framework, new team activation, engagement depth, and team retention, form the first layer of branches. But the tree does not stop there. Each input decomposes further into the specific drivers that teams can investigate and influence. When weekly active teams drops, you do not just know that retention is the problem. You can walk the tree to discover that product reliability declined, which dragged down the week-over-week retention rate, which reduced the total count of active teams. That diagnostic granularity is what the North Star Framework alone cannot provide.
This combined model also resolves a common tension in organisations that have outgrown the North Star Framework. As a company scales, three to six input metrics are no longer sufficient to cover the full surface area of the business. Marketing needs metrics for channel-level acquisition. Engineering needs metrics for deployment quality and incident response. Finance needs metrics for unit economics and cash efficiency. These metrics all matter, but they do not fit neatly into the North Star Framework without making it unwieldy. A metric tree absorbs this complexity naturally. The NSM and its input metrics remain at the top, providing the strategic focus the framework is known for. The deeper levels of the tree accommodate the operational detail that a growing organisation demands, without diluting the simplicity at the top.
Limitations of the North Star Framework that metric trees solve
The North Star Framework is a strong starting point, but like any simple model, its simplicity comes with trade-offs. As organisations mature, specific limitations emerge that a metric tree is structurally designed to address. Understanding these gaps is not a criticism of the framework; it is a recognition that different stages of organisational complexity require different levels of measurement depth.
Shallow decomposition
The North Star Framework stops at one level of decomposition: NSM to input metrics. When an input metric moves, the framework offers no structured way to investigate why. A metric tree continues decomposing through multiple levels, giving teams a diagnostic path from any high-level change to its operational root cause. The difference between "activation dropped" and "activation dropped because setup wizard completion fell after the last release changed the onboarding flow" is the difference between awareness and actionability.
Product-centric scope
The North Star Framework was born in the product-led growth community and it shows. The NSM and its inputs tend to focus on product engagement, activation, and retention. Functions like sales, finance, HR, and operations often struggle to see themselves in the framework. A metric tree is function-agnostic. It maps the entire business, including metrics that sit outside the product, like sales cycle length, gross margin, or employee attrition, and connects them to the same strategic outcome.
No feedback loops
The North Star Framework presents a one-directional model: inputs drive the NSM. In reality, business metrics form feedback loops. Higher engagement drives better retention, which drives word-of-mouth, which drives sign-ups, which feeds back into engagement. A metric tree can represent these circular dependencies explicitly, helping teams anticipate second-order effects and avoid optimising one input at the expense of another.
No guardrail metrics
The North Star Framework focuses on what to optimise but says little about what not to break. Aggressive activation improvements could degrade user experience. Engagement-boosting tactics could increase support load. A metric tree naturally accommodates guardrail metrics, constraints that sit alongside growth drivers, because every node in the tree is visible and monitored. When one branch improves while an adjacent branch deteriorates, the tree surfaces the trade-off immediately.
Limited cross-functional visibility
In the North Star Framework, teams outside product often cannot trace their contribution to the NSM. A marketing team running brand campaigns or a customer success team managing renewals may struggle to see how their work connects to the North Star. A metric tree makes these connections explicit. Every team can find their metrics in the tree and follow the causal path upward to the outcome that matters, creating genuine cross-functional alignment rather than product-team alignment with spectators.
Practical implementation
If your organisation already uses the North Star Framework, building a metric tree does not require starting from scratch. You already have the hardest part: a clearly defined North Star Metric and a set of validated input metrics. The work now is to extend downward, adding depth and rigour to the model you already have. The following steps describe how to make the transition smoothly.
- 1
Audit your existing North Star Framework
Start by documenting your current NSM and input metrics. For each input metric, write down the causal hypothesis: why do you believe this input drives the NSM? Rate your confidence in each hypothesis. If any input metric has a weak or unvalidated causal link, flag it for investigation. This audit often reveals that one or two of the original input metrics were chosen for convenience rather than causality.
- 2
Decompose each input metric one level deeper
Take each input metric and ask: what causes this to move? List the two to four drivers that sit beneath it. For "new team activation," the drivers might be sign-up volume, onboarding completion rate, and time to first value. For "engagement depth," the drivers might be core actions per session, session frequency, and feature adoption breadth. This single step of additional decomposition transforms your North Star Framework into a three-level metric tree.
- 3
Extend to operational inputs where needed
For the most critical branches, continue decomposing until you reach metrics that individual teams or contributors can directly influence. You do not need to decompose every branch to the same depth. Focus on the areas where your organisation spends the most effort or where you have the least clarity about what drives performance. A tree with uneven depth is perfectly normal and reflects the reality that some parts of your business are better understood than others.
- 4
Assign ownership to every node
In the North Star Framework, ownership sits at the input metric level. In a metric tree, every node has an owner. This does not mean every node needs a dedicated team. It means every metric has a named person who is responsible for understanding why it moves and escalating when it behaves unexpectedly. Ownership at every level prevents the common failure mode where input metrics are tracked but nobody is accountable for the drivers beneath them.
- 5
Connect to live data and review regularly
A metric tree on a whiteboard is a useful thinking tool. A metric tree connected to live data is an operating system. Connect each node to its data source so that values update automatically. Establish a regular cadence, weekly for operational levels, monthly for strategic levels, to review the tree, validate relationships, and update the model as the business learns. The tree should be a living artefact, not a planning-day deliverable.
The transition from North Star Framework to a full metric tree is not an overnight project, and it should not be. Start with the branches that matter most to your current priorities. Add depth where you have the most uncertainty. Let the tree grow organically as teams discover new relationships and challenge existing assumptions. Within two to three quarters, you will have a measurement system that preserves everything the North Star Framework gave you, a clear focal metric and a small set of strategic inputs, while adding the diagnostic depth, cross-functional coverage, and operational precision that a scaling organisation demands.
The organisations that get the most value from this combined approach are the ones that treat the tree as a shared model of reality, not a reporting tool. When a product manager opens the tree to understand why activation dropped, when a finance lead uses it to trace revenue variance to its operational source, when a new hire navigates it to understand how the business works, the tree is doing its job. The North Star Framework gave you the destination. The metric tree gives you the map.
Continue reading
Extend your North Star into a full metric tree
The North Star Framework gives you focus. A metric tree gives you depth. Place your North Star Metric at the root, decompose it through every level of your business, and give every team a clear line of sight from their daily work to the outcome that matters most.
