Most leadership teams spend their time reviewing results that are already locked in.
Revenue missed. Churn increased. Projects slipped. Margins compressed.
By the time these numbers show up in a report, the outcome is no longer changeable. Teams react, scramble, and promise to do better next quarter.
This is the execution gap that the second discipline of the 4 Disciplines of Execution is designed to close.
If Discipline 1 is about focus, Discipline 2 is about leverage. It teaches teams how to identify and act on the behaviors that actually drive results, not just measure them after the fact.
In this article, we will break down the difference between lead and lag measures, why most teams get this wrong, how to identify lead measures that actually predict success, and how to operationalize them inside a weekly execution rhythm. We will also show how Wave helps teams move from reactive reporting to proactive execution.
What Are Lag Measures?
Lag measures track the outcome you ultimately care about.
They answer the question:
Did we win or lose?
Common lag measures include:
- Revenue
- Profit
- Customer churn
- Net promoter score
- On-time delivery rate
Lag measures are essential. They define success. They tell you whether your strategy worked.
But they all share the same fatal flaw.
They are historical.
By the time a lag measure moves, the behaviors that caused it have already happened. You cannot change last quarter’s revenue or last month’s churn.
Lag measures are necessary, but they are not actionable in the moment.
What Are Lead Measures?
Lead measures track the behaviors that predict the lag measure.
They answer a different question:
Are we doing the right things right now to win later?
A strong lead measure has two defining characteristics:
- It is predictive of the lag measure
- It is influenceable by the team
Examples include:
- Number of qualified discovery calls completed per week
- Percentage of customers completing onboarding within seven days
- Weekly proactive retention conversations with at-risk accounts
- Code review turnaround time
Lead measures give teams leverage. They allow you to adjust behavior before results are locked in.
Why Most Teams Accidentally Track Lag Measures Twice
One of the most common execution mistakes is thinking you are tracking lead measures when you are really tracking lag measures in disguise.
Examples:
- Monthly pipeline value as a lead measure for revenue
- Customer satisfaction surveys as a lead measure for churn
- Velocity reports as a lead measure for delivery
These are still outcomes. They are closer to the result, but they do not tell teams what to do differently this week.
A true lead measure should guide behavior immediately.
If a metric does not change how someone works tomorrow, it is not a lead measure.
The Behavioral Power of Lead Measures
Lead measures work because they change behavior.
When teams know exactly which actions matter most, decision-making becomes simpler. Priorities become clearer. Tradeoffs become easier.
Lead measures also create ownership.
Teams cannot hide behind market conditions or downstream results. They know which levers they control, and they are accountable for pulling them consistently.
This is why teams that execute well often track fewer metrics, not more.
How to Identify Strong Lead Measures
Finding good lead measures is harder than it sounds. It requires experimentation and honesty.
Here is a practical approach.
Step 1: Start With the Lag Measure
Begin by clearly defining the lag measure you are trying to improve.
Examples:
- Increase monthly recurring revenue
- Reduce churn
- Improve on-time delivery
- Increase customer activation
If the outcome is vague, the lead measures will be too.
Step 2: Ask What Behaviors Drive That Outcome
Work backward and ask:
What do our best performers consistently do that others do not?
This often reveals patterns.
For example:
- High-performing sales reps schedule more high-quality discovery calls
- Retained customers receive proactive outreach before issues escalate
- Successful projects have clear weekly milestones reviewed consistently
These behaviors are candidates for lead measures.
Step 3: Pressure-Test Predictiveness
Not every behavior is predictive.
Ask:
- When this behavior increases, does the lag measure reliably improve?
- Can we influence this behavior weekly?
- Can the team clearly see how their actions impact it?
If the answer is unclear, refine the measure.
Examples of Strong Lead Measures by Function
To make this more concrete, here are examples by team.
Sales
Lag measure:
- Monthly revenue
Lead measures:
- Number of qualified discovery calls per week
- Follow-ups completed within 24 hours
- Proposals sent within five days of discovery
Customer Success
Lag measure:
- Churn rate
Lead measures:
- Weekly proactive customer check-ins
- Onboarding completion within first seven days
- Documented success plans per account
Product and Engineering
Lag measure:
- On-time delivery or product adoption
Lead measures:
- Stories completed per sprint
- Time from pull request to merge
- Weekly customer feedback reviews
Operations
Lag measure:
- Cycle time or cost efficiency
Lead measures:
- Weekly process bottleneck reviews
- Percentage of work following standard workflows
- Time to decision on operational blockers
The key is simplicity. Teams should track a small number of lead measures that directly influence the outcome.
Common Mistakes When Implementing Lead Measures
Even teams that understand lead measures conceptually often struggle in practice.
Mistake 1: Tracking Too Many Lead Measures
When everything is a lead measure, nothing is.
Most teams should track one to three lead measures per WIG. More than that dilutes focus and accountability.
Mistake 2: Choosing Measures That Are Easy Instead of Effective
Teams sometimes choose measures that are easy to track rather than ones that drive results.
Activity alone is not enough. The behavior must matter.
Mistake 3: Reviewing Lead Measures Too Infrequently
Lead measures lose power if they are reviewed monthly.
They should be reviewed weekly so teams can course-correct in real time.
Turning Lead Measures Into Weekly Commitments
Lead measures only work when paired with commitments.
Each week, teams should answer:
- Which lead measures are we committing to improve this week?
- What specific actions will we take?
- Who owns each commitment?
This creates a tight feedback loop between behavior and results.
Without commitments, lead measures become just another report.
How Wave Supports Lead and Lag Measures
This is where execution often breaks down. Teams know what to track but lack a system to support consistency.
Wave provides the structure that makes lead measures operational.
Connecting Lead Measures to Goals
Wave allows teams to link lead measures directly to company and team goals. This makes it clear why the metric matters and how it supports the WIG.
Nothing lives in isolation.
Weekly Scorecards That Drive Action
Wave Scorecards are built for weekly review, not passive dashboards.
Teams update lead measures consistently and review them inside meetings, creating a rhythm of accountability instead of reactive reporting.
Reinforcing Behavior in Meetings
Wave Meetings are designed around execution.
Teams review scorecards, discuss gaps, identify blockers, and make commitments tied directly to lead measures. This keeps meetings focused on what drives results, not status updates.
Making Accountability Visible
Commitments tied to lead measures are captured and tracked in Wave. Ownership is clear. Follow-through is expected.
This is how behavior changes week over week.
Conclusion
Lag measures tell you how you did. Lead measures tell you how to win.
For scaling companies, the ability to predict results before they are locked in is a massive advantage. It shifts teams from reactive to proactive and from busy to effective.
The hardest part is not understanding the concept. It is identifying the right behaviors and building the discipline to track and act on them consistently.
When teams focus on a small set of meaningful lead measures and review them weekly, execution improves fast.
Ready to move from hindsight to foresight? See how Wave helps teams track the behaviors that drive results and execute with confidence.
