Leading vs lagging indicators. Which ones a manager can actually act on.

The short answer. One predicts, the other reports.

Leading and lagging indicators are the two halves of any useful sales dashboard, and mixing them up is the most common reason a weekly pipeline review changes nothing. A leading indicator, qualified pipeline created, meetings booked, average time a deal sits in a stage, is a number that can still be influenced today and tends to move before the outcome it predicts. A lagging indicator, closed revenue, quarterly win rate, customer churn, is the outcome itself, already fixed by the time it appears on a report.

The distinction sits at the centre of the Balanced Scorecard, the performance management framework Robert Kaplan and David Norton introduced in a 1992 Harvard Business Review article. Kaplan and Norton built it explicitly to balance short-term and long-term measures, financial and non-financial ones, and, in their own words, lagging indicators against leading ones, precisely so a business could see a problem forming instead of only reading the damage once the quarter had already closed.

Applied to a sales pipeline, the practical rule is simple: revenue is a lagging indicator because it takes an entire sales cycle to show up and by then the deals that produced it are already won or lost. Pipeline volume, meetings booked and proposal-to-close ratio are leading indicators because a manager can still change them mid-week, and because history shows they tend to move ahead of the revenue number that eventually follows.

How they differ. Timing, not just terminology.

The real difference is timing, not just category. A lagging indicator answers "how did we do", after the fact and with no room left to change the answer. A leading indicator answers "how are we tracking, and is there still time to do something about it". That's why a sales dashboard built only from lagging metrics (closed-won revenue, this quarter's win rate) looks calm right up until the point it doesn't, because there was never a signal built in to catch the problem earlier.

Good leading indicators share three properties: they can genuinely still be influenced when you see them, they have a demonstrated historical relationship to the lagging result you actually care about, and they update often enough to be worth checking regularly. A metric that technically comes earlier in the funnel but has no proven link to eventual revenue isn't a leading indicator, it's just an earlier number.

Which to use and when. Leading for the weekly review, lagging for the scorecard.

Use leading indicators in the meeting where decisions actually get made, the weekly or biweekly pipeline review, because they're the only numbers in that room that can still change the quarter's outcome. If qualified pipeline created is down two weeks running, that's actionable today: more prospecting time, a tighter qualification bar, a look at whether marketing handoff has slowed down. Waiting for the lagging revenue number to confirm the problem means finding out a full sales cycle too late to fix it.

Use lagging indicators where they belong, in the monthly or quarterly scorecard that reports what actually happened against target. They're the right measure of success and the wrong tool for steering. A business that reviews SaaS KPIs only at quarter-end, treating the lagging revenue number as if it were also the management tool, is reviewing a number it can no longer influence.

Take a worked example. A ten-rep team tracks qualified pipeline created weekly against a target of £50,000 per rep. In week three of the quarter, three reps are running 30% below that figure. Revenue for the quarter, the lagging number, won't show any impact for another six to eight weeks, the length of this team's average sales cycle. But the leading indicator has already given a five to six week head start: coaching, a territory review, or a temporary lead-reallocation can happen now, while there's still a cycle's worth of time to change the outcome. By the time the lagging revenue figure confirms a shortfall, that window has closed.

The same logic applies in reverse when a leading indicator looks healthy but the underlying quality is weak. Pipeline volume can rise while win rate quietly falls, if a team starts logging lower-quality leads just to hit an activity target. That's why a single leading indicator in isolation is never enough: pair a volume metric (pipeline created) with a quality metric (proposal-to-close ratio) so a manager can tell the difference between genuine progress and a number being gamed to look healthy.

How Lauren would decide. Pick two or three, not everything you can measure.

When I build a reporting cadence for a client, I start by asking which leading metrics have historically moved before their revenue did, using their own pipeline history rather than a generic industry list. That's usually two or three numbers, not the dozen activity metrics a CRM can technically report. A dashboard crowded with every measurable activity gets glanced at once and ignored; a short one built from indicators a manager has actually watched predict next quarter's number gets checked every week, which is the entire point.

The build itself matters as much as the choice of metric. This is exactly where I start with a client's reporting and dashboard build, because a leading indicator that lives in a spreadsheet nobody updates predicts nothing. Get the two or three real leading indicators into a dashboard the team actually opens, and the lagging number stops being a surprise.

One common mistake worth naming directly: teams that inherit a dashboard template from a previous role or a generic sales playbook, rather than testing which metrics actually predicted revenue in their own pipeline history. A metric that's a strong leading indicator for a six-month enterprise sales cycle is often close to useless for a two-week transactional one, because the lag between the leading signal and the lagging outcome is completely different. Test the relationship against your own closed deals before building a dashboard around someone else's list.