DS-301d · Module 1

Leading vs. Lagging Indicators

3 min read

Revenue is a lagging indicator. By the time it shows up in the metric, the actions that created it happened months ago. Pipeline velocity is a leading indicator. It predicts revenue before it arrives. The distinction is operational: lagging indicators measure results. Leading indicators predict them. A KPI system built entirely on lagging indicators is a rearview mirror — it tells you where you have been but not where you are going. A KPI system that combines leading and lagging indicators is a windshield and a rearview mirror — it shows both direction and destination. For every lagging metric in the hierarchy, identify the leading indicator that predicts it. Revenue is predicted by pipeline velocity. Retention is predicted by product usage frequency. Customer satisfaction is predicted by support ticket resolution time. The leading indicator is always more actionable because you can still change it.

Do This

  • Pair every lagging indicator with one or two leading indicators that predict it
  • Manage the business on leading indicators and report on lagging indicators
  • Validate the predictive relationship between leading and lagging with historical data

Avoid This

  • Build a KPI dashboard of only lagging indicators — you are measuring the past, not managing the future
  • Assume a metric is leading without testing the predictive relationship — correlation is not causation
  • Ignore lagging indicators because "leading is more actionable" — lagging indicators confirm whether leading indicator improvements actually produce outcomes