Most strategic KPIs tell you what already happened. A lean organization, which improves daily, needs measures that move daily and tell it early whether the strategy is on course. The hard part isn’t finding leading indicators. It’s finding ones that actually lead.
In this guide
Key Takeaways
- →A leading indicator moves before the result and can be influenced daily or weekly.
- →An activity measure shows effort and predicts nothing by itself.
- →Draw candidates from the drivers in the KPI tree, not from what is easy to count.
- →Write down the expected lag before you watch, or the test is unfalsifiable.
- →Teams that improved an indicator at different times make the test much clearer.
- →An indicator that moves while the result doesn’t is a false green light.
Lagging, leading and activity
Three kinds of measure get called leading indicators in practice, and only one of them is. Telling them apart is most of the work.
The third row is where programs go wrong. Activity measures are easy to collect, they move quickly, and they respond to management attention, which makes them feel like the others. They are worth tracking as hygiene. They are not worth steering by.
| Type | Example | Use |
|---|---|---|
| Lagging strategic KPI | On-time delivery to customer | Tells you whether the strategy worked |
| Leading indicator | Parts available at kitting | Moves first; predicts the KPI |
| Activity measure | Kaizens completed on delivery | Shows effort; predicts nothing by itself |
A leading indicator that moves while the result doesn’t isn’t leading. It’s just busy.
Tests for a good leading indicator
- It moves before the result, by a time you can state.
- Teams can influence it daily or weekly.
- It is measured often enough for huddles to use it.
- When it moves, the result follows. Checked over months, not assumed.
The first test is the one people skip, and skipping it is what makes the fourth test impossible. “It should feed through eventually” can never be wrong, so it never retires a bad indicator. “On-time delivery should respond within six weeks” can be wrong by week eight, which is exactly what you want from it.
Testing the relationship
Choose candidates from the drivers in the KPI tree. For each, write down how long the strategic KPI should take to respond when the indicator improves. Then watch. If parts availability rose two months ago and on-time delivery hasn’t moved, either the lag is longer than you thought or the indicator doesn’t lead. Plants or teams that improved the indicator at different times make the test much clearer.
Two ways of laying that tree out, and what each one makes easy to see, are compared in Goal Tree vs X-Matrix: Two Ways to Show Strategy Deployment.
This is the same discipline as testing a correlation on a hoshin X-matrix; see The X-Matrix Is a Set of Hypotheses. Treat It Like One.
A worked example: three candidates, one keeper
Here are three hypothetical candidate indicators, each tested against whether on-time delivery followed:
| Candidate | Moved? | On-time delivery followed? | Verdict |
|---|---|---|---|
| Parts available at kitting | Up 8 points | Yes, after about six weeks | Keep |
| Huddle attendance | Up to 95% | No change | Drop as a leading indicator; keep as hygiene |
| Changeover time | Down 15% | Small change, only on two lines | Partial: lines with frequent changeovers only |
Huddle attendance is worth tracking, but it doesn’t predict delivery. Treating it as a leading indicator would have told the strategy it was on course when it wasn’t.
The third row is the more common outcome and the more useful one. Changeover time leads delivery where changeovers are frequent and does nothing where they are not, which is a finding about which lines deserve the investment, not a failed candidate.
What a false leading indicator costs
A false leading indicator is more expensive than no leading indicator at all, because it buys silence. Two quarters of rising huddle attendance read as a strategy on course, so nobody opens the delivery question until the lagging KPI finally reports, by which point the year’s improvement capacity has been committed. The bill is a late correction rather than an early one, and late corrections are the costly kind.
Among published alternatives, OnStrategy lists $200 per month for unlimited users and i-nexus publishes a free Starter tier for up to five users with $28 per user per month at its Standard tier. What to test in a trial is specific: can you record an expected lag against the relationship between an indicator and its KPI, and will the system tell you when the lag has elapsed and the result has not followed? Charting both series on one screen is not the same capability.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate, so you can start with the handful of KPIs the plan depends on. Hoshin Kanri, OKRs and Goals and Balanced Scorecard sit in Essentials, and the 30-day free trial covers roughly the shortest lag worth stating, which is enough to see the mechanism work once.
The expected lag, stored
In Profit.co, leading indicators can sit beside the strategic KPI they should move, with the expected lag stored on the correlation, so the review can see whether the result followed, and the exception queue flags cases where it didn’t. See the lean strategy software page.
Storing the lag rather than remembering it is what turns this from an opinion into a test:
- The claim is on the record before the evidence. Six weeks was written down in January, so August cannot quietly become the expected lag.
- The failure is pushed at you. An indicator that moved and a result that didn’t arrives in the exception queue rather than waiting to be noticed.
- Verdicts accumulate. After a year you have a short list of indicators that have earned their place and a longer list you have retired, which is the real asset.
Where these indicators come from on the floor is covered in Gemba Walks That Feed the Strategy, and the phase of a transformation where they start to matter is in The Lean Transformation Roadmap: Where Strategy Deployment Fits.
Free Product Demo
Test your leading indicators
A 30-minute walkthrough, tailored to your team.
Book a free demoWhat happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
A measure that moves before a strategic KPI, can be influenced daily or weekly, and genuinely predicts the result.
State how long the strategic KPI should take to follow, then watch over months whether it does when the indicator moves, ideally comparing teams or sites.
No. Counts of kaizens or meetings show effort but don’t predict results by themselves.
From the drivers in the KPI tree beneath the strategic KPI, so each candidate already has a stated mechanism rather than only a correlation.
Keep it where it leads and say where that is. Changeover time predicts delivery on lines with frequent changeovers and not elsewhere, which tells you where the investment belongs.