A KPI hierarchy separates the results the business cares about from the numbers that help explain why those results moved.
Start with the business result
Choose a small number of outcomes that describe sustainable performance. Revenue alone is rarely enough; margin, customer mix and repeat behaviour often change the interpretation.
Add the early indicators
Product discovery, checkout progress and returning-customer behaviour can show that something is changing before revenue catches up.
Keep diagnostics close to the work
Detailed metrics belong with the people who can act on them. They should explain one part of the journey, not compete for space in an executive report.
Use three levels, not one crowded dashboard
- Level 1: business results such as contribution, revenue quality, customer value and sustainable growth.
- Level 2: early indicators such as product discovery, journey progress and repeat behaviour.
- Level 3: detailed measures for the channel, page or journey the team can change.
A practical checkout example
Checkout completion can be an early indicator, but it needs context. Keep revenue quality visible, and give payment errors, delivery availability and device mix to the teams that can fix them. That stops a small funnel change being mistaken for a wider business improvement.
Review the hierarchy when the business changes
New markets, tighter margins, subscriptions or fulfilment limits can all change what good performance looks like. Review the hierarchy every quarter and remove numbers nobody uses.
If the team spends more time debating the dashboard than using it, the Measurement Foundation package can help sort out definitions, data checks and ownership.
Worked example