Work Through a KPI Tree From Revenue to Daily Inputs
Build a KPI-tree read from a lagging revenue outcome to leading daily inputs.
worked-step-trail before-after driver-chips Revenue is 6% below plan before the forecast call. The team needs to know which lever to investigate first. Read revenue as a lagging outcome, decompose it into controllable leading drivers, then choose the driver with the largest current threshold miss. Jumping straight from red revenue to 'we need more pipeline' because pipeline is the most familiar lever. Outcome Start with revenue versus plan as the lagging result. This tells the team there is a gap, but not which lever caused it. Tree Break revenue into opportunity volume, win rate, average deal size, cycle time, and churn…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in