Leading and Lagging Indicators: Different Types of Measurement for Different Decisions

Definition

A leading indicator detects a change in Key Value Measures (KVMs) with relative speed, enabling faster response. A lagging indicator only shows change after a long delay. Critically, the same measure can be either leading or lagging depending on measurement frequency—revenue measured daily is a leading indicator; revenue measured only quarterly is lagging. Choosing which indicators to track determines whether an organization responds to problems early (leading) or discovers them post-hoc (lagging). True leading indicators allow inference about likely outcomes of lagging indicators before the lagging indicator has time to move.

In the Book

The Evidence-Based Management Guide states: "Leading indicators detect changes in KVMs with relative rapidity, enabling faster response, while lagging indicators may only show changes after a long delay. Many indicators are neither intrinsically leading or lagging, but only become one or the other depending on how frequently they are measured. Thus, when revenue is measured every day, it is a leading indicator, but when it can only be measured monthly or less frequently it becomes a lagging indicator."

The guide provides concrete examples: "Build and integration success is a fair predictor for the likely stability and predictability of the overall release" (leading), while "Revenue per Employee, or the Product Ratio...are influenced by so many contributing factors that they provide mostly only general ideas of how well the product is creating value" (lagging).

For customer satisfaction: "Leading indicators of customer satisfaction are hard to obtain, but usage data can serve as a proxy. Transaction abandon rates can give insight into successful completion of an activity, and simple usage data can at least inform whether features are being used." For employee satisfaction: "Leading information about Employee Satisfaction can be gathered using something as simple as a 'How was work today?' button."

Importantly, the guide warns about causality: "It requires human judgment and bottom-up intelligence to have meaningful data-driven conversation to hypothesize about the root causes behind shifts in indicators. These conversations might trigger new actionable insights, hypotheses and experiments."

Why It Matters

Organizations that track only lagging indicators (quarterly revenue, annual customer satisfaction surveys) are always fighting the last battle—problems are visible only after they have compounded. Leading indicators (daily build success, weekly usage patterns, real-time support ticket volume) enable early course correction. However, leading indicators are harder to identify and require more frequent measurement. The distinction forces teams to choose: do we want to know about problems early (and pay for frequent measurement), or do we accept latency in our knowledge? In any adaptive system, lag between decision and feedback determines response speed. The faster the feedback, the tighter the learning loop.