Hoshin Kanri
Hoshin Kanri ("direction management", usually rendered policy deployment) grew inside 1960s Japanese manufacturing on Deming’s PDCA foundations. It is the goal-setting shelf’s grandparent, and it was right about almost everything first.
Its machinery: a True North direction, a handful of annual breakthrough objectives deliberately separated from daily management, the X-matrix correlating objectives, initiatives, metrics and owners on one page, and review cycles running up to the president's diagnosis.
What it teaches, and what we carry
Hoshin's crown jewel is catchball: objectives are not handed down, they are thrown back and forth between levels, each catch adding local knowledge the level above does not have, until both sides genuinely commit. This is aligned, not cascaded proven at industrial scale decades before OKRs existed; when a client hears "aligned, not cascaded" as a novelty, Toyota is the receipt. Hoshin also drew the breakthrough-versus-daily wall a generation early: hoshin objectives are the few things that change the company, daily management keeps it running, the same separation as OKRs versus business-as-usual on the KPI scorecard, and EOS rediscovered it again fifty years later. Three eras, one wall. Its PDCA inheritance makes review a learning act rather than an accounting one, the ancestor instinct behind graded retrospectives, and the X-matrix's insistence that objectives, initiatives, metrics and owners appear on one connected page is metric trees and strategy alignment in a single artefact.
The natural hybrid
Hoshin's rhythms were tuned to manufacturing: annual planning cycles, capital timelines, physical processes. Software-speed companies keep Hoshin's architecture and quicken its pulse, which is essentially what modern OKR practice is: catchball compressed from weeks into the OKR creation process, with the executive sponsor as a standing catchball partner rather than a seasonal one; breakthrough objectives refreshed quarterly; the president's diagnosis distributed into weekly check-ins and confidence assessment. Companies with Hoshin heritage (manufacturing, hardware, pharma) should treat that lineage as an asset when adopting OKRs: the hard cultural work, dialogue over dictation and review as learning, is already done, and only the clock needs changing. The full lineage is mapped at Goal Setting.
One line to keep: OKRs are Hoshin Kanri at software speed; catchball got there first.
Credited to the Japanese quality movement: Bridgestone, Toyota, Komatsu, on Deming’s PDCA foundations. Machinery connections are ZOKRI methodology.
Can Hoshin Kanri and OKRs run together? +
They are the same architecture at different speeds. Companies with Hoshin heritage keep catchball and the breakthrough-versus-daily wall, and quicken the pulse: quarterly objectives, weekly check-ins, confidence assessment. The cultural work is already done; only the clock changes.
What is catchball in OKR terms? +
Aligned, not cascaded: objectives thrown between levels until both sides genuinely commit, compressed from weeks into the OKR creation process with the executive sponsor as a standing partner.
If your company has Hoshin heritage, you are closer than you think. We change the clock, not the culture, and install the OS that runs the new pulse.