Point too little improvement at the strategy and the breakthroughs stall. Point too much and kaizen becomes another top-down program, and the ideas stop coming. The answer is a deliberate, visible share, not a mandate.
In this guide
Key Takeaways
- →Too little steering starves the breakthroughs; too much dries up the ideas.
- →There is no correct number, and inventing one would be misleading.
- →Many organizations find a third to a half of structured effort is enough.
- →Raise the share for the KPI that needs it, not across the board.
- →Steer with focus KPIs, targeted events and visible reporting, never approvals.
- →Nobody’s idea system has to change. Only the direction does.
The two failure modes
Both failures look like a healthy improvement system from the outside, which is why they run for years before anyone names them.
They also fail in opposite directions, so the correction for one is the cause of the other. That is what makes the share a judgment rather than a policy.
| Too little steering | Too much steering |
|---|---|
| Kaizen goes wherever people notice problems | Every improvement must link to a strategic KPI |
| Breakthrough KPIs get little improvement effort | Local and base problems are ignored |
| Strategy relies only on big projects | Ideas dry up; kaizen feels like another program |
Kaizen works because people improve what they see. Steering should add a direction, not take that away.
Setting the share
There is no correct number, and inventing one would be misleading. Many organizations find that a third to a half of structured improvement effort on strategic KPIs is enough to move them without starving the base. Start from what the breakthroughs need: if a strategic KPI needs a large step this year and has little improvement effort today, raise the share for that KPI, not across the board.
Raising it per KPI rather than per site is the detail that keeps the number honest. A site already putting 45% of its effort against the right measure does not need a target; a site at 12% against the measure its breakthrough depends on needs one specific conversation, not a group-wide memo.
Mechanisms that steer without mandating
| Mechanism | How it works |
|---|---|
| Quarterly focus KPIs | Each site or team picks one or two strategic KPIs to emphasize this quarter |
| Targeted kaizen events | Planned events aimed at a strategic KPI’s biggest gap |
| Problem themes at huddles | A recurring huddle question about the focus KPI |
| Visible effort by KPI | Reporting that shows where improvement is pointed, without approving each idea |
| Recognition | Celebrating improvements that moved a strategic KPI, alongside the rest |
Every mechanism in that list works by changing what people notice, not what they are allowed to do. That is the whole design. An approval gate would produce the same chart next quarter and a thinner pipeline the quarter after.
A worked example: three sites, one quarter
Here are three hypothetical sites, each choosing a focus KPI and changing its share of effort on strategic KPIs:
| Site | Share on strategic KPIs last quarter | Focus KPI chosen | Share this quarter |
|---|---|---|---|
| Site A | 45% | Services attach rate | 45% |
| Site B | 12% | On-time delivery | 35% |
| Site C | 20% | Scrap rate | 30% |
Site A is already well steered and keeps its mix. Sites B and C raise their share by choosing a focus KPI and scheduling two targeted kaizen events each. Nobody’s idea system changed; the direction did.
Site A is the row most programs would have overlooked, because its number needed no action. Leaving a well-steered site alone is a decision, and making it deliberately is what stops a steering exercise turning into a uniform target that penalizes the site already doing it right.
What each failure mode costs
Site B is the arithmetic worth doing. Eighty-eight percent of a site’s structured improvement capacity was going somewhere other than the measures the plan depends on, for a full quarter. Nothing was wasted in the ordinary sense; every one of those improvements fixed something real. But the breakthrough the year is staked on got the leftovers, and that is an expensive way to find out in December.
The opposite failure costs more and recovers slower. A mandate that every improvement name a strategic KPI reliably produces a short-lived spike in the share, then a collapse in volume, because people stop raising the local problems that do not fit. Rebuilding a suggestion habit takes a year or two; moving a share from 12% to 35% takes a quarter.
Among published alternatives for seeing the share at all, OnStrategy lists $200 per month for unlimited users, which fits when every team needs to see its own mix. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. For either, test the exact table above: can you produce share-by-site-by-KPI for last quarter without an export, and can a site set a focus KPI that shows up on its huddles?
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate, which suits wide, light use at the point where improvements are raised. Hoshin Kanri, OKRs and Goals and Balanced Scorecard sit in Essentials, and the 30-day free trial is enough to load last quarter’s records and see your own version of the three-site table.
The share, visible by site
In Profit.co, improvement ideas link to the strategic KPI they should move, so the share of effort by KPI and site is visible, and huddles from daily to quarterly can carry a focus KPI on the same objectives as the hoshin plan. See the lean strategy software page.
Two things follow that make steering light rather than administrative:
- The share is a reading, not a report. Nobody compiles it, so the quarterly conversation starts from a number neither side can dispute.
- A focus KPI is a setting, not a campaign. It appears on the site’s huddles against the objectives the plan already tracks, so it steers attention without anyone approving an idea.
The field that makes all of this possible is described in Linking Kaizen and CI Projects to Strategic KPIs, and the same discipline applied to formal projects is in Aligning Lean Six Sigma Projects With Strategy.
Free Product Demo
Set your improvement share by KPI
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
There is no universal number. Many organizations find a third to a half of structured effort on strategic KPIs is enough. Set it by what each strategic KPI needs.
Use quarterly focus KPIs, targeted kaizen events and visible effort reporting, not approvals or mandates, and protect space for base and local improvements.
Ideas tend to dry up and local problems go unsolved, because improvement starts to feel like another top-down program.
No. Raise it for the KPI that needs it. A site already at 45% against the right measure needs no target; one at 12% needs a specific conversation.
A quarter, with a focus KPI and two targeted events. Recovering a suggestion habit killed by a mandate takes a year or more, which is why steering beats mandating.