Hoshin kanri is a strategy deployment method that aligns an organisation's few breakthrough objectives with annual goals, team targets and daily work. "Hoshin" means direction or compass, and "kanri" means management. Leaders set direction, teams negotiate how they will contribute through "catchball", and progress is reviewed through regular PDCA cycles until the next annual plan.
Originally written by Paul Dunlop. Updated in October 2026 by the TeamAssurance team with the 7-step process and how hoshin kanri connects to tiered daily management.
What Hoshin Kanri Means
Hoshin kanri is often translated as "policy deployment" or "direction management". The image behind the name is a compass needle: everyone in the organisation pointing the same way. The method emerged in Japanese industry in the 1960s, building on Deming's PDCA cycle and management by objectives, and was adopted by Toyota and later by lean organisations around the world.
Three ideas set it apart from ordinary annual planning:
- Focus on the vital few. A hoshin plan has three to five breakthrough objectives, not a long wish list. Everything else is managed through daily management.
- Plans are built with people, not handed to them. Through catchball, each level proposes how it will contribute and the level above responds, until targets and the means to reach them are agreed.
- The plan itself runs on PDCA. Progress is checked every month, gaps trigger countermeasures, and an annual reflection feeds the next year's plan.
A strategy acts as the rudder of the ship: it keeps the organisation on course as conditions change. Hoshin kanri is how you make sure the whole crew is steering by the same rudder.
The 7 Steps of Hoshin Kanri
Step 1: Set the long-term vision
Agree where the organisation must be in three to five years. Keep it concrete enough to test decisions against, for example "the most reliable supplier in our category" rather than "world class".
Step 2: Pick 3–5 breakthrough objectives
Choose the few changes that would transform performance if achieved, such as halving the cost of poor quality or reaching zero lost-time injuries. If an objective can be reached by doing the same things a little better, it belongs in daily management, not in the hoshin plan.
Step 3: Set this year's objectives
Decide what must be true by the end of this year to stay on track for each breakthrough objective. Each annual objective needs a measure and a target.
Step 4: Deploy through catchball
Each level takes the objectives from the level above and proposes how it will contribute: the improvement priorities, the measures and the resources it needs. The level above responds, and the ball goes back and forth until both agree. Catchball is where commitment is built, and it draws on the consensus-building practice of nemawashi. It is also where unrealistic plans are caught before they fail.
Step 5: Execute
Improvement priorities become projects, A3 problem solving and actions with owners and dates. The key is to track them where work is already managed, in the daily and weekly tier meetings, rather than in a separate strategy spreadsheet that nobody opens.
Step 6: Review monthly
Leaders review each objective against its target, usually with a simple green, amber or red status and a trend. When a goal is off track, the owner brings the cause and a countermeasure, not just a status update.
Step 7: Reflect annually (hansei)
At year end, reflect honestly on what worked, what didn't and why. Those lessons are the first input to next year's step 1, so the planning process improves through the same PDCA loop as the work itself.
How Hoshin Kanri Connects to Tiered Daily Management
Most hoshin plans fail in the gap between the annual plan and the shift floor. The objectives are clear in the boardroom, but on Tuesday morning a line team is fighting the same breakdowns as always and can't see how their work connects to the strategy.
Hoshin kanri was never meant to replace daily management. It depends on it. The breakthrough work runs through the same tiered daily management structure that runs the business every day:
- Tier 1 (daily, 5–10 minutes, frontline team). The team's hoshin-linked measure, such as label defects per shift, sits on the tier board next to safety and output. New problems are raised and owned the same day.
- Tier 2 (daily, 15–20 minutes, supervisors). Unresolved Tier 1 issues are escalated, and actions from the A3s behind each priority are checked for progress.
- Tier 3 (weekly, 30–45 minutes, site leaders). Trends are reviewed and resources are moved to where a goal is at risk.
- Monthly hoshin review. Goal status comes from the same data the teams discuss every day, so there is no separate strategy report to compile.
This is what "linking the top to the bottom" means in practice. Strategy travels down through catchball; results, problems and ideas travel back up through the tiers. Each loop runs on PDCA, and each one makes the other more reliable.
Hoshin Kanri vs OKRs vs Balanced Scorecard
| Hoshin kanri | OKRs | Balanced scorecard | |
|---|---|---|---|
| Core idea | Deploy a few breakthrough objectives to every level and review them through PDCA | Set ambitious objectives with measurable key results | Measure strategy across financial, customer, internal process and learning perspectives |
| Time horizon | 3–5 year vision, annual objectives, monthly reviews | Usually quarterly | Annual, with periodic reviews |
| How goals are set | Catchball between levels | Mix of top-down and team-proposed | Mostly top-down, often with strategy maps |
| Link to daily work | Strong: priorities run through A3s and tier meetings | Varies by organisation | Indirect, through measures |
| Best suited to | Operations-heavy organisations running lean | Fast-moving teams wanting focus and transparency | Leadership teams wanting a balanced view of performance |
The approaches can be combined. Many operations use hoshin kanri for site and department strategy and a balanced set of measures on their tier boards.
5 Common Hoshin Kanri Mistakes
- Too many objectives. When everything is a priority, nothing gets real resources. Hold the line at three to five.
- Top-down cascading without genuine catchball. Targets that are imposed rather than negotiated get compliance, not commitment.
- Loading routine KPIs into the hoshin plan. Keeping the lights on belongs in daily management. Hoshin is for breakthrough change.
- Setting the plan and never reviewing it. A plan that isn't reviewed monthly with real data is a poster, not a plan.
- No link to daily work. If frontline teams can't see a hoshin-linked measure on their board, the strategy hasn't been deployed, only announced.
How TeamAssurance Supports Hoshin Kanri
TeamAssurance's Strategy Deployment capability lets you create goals with clear owners and dates and cascade them in a tree view, so each goal contributes to its parent. Goals can be linked to A3 reports, improvement activities and measures, and a monthly status history highlights goals at risk. Because strategic tasks are tracked through tiered daily management alongside the day-to-day, teams improve the business while running the business.
Frequently Asked Questions About Hoshin Kanri
What is hoshin kanri?
Hoshin kanri is a lean strategy deployment method. It focuses an organisation on three to five breakthrough objectives, deploys them to every level through catchball, and reviews progress monthly using PDCA.
What does hoshin kanri mean?
"Hoshin" means direction or compass and "kanri" means management or control. The name is often translated as policy deployment or direction management.
How do you implement hoshin kanri?
Follow the 7 steps: set a 3–5 year vision, choose 3–5 breakthrough objectives, set annual objectives, deploy them through catchball, execute through projects and A3s tracked in tier meetings, review monthly, and reflect at year end. Start with one site or division for the first cycle.
What is catchball in hoshin kanri?
Catchball is the negotiation between management levels during planning. One level proposes objectives and means, the next responds with what it can deliver and what it needs, and the exchange continues until both agree.
What is the difference between hoshin kanri and OKRs?
Both align teams around a small set of goals. Hoshin kanri adds a long-term vision, catchball, a close link to lean problem solving and a monthly PDCA review, while OKRs usually run on quarterly cycles with ambitious key results.
How long does a hoshin kanri cycle take?
The main cycle is annual, with monthly reviews in between. Breakthrough objectives usually look three to five years ahead, so most organisations see the full benefit after two or three cycles.
Want to see how TeamAssurance connects hoshin kanri goals to daily tier meetings? Book a demo.