Hoshin Kanri vs OKRs: turning strategy into what teams do on Monday
Two proven ways to connect strategy to daily work. How Hoshin Kanri cascades a breakthrough objective with catchball and monthly reviews, how OKRs set quarterly stretch goals, one worked example in both, and when to combine them.
Most companies don't lack strategy. They lack the connection between the strategy slide and what a team lead decides to do on Monday morning. In a survey of 7,600 managers across 262 companies, only 55% of middle managers could name even one of their company's top five priorities. By the time a five-year ambition has passed through three layers of management, it has usually turned into forty initiatives, each with its own dashboard, and nobody can say which three matter most.
Two methods are built to close that gap. Hoshin Kanri came out of Japanese quality management and is the backbone of strategy deployment in lean organisations. OKRs, objectives and key results, came out of Intel and spread through Google to much of the tech world. They solve the same problem differently, and they work well together.
Hoshin Kanri: few things, fully deployed
Hoshin kanri roughly translates as "direction management". It grew in Japanese companies from the 1960s and was brought to Western readers by Yoji Akao's book Hoshin Kanri: Policy Deployment for Successful TQM. Its central idea is ruthless focus: choose a vital few breakthrough objectives, and make sure every level of the organisation knows exactly how its work contributes to them.
The structure has four levels:
| Level | Horizon | Example |
|---|---|---|
| Breakthrough objective | 3 to 5 years | Halve order-to-delivery lead time |
| Annual objectives | This year | Cut lead time 20%; raise on-time delivery to 95% |
| Top-level priorities | This year | Pull planning in two plants; a supplier lead-time program |
| Targets and measures | Monthly, per team | Plant A: WIP down 30% by June. Procurement: 10 suppliers on vendor-managed inventory |
On paper, many companies show all of this on a single page called an X-matrix: the four levels around the edges and small correlation grids in the corners, showing which priority serves which objective and who owns what. Thomas Jackson's Hoshin Kanri for the Lean Enterprise popularised it. It looks intimidating the first time, but its purpose is simple: to prove that every priority serves an objective, and every objective has someone working on it.
Catchball: the part people skip
In a top-down cascade, targets fall on teams like weather. In Hoshin, each level proposes how it will contribute, the level above reacts, and the ball goes back and forth until both agree. The plant manager might say: "30% less WIP is possible in Plant A by June, but only if maintenance gets two extra technicians." That conversation either finds the resources or adjusts the target, before the year starts rather than in a painful review in October.
Catchball takes time. It's also what turns targets into commitments.
Monthly reviews and the bowling chart
Hoshin runs on a monthly check: plan versus actual, with red and green, for every target. The usual tool is a bowling chart:
| Measure (Plant A) | Target by June | Jan | Feb | Mar | Apr |
|---|---|---|---|---|---|
| Work in process (units) | 7,000 | 9,600 | 9,100 | 8,900 | 8,000 |
| Monthly plan | 9,500 | 9,000 | 8,500 | 8,000 | |
| Status | Red | Red | Red | Green |
A red month doesn't trigger blame. It triggers a short countermeasure, often on a single A3 page: what's the gap, why, and what will we do. The discipline is the rhythm: every month, every target, same format. It's PDCA applied to strategy.
OKRs: quarterly focus and stretch
OKRs were developed by Andy Grove at Intel and brought to Google by John Doerr in 1999. The format is compact:
- An objective: qualitative, directional, memorable. What do we want to achieve?
- Three to five key results: measurable, time-bound. How will we know we got there?
The same lead-time ambition, written as one quarter's OKR for the operations team:
A few conventions matter:
- Key results are outcomes, not tasks. "Launch the new planning tool" is a task. "Lead time from 12 to 10 days" is a result.
- They're meant to stretch. In the Google tradition, scoring around 0.6 to 0.7 on an ambitious OKR is healthy. Hitting 1.0 every time suggests the goals were too safe.
- They're usually kept separate from pay. Tie them to bonuses and people stop setting ambitious ones.
- They're transparent. Everyone can see everyone's OKRs, which is how alignment happens without a formal cascade.
Side by side
| Hoshin Kanri | OKRs | |
|---|---|---|
| Horizon | 3 to 5 years, then annual | Usually quarterly, sometimes annual |
| Focus | A vital few breakthroughs | A few objectives per team, per quarter |
| Alignment | Formal cascade with catchball | Transparency and linking, lighter touch |
| Targets | Committed, expected to be met | Often stretch; 70% can be success |
| Review | Monthly, plan vs actual, countermeasures | Weekly check-ins, quarterly scoring |
| Visual tools | X-matrix, bowling chart, A3 | OKR lists, scorecards |
| Best fit | Operational transformation over years | Fast-moving teams, product and growth goals |
| Common failure | Heavy paperwork, too many priorities | Task lists as key results, goals disconnected from strategy |
Using both
The two fit together naturally. Hoshin sets the direction and the annual commitments, which rarely change. OKRs describe how each team will move those numbers this quarter, and can change every three months as teams learn.
In the example, the breakthrough objective and the annual targets come from Hoshin. The operations team's quarterly OKR above is how they plan to deliver their part of the 20% lead-time cut this year. The monthly bowling chart tracks the committed annual numbers; the OKR check-ins track the quarterly bets.
Mistakes that break strategy deployment
- Too many priorities. If everything is a breakthrough, nothing is. Three to five objectives at the top is plenty.
- Cascading by copy and paste. Each level should translate the target into its own terms and levers, not repeat the level above.
- Skipping catchball. Targets set without the people who deliver them become targets nobody believes.
- Key results that are task lists. Measure the change, not the activity.
- No review rhythm. Without a monthly or weekly check, both methods decay into annual paperwork.
- Linking stretch goals to pay. People will protect their bonus by setting safe targets.
Whichever method you choose, the test is the same. Ask a team lead what the company's top three priorities are this year, and which of their own targets serves each one. If they can answer in a minute, the strategy has been deployed.
Sources
- Lean Enterprise Institute. Strategy deployment and hoshin kanri. Lean lexicon.
- Akao, Y. (ed.). Hoshin Kanri: Policy Deployment for Successful TQM. Productivity Press.
- Jackson, T. L. (2006). Hoshin Kanri for the Lean Enterprise. Productivity Press.
- Doerr, J. (2018). Measure What Matters. Portfolio/Penguin.
- Grove, A. S. (1983). High Output Management.
- Sull, D., Homkes, R. & Sull, C. (2015). Why strategy execution unravels, and what to do about it. Harvard Business Review.
- Sull, D., Sull, C. & Yoder, J. (2018). No one knows your strategy, not even your top leaders. MIT Sloan Management Review.
- Locke, E. A. & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation. American Psychologist, 57(9).
The manufacturer and its targets are illustrative.