Hoshin Kanri
Policy management: aligning breakthrough goals to daily work
Hoshin Kanri is a yearly planning and review cycle that ties a few breakthrough goals to the work of every team. Leaders set three to five long-range goals, each level agrees what it will do toward them through a back-and-forth called catchball, and progress is reviewed every month so the plan is corrected as the year goes.
TL;DR
- What it is
- A yearly cycle that ties a few breakthrough goals to the work of every team, agreed level by level and reviewed every month. Built by Japanese companies in the 1960s.
- Best for
- Companies with several levels or sites that need everyone pulling toward the same few goals for years.
- First cycle
- One to three months to set the goals and agree them down the levels, then a full year of monthly reviews.
- You leave with
- Three to five breakthrough goals, this year's targets for each, and an owner for every improvement that moves them.
- Breakthrough objectives (3 to 5 years)
- Annual objectives
- Improvement priorities
- Targets to improve
- Owners, agreed through catchball
Hoshin Kanri (roughly "direction management") keeps a whole organization pointed at a small number of breakthrough objectives for years at a time. Each year those objectives become annual goals, the goals become a few improvement priorities, and each priority gets targets and an owner.
Its discipline is "catchball": draft plans are passed down and back up until each level agrees on what it owns, so the strategy is negotiated rather than dictated. Many teams draw the result on a one-page "X-matrix," but that chart is a later Western format. The method is the cycle of agreeing, doing and reviewing.
The original Hoshin Kanri, in brief
Built by Japanese companies in the early 1960s as part of total quality control; Toyota and Komatsu were early users, and a Bridgestone study gave it its name. Its standard English text is "Hoshin Kanri: Policy Deployment for Successful TQM," edited by Yoji Akao (1991).
The standard English text is Hoshin Kanri: Policy Deployment for Successful TQM, edited by Yoji Akao and published by Productivity Press in 1991. It is a translation of a Japanese book from 19881. Akao documented and taught the method. He did not invent it2.
No single person or company did. Japanese manufacturers built the practice in the early 1960s as part of total quality control, the company-wide quality movement of the time2. Toyota wrote down its first company hoshin in 1963, and Komatsu was deploying targets through its own method by 1964, the year it won the Deming Prize2. A study by Bridgestone of how Deming Prize winners planned gave the practice its name. Sources differ on the year: 1965 in one history2, 1968 in a 2022 review3.
The words mean roughly "direction" and "management." Hoshin joins the characters for direction and needle, as in a compass. Kanri means to manage or control4. Akao's book sets out a yearly cycle: a long-range vision, a one-year plan, deployment to every level, the work itself, monthly reviews and a review at year end1. Plans travel down and back up through discussion, called catchball in English, until each level agrees what it will do3. The few breakthrough goals sit on top of daily management, the ordinary control of routine work, which the book treats as a partner system1.
Common misreadings
- "The X-matrix is hoshin kanri." The one-page X-matrix came into Western use through quality function deployment and the US consultancy GOAL/QPC. It was not part of Toyota's own hoshin system5. Thomas Jackson's 2006 handbook is the best-known Western guide to it6. You can run hoshin kanri without one.
- "Akao invented it." Companies had been running it for about 25 years when his edited book appeared in Japan2.
- "It is a lean tool from the Toyota Production System." It grew out of total quality control. It developed alongside lean production, not from it7.
- "Policy deployment means cascading goals down." The Japanese stresses managing, including checking and correcting. "Deployment" suggests a one-way rollout, which it is not4. Catchball sends plans back up before anyone commits.
- "Every goal belongs in the hoshin." Only the few breakthroughs do. Everything else is run through daily management1.
The Hoshin Kanri template
Breakthrough objectives (3 to 5 years)
The handful of goals that need real change to reach and that define the next few years.
Annual objectives
What must be true this year to stay on track for the breakthroughs.
Improvement priorities
The few initiatives that will move the annual objectives. Routine work stays out.
Targets to improve
The measures each priority must move, with a start and a target.
Ownership
Who owns each priority and measure, agreed through catchball rather than assigned.
Hoshin Kanri examples
A 300-person manufacturer
Two plants, and customers asking for shorter lead times every year.
A 120-person software company
Growing through new sales but losing too many customers after the first year.
A 900-person regional hospital group
Three hospitals with long waits for planned surgery.
When Hoshin Kanri fits, where it struggles, and what it does not answer
Use it when
- You have three or more levels of management, or several sites, and goals get lost between them.
- The goals take years, not a quarter, and each year has to add up to them.
- You already run regular reviews of numbers and want the strategy inside them.
- Middle managers feel handed targets they had no say in.
- A lean or quality program is improving things, but not the things the strategy needs.
It struggles when
- It takes time and people. At Rover Group, catchball for the quality strategy involved about 700 managers and took 12 months, by one review's account. The authors designed a faster method to shorten it83.
- It stalls when reviews lapse. A two-year study of three Japanese-owned plants in the UK found the hard parts were keeping periodic reviews going, changes of people and structure, and work that crossed departments9. In one plant the reviews faded after the general manager changed3.
- Too many goals. Another plant in the same study set so many goals that the system was hard to sustain3.
- It can feel too formal for a small company. In four Swedish manufacturers, a formal rollout worked only in part. The researchers proposed starting smaller and learning by doing10. In five small manufacturers, how the managers took part decided how far it went11.
- It assumes the strategy is chosen. It deploys breakthrough goals. It does not tell you what they should be.
What it does not answer
- Which breakthrough goals to pick. It carries a strategy; it does not make one.
- What is changing in your market, or what competitors will do.
- How to run a fast-moving startup whose goals change every quarter.
- Whether or how to tie pay or bonuses to the targets.
Pair it with
- Playing to Win Choose where to play and how to win first. Hoshin kanri then carries those choices to every team.
- Balanced Scorecard Adds a balanced set of measures for the long run. Researchers have argued the two work as one system12.
- OKR Some teams keep the hoshin for the multi-year goals and use quarterly OKRs for team-level focus.
How to implement Hoshin Kanri
- Set three to five breakthrough objectives. Goals that take several years and real change to reach. If a goal can be met by doing the same work harder, it belongs in daily management instead.
- Choose this year's objectives. For each breakthrough, write what must be true by the end of this year. Keep the list short; too many goals is a common reason the method fades.
- Run catchball down the levels. Each level drafts the priorities and targets it can own and sends them back up. Leaders adjust the plan where it does not add up, and repeat until both sides agree.
- Name owners and targets. Every priority gets one owner and a measure with a start and a target. Put it on one page, as an X-matrix or a simple table.
- Review every month. Look at what moved, what did not and why, and what changes. Keep the reviews going even in busy months; lapsed reviews are how the system dies.
- Review the year and plan the next. At year end, check each objective against its target and carry the lessons into next year's plan.
Adopting Hoshin Kanri: the first cycle and the rhythm
First cycle. Plan on one to three months before the year starts. Leaders draft the long-range goals and this year's objectives, then catchball runs down the levels and back until each owner agrees. Allow more time for more levels: the Rover case ran about a year3.
Rhythm. Akao's cycle reviews progress every month and the whole year at year end1. The monthly review asks what moved, what did not and why, and what changes. The year-end review feeds next year's plan.
How long until it runs itself. Expect several yearly cycles. The 2022 review found that results take a long time to show3. The first year mostly teaches people the rhythm.
What derails it. Letting the monthly reviews slip. A change of leader with no one else owning the process. Too many goals93. In small companies, managers who demand results without taking part themselves11.
How to set Hoshin Kanri at your leadership retreat
The decision the session has to produce: The three to five breakthrough objectives, this year's objectives for each, and a first draft of the improvement priorities to take into catchball.
A half-day outline
- Review last year: what the objectives were and what actually moved (30 minutes).
- Everyone writes the breakthroughs they would choose alone, before anyone speaks (20 minutes).
- Debate and choose three to five breakthrough objectives (60 minutes).
- Break.
- For each breakthrough, agree what must be true by the end of this year (45 minutes).
- Draft the improvement priorities and who will lead catchball on each (40 minutes).
- Set the catchball deadline and the date of the first monthly review (15 minutes).
Ask the team beforehand
- What would have to be true in three to five years for this company to be in a different league?
- Which of this year's goals could be met by doing the same work harder, and so belong in daily management?
- Which managers need to push back on these goals before they commit to them?
Who should be in the room
The CEO and the leadership team. The retreat sets the direction; the managers below take part in catchball afterwards, so their say comes before the plan is final.
Make a full retreat agenda with the free agenda maker.
Common Hoshin Kanri mistakes
- Too many objectives. A hoshin with a dozen goals is a to-do list. Keep three to five breakthroughs and let the rest run as daily management.
- Skipping catchball. Handing targets down with no chance to push back turns the method into top-down orders, and loses the commitment it exists to build.
- Mistaking the X-matrix for the method. Filling in the chart is the easy part. The value is in the agreement between levels and the monthly reviews.
- Letting reviews lapse. The monthly review is the engine. When it slips, or a new leader stops holding it, the plan quietly stops being managed.
- Putting routine work in the hoshin. Keeping the lights on is daily management. The hoshin is only for what needs to change.
Does Hoshin Kanri work? The evidence
The evidence is almost all case studies. Barry Witcher and Rosie Butterworth described Xerox's UK operation in Long Range Planning in 199913. In the Journal of Management Studies in 2001, they reported a two-year study, funded by the UK Economic and Social Research Council, that followed three Japanese-owned plants in real time9. One plant had saved millions of pounds and in 1997 was named its main customer's most improved supplier. Keeping the method going was still the hard part39.
A systematic review in Processes in 2022 searched two major research databases and kept 26 journal articles that describe real implementations. Of these, 23 were in Europe, spread over seven countries. Most were written by researchers who helped run the program they describe. The authors wrote that the results presented were "not very visible"3.
John Nicholas, in Total Quality Management and Business Excellence in 2016, reviewed studies of quality and lean programs. He argued that many factors linked to their success are built into hoshin kanri7. That is an argument from other research, not a test of hoshin kanri itself.
The research for this page found no study that compares companies using hoshin kanri with similar companies that do not, over time. Read it as a method with a long record in Japanese industry and many positive case reports, not as one proven to raise results.
Hoshin Kanri compared
| Hoshin Kanri | OKR | Balanced Scorecard | |
|---|---|---|---|
| Horizon | Three to five years, planned each year | Usually a quarter | A year or more |
| How goals are set | Drafted by leaders, agreed level by level through catchball | Set by teams, often both top-down and bottom-up | Set by leaders across four perspectives |
| What it covers | A few breakthroughs; routine work stays in daily management | Two or three objectives per team | A balanced set of measures for the whole strategy |
| Review rhythm | Monthly, plus a year-end review | Weekly or fortnightly check-ins | Monthly or quarterly strategy reviews |
After the retreat: Hoshin Kanri in Throughline
What it holds. The breakthrough and annual objectives become priorities, each with an owner, a date and a measure, and the improvement priorities sit under them and roll up into them. Owners check in from an email in one click on the rhythm you set; a missed check-in counts as off track and their manager is told.
What it doesn’t. Throughline does not draw an X-matrix or record how strongly each priority relates to each goal. Catchball happens in your own conversations, and daily management of routine work stays in your own systems.
Hoshin Kanri glossary
- Hoshin
- Direction or policy. The characters mean direction and needle, as in a compass4.
- Hoshin kanri
- Managing toward that direction: setting a few breakthrough goals, deploying them and reviewing them all year.
- Breakthrough objective
- One of the few goals that need real change to reach, usually three to five years out.
- Catchball
- The back-and-forth in which a draft plan is passed down, questioned and sent back up until both levels agree3.
- Nemawashi
- The Japanese practice of quiet, informal consultation before a decision. Catchball is close to it3.
- Daily management
- The routine control of normal work with standard measures, kept separate from the few breakthrough goals1.
- X-matrix
- A one-page chart that links long-range goals, annual goals, improvement priorities, targets and owners. A later Western format5.
- PDCA
- Plan, do, check, act: the improvement loop the whole yearly cycle follows.
- Top executive audit
- A review in which senior leaders visit units to check progress on the goals and the way they are being run12.
Free tools that help
Hoshin Kanri: frequently asked questions
- What is Hoshin Kanri?
- A yearly planning and review cycle that connects a few multi-year breakthrough goals to the work of every team. Goals are agreed level by level through catchball and reviewed every month.
- What is the X-matrix?
- A one-page chart that links long-term objectives, annual objectives, improvement priorities, target measures and owners, showing how each connects to the others. It is a later Western format; you can run Hoshin Kanri without one.
- What does "catchball" mean?
- The back-and-forth of passing draft goals down and back up the organization until each level agrees on what it will commit to. It builds real agreement instead of handing down orders.
- Who invented Hoshin Kanri?
- No single person. Japanese companies such as Toyota and Komatsu built it in the early 1960s as part of total quality control. Yoji Akao edited the best-known book on it, published in English in 1991.
- What does Hoshin Kanri mean?
- Roughly "direction management." Hoshin means direction or policy, and its characters suggest a compass needle. Kanri means management or control. "Policy deployment" is a common English name.
- How is Hoshin Kanri different from OKRs?
- Hoshin Kanri is built for multi-year goals, with every level agreeing its part and monthly reviews. OKRs are lighter and faster, usually quarterly. Some teams use Hoshin Kanri for the long horizon and OKRs for quarterly focus.
- Does Hoshin Kanri work for small companies?
- It can, but a full formal rollout is heavy for a company with one or two levels. Studies of small manufacturers found that starting small and having managers take part themselves mattered most.
- How often should you review a Hoshin plan?
- Every month, with a full review at year end that feeds the next year's plan. Letting the monthly reviews slip is one of the most common reasons the method fades.
Sources
- Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991. English edition of a 1988 Japanese book. routledge.com
- Art Smalley, "Who Invented Hoshin Kanri?", Art of Lean, July 2026. artoflean.com
- Marcela Pavlíčková, Andrea Mojžišová and Jana Pócsová, "Hoshin Kanri Process: A Review and Bibliometric Analysis on the Connection of Theory and Practice," Processes 10(9), 2022. doi.org
- Art Smalley, "What Does Hoshin Kanri Mean in Japanese?", Art of Lean, July 2026. artoflean.com
- Art Smalley, "What Is the Hoshin Kanri X-Matrix?", Art of Lean, July 2026. artoflean.com
- Thomas L. Jackson, Hoshin Kanri for the Lean Enterprise, Productivity Press, 2006.
- John Nicholas, "Hoshin kanri and critical success factors in quality management and lean production," Total Quality Management and Business Excellence 27(3-4), 2016. doi.org
- Charles Tennant and Paul Roberts, "Hoshin Kanri: Implementing the Catchball Process," Long Range Planning 34(3), 2001. doi.org
- Barry J. Witcher and Rosemary Butterworth, "Hoshin Kanri: Policy Management in Japanese-Owned UK Subsidiaries," Journal of Management Studies 38(5), 2001. doi.org
- Anders Melander, Malin Löfving, David Andersson, Fredrik Elgh and Mikael Thulin, "Introducing the Hoshin Kanri strategic management system in manufacturing SMEs," Management Decision 54(10), 2016. doi.org
- Malin Löfving, Anders Melander, Fredrik Elgh and David Andersson, "Implementing Hoshin Kanri in small manufacturing companies," Journal of Manufacturing Technology Management 32(9), 2021. doi.org
- Barry J. Witcher and Vinh Sum Chau, "Balanced scorecard and hoshin kanri: dynamic capabilities for managing strategic fit," Management Decision 45(3), 2007. doi.org
- Barry J. Witcher and Rosie Butterworth, "Hoshin Kanri: how Xerox manages," Long Range Planning 32(3), 1999. doi.org
Hoshin kanri was developed by Japanese companies in the 1960s and is not owned by any single company; Yoji Akao edited its best-known English text, and Throughline is not affiliated with him, his publishers, GOAL/QPC or any author cited here. Written by Tom Olajide, Founder. Last reviewed September 24, 2026.