OKRs and metric trees: how they work together
Every article about OKRs and KPIs frames them as competing frameworks. They are not. OKRs set direction and ambition. Metric trees provide the structural understanding of cause and effect that makes every key result more rigorous. Here is how they work together.
9 min read
OKR vs KPI: the false choice
The core idea
OKRs and metric trees are not competing frameworks. They are complementary layers of the same system. OKRs tell you what to achieve and by when. Metric trees tell you how the business actually works, which levers connect to which outcomes, and where a change will propagate. You need both.
Search for "OKRs vs KPIs" and you will find hundreds of articles arguing for one over the other. The framing is almost always adversarial: choose OKRs for ambition, choose KPIs for accountability, pick a side. This is a false choice born from a misunderstanding of what each framework actually does. OKRs are a goal-setting cadence. Metric trees are a structural model of cause and effect. They operate at different levels of abstraction and serve different cognitive purposes. Asking which one to use is like asking whether you need a compass or a map. The compass gives you direction. The map shows you the terrain. You would not navigate difficult country with only one.
The "vs" framing persists because most organisations adopt OKRs without any structural model of their business underneath. They set ambitious objectives, brainstorm key results in a workshop, and launch into the quarter hoping the numbers they chose are the right ones. Three months later, they discover that the key result moved but the objective did not, or that the metric they targeted was a symptom rather than a cause. This is not a failure of OKRs. It is a failure of structural understanding. The OKR framework was never designed to tell you which metrics matter most or how they connect to each other. That is exactly what a metric tree does.
What OKRs do well
OKRs have earned their place in modern organisations for good reason. When implemented well, they solve several real problems that strategic planning alone cannot address. The framework originated at Intel and was popularised at Google precisely because it fills a genuine gap between annual strategy and weekly execution. Understanding what OKRs do well is essential before examining where they fall short, because the goal is not to replace them but to strengthen them.
Ambition and stretch
OKRs encourage teams to set goals beyond what feels comfortable. The distinction between committed and aspirational OKRs gives organisations a structured way to push boundaries without penalising teams for aiming high. Research on goal-setting theory, particularly the work of Locke and Latham, consistently shows that specific, challenging goals produce higher performance than vague or easy ones. OKRs operationalise this insight.
Alignment across teams
When every team publishes their OKRs, the entire organisation can see who is working toward what. This transparency reduces duplicated effort and surfaces conflicts early. A product team can see that their conversion rate objective aligns with the growth team's acquisition objective, or that their planned infrastructure work conflicts with a revenue target. Alignment does not happen automatically, but OKRs create the conditions for it.
Quarterly cadence
Annual goals decay rapidly. By the time Q3 arrives, the market has shifted and the priorities set in January feel disconnected from reality. OKRs reset every quarter, forcing teams to reassess what matters most given current conditions. This cadence is fast enough to stay relevant and slow enough to allow meaningful progress. It creates a natural rhythm of planning, execution, and reflection that annual cycles cannot match.
Focus and prioritisation
The constraint of three to five objectives per team forces difficult conversations about what matters most. When you cannot list everything, you must choose. This constraint is one of the most valuable features of OKRs, because it compels trade-offs that most planning processes avoid. Teams that set fifteen priorities have none. Teams that set three can concentrate their energy where it will have the most impact.
What OKRs miss
For all their strengths, OKRs have structural blind spots that become more apparent as organisations mature. These are not implementation failures or signs that a team is "doing OKRs wrong." They are inherent limitations of a framework designed for direction-setting, not for understanding the mechanics of how a business operates. Recognising these gaps is the first step toward addressing them.
No causal model
OKRs describe what you want to achieve but not how changes propagate through the business. A key result like "Increase trial-to-paid conversion to 8%" says nothing about what drives conversion, which sub-metrics influence it, or what trade-offs might emerge when you optimise for it. Without a causal model, teams are left to guess which lever to pull. They might invest in onboarding improvements when the real bottleneck is pricing page friction, or they might optimise for a metric that improves locally but damages something upstream.
Quarterly reset creates strategy debt
Every quarter, OKRs are retired and new ones are written. The institutional knowledge embedded in last quarter's OKRs, what worked, what did not, which assumptions were wrong, often evaporates during the transition. Teams start fresh rather than building on what they learned. Over multiple quarters, this creates a form of strategy debt: the organisation repeats patterns, revisits abandoned initiatives, and loses the compounding benefit of accumulated understanding.
Key results chosen without structural understanding
In most OKR-setting workshops, teams brainstorm key results based on intuition, past experience, and available data. This process rarely involves a rigorous analysis of which metrics actually drive the objective. The result is key results that feel reasonable but may be weakly connected to the outcome they are supposed to influence. A team might choose "Reduce churn to 3%" as a key result for a revenue objective without understanding that churn in their business is primarily driven by onboarding failures in the first fourteen days, not by ongoing product dissatisfaction.
No verified impact
OKRs track whether the key result number moved, but they rarely close the loop between the actions taken and the metric change observed. Did conversion increase because of the new onboarding flow, or because of a seasonal uplift? Did churn decrease because of the retention campaign, or because a large unhappy cohort had already left? Without a mechanism to verify causal impact, OKRs become a scorecard rather than a learning system. Teams celebrate green metrics without understanding what actually caused them.
What metric trees add
A metric tree fills precisely the gaps that OKRs leave open. It does not replace the goal-setting cadence or the alignment benefits of OKRs. Instead, it provides the structural foundation that makes every OKR cycle more rigorous. Think of the metric tree as the permanent map of the business that persists across quarters, while OKRs are the routes you choose to travel each quarter based on your current position and destination.
A persistent causal model
A metric tree maps how every metric in your business connects to every other. Revenue decomposes into its component drivers. Each driver decomposes further into the operational inputs that teams control. This model persists across quarters and across OKR cycles. It accumulates institutional knowledge about how the business actually works, rather than resetting that knowledge every ninety days. When you set OKRs against this structure, you can see exactly where each key result sits in the system and what it connects to.
Rigorous key result selection
Instead of brainstorming key results from intuition, teams can navigate the metric tree to identify which nodes have the highest leverage on the objective. If the objective is "Accelerate revenue growth," the tree might reveal that conversion rate improvement has a 3x stronger causal relationship with revenue than reducing churn in the current business context. This does not mean churn is unimportant, but it means the team can allocate effort based on evidence rather than gut feeling.
Root cause diagnosis
When a key result is off track mid-quarter, the metric tree provides an immediate diagnostic path. Instead of scheduling a cross-functional investigation, the team can trace the key result node downward through the tree to identify which sub-driver is underperforming. This turns a two-week investigation into a five-minute navigation exercise. More importantly, it surfaces the root cause rather than the symptom, so corrective action targets the right lever.
Cumulative organisational learning
Each quarter, the metric tree absorbs new data about the strength and direction of relationships between metrics. Actions taken against specific nodes are logged with their outcomes. Over time, the organisation builds an evidence base of what works: which levers have the most impact, which interventions produce sustained change, and which assumptions were wrong. This compounding knowledge is exactly what quarterly OKR resets tend to destroy.
How to connect OKRs to a metric tree
Connecting OKRs to a metric tree is not a theoretical exercise. It is a practical workflow that changes how teams set, track, and learn from their quarterly goals. The process starts with the tree and ends with OKRs that are structurally grounded rather than aspirationally vague. The following steps describe how to integrate the two frameworks into a single, coherent system.
- 1
Build the metric tree first
Before setting any OKRs, establish a metric tree that models how your business creates value. Start with your North Star metric at the top and decompose it through two to four levels of drivers. This tree does not need to be perfect or exhaustive. It needs to capture the most important causal relationships in your business. If you already have a metric tree, review it before each OKR cycle to ensure it reflects current reality.
- 2
Set objectives against tree regions, not isolated metrics
Rather than setting objectives in a vacuum, identify which region of the metric tree each objective targets. An objective like "Accelerate new customer acquisition" maps to a specific branch of the tree. This immediately clarifies the scope of the objective and prevents teams from accidentally optimising a metric that sits outside their area of influence. It also surfaces potential conflicts: if two teams set objectives that target the same branch, that conversation should happen before the quarter begins.
- 3
Select key results by navigating tree nodes
For each objective, navigate the relevant branch of the metric tree to identify the specific nodes that serve as key results. Instead of brainstorming "What metrics could we track?", the team asks "Which nodes in this branch have the highest leverage and are within our control?" This grounds key result selection in the causal structure of the business. A key result like "Increase conversion rate to 4%" is chosen because the tree shows that conversion rate is the highest-leverage driver of new customer revenue, not because someone suggested it in a workshop.
- 4
Track progress by monitoring the tree path
During the quarter, do not track key results in isolation. Monitor the full path from each key result node up through the tree to the objective. If conversion rate is improving but new customer revenue is flat, the tree will show you why: perhaps average deal size is declining, or the traffic mix has shifted toward lower-intent channels. This contextual monitoring prevents teams from celebrating key result progress that is not translating into objective progress.
- 5
Close the quarter by updating the tree with what you learned
At the end of each OKR cycle, feed what you learned back into the metric tree. Did the causal relationship between conversion rate and revenue hold as expected? Was the leverage estimate accurate? Were there unexpected side effects on adjacent nodes? This step is what transforms a quarterly planning exercise into a compounding knowledge system. Each cycle makes the tree more accurate, which makes the next cycle's OKRs more rigorous.
The following metric tree illustrates how this works in practice. An e-commerce business has Revenue as its North Star metric, decomposed into its causal drivers. During OKR planning, the team navigates the tree and selects specific nodes as key results. The key result "Increase conversion rate to 4%" maps directly to the Conversion Rate node, chosen because the tree shows it has the strongest causal link to revenue growth given current performance levels.
Notice that the key result is not floating in isolation. It sits within a structure that shows what drives it (Landing Page CVR and Checkout Completion Rate) and what it drives (Number of Orders, and ultimately Revenue). This context changes how the team thinks about the key result. They can see that improving Landing Page CVR is one path to the key result, and improving Checkout Completion Rate is another. They can also see that even if Conversion Rate improves, Revenue will only grow if Website Traffic and Average Order Value hold steady. The tree provides the contextual awareness that isolated key results lack.
The persistence advantage
The single most important difference between OKRs and metric trees is their relationship with time. OKRs are designed to reset. Every quarter, objectives are retired, key results are scored, and the slate is wiped for a fresh set. This cadence is valuable for maintaining urgency and relevance, but it carries a hidden cost: institutional knowledge about how the business works is discarded along with the objectives.
Consider a team that spends Q1 pursuing a conversion rate target. By the end of the quarter, they have learned that checkout page load time is the primary driver of cart abandonment in their business. They have data showing the relationship between load time and completion rate. They understand which user segments are most affected. This is valuable, hard-won knowledge about the causal structure of their business. But when Q2 arrives, the team sets new OKRs. The conversion rate work is "done" or "parked." The new objectives focus on retention. The knowledge accumulated in Q1 lives in a retrospective document that nobody will read again.
A metric tree prevents this loss. The relationship between checkout page load time and conversion rate does not disappear when the quarter ends. It is encoded in the tree as a permanent structural fact about the business, with correlation data that strengthens over time. When Q3 rolls around and the team revisits conversion rate, they do not start from scratch. They start from the accumulated evidence of every previous cycle. This is the compounding effect that OKRs alone cannot achieve.
“OKRs reset every quarter. The metric tree persists. Over time, the tree becomes the organisation's accumulated understanding of how the business works, a structural memory that makes every future quarter's planning more informed, more precise, and less dependent on intuition.”
There is a behavioural dimension to this persistence that deserves attention. Research on organisational learning, particularly the work of Argyris and Schon on double-loop learning, distinguishes between adjusting actions within existing assumptions (single-loop) and questioning the assumptions themselves (double-loop). OKRs naturally encourage single-loop learning: did we hit the number? Metric trees encourage double-loop learning: is our model of the business correct? When a team discovers that the assumed relationship between two metrics is weaker than expected, or that an undocumented driver has a stronger influence than anything in the current tree, they are updating the model itself, not just the targets within it. This kind of learning compounds across quarters and across teams. It is the difference between an organisation that gets better at hitting targets and one that gets better at understanding itself.
When to use each framework
The question is not whether to use OKRs or metric trees. It is understanding which situations call for the strengths of each framework and where combining them produces outcomes that neither can achieve alone. The following table maps common organisational situations to the framework best suited to address them.
| Situation | OKRs | Metric trees | Both together |
|---|---|---|---|
| Setting quarterly priorities | Define 3-5 ambitious objectives that focus effort | Identify which tree branches have the most leverage | Objectives grounded in structural understanding, key results selected from high-leverage nodes |
| Aligning teams across the organisation | Published OKRs make each team's focus visible | Shared tree shows how each team's metrics connect to company outcomes | Teams see both what others are targeting and how their work relates structurally |
| Diagnosing a metric that is off track | Flags that a key result is behind target | Traces the root cause through causal relationships to the driver that changed | Early warning from OKR tracking, rapid diagnosis through tree navigation |
| Building institutional knowledge | Quarterly retros capture lessons, but they are rarely revisited | Causal relationships and correlation strengths accumulate in the tree permanently | Lessons from OKR cycles are encoded as structural knowledge in the tree |
| Onboarding new team members | Current OKRs show what the team is working toward this quarter | The tree shows how the business works and where the team fits within it | New hires understand both the immediate priorities and the structural context |
| Evaluating the impact of an initiative | Did the key result number move? | Did the target node move, and did the change propagate as expected through the tree? | Confirmed outcome achievement with verified causal impact and no unintended side effects |
The pattern in this table is consistent. OKRs excel at creating focus, urgency, and alignment on what to achieve within a bounded time frame. Metric trees excel at providing structural understanding, causal diagnosis, and persistent knowledge. Neither is complete without the other. An organisation that uses only OKRs has direction without understanding. An organisation that uses only metric trees has understanding without cadence. The most effective approach treats OKRs as the quarterly rhythm and the metric tree as the enduring structure that makes each cycle more intelligent than the last.
Continue reading
Give your OKRs a structural foundation
OKRs set direction. Metric trees provide the causal understanding that makes every key result more rigorous, every quarterly cycle more informed, and every team more aligned. Stop guessing which metrics to target. Start with the structure.
