A mature improvement system generates hundreds or thousands of improvements a year. Almost none of them carries a note saying which strategic KPI, if any, it was meant to move. Adding that one field changes what the organization can learn from its own improvement work.
In this guide
Key Takeaways
- →Counts show that improvement is happening, never where it is pointed.
- →One field with three values: a strategic KPI, base improvement, or local.
- →The person raising the improvement sets it, in seconds, with no approval.
- →Base and local improvements stay valued; the field is visibility, not ranking.
- →Patterns of ideas by KPI tell a bet owner what no dashboard will.
- →Review the links quarterly, not idea by idea.
Counting isn’t connecting
Improvement systems usually report counts: ideas submitted, kaizens completed, projects closed, savings logged. Counts show that improvement is happening. They don’t show where it’s pointed, or whether improvement aimed at a strategic KPI actually moved it.
This is why a healthy improvement report and a stalled strategy coexist so comfortably. Nothing in the report is false, and nothing in it can contradict the plan, because the two were never measured against each other.
One field, three values
The fix is deliberately small. One field on the record the team already fills in, with three values, chosen by whoever raised the improvement.
Three values, not two, is the part that makes it survive contact with the floor. A binary strategic-or-not field quietly tells people that most of their work does not count; naming base and local improvements as their own categories says the opposite.
| Value | Meaning | Example |
|---|---|---|
| Strategic KPI | Meant to move a KPI on the hoshin plan | Pre-kitting parts check → on-time delivery |
| Base improvement | Improves a fundamental not on the plan | Tool crib reorganized → time to find tools |
| Local | Matters to the team; no wider KPI | Break room layout |
The field is set by whoever raises the improvement, in seconds. Base and local improvements are valuable; the field just makes the mix visible.
You can’t steer improvement capacity you can’t see. One field is enough to see it.
What to do with the links
| Report | Question it answers |
|---|---|
| Improvement effort by strategic KPI | Is improvement pointed at what the strategy needs? |
| Effort beside KPI movement | Is that improvement moving the KPI? |
| KPIs with little improvement effort | Which strategic results is nobody improving? |
| Patterns of ideas by KPI | What does the front line keep seeing about a strategic KPI? |
The fourth report is the one that feeds strategy. Twenty ideas in a quarter about the same supplier problem tell the KPI owner something no dashboard will.
Avoiding bureaucracy
- No approval to link. The person raising the idea picks the KPI.
- No extra form. One field on the existing idea or kaizen record.
- No penalty for base or local. They remain valued; the link is for visibility, not ranking.
- Review links quarterly, not idea by idea.
Every one of these rules exists because the opposite has been tried. An approval step turns a ten-second field into a queue; a separate form halves submissions; ranking by category teaches people to mislabel. The field survives only while it costs nothing to use.
A worked example: a quarter’s improvements, linked
Here is a hypothetical quarter of improvements, linked to the strategic KPIs they were meant to move:
| Strategic KPI | Improvements | Movement |
|---|---|---|
| On-time delivery | 38 | +2 points |
| Scrap rate | 22 | −0.4 points |
| Services attach rate | 3 | Flat |
| Base improvements | 140 | — |
| Local improvements | 95 | — |
The site is good at delivery and scrap improvement. Almost nobody is improving anything that affects services attach rate, which is the KPI the breakthrough most depends on. That’s a steering conversation for next quarter, covered in Steering Improvement Capacity Toward Breakthroughs, Without Killing Kaizen.
Read the first column as a budget and the picture sharpens. Of 298 improvements, three went to the measure the year’s biggest bet depends on. Nobody decided that; it is simply what happens when the allocation is invisible.
What the missing field costs
Improvement capacity is real money. A site running three hundred improvements a quarter is spending a substantial, recurring share of its people’s discretionary time, and that spend is already approved, already budgeted and already happening. The field does not add cost; it tells you where the cost went. In the table above, the gap between 38 improvements on delivery and 3 on attach rate is not a reporting problem, it is a misallocated quarter that will repeat until someone can see it.
Among published alternatives for making this visible, OnStrategy lists $200 per month for unlimited users, which matters when the people setting the field are everyone who raises an improvement. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier, which prices better for a central improvement team than for a shop floor. Whichever you test, the question is narrow: can the person raising an idea pick the KPI themselves, in one field, without an approval step, and does the resulting effort total appear beside that KPI’s movement?
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate, which fits a population where most people write one field occasionally and a few read the totals constantly. Hoshin Kanri, OKRs and Goals and Balanced Scorecard sit in Essentials, and the 30-day free trial covers enough of a quarter to see a real mix emerge rather than a demo one.
Effort and movement on one objective
Profit.co’s improvement-idea capture links each idea to the strategic KPI it should move, so effort by KPI and the movement beside it are visible on the same objectives the hoshin plan tracks. See the lean strategy software page.
Holding both numbers on one record, rather than in two systems joined by a spreadsheet, is what makes the quarterly review short:
- The totals are a by-product. Nobody compiles effort by KPI; it accumulates as people log work, so it cannot be presented selectively.
- A starved KPI announces itself. Three improvements against a breakthrough measure is visible without anyone going looking for it.
- Patterns stay attached. Twenty ideas about one supplier sit against the objective they concern, where the owner will meet them.
How that connection is tested in a demo, against a tool that only counts, is in How to Evaluate Lean Strategy Software.
Free Product Demo
See where your improvement effort points
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
Add one field to each improvement: the strategic KPI it should move, or base or local. Then report effort by KPI beside KPI movement, and review quarterly.
No. Base and local improvements are valuable. The link makes the mix visible so a deliberate share can be pointed at strategic KPIs.
No approval to link, no extra form, no penalty for base or local improvements, and a quarterly rather than item-by-item review.
A binary field tells people most of their work does not count. Naming base and local improvements as categories of their own keeps them valued and keeps the field honest.
Seconds per improvement and one review a quarter. The improvement capacity it makes visible is already being spent, which is the point.