Method · May 13, 2026 · 6 min read

The growth metric tree, explained

"Grow faster" is not a plan. It's a wish. A metric tree is how you turn it into something you can actually work on.

What a metric tree is

A metric tree starts with one number you care about most, your North Star, and breaks it down into the inputs that drive it, level by level, until you reach things a team can directly influence.

For a B2B SaaS business it might look like:

• North Star: weekly active teams
• broken into new teams activated and existing teams retained
• new teams activated breaks into signups × activation rate
• signups breaks into traffic × signup conversion

Each branch keeps going until you hit a lever, a thing you can run an experiment against.

Why everything starts here

Without a tree, growth work is a pile of disconnected tactics: a landing page test here, an email there. With a tree, every tactic is attached to a number, and every number rolls up to the North Star. You can see why a piece of work matters before you do it.

The tree is also how we stay honest about results. If a number moves, we can trace it. If it doesn't, we can see that too.

Finding the binding constraint

The real payoff is prioritization. At any moment, one branch of the tree is the binding constraint, the input that, if improved, would move the North Star the most. Pour effort everywhere else and you're polishing branches that don't matter yet.

We use the tree plus a forecast to find that constraint, focus the experiment backlog on it, and re-check every week as the system moves.

How we build yours

In an AI Visibility Audit, we connect your analytics and product data, assemble the tree, set a baseline on every node, and identify the current constraint. You leave with the map, and a 90-day plan to move the node that matters most.

That map is the thing the whole system runs on. Everything else is downstream of getting it right.