What is Hoshin Kanri? A definition, the X-Matrix and one example
Hoshin Kanri is a management method for deploying a strategy: leadership chooses a few changes for the year from its long-term direction, each level of the company answers with its own objectives and means, and regular reviews check that the work still serves the direction. In English it is also called policy deployment or strategy deployment.
It took shape in Japanese industry in the 1960s, within the total quality movement. Its best-known document is the X-Matrix, one page that links long-term objectives, annual objectives, initiatives and indicators. This page gives the definition, the four principles, how to read a matrix on one example, and what the method is not.
See also: The Hoshin Kanri process: the annual cycle, step by step
Hoshin Kanri in one page
The name says what it does. Hōshin (方針) is the everyday Japanese word for a policy or a course; it is written with the characters for direction (方) and needle (針), and the compass is the image usually given for it. Kanri (管理) means management or control. Hoshin Kanri is management by policy: the company is steered by a few chosen directions, and not only by its budget and its operations.
The board below holds the whole method: the four quadrants of the X-Matrix, the four questions they answer, and the four principles the primary sources share.

Four principles, from the primary sources
Yoji Akao’s book, published in Japanese in 1988 and in English in 1991, is the reference text. The Japanese standard JIS Q 9023 describes the method as guidelines for policy management, and Thomas Jackson’s 2006 book is the main source for the X-Matrix in lean companies. Four principles run through all three.
- Few priorities, chosen by leadership. The hoshin is a handful of changes for the year, not the list of everything the company does.
- Two kinds of management. Management by policy drives change; daily management keeps the existing business running to standard. Mixing them drowns the priorities.
- Catchball. Objectives are negotiated down and back up: each level answers the one above with its own means and its own targets. See the catchball guide.
- Plan-Do-Check-Act on the policy itself. Leadership reviews progress regularly, and the reflection at the end of the cycle feeds the next policy. Moen and Norman (2010) trace how the Deming cycle took that form in Japan in the 1950s.
The X-Matrix: four quadrants and their links
The X-Matrix puts the policy on one page, in four quadrants around a central X. The method came first: the one-page format appeared later, and Jackson’s book is its main reference, as the history of the X-Matrix explains.
- North: long-term objectives, the few breakthroughs on a horizon of 3 to 5 years.
- East: annual objectives, what must be true in 12 months for the long-term objectives to stay credible.
- South: initiatives, the improvement work of the year.
- West: indicators, how the company will know it is working, with a mix of result indicators and of performance indicators that move earlier.
- In the four corners, the links. Each one ties an element to an element of the neighboring quadrant, and has a strength: strong, medium or weak.
One example: follow a chain
Hoshimeca is the fictional precision machining company of the public demo, 120 people. Take one of its long-term objectives, “zero customer defects”. This year it becomes an annual objective: customer non-conformity from 1.8% to 0.8%. One initiative carries it, in-line quality control with machine vision in the milling shop. One indicator proves it early: internal defects per million, 720 today for a target of 450. Each line answers the one before it, and each link is marked strong.
The same matrix shows two gaps, left there on purpose. “Absenteeism below 4%” is an annual objective with no initiative: nobody is working on it. “Employer brand” is an initiative linked to no objective and no indicator: nothing says why it is funded. Neither gap is a formatting problem. Each one is a decision for leadership, to add the missing work or drop the objective, to link the initiative or stop it.

What Hoshin Kanri is not
Most misunderstandings of the method come from asking it to be something else.
- Not a list of projects. A portfolio says what is being done; the matrix says why, and what would prove it.
- Not daily management. Standards, routines and tasks live in the execution tools. The matrix carries only what changes this year.
- Not the pyramid of values, vision and mission. That comes from the corporate vision literature, notably Collins and Porras. Purpose and vision sit above the matrix, with leadership; the process guide shows where each level lives.
- Not OKRs. OKRs set objectives and key results per quarter and per team. Hoshin Kanri adds the long-term layer, the initiatives and the explicit links between the four. The two combine, as the OKR comparison details, and a team that already runs OKRs can move to Hoshin Kanri without starting from scratch.
- Not a top-down decree. Without catchball, the matrix is a list of targets nobody agreed to.
Reviews: where the method lives or dies
The sources ask for regular reviews by leadership and a reflection at the end of the cycle. The rhythm is each company’s choice: a common one is a monthly review of the annual objectives and a quarterly review of the long-term objectives. This is often where a deployment stops: the matrix is built in a January workshop, lives in Excel or PowerPoint, and nobody updates it after March.
What keeps a matrix alive is unglamorous work: taking the reading of each indicator, noting the progress of each initiative, preparing the review, writing down what was decided. The matrix is worth what its last review is worth, and a review is worth its questions: the guide on the routines of questions covers the coaching kata, the A3 dialogue and the after-action review.
With AI agents: who does what
That upkeep is the part an AI agent can take on. Connected to the matrix over MCP, an assistant reads what is due before the next review, takes the readings, prepares the review and records its decisions. Progress on the initiatives comes from the execution tools through their own MCP servers; hoshin.app itself reads no plant or project system. The agent scenarios show real runs on the demo.
The split of roles is the method’s own. Leadership chooses the objectives and the trade-offs, teams choose how to reach their targets, and the agent prepares, updates and records. For Claude, a plugin packages this as eight skills; it also sits above the plant skills of Claude for Manufacturing, which run the day without knowing what the year is for.

Is Hoshin Kanri right for your organization?
It fits organizations that have a real multi-year ambition and will hold the reviews: industrial SMEs and mid-caps with a lean culture, groups that need the same direction across several sites, and leadership teams tired of a strategy that lives in a slide deck. It is too much for a team of five with one product and one goal. An IT department will have its own questions about agents and data: they are answered in Hoshin Kanri for IT departments.
Frequently asked questions
What does “Hoshin Kanri” mean literally?
Hōshin (方針) means policy or course, and is written with the characters for direction (方) and needle (針); the compass is the image usually given for it. Kanri (管理) means management or control. Together: management by policy. The usual English names are policy deployment and strategy deployment.
What is the difference between Hoshin Kanri and the X-Matrix?
Hoshin Kanri is the method: few priorities, catchball, reviews, Plan-Do-Check-Act on the policy. The X-Matrix is its best-known document, one page that links long-term objectives, annual objectives, initiatives and indicators. The method came first; the one-page format appeared later.
Who invented Hoshin Kanri?
No single inventor. The method grew out of Japanese industry in the 1960s, within the total quality movement. Yoji Akao’s book (1988 in Japanese, 1991 in English) is the reference text, and JIS Q 9023 made it a Japanese standard.
How long does a Hoshin Kanri cycle take?
The cycle is annual, framed by long-term objectives at 3 to 5 years. Inside the year, leadership reviews progress regularly, and a reflection at the end of the cycle prepares the next one.
Do I need software to run Hoshin Kanri?
No. The method predates software, and many teams start in a spreadsheet. What a spreadsheet does not do is check the links, keep the history of readings and decisions, or give an agent a structured way to update the matrix.
Can AI agents help with Hoshin Kanri?
Yes, with the upkeep: taking readings, noting progress, preparing reviews, recording decisions, checking that every objective is served. Choosing the objectives, running catchball and deciding the trade-offs stay with people.
Sources
- Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991
- Japanese Standards Association, JIS Q 9023:2018, Guidelines for Policy Management
- Thomas L. Jackson, Hoshin Kanri for the Lean Enterprise, Productivity Press, 2006
- James C. Collins and Jerry I. Porras, “Building Your Company’s Vision”, Harvard Business Review, 1996
- Ronald Moen and Clifford Norman, “Circling Back: Clearing up myths about the Deming cycle”, Quality Progress, November 2010