OKR vs Hoshin Kanri: what actually differs, and how to combine them
OKR and Hoshin Kanri answer the same question, how to align work with strategy, at different altitudes. OKR is a goal-setting method created at Intel and made famous by Google: objectives and key results, set for the year and the quarter. Hoshin Kanri is a strategy deployment method born in Japanese quality management: a direction over several years, deployed into the year and reviewed on a fixed rhythm.
The practical difference: OKR covers the objectives and how they are measured. Hoshin Kanri adds a direction over three to five years above them, explicit links between the layers, the catchball negotiation and a system of reviews. The two combine: objectives and key results have a natural place on an X-Matrix.
See also: From OKR to Hoshin Kanri: what to keep, what to add
The five real differences
Beyond vocabulary, five differences matter in practice:
- Time horizon. OKR: the year and the quarter. Hoshin: three to five years, deployed into annual objectives.
- Achievement philosophy. Google’s playbook expects committed OKRs at 1.0 and aspirational ones at 0.7 on average. A hoshin annual objective is always of the first kind: a commitment negotiated between levels.
- Alignment mechanism. OKR aligns by nesting: high-level OKRs for the whole group, more detailed ones for its teams. Hoshin aligns by links drawn one by one, which can be audited.
- Deployment process. OKR guides ask for a mix of top-down and bottom-up suggestions, without prescribing how. Hoshin names the step: in catchball, objectives go down and answers come back up until each level commits.
- Review system. OKRs are graded at the end of the quarter, and check-ins are a habit teams adopt or not. Hoshin schedules reviews at several levels, from the annual review to the weekly one, with the matrix as their agenda.
Where OKR wins
OKR is lighter to adopt, well documented for product and engineering teams, and its vocabulary is already spoken by many of the people you hire. For a young company whose horizon is eighteen months, a full X-Matrix is ceremony without payoff: annual and quarterly OKRs are enough structure.
OKR also has a named place for ambition: aspirational OKRs, expected to land around 0.7, invite stretch goals. A hoshin annual objective is a commitment, which can push teams to promise less than they can deliver if leadership does not run catchball honestly.
Where Hoshin Kanri wins
The OKR guides we read describe annual and quarterly objectives, and nothing beyond. Teams can hit their key results while the company drifts. The North of the X-Matrix forces the conversation about the next three to five years, and reading the links exposes work that supports nothing.
The second gain is the review system. Goals that are set and then forgotten kill both methods, but hoshin prescribes the cure: reviews at several levels where the matrix is the standing agenda. And the completeness checks have no OKR equivalent: does every objective have both a result indicator and a performance indicator? Does every long-term objective chain down to an indicator?
How to run both on one X-Matrix
The mapping is clean: annual objectives sit at the East of the matrix, key results at the West as indicators, projects at the South as initiatives. The X-Matrix adds the North, the direction over three to five years, and the links. Quarterly OKR cycles keep their rhythm while the matrix shows what they serve.
A team that runs both can keep its OKR habits, check-ins and grading, and use the matrix at the quarterly and annual reviews to re-anchor. The move itself, line by line and over one quarter, is in from OKR to Hoshin Kanri. An AI assistant connected to both layers can prepare each review: it brings progress from the execution tools into the initiatives, through those tools’ own MCP servers, and points out key results that no longer link to any objective.
Decision guide
Choose OKR alone if your horizon is under two years, your team under about thirty people, and your main problem is quarterly focus. Choose Hoshin Kanri if you have a real ambition over several years, an industrial or lean culture, or a leadership team that reviews strategy once a year and wants to change that. Combine them if you already run OKRs and keep asking "but where is all this going?": that question is the North of the matrix asking to exist. If a scorecard is also on the table, see Balanced Scorecard, OKR or X-Matrix; if you run a plant, see OKRs in manufacturing.
Frequently asked questions
Can OKR and Hoshin Kanri be used together?
Yes. Annual objectives go to the East of the X-Matrix, key results to the West as indicators, projects to the South as initiatives. Hoshin adds the long-term objectives at the North and the links between the lines, which OKR guides do not describe.
Is Hoshin Kanri older than OKR?
Yes. Hoshin Kanri took shape in Japanese industry in the 1960s, within the total quality movement. OKR was created by Andy Grove at Intel and taught to John Doerr, who brought it to Google’s founders in 1999 according to What Matters.
Which is better for a startup?
Usually OKR: lighter, quarterly, well documented for product teams. Hoshin Kanri starts paying off when a direction over several years exists and the organization is too big to align in one room.
What replaces OKR check-ins in Hoshin Kanri?
The review system: reviews at several levels (annual, quarterly, monthly, weekly) where the X-Matrix is the standing agenda. An AI assistant can prepare each one by bringing in progress from your execution tools, through their own MCP servers.
Sources
- Google re:Work, “Guide: Set goals with OKRs”
- Google, “Google’s OKR Playbook”, reprinted by What Matters
- What Matters, “What is an OKR? Meaning, definition and examples”
- Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991
- Japanese Standards Association, JIS Q 9023:2018, Guidelines for Policy Management