When a plant introduces OKR, the first question is usually: do we still need our KPIs? The second one comes from the leadership team: what about our strategy deployment?
Both questions have the same answer. The three tools do different jobs, and most operations organizations need all three.
Three jobs
| OKR | KPI and health metrics | Hoshin Kanri | |
|---|---|---|---|
| Purpose | Change something in one quarter | Keep the business healthy | Breakthrough over several years |
| Horizon | Three months | Ongoing, daily or weekly | Three to five years |
| Number | One to three objectives per team | Five to ten per area | Three to five per company |
| Ambition | Stretch, 0.7 is a good score | Hold the standard | Breakthrough, yearly targets |
| Linked to pay | No | Sometimes | Sometimes |
KPIs and health metrics keep the daily business stable. Safety, output, scrap, inventory accuracy and overtime stay on the shop floor board. They have a range, and when a number leaves it, the team reacts.
OKR are the change layer. They describe what a team will make different in the next thirteen weeks and how it will prove it.
Hoshin Kanri, often called strategy deployment, sets a few breakthrough objectives for several years and deploys them down the organization with catchball and an X-matrix. It is heavier, slower and more binding.
How they fit together
Think of three levels. At the top, the plant has a multi-year direction, for example delivery reliability above 97 percent by the end of 2027. In the middle, each quarter, teams choose OKR that move toward it. At the base, health metrics make sure that nothing else breaks while the teams work on the change.
A health metric becomes an OKR only when it leaves its range and needs a real change to get back. When purchasing saw supplier delivery reliability fall below 92 percent for two months, causing eleven line stops, it made that problem an objective for the next quarter. When the number is stable again, it returns to the board.
Where to start
A plant without any structured deployment should start with OKR in one area. OKR are easy to learn, give results within a quarter and build the habits that strategy deployment needs later: clear priorities, measured outcomes, a regular review.
When three or more areas run OKR well and the strategy needs a multi-year frame, add Hoshin Kanri on top. The breakthrough objectives then set the priorities that the teams use to write their OKR.
A plant that already runs Hoshin Kanri can use OKR as the quarterly layer for teams. The yearly targets stay, and the OKR translate them into what each team changes this quarter.
The one rule that matters
Do not put the same number in all three systems. If on-time delivery is a breakthrough objective, a team OKR and a health metric at the same time, nobody knows which conversation it belongs to. Give each number one home and one rhythm.