OKRs vs Hoshin Kanri
Hoshin Kanri is an annual policy-deployment method built for stable, process-heavy organisations: a small number of breakthrough objectives negotiated down through the company by catchball, and reviewed rigorously. OKRs are quarterly, lighter and assume teams will work out the how themselves. Hoshin buys alignment through negotiation; OKRs buy speed through autonomy.
| Hoshin Kanri | OKRs | |
|---|---|---|
| Cycle | Annual, with monthly review | Quarterly, with weekly check-ins |
| Direction of travel | Top-down, negotiated back up (catchball) | Set locally, aligned to a written strategy |
| How alignment happens | Explicit negotiation, level by level | Comprehension of the strategy, not cascade |
| Assumes | A stable process you're improving | A changing environment you're betting in |
| Strength | Rigour, and genuine buy-in before commitment | Speed, focus and honest mid-course correction |
| Weakness | Slow, and heavy if the year changes shape | Drifts into a task list without real strategy above it |
| Home ground | Manufacturing, operations, regulated industries | Software, services, fast-moving markets |
Catchball is the bit worth stealing
The single best idea in Hoshin Kanri is catchball: an objective is thrown down a level, the level below pushes back with what it would really take, and it goes back up. Nothing is committed until both sides have argued.
Most OKR rollouts skip this entirely and then wonder why teams treat goals as something that happened to them. You don't need to adopt Hoshin to fix that. You need one honest round of push-back before the quarter is signed off.
If you take nothing else from Hoshin, take the rule that a target nobody argued about is a target nobody owns.
Where Hoshin genuinely beats OKRs
If your business is a process you're improving rather than a bet you're placing, an annual cycle isn't a weakness, it's a match. Changing direction every ninety days in a plant isn't agility, it's churn.
Hoshin also handles the relationship between improvement work and business-as-usual better than most OKR implementations, because the daily management layer is explicitly part of the method rather than an afterthought.
Where OKRs beat Hoshin
When you genuinely don't know the answer. OKRs are honest about uncertainty: you name the outcome you want, you accept you might be wrong, and you build in the checkpoints to find out early.
A twelve-month negotiated commitment is a poor container for a bet. If the useful unit of learning in your business is measured in weeks, the annual cycle will always be arriving after the answer.
Running both
Plenty of manufacturers do. Keep Hoshin for the annual breakthrough objectives and the daily management system, and use a quarterly OKR-style layer for the genuinely uncertain work: new products, new markets, anything where the plan is a hypothesis.
What breaks is running both as one thing. Two cycles is fine. Two cycles pretending to be one produces a plan nobody can recall.
Is Hoshin Kanri better than OKRs? +
Neither is better in the abstract. Hoshin fits stable, process-heavy organisations improving something they understand. OKRs fit organisations placing bets in uncertainty. The mismatch, not the method, is what usually causes the pain.
Can you use Hoshin Kanri and OKRs together? +
Yes, and it's common in manufacturing. Keep Hoshin for annual breakthrough objectives and daily management, and run a quarterly OKR layer over the uncertain work. Keep them visibly separate so people know which rules apply.
What is catchball? +
The Hoshin practice of passing a proposed objective down a level, having that level push back with what it would genuinely take, and passing it back up before anything is committed. It's the mechanism that produces real ownership rather than compliance.