PRODUCTIVITYWeeks to result

The Lead Measures System

Focus on the predictive activities you can influence, not lagging outcomes

Problem it solves

low productivity

Best for

Teams that set goals but struggle to identify the specific daily or weekly activities that will actually move the needle toward those goals

Not ideal for

Situations where the cause-and-effect relationship between activities and outcomes is genuinely unknown and requires experimentation first

Overview

Why this framework exists

The Lead Measures System is the second discipline of 4DX and addresses a critical gap in most goal-setting approaches: they focus on lag measures (the outcomes you want to achieve) rather than lead measures (the activities that will produce those outcomes). Lag measures like revenue, weight, or customer satisfaction tell you whether you have achieved your goal, but they come too late to change your behavior. Lead measures are the daily and weekly activities that predict whether you will achieve the lag measure.

The power of lead measures lies in two characteristics: they are predictive of achieving the WIG, and they are influenceable by the team. Revenue is a lag measure—you cannot directly control it. But the number of sales calls per day or the percentage of customers who receive a follow-up email are lead measures—you can directly influence them, and they predict revenue.

Identifying the right lead measures is both the most difficult and the most valuable part of the 4DX process. When teams get this right, they shift from hoping for results to actively driving them. The shift from tracking lagging outcomes to tracking leading activities transforms the teams sense of agency and control.

Core principles

5 total
  1. Lag measures tell you if you have won but lead measures tell you if you are likely to win
  2. Effective lead measures must be both predictive of the goal and influenceable by the team
  3. Tracking lead measures shifts the team from hoping for results to actively driving them
  4. The best lead measures are specific daily or weekly behaviors not vague intentions
  5. When lead measures move consistently the lag measure follows with mathematical certainty

Steps

3 steps
  1. Identify Candidate Lead Measures
    For your WIG, brainstorm every activity or behavior that could influence the outcome. Think about what the highest performers do differently from average performers. Consider actions at every stage of the process that leads to your goal. Cast a wide net initially—you want at least five to ten candidate lead measures before narrowing. Involve the team in this brainstorm because those closest to the work often know the leverage points best.
    Pro tipStudy your best performers and ask them what they do differently on their best days—these daily behaviors are often the hidden lead measures
  2. Evaluate and Select Lead Measures
    Evaluate each candidate against two criteria: is it truly predictive of achieving the WIG, and can the team directly influence it? Eliminate measures that fail either test. From the remaining candidates, select the one or two that have the highest leverage—the activities where a small increase in effort will produce the largest movement in the lag measure. Resist selecting too many lead measures as this dilutes focus.
    Pro tipWhen uncertain about which lead measure has the highest leverage run a two-week experiment tracking both and comparing their correlation with outcomes
    WarningAvoid selecting lead measures that are easy to track but weakly predictive—convenience should never override leverage
  3. Define and Track Lead Measures Weekly
    Define the selected lead measures with the same precision as the WIG. Specify the exact behavior, the frequency, and the target. Create a simple tracking mechanism and review lead measure performance weekly in a team accountability session. The weekly cadence is critical—it creates a rhythm of commitment and accountability that keeps the lead measures alive amidst the daily whirlwind.
    Pro tipMake lead measure tracking as simple as possible—if it takes more than five minutes to update people will stop doing it
    WarningDo not wait for a perfect tracking system before starting—a simple spreadsheet updated manually is vastly better than a sophisticated system that is never built

Checklist

Saved in your browser

Examples

1 cases
Weight Loss Lead Measures

A person sets a WIG to go from 200 pounds to 180 pounds by June. Instead of obsessing over the scale (lag measure), they identify two lead measures: consume fewer than 1500 calories per day and exercise for 45 minutes five days per week. These are behaviors they can control daily that predict the desired weight loss outcome.

OutcomeBy focusing on and tracking the lead measures weekly the individual lost 22 pounds in four months, exceeding their goal
The 4 Disciplines of Execution, Chapter 3

Common mistakes

2 traps
Tracking Lag Measures Disguised as Lead Measures
Many teams think they have identified lead measures but are actually tracking miniature lag measures—smaller outcomes rather than the behaviors that produce them. A true lead measure is an activity you perform, not a result you observe.
Selecting Measures That Cannot Be Influenced
If the team cannot directly control the measure through their own effort it is not a valid lead measure. Market conditions, competitor actions, and macroeconomic factors are not lead measures no matter how predictive they are.

Origin story

How this framework came to be

The concept emerged from FranklinCovey's observation that most organizations track the wrong things. They found that teams almost universally measured lag measures—the results they wanted—but rarely identified or tracked the specific behaviors that would produce those results. The breakthrough came when they realized that lead measures give teams the power to act before the outcome is determined, creating a fundamentally different relationship between effort and results.

Source

Traced to primary
Source · BOOK
The 4 Disciplines of Execution
Chris McChesney, Sean Covey, Jim Huling · 2012
Open source →

Related frameworks

Browse all Productivity →