What is a Lag Indicator?
A lag indicator is a backward-looking performance metric that measures the result of an activity after it has occurred. Examples include revenue, profit margin, customer retention, and employee turnover. Lag indicators confirm whether a goal was reached, but the underlying behavior that produced the number has already happened and cannot be changed.
- Backward-looking by design: Lag indicators report outcomes such as revenue, churn, and defect rates after the work that produced them is complete.
- Cannot be moved directly: You can only influence a lag indicator by changing the upstream activities that a corresponding lead indicator tracks.
- Best paired, never solo: Used alone, lag indicators create surprise quarters; paired with two or three lead indicators, they become the score that closes the loop.
- Anchor for OKR Key Results: Most outcome-based Key Results are lag indicators, which is why OKR programs add weekly lead-indicator check-ins to stay actionable.
Definition: A lag indicator is a metric that occurs with a time delay and reflects past performance without being directly influenced.
What makes a metric a lag indicator
Lag indicators share three properties that separate them from leading metrics. First, they measure an outcome rather than an activity, so the data only exists after the work is complete.
Second, the value is shaped by many upstream variables, so no single team can move the number on demand. Third, the reporting cycle is slow: monthly close, quarterly NPS, annual retention, year-end audit.
The classic frame comes from Chris McChesney and the team behind The 4 Disciplines of Execution.
That asymmetry is the whole problem. By the time a CFO sees a missed quarter, the behaviors that caused it happened twelve weeks ago. Lag indicators tell you the score after the game is over.
Examples of lag indicators across functions
Lag indicators vary by function but share the same retrospective shape. The list below maps the most common ones used in modern operating models.
Function | Lag indicator | What it reports |
|---|---|---|
Finance | Revenue, EBITDA, free cash flow | Whether the quarter hit plan |
Sales | Closed-won ARR, quota attainment | Whether the pipeline converted |
Customer success | Net retention, churn rate, NPS | Whether existing customers stayed and recommended |
Product | Monthly active users, feature adoption rate | Whether shipped work changed behavior |
Operations | Defect rate, on-time delivery, cost per unit | Whether the process held standards |
People | Voluntary turnover, eNPS, time-to-hire | Whether the org retained and attracted talent |
A useful diagnostic question: if you held a one-hour meeting today, could you move the metric this week? If not, you are looking at a lag indicator.
Lag vs lead indicators
The pairing of lead indicators and lag indicators is the foundation of modern performance frameworks, from the balanced scorecard to the 4 Disciplines of Execution. The two metric types answer different questions.
Dimension | Lag indicator | Lead indicator |
|---|---|---|
Time horizon | Reports past results | Predicts future results |
Influence | Cannot be moved directly | Can be acted on this week |
Reporting cadence | Monthly, quarterly, annual | Daily or weekly |
Owner accountability | Hard to assign to one team | Owned by the team doing the work |
Example | Quarterly revenue | Number of qualified discovery calls |
Failure mode if used alone | Surprise misses, no time to correct | Activity theatre, no proof of impact |
Used together, a lead indicator predicts what a lag indicator will eventually report. The diet-and-exercise example is canonical: weight is the lag measure, calories consumed and minutes of cardio are the lead measures.
The lead measures are boring, weekly, and entirely within your control. That is exactly why they work.
Where lag indicators belong in an OKR or KPI system
Most outcome-based Key Results are lag indicators. "Grow ARR from 8M to 12M" or "Lift NPS from 32 to 45" both report what happened after the work. That is by design: OKRs are supposed to measure outcomes, not activity. The catch is that a lag-only OKR set leaves the team with no early signal during the quarter.
Strong OKR programs handle this in one of two ways. Either they pair every outcome Key Result with a weekly leading metric tracked in OKR check-ins, or they add a small number of activity Key Results the team can act on directly.
The second pattern shows up most often in sales and customer success orgs, where the conversion math from activity to outcome is well understood.
The same logic applies to KPI dashboards. A dashboard that shows only lag KPIs is a quarterly autopsy report. A dashboard that pairs every lag KPI with one or two lead KPIs becomes a steering tool.
Where lag-indicator programs typically break
Three failure patterns show up across implementations.
The first is over-indexing on lag indicators because they are easier to define. Finance teams already report revenue. HR already tracks turnover.
Treating those as the goal system is appealing because the data already exists. The cost: the operating cadence collapses into quarterly reviews, and corrective action is always twelve weeks late.
The second is treating any forward-looking metric as a lead indicator. A "qualified opportunities" count is only a lead indicator if the team has direct, this-week influence over it. If it depends on a marketing campaign that runs next month, it is a mid-cycle lag indicator wearing a lead-indicator label.
The third is the absence of a proven correlation between the lead and the lag. Bain and Company found that executives lose roughly 40% of their strategy's potential value to breakdowns in execution (Bain and Company, HBR 2017), and the most common breakdown is acting on lead indicators that never actually moved the lag. Validating the link with at least one historical cycle of data is the cheapest way to avoid it.
Using lag indicators in your quarterly cycle
Treat lag indicators as the scoreboard, not the play. Set them at the start of the quarter as outcome targets, then plan two or three lead indicators per lag that the team will move weekly.
Review the lead indicators in weekly OKR check-ins and the lag indicators in monthly business reviews. That cadence preserves the discipline of measuring real outcomes while giving the team something to act on between reviews.
The asymmetry stays useful as long as you respect it: lag indicators prove impact, lead indicators create it.
