The KPI Tree Framework
One metric at the top. Everything else branches down from it. How to build a KPI tree that makes every team row in the same direction.
Key Takeaways
- A KPI tree starts with one North Star metric and branches into the 3-5 driver metrics that feed it.
- Every team should own exactly one branch of the tree. Shared ownership means no ownership.
- If two teams are optimizing for metrics that conflict, the KPI tree is broken.
- Build your KPI tree in 90 minutes with your leadership team. The alignment it creates is worth more than most strategy offsites.
I walked into a company last year where the product team tracked activation rate, the sales team tracked pipeline value, the CS team tracked NPS, and the CEO tracked revenue. Four teams, four metrics, zero alignment.
Everyone was hitting their own numbers. Revenue was flat.
This is what happens when metrics are chosen in isolation. Each team picks the metric that makes them look good, and nobody connects them into a system. The KPI tree fixes this.
How It Works
A KPI tree is a visual hierarchy. One metric at the top. Everything else branches down from it.
Level 0: North Star Metric. The single number that best represents the value your company delivers. For most B2B SaaS companies, this is Monthly Recurring Revenue or Net Revenue Retention. Pick one.
Level 1: Driver Metrics (3-5). These are the inputs that directly feed the North Star. For MRR, the drivers might be: New Logo MRR, Expansion MRR, Churned MRR.
Level 2: Team Metrics (2-3 per driver). Each driver breaks into metrics that individual teams control. New Logo MRR breaks into: Qualified Pipeline (marketing), Win Rate (sales), Average Deal Size (sales + product).
Level 3: Activity Metrics. The leading indicators that predict team metrics. Qualified Pipeline breaks into: Campaigns Launched, MQL Volume, MQL-to-SQL Conversion Rate.
Building Your Tree
Step 1: Put your North Star at the top. Write it on a whiteboard.
Step 2: Ask: "What are the 3-5 inputs that directly determine this number?" Write them on the next level down. Draw lines connecting them.
Step 3: For each Level 1 metric, ask: "Which team owns this, and what do they control that moves it?" Those become Level 2.
Step 4: Check for conflicts. If two teams are optimizing for metrics that pull in opposite directions (marketing optimizing for lead volume while sales needs lead quality), you have found a misalignment. Fix it by choosing which metric takes priority.
Step 5: Assign ownership. Every metric at Level 2 gets one name next to it. Not a team. One person.
The whole exercise takes about 90 minutes with your leadership team. The clarity it produces is immediate.
The Conflict Test
The most valuable part of building a KPI tree is finding the conflicts. In one company, I found that the product team was optimizing for feature adoption (which required long onboarding flows) while the sales team was optimizing for time-to-close (which required fast onboarding). Both were rational strategies that canceled each other out.
The KPI tree exposed the conflict, and we resolved it by defining a shared metric: time-to-first-value. Both teams could optimize for it without working against each other.
Common Mistakes
Too many metrics. If your tree has more than 20 metrics across all levels, it is too complex. Nobody can track 20 things. Aim for 12-15 total.
Vanity metrics at Level 2. Page views, app downloads, and social followers are not driver metrics. They are activity metrics at best. Keep Level 2 focused on metrics that directly predict revenue.
No owner. A metric without a named owner is a metric nobody manages. Assign one person to every Level 2 metric.
Your First Step
Get your leadership team in a room for 90 minutes. Whiteboard your North Star at the top and build down from there. You will find at least one conflict and at least one metric that nobody actually owns. Fix those two things and you will see alignment improve within 30 days.