Churn rate and MRR are the numbers that define success, but by the time they move, it is already too late to act, which is exactly why lag measures need a lead measure partner.

What is a lag measure?

Product teams are surrounded by metrics, but not all metrics are created equal. Some tell you where you are heading. Others tell you where you have already been. A lag measure belongs to the second category: it is the outcome you are trying to achieve, visible only after the work that produces it is done. Understanding the difference between lag measures and their counterpart, lead measures, is foundational to building a measurement system that actually drives decisions rather than just reporting on them.

Understanding lag measures

A lag measure is a metric that records the result of a completed set of actions. It is called a lag measure because it lags behind the behaviors that caused it. By the time it appears in a dashboard, the work that determined its value has already happened.

Common lag measures in SaaS include monthly recurring revenue (MRR), customer churn rate, annual contract value (ACV), Net Promoter Score, and 90-day retention rate. These are the numbers that ultimately define business performance, but they cannot be directly managed in the moment. A team cannot decide on Monday to have a lower churn rate by Friday. They can only influence the behaviors and processes that, over time, produce a lower churn rate.

This is the central tension with lag measures: they are the most meaningful metrics a business tracks, and the least actionable on any given day.

Lag measures vs. lead measures

The lead measure / lag measure framework was popularized by the business execution model outlined in "The 4 Disciplines of Execution." The distinction is simple but consequential:

• A lead measure is predictive and influenceable. It tracks a behavior or activity that is known to drive the lag measure outcome. It can be acted on today.

• A lag measure is the goal itself. It confirms whether the lead measure activity worked. It cannot be acted on directly.

In a product adoption context, a lag measure might be 30-day retention rate. The lead measures that predict it could be activation rate, time to value, or the percentage of users who complete a core workflow in their first session. The team cannot change their 30-day retention number today, but they can change how many users complete that first workflow, and measure whether doing so moves retention in the next cohort.

Why lag measures alone are insufficient for product teams

Reporting on lag measures without tracking the lead measures that drive them creates a common and costly problem: teams find out about performance failures too late to intervene. A retention cohort that shows poor 30-day numbers reflects decisions and experiences from a month ago. The users who churned have already left. The friction that drove them out is still in the product.

This is particularly acute during user onboarding, where the behaviors in the first few sessions have an outsized influence on whether a user ever reaches the value moment that predicts retention. Teams that only track lag measures at this stage are flying blind through the period where intervention would have the highest impact.

How lag measures fit into a product measurement system

The most useful measurement systems pair lag measures with lead measures at every level. The lag measure defines what success looks like. The lead measures define the behaviors the team will track and act on to get there.

For a team focused on improving 90-day customer retention (lag), the lead measures might include feature adoption depth, activation rate within 7 days, and the number of users who complete a second meaningful session within the first week. Jimo's Success Tracker makes it possible to instrument these behavioral milestones at the feature level without engineering dependency, so teams can monitor the lead measures that predict their lag outcomes in near real time rather than waiting for a monthly cohort report to surface a problem.

For a practical framework on which behavioral metrics to pair with your lag outcomes, how to measure product adoption covers the full measurement stack in detail.