Most companies do not lack indicators; they have too many. A typical management report lists dozens of KPIs, each one sensible on its own, with no visible link between them. When one turns red nobody knows how much it matters, and when the profit falls nobody can say which of the dozens explains it.
One goal, broken down until someone can act
A KPI tree starts from the one number the strategy is meant to improve and breaks it down, mathematically where possible, into its drivers. Each branch is split again until it reaches a measure that a specific team influences directly. The tree makes the logic of the business explicit: if this goes up by so much, that goes up by so much.
What the tree gives you
- Priorities: with a simple sensitivity on each branch you can see that one point of price realisation is worth more than five days of inventory, or the opposite.
- Ownership: every leaf has a team and every team can see how its number climbs to the top of the tree.
- Faster diagnosis: when the result moves, you walk down the branches instead of debating the whole report.
- Fewer metrics: an indicator that does not fit anywhere in the tree is a candidate to stop measuring.
Building one in a workshop
- Agree on the single top metric with the leadership team. Return on capital, free cash flow or economic profit work well because they balance growth, margin and capital.
- Break it down with real formulas first, then add the operational drivers that explain each formula term.
- Stop at the level where a single team can act and name the owner of each leaf.
- Put the values on the tree and review it monthly, from the top down.
A good KPI tree fits on one page and changes the conversation in the management meeting: from defending individual numbers to understanding how the business creates value, and where the next improvement will come from.
Bartor S.
Founder
