A lagging indicator tells you what already happened: revenue closed, customers lost, projects delivered. A leading indicator measures the activities that produce those outcomes: proposals sent, at-risk accounts contacted, milestones cleared. The distinction sounds academic until you build a weekly scorecard, at which point it becomes the single most important design decision on the page — because a scorecard of lagging indicators is a rearview mirror, and you can't steer with one.
You can't manage revenue weekly
Put monthly revenue on a weekly scorecard and watch what happens: the number barely moves for three weeks, then jumps at close. The owner has nothing to say except "we'll see." Nobody can act on it, because by the time revenue moves, the work that produced it happened one or two months ago. That's the defining trait of a lagging indicator — by the time it's red, the damage is banked.
Now put proposals sent on the same scorecard. That number is fully ownable this week. If it's red, the fix starts tomorrow morning, and the revenue number two months from now just changed. That's the whole trade: lagging indicators are certain but unactionable; leading indicators are imperfect but steerable. The weekly meeting exists to act, so the weekly scorecard should be built mostly from numbers someone can act on.
Leading indicators, function by function
- Sales: first meetings booked, proposals sent, pipeline added this week — not bookings, which lag the work by a full cycle.
- Marketing: qualified leads generated, content shipped, campaign responses — not brand awareness, which lags everything.
- Delivery & operations: milestones cleared on time, backlog age, utilization — not project profitability, which arrives at the retrospective.
- Customer health: at-risk accounts contacted, response time, usage or engagement checks — not churn, which is the funeral, not the diagnosis.
- People: candidates in process, interviews held, offers out — not open-role count, which just measures the size of the hole.
- Finance: invoices sent, collections activity, cash position — the one place a "lagging" number (cash) earns a weekly seat, because running out of it is not a lesson you want monthly.
The pairing rule
The scorecard trap is choosing leading indicators and then celebrating them in a vacuum. Activity without outcome is a treadmill: proposals sent can hit goal for a quarter while win rate quietly collapses. The fix is pairing — every leading indicator on the weekly board should have the lagging outcome it exists to drive reviewed at the monthly or quarterly level, and when the pair diverges (inputs green, outcome flat), that divergence goes on the issues list by name. The leading number is the steering wheel; the lagging number is the proof the wheel is connected to anything.
The three-question test
For any candidate number, ask: Does it predict an outcome you care about? Does its owner control it this week? Does it have a weekly heartbeat, or are you slicing a monthly number thin and calling it signal? Two yeses isn't enough. A number that predicts but can't be controlled is weather. A number that's controllable but predicts nothing is busywork. A number without a weekly pulse belongs on a different review — which is fine; that's what monthly reviews are for.