KPI Tree

What it is and when to use it

A single result number — revenue, margin, satisfaction — tells you something is wrong but never what to do about it Monday morning. A KPI tree connects that result to two or three process indicators a manager can actually move that same week, and shows the causal link between them instead of a wall of metrics nobody owns. It works the same way for a service business or a retail floor as it does for a production line — the “product” just changes from units to visits, tickets, or bookings.

What goes on the sheet

1. Top-level (lagging) KPI: what it is, current baseline, and target
2. 2-4 process (leading) KPIs beneath it that a supervisor can move within the week
3. For each KPI: owner (one named person, not a department)
4. Review frequency per KPI (daily/weekly/monthly) and where it gets reviewed
5. Data source for each number, and how it's calculated
6. Evidence the leading indicator actually predicts the lagging one (historical check, not assumption)
7. Safety/non-negotiable indicators flagged separately, never traded off against commercial ones

In a business like yours

• Family play center: revenue splits into visits, conversion and average ticket, so the team knows which lever to pull.
• Restaurant: sales broken into covers, table turns and average check, with food safety as a locked guardrail.
• Service company: profit traced down to jobs per tech per day and callbacks.

Illustrative examples, not client cases.