OKRs in manufacturing: what a plant needs beyond them

OKRs work in a plant for what they are: a way to choose a few objectives and say how each will be measured. What a plant needs beyond them is what the OKR guides do not describe: a line between improving and keeping to standard, links across functions, a negotiation about means, and reviews on a fixed rhythm, from the week to the year. Hoshin Kanri, which came out of Japanese industry, was built around those four things.

This page is for a plant manager or an operations director who has been handed OKRs by a group, or who is about to adopt them. It says where they hold, where they stop, and how to add what is missing without starting over.

What OKRs do well, in a plant too

Three to five objectives, about three measurable results for each, reviewed every quarter: Google’s guide describes a discipline of choice that suits any team. In a plant it fits well the work that looks like a project: launching a product, starting a line, a team in methods, purchasing or maintenance with a clear quarterly goal.

It also brings a habit worth keeping: results worded as outcomes, not activities. "Scrap on line 3 below 2%" is a key result; "run a scrap workshop" is not.

Four things a plant needs that the guides do not describe

None of these is a flaw of OKRs. They are outside what the method sets out to do.

  • A line between improving and holding the standard. Most of what a plant measures every day (safety, quality, delivery, cost) is daily management: keeping the existing business to standard. Hoshin Kanri, in Akao’s account, is the other kind of management: the few changes of the year. Mixing the two in one list of OKRs drowns the priorities.
  • Links across functions. A quality objective is carried by methods, production, purchasing and quality together. OKRs nest from the group to its teams; they do not show that this initiative in methods and that indicator in production serve the same objective. The corners of an X-Matrix do.
  • A negotiation about means. A plant commits with machines, hours and people. In catchball, each level answers a target with what it would take to reach it, before anyone commits. Google’s OKR playbook asks managers to assess the resources an aspirational objective requires and to ask for them each quarter; it does not describe how the answer is negotiated.
  • Reviews at several levels. A plant already meets every week and every month. Hoshin gives each level of review its place and puts the same page on the table, where OKRs are graded once a quarter.

What it looks like on one objective

Take the fictional machining company of our demo, Hoshimeca. Written as an OKR, its quality objective would read: "Customer non-conformity from 1.8% to 0.8%", with key results. On its X-Matrix, the same objective sits in a chain that can be read line by line.

  • Long-term objective: zero customer defects, aerospace-grade quality on every line.
  • Annual objective: customer non-conformity from 1.8% to 0.8%.
  • Initiative: in-line quality control with machine vision, in the milling shop, with an owner.
  • Indicator: internal defect PPM, 720 against a target of 450. It is a performance indicator: it moves before the customer rate does.

What the page then shows

The same matrix carries two gaps left on purpose in the demo: an annual objective on absenteeism that no initiative carries, and an initiative on the employer brand that serves no objective. A list of OKRs would show neither, because nothing in it says what serves what. You can read them yourself on the demo, without an account.

If the group has handed you OKRs

Keep them as the interface with the group, and run the plant on a matrix. The group’s objectives for your site become your annual objectives. Your key results become indicators with a monthly reading. The plant’s projects become initiatives with an owner, each linked to the objective it carries. At the end of the quarter you report to the group in its format, from numbers the plant already reviews every month.

The move, line by line and over one quarter, is in from OKR to Hoshin Kanri. In a group with several sites, each site has its own matrix that takes up lines of the one above: what the group decided and no site carries shows at once.

And with agents on the shop floor

An AI assistant that reads the plant every morning sees the gap to yesterday and to the standard. To say whether a gap matters, it needs what the plant decided to improve this year, with the links. That is a matrix, not a list of quarterly objectives.

We tried this once, on November 13, 2026, on a copy of our demo plant with synthetic records: the assistant wrote a monthly quality reading resting on the 20 complete days out of 22 and named the two others, and opened one improvement idea for a defect that kept coming back. It was not a real plant. The account, with what was not tested, is in agentic lean, and the wider picture in Hoshin Kanri for manufacturing.

Frequently asked questions

Do OKRs work in manufacturing?

For what they are, yes: choosing a few objectives and saying how each is measured, especially for project-like work such as a product launch. What they do not describe is daily management, the links between functions, the negotiation of means and reviews at several levels, which a plant needs to deploy a strategy.

Should safety, quality and delivery indicators be OKRs?

Mostly not. Keeping them to standard is daily management, with its own boards and routines. They become objectives of the year only where the plant has decided to change the level: for instance bringing customer non-conformity from 1.8% to 0.8%.

Our group imposes OKRs. Can a site still use Hoshin Kanri?

Yes. Treat the group’s OKRs as the objectives your site receives: they become the annual objectives of your X-Matrix, with your initiatives and monthly indicators underneath. You report to the group in its format, from the same numbers.

Is Hoshin Kanri heavier than OKRs?

It asks for more at the start: writing the long-term objectives, drawing the links, one round of catchball. In return, the reviews have a standing agenda and the gaps show on the page. For a small team with a short horizon, OKRs alone are often enough.

Sources