A KPI tree is a hierarchical breakdown of a top-level business metric into its underlying drivers, connected by explicit math. Each branch shows how a parent metric equals the sum, product, or ratio of its children, turning root cause analysis into a walk down the tree instead of a scavenger hunt across dashboards. A KPI tree is also called a driver tree or metric tree.
Dashboards show what changed. KPI trees explain why. When revenue drops 8%, a dashboard tells you revenue dropped. A KPI tree shows that returning customer count fell 12% while new acquisition grew, focusing the conversation on retention.
Every branch is a math relationship between a parent metric and its children: multiplication (Revenue = Traffic × Conversion × AOV), addition (ARR = New + Expansion − Churn − Contraction + Beginning), or ratio. The tree is auditable: every number reconciles up.
A value tree, or value map, starts from enterprise value and works down through the financial levers that determine it. A KPI tree uses the same decomposition logic but starts from whichever operating metric a team owns. A value tree is one KPI tree with enterprise value at the root. For the short definition only, see the KPI tree definition.
KPI tree methodology is the discipline of decomposing one metric into drivers that are mutually exclusive and collectively exhaustive, so every branch reconciles to its parent with no double counting and no gaps. Every branch is an identity rather than a correlation, siblings are MECE, and decomposition stops once a named team can move the leaf. Derived KPIs such as conversion rate or average order value are computed inside the tree by dividing two summable columns, which keeps every aggregate period correct.
For worked examples, see KPI tree examples and how to build a KPI tree. For a ready-made structure, see the KPI tree template.