Leading vs lagging indicators

Friday review. The bookings tile is green. Everyone relaxes. Monday morning, three large deals that were “sure things” slip a quarter. Pipeline coverage was already thin last week, but it sat on page two of the dashboard in a smaller font. The room optimized for a lagging win signal and ignored the leading warning. That pattern is so common it feels like weather. It is not weather. It is metric design.

This is Part 2 of Metrics that matter. Part 1 built the chain from objective to behavior to measure to target. Here we split measures into two jobs people mix up constantly: leading indicators and lagging indicators. You need both. You manage them differently. If KPI basics still feel fuzzy, keep All About KPIs open as the prequel. For the series map and related paths, see Learn.

What you’ll learn

Plain definitions of leading vs lagging indicators (no finance jargon required)
Why lagging metrics win meetings while leading metrics win weeks
How to pair them so you do not manage only rear-view mirrors
One full B2B sales example with a comparison table and coaching uses
Mistakes that turn “leading” into vanity activity counts

Two clocks on the same business

A lagging indicator tells you what already happened. Revenue last month. Churn last quarter. Support tickets closed yesterday. Gross margin for the fiscal period. Lagging metrics are usually clearer, more trusted, and more tightly tied to the outcome leadership cares about. They also arrive late relative to the work that produced them.

A leading indicator moves earlier. It is a measurable signal that tends to change before the lagging outcome, and that you can still influence. Qualified pipeline created this week. Kickoff calls completed within SLA. Percentage of accounts that hit a first-value event in their first seven days. Leading metrics are often messier and more gameable, but they are where coaching lives.

Think of a kitchen timer and a restaurant review. The timer (leading) tells the cook when to pull the bread. The review (lagging) tells you whether customers liked dinner. You need both. If you only watch reviews, you learn too late. If you only watch timers, you might serve on-time bread that nobody ordered.

Rule of thumb: Lagging metrics judge the season. Leading metrics coach the next play.

Why teams get stuck on lagging metrics

Lagging metrics feel adult. They show up in board packs. Finance already reconciles them. Nobody wants to defend “number of discovery calls” to a skeptical director when “bookings” is sitting right there. So the scorecard fills with outcomes, and the organization becomes excellent at storytelling after the fact.

That is not evil. Outcomes matter. The failure mode is exclusive focus. When every conversation starts with last month’s number, people learn to explain variance instead of prevent it. The meeting becomes archaeology: dig through the past until you find a narrative. Useful once. Expensive as a weekly habit.

Foundations thinking still applies. In Analytics foundations, the loop is not “report, then shrug.” It is question, analyze, decide, measure again. Leading indicators are how you put measurement closer to the decide step, while the work can still change.

What makes a leading indicator real (not a vanity count)

Example:

Leading, lagging, and guardrail set

Example: leading demos vs lagging revenue over weeks:

Not every early number is leading. “Emails sent” is early and often weakly related to revenue. A useful leading indicator usually has four properties:

Temporal lead: it reliably moves before the lagging outcome, or at least early enough to act
Causal story: you can explain why moving this should help the outcome (even if the world is noisy)
Controllability: the team can change the inputs without needing a miracle from another department
Integrity under pressure: if people optimize it, the side effects are acceptable or detectable

That last property is a preview of Part 5 (gaming and Goodhart). For now, keep a light touch: if the only way to hit the leading metric is to spam, lie, or redefine, it is not a coaching tool. It is a trap.

Quality matters here too. A leading metric built on half-filled CRM fields will train people to fill fields, not to sell better. If the data path is messy, fix definitions and completeness with habits from the data quality series before you put the metric on a bonus plan.

How to pair leading and lagging without drowning

A practical pattern for one objective:

One primary lagging metric that defines success for the period
One to three leading metrics that predict or enable that lagging result
One health or guardrail metric that catches side effects (margin, quality, customer effort, refund rate)

That set is small on purpose. If you need twelve leadings, you probably have several objectives pretending to be one. Go back to Part 1’s chain and split the objectives.

Review cadence can differ. Leading metrics often deserve weekly attention. Lagging metrics may be monthly or quarterly, with a weekly “are we on pace?” view only when the lag is short enough to be useful. Part 6 of this series will go deeper on meetings that do not suck. The design idea starts here: do not force every metric onto the same clock.

Worked example: one sales team, two clocks

Use a single business story so the difference is concrete. Meet Northline, a fictional B2B team selling a collaboration product to mid-market companies. Their quarterly objective (from Part 1’s language): Grow new ARR without collapsing win rate through panic discounting.

Lagging side: what “won” means

Primary lagging metric: New ARR closed in the quarter (excluding churn-save expansions that are tracked separately). Secondary lagging: Win rate on qualified opportunities. Guardrail lagging: Average discount on closed-won deals.

These numbers tell the executive team whether the quarter worked. They arrive when deals close. By the time New ARR is red in week 11, many of the behaviors that could have fixed it already happened in weeks 3 through 8.

Leading side: what to coach this week

Northline picks three leading metrics with a clear story:

Qualified pipeline created ($) each week, using a shared definition of “qualified” (budget conversation held, problem confirmed, next step scheduled)
Pipeline coverage ratio for the quarter (qualified open pipeline divided by remaining ARR target), refreshed weekly
Stage 2 to Stage 3 conversion rate over a rolling four weeks (shows whether discovery quality is slipping before close rates show it)

Optional process leading metric for managers: percent of open opps with a next step date in the next 14 days. That one is close to behavior. It is useful only if CRM hygiene is real. If reps invent fake next steps, you taught compliance theater. Definitions and quality checks matter before you celebrate green hygiene tiles.

Here is the pairing in one table.

Metric	Type	When it moves	How a manager uses it	Failure if used alone
New ARR closed (QTD)	Lagging	When deals close	Judge quarter health; set hiring and capacity	Explains failure after the window to fix pipeline
Win rate (QTD)	Lagging	As outcomes land	Spot quality vs volume problems	Too late to repair weak discovery from month one
Avg discount on closed-won	Lagging guardrail	At close	Catch “win at any price” behavior	Misses discounts already promised in open pipeline
Qualified pipeline created ($/week)	Leading	Early in the funnel	Coach prospecting and qualification this week	Can become junk pipeline if “qualified” is soft
Pipeline coverage vs remaining target	Leading	Weekly	Decide whether to add volume or fix conversion	Coverage on paper if stages are inflated
Stage 2 to 3 conversion (4 week)	Leading	Mid-funnel, before close	Inspect discovery quality and ICP fit	Noise if stages mean different things by rep

A week that uses both clocks

Week 6 snapshot (illustrative numbers, not a claim about any real company):

LAG (QTD):
  New ARR closed:        $1.8M  (plan pace: $2.1M)
  Win rate:              22%    (target band: 24 to 28%)
  Avg discount:          14%    (guardrail: <= 12%)

LEAD (last 7 days / current):
  Qualified pipeline created:  $420k  (weekly need: ~$500k)
  Coverage vs remaining:       2.4x   (team standard: 3.0x)
  Stage 2 to 3 conversion:     31%    (baseline: 38%)
  Opps with next step <=14d:   61%    (standard: 85%)

COACHING READ:
  Behind on lag, and lead is not rescuing us.
  Action this week: tighten qualification definition,
  double down on ICP accounts, inspect three stuck Stage 2 deals,
  freeze discretionary discounting on new quotes.

The point is not the exact thresholds. The point is the conversation shape. Without leading metrics, the meeting only says “we are behind on ARR.” With leading metrics, the meeting says where to intervene while intervention still works.

When you chart this, purpose still rules. A weekly ops view might show coverage and conversion as the heroes, with ARR as context. An executive monthly might reverse that hierarchy. The data-viz series is about jobs for charts; this series is about jobs for metrics. They stack.

Leading does not mean “more activity forever”

Activity metrics are seductive because they move when people move. Calls logged. Emails sent. Meetings held. Sometimes activity is the right leading layer, especially early in a rebuild. Over time, activity without quality becomes a treadmill. People hit call quotas and miss revenue. Then leadership concludes “leading indicators do not work,” when the real issue was a weak definition of quality.

Prefer leading metrics that encode quality, not only motion:

Qualified pipeline, not raw pipeline
First-value activation, not logins
Resolved on first contact with CSAT held, not tickets closed at any cost
Experiments shipped with a decision logged, not “tests launched”

If you implement these in SQL or Python, write the quality filters into the metric, not into a verbal footnote nobody remembers. A small reproducible script or model from the Python for analytics path can help, but only after the definition is stable on paper (Part 3 will give you the spec template).

Other domains, same pattern

The sales example is one domain. The pattern ports.

Domain	Lagging	Leading (examples)	Guardrail
Product activation	90-day retention	7-day first-value rate; setup completion	Support tickets per new account
Customer support	CSAT / NPS period score	First response time; reopen rate	Handle time that harms quality
Marketing	Pipeline or revenue attributed	Qualified demo requests; content-assisted opps	Cost per qualified lead
Data platform	Stakeholder trust survey; incident count	Freshness SLA hit rate; failed job rate	Unplanned schema changes

Always ask: if this leading number improves and the lagging never does, what did we actually improve? That question keeps vanity out of the system.

How this ties back to the goal chain

Part 1’s chain still sits underneath every leading and lagging choice. The objective names the win. Behaviors name the work. Leading measures usually sit closest to those behaviors. Lagging measures sit closest to the objective’s outcome. Targets apply to both, with different clocks.

If a leading metric has no behavior behind it, it will become a dashboard pet. If a lagging metric has no leading pair, the team will excel at postmortems. If neither has a written definition (Part 3), both will become negotiation topics instead of management tools.

A short pairing sentence helps in meetings: “We track coverage and Stage 2 to 3 conversion so we can fix the quarter while New ARR can still move; New ARR remains the score that says whether the quarter worked.” That sentence is the two-clock model in plain English.

Write that sentence on the scorecard itself when you can. People reuse slides. A metric without its partner and purpose will be copied into the wrong meeting and treated as a standalone truth. Context travels poorly unless you pack it with the number.

If you are building the underlying tables in SQL or a notebook, name columns so the type is obvious: new_arr_closed_qtd for lag, qualified_pipeline_created_7d for lead, avg_discount_closed_won for guardrail. Naming will not fix a bad definition, but it stops accidental swaps when someone joins the wrong field into a chart from the data-viz toolkit.

Common mistakes

Only lagging on the wall. Great for blame, weak for coaching.
Only leading on the wall. Busy teams, confused executives, no outcome proof.
Calling any early metric “leading.” Early plus weak causal story equals vanity.
Soft qualification. Pipeline coverage looks healthy while win rate dies later.
Different stage definitions by rep. Your mid-funnel conversion becomes fiction.
Weekly deep-dives on annual lagging metrics. Wrong clock for the signal.
Bonusing a leading metric with no guardrail. People will hit it sideways.
Ignoring data quality. Leading metrics amplify CRM garbage faster than lagging finance numbers do.

How to practice this week

Pick one lagging metric your team already loves (revenue, retention, CSAT, cost).
Write the objective sentence it serves (Part 1 chain).
Propose two leading candidates and one guardrail. For each leading candidate, write the causal sentence: “If this rises, we expect ___ to improve because ___.”
Check controllability: who can change the inputs this month?
Check integrity: how would a clever person game it? Note the risk for later (Part 5).
Put the pair on one page for next week’s meeting: lag status, lead status, one action.

Next in the series: definitions and metric specs (owner, grain, formula, filters, caveats) so “qualified pipeline” means the same thing on Tuesday as it did on Monday. Related reading still includes the KPI prequel and the quality habits that keep leading metrics honest.

Quick recap

Lagging indicators report outcomes; leading indicators help you act earlier.
Pair one primary lag with a few quality-aware leads and a guardrail.
Leading is not the same as raw activity.
Use different review clocks: weekly coaching for leads, period judgment for lags.
Soft definitions and dirty data turn “leading” into theater.
Sales, product, support, and marketing all use the same two-clock pattern.

Sources

BMC, Leading vs lagging indicators overview: https://www.bmc.com/blogs/leading-vs-lagging-indicators/
Amplitude, Leading vs lagging indicators (product analytics framing): https://amplitude.com/blog/leading-lagging-indicators
What Matters, OKRs explained (objectives vs measurable results): https://www.whatmatters.com/okrs-explained
Analytics Made Simple, All About KPIs: https://analyticsmadesimple.com/analytics/all-about-kpis/
Analytics Made Simple, Analytics foundations: https://analyticsmadesimple.com/series/analytics-foundations/
Analytics Made Simple, Data quality series: https://analyticsmadesimple.com/series/data-quality/
Analytics Made Simple, Charts that make sense: https://analyticsmadesimple.com/series/data-viz/
Analytics Made Simple, Learn hub: https://analyticsmadesimple.com/learn/