Hoshin Kanri sits at the intersection of strategy and execution. Most strategic plans fail there, in the gap between the boardroom whiteboard and the shop floor. 90% of organizations fail to execute their strategies, and 95% of employees are unaware of or don't understand their company's strategy. Those two numbers explain why Hoshin Kanri exists. It is not a grander planning framework. It is a system for closing the gap.
Hoshin Kanri is often taught as a standalone strategic planning framework, but its real power comes from how it connects strategy to daily improvement work, the same Kaizen and PDCA cycles Lean practitioners already use. It turns the strategy-execution gap into a closed-loop system where breakthrough objectives and daily improvement feed each other, making it a practical operating system rather than an annual planning exercise.
What Hoshin Kanri means
The phrase Hoshin Kanri (方針管理) means policy management and represents the concept of guiding an entire company in an agreed-upon, clear direction. It is made of three Japanese words: Ho (method), Shin (compass), and Kanri (management or control). The term translates roughly to direction management or compass management.
The compass metaphor is deliberate. A compass does not prescribe the terrain. It gives you a bearing, and you navigate from wherever you stand. That is how Hoshin Kanri works. Leadership sets the direction. Teams at every level figure out how to move toward it from their current position, and they feed back what they learn along the way.
Where Hoshin Kanri came from
Hoshin Kanri was developed by Professor Yoji Akao in Japan in the 1950s and became a cornerstone of the Toyota Production System. It grew out of the Total Quality movement in the early 1960s, with much of the technical detail developed by Japanese quality experts based on the experience of Bridgestone Tire Co..
Bridgestone is often cited as the first to formally adopt the term hoshin kanri and in 1965 published a study about hoshin kanri activities of various companies. Toyota followed closely. Toyota put its hoshin to paper for the first time in January 1963, consisting of three parts: basic hoshin, long-term hoshin, and annual hoshin. That three-part structure, vision, long-term goals, annual targets, is still the spine of Hoshin Kanri today.
The methodology also draws from two American quality pioneers. Hoshin Kanri is closely connected to Deming's Plan-Do-Check-Act cycle, as well as to Joseph M. Juran's teachings about the role of management in quality control methods needed for strategic development. What started as a Japanese manufacturing practice became a global management discipline.
The strategy-execution problem it solves
Strategy fails most of the time. The 90% failure rate and 95% employee unawareness figures are not outliers. They are the norm across industries and organisation sizes. The root cause is rarely the quality of the strategy itself. It is the distance between the people who set the strategy and the people who have to execute it.
Conventional strategic planning moves in one direction. Leadership sets goals. Middle management translates them into targets. Frontline teams receive their assignments. At each handoff, fidelity drops. By the time strategy reaches the people who do the work, it has been filtered through layers of interpretation, and none of the context that made the goals make sense survived the trip.
Hoshin Kanri breaks that pattern. It connects long-term strategy to annual goals to daily improvement work. The connection is not conceptual. It is built into the planning process through a mechanism called catchball, which we will come to shortly.
The 7 steps of Hoshin Kanri planning
The process follows a structured annual cycle. Each step builds on the one before it.
1. Establish the organisational vision and assess the current state
What is your current state with respect to your vision, business planning processes and execution engine? This step is honest. It asks what the organisation actually does well, where it stalls, and whether the existing planning process produces results or just documents. Skip this, and the rest of the cycle rests on assumptions.
2. Develop breakthrough objectives
Breakthrough objectives are significant improvements that require your organization to stretch itself and will take three to five years to achieve. These are not incremental targets. They are the two or three things that would transform the business if achieved. Most organisations try to pursue too many simultaneously. Three to five is the right range. If everything is a breakthrough priority, nothing is.
3. Develop annual objectives
Breakthrough objectives span years. This step asks: what will you need to achieve this year in order to reach those three- to five-year breakthrough objectives? Annual objectives are the bridge between the long-term vision and the current year's work. They convert ambition into a twelve-month scope.
4. Deploy annual objectives through catchball and the X Matrix
This is where Hoshin Kanri diverges from conventional strategic planning. Goals do not simply flow downward through the hierarchy. Through catchball, they move up and down. Leadership sets direction, teams pressure-test feasibility, and the plan adjusts based on ground-truth feedback. The X Matrix, which we will cover in detail, captures the result on a single page.
5. Implement annual objectives
This is where improvements are executed, using the most appropriate problem solving approach. Kaizen events, DMAIC projects, PDCA cycles, the method depends on the nature of the improvement. A structured Kaizen methodology delivers improvements up to 70%. Kaizen events are typically implemented over the course of one week and divided into three phases: Preparation, Implementation, and Follow-Up.
6. Monthly review
How successful is the organization in meeting the action plan deliverables? What corrective actions are needed for those that are behind? A monthly review fosters a culture of accountability and action. It is not a status report. It is a decision point. If something is off track, the review triggers a correction, not a note in the minutes.
7. Annual review
At the end of the annual cycle, a thorough review of the year's objectives shows how far ahead or behind the organization is against the stated objectives and what adjustments must be made to the next cycle. The annual review closes one cycle and feeds the next. It is where the organisation learns whether its breakthrough objectives still make sense or whether the current state has shifted enough to warrant a new direction.
Catchball: the mechanism that makes it work
Catchball is the defining mechanism of Hoshin Kanri. It is the structured two-way dialogue between leadership and employees that ensures strategic objectives are both communicated effectively and refined based on input from all levels.
The metaphor is literal. Leaders throw the ball, teams catch it, pressure-test it, and throw back feedback. Senior leaders define a goal and pass it down to mid-level management. Those managers provide tactical input and toss it further down the chain. The ball moves back up carrying operational reality.
The typical catchball cycle has six steps:
- Set a clear objective. Leadership defines a strategic direction aligned with company goals.
- Toss the ball. Share the strategy with mid-level managers or relevant team leaders.
- Collect feedback and suggestions. Encourage modifications based on operational experience and practical insights.
- Evaluate input collaboratively. Discuss the suggestions as a team and refine and improve the original plan.
- Loop back to leadership. Present revised strategies for approval or further iteration.
- Cascade and repeat. Push the aligned plan down to individual contributors, repeating the cycle as needed.
Without catchball, strategy deployment becomes top-down command-and-control and the 90% failure rate applies. With it, employees understand how their daily work connects to breakthrough objectives, and leaders get ground-truth feedback before committing resources to the wrong priorities.
The X Matrix: strategy on one page
The X Matrix is the visual centre of Hoshin Kanri. It places the entire strategic plan, from multi-year breakthrough objectives down to responsible owners, on a single page.
The matrix is split into four quadrants, planned in this order:
| Quadrant | Position | What it contains |
|---|---|---|
| South | Bottom | 3 to 5 Year Breakthrough Objectives |
| West | Left | 1 Year Breakthrough Objectives |
| East | Right | Targets (KPIs and metrics) |
| North | Top | Improvement Priorities (the work to be done) |
The matrix answers five key questions: What do you want to achieve in 3 to 5 years? How far do you want to go in the first year? How are you going to do it? How will you measure success? Who is responsible?
The top-level X Matrix is then cascaded into second and third-level matrices, translating strategic objectives into specific goals and initiatives for each functional area. These intermediate matrices ensure both vertical and horizontal alignment, allowing each team to understand its direct contribution to achieving the organisation's overall goals.
A note of caution: Toyota itself never used the Hoshin Planning Matrix, in trust that tools like that could degrade into fancy charts that do not produce any discipline or focus on improvement. The X Matrix is a tool, not the method. It works when it reflects real catchball conversations. It fails when it becomes a wall decoration.
Hoshin Kanri and Kaizen: two sides of the same coin
Kaizen delivers incremental, daily improvements; Hoshin Kanri sets the strategic direction. Kaizen, meaning "change for the better," is the discipline of making small, incremental improvements continually. Instead of waiting for big transformation projects, Kaizen focuses on steady progress that compounds over time.
They need each other. Without integration, Kaizen can drift off-strategy, and Hoshin Kanri can become stagnant. Kaizen without direction produces activity without progress. Hoshin Kanri without Kaizen produces plans without execution.
When they work together, strategy and improvement feed each other in a closed loop:
- Set Strategic Objectives (Hoshin Kanri): Annual objectives cascade to departments and teams.
- Identify Improvement Opportunities (Kaizen): Teams spot daily problems and propose solutions.
- Filter and Align: Evaluate Kaizen ideas against strategic objectives.
- Implement and Measure: Track the impact of improvements using KPIs in the X Matrix.
- Review and Adjust: Monthly and quarterly Hoshin reviews incorporate Kaizen results and redirect focus.
This loop is what makes Hoshin Kanri an operating system rather than an annual planning exercise. Strategy informs improvement. Improvement informs strategy. Neither operates in isolation.
Is Hoshin Kanri a Lean tool?
Hoshin Kanri is a Lean approach used for strategic company-wide improvements. But calling it a tool understates what it does. Hoshin kanri is more than a strategic planning tool. It is a dynamic, socio-technical process that aligns organizations at every level through shared purpose, problem-solving, and continuous learning.
It embodies PDCA (plan, do, check, act), both long-cycle and short-cycle. The annual planning cycle is the long-cycle PDCA. The monthly reviews are the short-cycle PDCA. The daily Kaizen activity is the shortest cycle of all. Each level of PDCA feeds the one above and below it.
At Toyota, Hoshin Kanri's key focus has been to develop its people and leaders, not to be a cost-cutting, quick profit-making tool. It is a long-term philosophy focused on building a process relevant to producing the best results.
Common pitfalls and how to avoid them
Too many breakthrough objectives. Most organizations try to pursue too many breakthrough objectives simultaneously, diluting focus and resources. Three to five is the right range. Cut beyond that.
Objectives that ignore current-state constraints. Most hoshin failures start here, with objectives that ignore current-state constraints. A breakthrough objective that requires a capability you do not have is not a stretch goal. It is a wish. Assess the current state honestly before setting objectives.
Skipping catchball. When catchball is treated as a formality, the plan reverts to top-down. Leadership rejects grassroots ideas that do not perfectly match top priorities, and engagement collapses. The ball has to move both ways.
No alignment filter for improvement ideas. Approving every Kaizen idea without checking strategic fit spreads resources across unrelated problems. Not every good idea serves the breakthrough objectives.
One-way flow. Strategy informs improvement, but improvement insights don't influence strategy updates. The loop has to close. If frontline improvement data never reaches the strategy review, Hoshin Kanri is just a planning document with a Japanese name.
Treating it as a document rather than an operating system. The X Matrix is not the output. The aligned, improving organisation is the output. If the matrix is complete but the monthly reviews are not happening and catchball is not real, the organisation has produced a poster, not a plan.
How to get started
Start with where you are. Trying to copy Toyota's Hoshin Kanri without a preexisting Lean culture would be like expecting a kid playing in their backyard to perform a triple salchow. Your journey should start with maturing present working models before you begin emulating Toyota. If your current planning process is a spreadsheet emailed once a quarter, build the monthly review rhythm before introducing the X Matrix.
Limit breakthrough objectives to three to five. This is the single most important structural decision. It forces the organisation to choose, and choosing is what makes strategy real.
Use nemawashi. The Hoshin Kanri process uses nemawashi, a collaborative approach in which senior and mid-level management discuss the viability of proposed objectives before finalising them. This is the informal precursor to formal catchball. It surfaces objections and constraints before the plan is set, not after.
Build the review cadence from day one. The monthly and annual reviews are not optional. They are the engine of the system. If you are not prepared to run them, you are not prepared to run Hoshin Kanri. Start with the reviews, however simple, and build the rest of the process around them.
For organisations that already use Lean tools like KPI dashboards and goal statement templates, Hoshin Kanri provides the strategic framework that connects those tools to breakthrough objectives. SimplicityHub's academy offers training that helps continuous improvement leaders build the skills to run a full Hoshin Kanri cycle, from vision setting through monthly review.
Hoshin Kanri succeeds when it stops being a planning exercise and becomes how the organisation thinks about improvement. The compass points. The teams navigate. The feedback loops close. That is the system.