methodatlas

Product Strategy Mapping tool

KPI Tree

Decomposes a measurable outcome into causally justified drivers and operational input metrics without presenting correlation as causation.

A KPI Tree connects outcome, driver, and input metrics. Every edge is a hypothesis about influence and needs a definition, formula, owner, and validation path. The tree supports control rather than decorating existing dashboards.

Core question
Which changeable drivers explain our outcome, how are they calculated, and which input metrics can teams control?
Plan KPI TreeMethod guide
Start comparison
Give feedbackIs this method useful to you?
Participants
3-8
Time
90-180 min initial, dann laufend

KPI Tree uses a hierarchical outcome-driver-input chain with a formula and hypothesis for every link. Assessments remain justified and context-bound.

Paper illustration of KPI Tree with its method-specific working model.

  1. Define outcome

    Define outcome

    Define outcome, population, window, formula, and guardrails unambiguously.

  2. Decompose drivers

    Decompose drivers

    Decompose the outcome into a few non-overlapping drivers and state every edge as a hypothesis.

  3. Define inputs

    Define inputs

    Set controllable inputs, definitions, data owners, and refresh cadence for each driver.

  4. Validate links

    Validate links

    Validate driver hypotheses through analysis or experiments and revise the tree on counter-evidence.

Review data quality and driver relationships monthly; version edges after experiments or strategy changes.

A good fit when

Useful for products or value streams with a clear outcome and measurable drivers. Clarify strategy and guardrails first when goals conflict.

Ideal for

  • Growth teams
  • OKR rollouts
  • Strategy alignment

Not good for

  • Early phases without data

Outputs

  • KPI tree

    KPI tree with traceable sources, assumptions, and domain decisions.

  • Decision and review trail

    Owners, dates, and next review for KPI tree.

KPI tree

Fictional worked example

a hierarchical outcome-driver-input chain with a formula and hypothesis for every link as a precise working structure with a fictional example.

Outcome

Definition · population · formula · window

Successful team reviews / active teams per week.

Drivers

Activation · repeat · value realisation · edge hypotheses

Activation within 7 days; reviews in 3 of 4 weeks.

Controllable inputs

Team-level actions and input metrics

Share of reviews with a prepared agenda.

Guardrails

Side effects and metrics that must not degrade

Abandonment rate and support cases per review.

Metric contracts

Formula · source · owner · quality · validation

Analytics owner; review_completed event; monthly edge check.

Every link is a testable influence hypothesis rather than established causality.

Amplitude: North Star Playbook

First step

Start with the core question: Which changeable drivers explain our outcome, how are they calculated, and which input metrics can teams control?

Open the method guide

Good to do first

A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric

Supplies the leading product metric that is broken down into drivers here.

Where to go next?

A paper-based illustration representing OKRs with its core stages and visible working result.
Product Strategy
OKRs

Translates confirmed drivers into measurable key results for the next period.

Growth Experiment workspace showing the question, observations, and next decision.
Growth
Growth Experiment

Tests a targeted intervention against the validated driver.

Deep dive

Purpose

When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.

How it works

It breaks a core metric down into its driving factors and makes cascades of cause and effect visible. Drivers, leading indicators, and target metrics are connected so that strategy becomes steerable through traceable levers.

In detail

A KPI Tree, also called a Metric Tree, is a hierarchical decomposition of a top metric into sub-metrics that affect the business causally. It is often used in growth teams, complements OKRs, or acts as a bridge between a North Star and the team backlog. Owners, current status, and levers are noted for each node.

Facilitation

Start at the top. Define clearly what counts as numerator and denominator for each node. Avoid artificial symmetry in the tree.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics
MetricsStrategyAlignmentMeasurement
Sources
Amplitude: North Star Playbookamplitude.comAmplitude; the North Star Playbook that connects customer, product and business language into one north star metric.
In playbooks
Derive Product Strategy from VisionMove from a shared product vision through a solid bet to a measurable KPI structure.
Artifact templates
KPI Tree: WorksheetPlan KPI Tree around its domain steps and the concrete decision question.
markdown

kpi-tree-working-template.md

Plan KPI Tree around its domain steps and the concrete decision question.

KPI Tree: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Establish and review the practice Time: 60–90 minutes initially; monthly 30-minute review

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Strategic outcome, Metric definitions and data sources, Known value drivers, shared workspace, source links, and decision log.
  • Roles: Product/business owner · Analytics · data owners · representatives of teams controlling inputs
  • Advance information: Collect Strategic outcome, Metric definitions and data sources, Known value drivers in advance and mark open assumptions.
  • Overall time needed: 60–90 minutes initially; monthly 30-minute review
  • Setup: Prepare a hierarchical outcome-driver-input chain with a formula and hypothesis for every link visibly and calibrate assessment terms before starting.

Prepare for the work steps

Define outcome: Define outcome

  • Strategic outcome
  • Metric definitions and data sources
  • Known value drivers

Decompose drivers: Decompose drivers

  • outcome definition
  • Metric definitions and data sources
  • Known value drivers

Define inputs: Define inputs

  • driver tree
  • Metric definitions and data sources
  • Known value drivers

Validate links: Validate links

  • metric contracts
  • Metric definitions and data sources
  • Known value drivers

KPI tree

Outcome

Definition · population · formula · window

...

Drivers

Activation · repeat · value realisation · edge hypotheses

...

Controllable inputs

Team-level actions and input metrics

...

Guardrails

Side effects and metrics that must not degrade

...

Metric contracts

Formula · source · owner · quality · validation

...

Enter only real input, sources, and decisions.

Amplitude: North Star Playbook

Define outcome: Define outcome

Expected artifact: outcome definition

outcome definition · source · uncertainty · next decision

Entry:

...

  • Can two analysts calculate the same value from the same raw data?

Decompose drivers: Decompose drivers

Expected artifact: driver tree

driver tree · source · uncertainty · next decision

Entry:

...

  • Are drivers jointly sufficient, separable, and plausibly influenceable?

Define inputs: Define inputs

Expected artifact: metric contracts

metric contracts · source · uncertainty · next decision

Entry:

...

  • Does every metric have a formula, source, owner, and known data gap?

Validate links: Validate links

Expected artifact: validation log

validation log · source · uncertainty · next decision

Entry:

...

  • Is the evidence supporting or weakening each critical edge explicit?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/kpi-tree/run-sheet

Alternatives and neighbors

Fitting alternatives with decision guidance, followed by other related methods.

All methods
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping

Instead of KPI Tree, choose Impact Mapping when you want to structure a goal-to-impact chain with stakeholders, outcomes, and actions.

Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics

Moves target group, value, goals, and priorities toward a concrete result through "name the main metric", "collect possible unintended side effects", and "use counter metrics alongside the main metric in reviews".

Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric

Moves technical problems, hypotheses, and next steps toward a concrete result through "formulate the goal clearly", "derive probing questions for each goal", and "set the review cadence".

Paper illustration of Product Vision Board with its method-specific working model.
Product Strategy
Product Vision Board

Vision, target group, needs, value, and business goals fit onto one board that exposes assumptions for validation.

Paper objective sheet with five SMART fields, baseline, target, owner, deadline and a complete result statement.
Product Strategy
SMART Goals

Formulates goals precisely enough that measure, relevance, and deadline together form a clear basis for steering.

Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework

Moves observations, needs, and patterns toward a concrete result through "define a goal for each HEART dimension", "identify signals for each goal", and "agree on a review cadence".

Constraints and origin
MediumWorkshop + async90-180 min initial, dann laufend

Profile

Method form
Mapping tool
Participants
3-8
Time
90-180 min initial, dann laufend
Maturity
Established
Origin
Praxisgemeinschaft
A paper-based illustration representing OKRs with its core stages and visible working result.
Next up: OKRs