1. Define the outcome metric

Choose the result the team is trying to change and define it precisely. Include the formula, unit, population, segment, time window, baseline, target, and deadline. “Improve activation” is not sufficient; “increase the percentage of new workspaces completing three core actions within 14 days from 22% to 32% by Q4” is operable.

Add guardrails that protect quality, economics, or risk. An activation initiative might track support contacts, refund rate, or downstream retention so the team cannot win the headline metric by creating a later problem.

2. Decompose the outcome into drivers

Ask what mathematically or behaviorally determines the outcome. Revenue may decompose into customers, purchase frequency, and average order value. Activation may decompose into eligible users, setup completion, time to first value, and repeated core behavior.

Keep decomposing until the team reaches drivers it can influence through a process, product change, channel decision, or resource allocation. Do not force every relationship into multiplication; label hypothesized behavioral links honestly.

  • Outcome or lagging metric
  • Direct business drivers
  • Leading operational indicators
  • Quality, cost, and risk guardrails

3. Define and validate each metric

Create a metric dictionary with business meaning, formula, inclusion rules, exclusions, source, refresh frequency, owner, and known limitations. Two teams using the same label with different denominators do not share a KPI.

Test the tree against historical data and domain knowledge. A plausible driver is not automatically causal. Use experiments, cohort analysis, and operational observation to refine the model.

4. Turn the tree into an operating cadence

Assign one accountable owner per metric and define the decision expected when it crosses a threshold. Review leading indicators frequently enough to act and lagging outcomes frequently enough to judge the strategy.

A good KPI review asks what changed, which driver explains it, what evidence supports that explanation, what action follows, who owns it, and when the team will know whether it worked.