Hoshin Kanri is a method for turning a company’s strategy into work that every team understands and owns. Leadership picks a few breakthrough goals for the next three to five years, each level of the organisation agrees what it will do to reach this year’s part of them, and progress is reviewed every month. The idea is simple: everyone pulls in the same direction, and the daily work and the strategy are the same thing.
Most companies already have a strategy. What they lack is the link between the slide in the boardroom and the work on the floor. Hoshin Kanri is that link, and it is why many lean companies use it alongside continuous improvement.
What does Hoshin Kanri mean?
Hoshin means direction, or the needle of a compass. Kanri means management or control. Together they are usually translated as policy deployment or strategy deployment: setting a direction and making sure the whole organisation follows it.
The method grew out of Japanese quality management in the 1960s. Yoji Akao’s book Hoshin Kanri: Policy Deployment for Successful TQM, published in English in 1991, traces the term to an internal document at Bridgestone Tire in that decade and describes how Japanese companies combined management by objectives with the PDCA cycle.
How does Hoshin Kanri work?
Hoshin Kanri runs on two levels at once.
| Level | What it covers | Who owns it | How often it is reviewed |
|---|---|---|---|
| Breakthrough objectives | The three to five changes that matter most for the next three to five years, and this year’s part of them | Leadership, then deployed to every level | Monthly, with a full review once a year |
| Daily management | Keeping the business running well: safety, quality, delivery, cost | Every team, as part of normal work | Daily and weekly |
The breakthrough objectives are the “hoshin”. Daily management, sometimes called business fundamentals, is everything else. Keeping the two apart stops the strategy from turning into a list of 40 priorities.
What are the seven steps of Hoshin Kanri?
Most descriptions use seven steps, close to these:
- Set the vision. Where should the organisation be in five to ten years? This is the direction the needle points to.
- Choose three to five breakthrough objectives. The few changes that would move the organisation furthest towards the vision. Saying no to everything else is the hard part.
- Set this year’s objectives. What part of each breakthrough must happen in the next twelve months, with a measure for each.
- Deploy them through catchball. Each level proposes what it will do to reach the objectives above it, and the two sides discuss until they agree. More on catchball below.
- Do the work. Teams carry out the projects and improvements they agreed on, alongside daily management.
- Review every month. Each level checks its measures, finds the cause of any gap and adjusts. This is the Check and Act of PDCA.
- Review the year. What worked, what did not, and what that means for next year’s objectives.
What is catchball?
Catchball is how the objectives travel down and the plans travel back up. Leadership “throws” an objective to the next level. That level comes back with how it will contribute, what it needs and what it thinks is unrealistic. The ball goes back and forth until both sides agree.
Catchball is what makes Hoshin Kanri different from simply cascading targets. A target that is handed down is someone else’s goal. A plan a team has argued for is its own. It is also where leadership hears what the organisation actually knows: the constraint nobody mentioned in the strategy workshop, or the better idea from the people closest to the work.
What is the X-matrix?
The X-matrix is a one-page chart that shows how the parts of a Hoshin plan connect. It has four sections arranged around an X, with grids in the corners showing which items support which.
| Section | What it holds | Example |
|---|---|---|
| Breakthrough objectives (3 to 5 years) | The few big changes | Become the most reliable supplier in our market |
| Annual objectives | This year’s part of each | Cut late deliveries from 8 to 3 percent |
| Improvement priorities | The projects that will get there | Shorter changeovers on lines 2 and 3; a new planning process |
| Measures | How progress is tracked | On-time delivery rate, changeover time, planning accuracy |
A fifth part, often on the right-hand side, names who owns each priority. Reading across the corners, anyone can see why a project exists and which goal it serves. Thomas L. Jackson’s book Hoshin Kanri for the Lean Enterprise (2006) is the common reference for building one.
You do not need an X-matrix to do Hoshin Kanri. Many companies start with a simple table of objectives, measures, owners and projects, and add the matrix once the rhythm of monthly reviews is working.
What does Hoshin Kanri look like in practice?
Here is a typical example from a manufacturer, simplified.
Breakthrough objective: become the supplier customers trust most on delivery within three years. This year: cut late deliveries from 8 to 3 percent. Catchball: the plant manager proposes shorter changeovers and a weekly planning meeting with sales; the planning team adds that half of the late orders start with wrong forecasts, so a forecasting project is added. Deployment: each line leader agrees a changeover target and runs PDCA cycles to reach it. Monthly review: in month four, late deliveries are at 6 percent; the cause of most remaining delays is one supplier, so a supplier project is added.
The point of the example is the forecast. Leadership would not have found that cause on its own; catchball brought it up.
How does Hoshin Kanri compare with OKRs and the balanced scorecard?
| Method | What it does | Typical rhythm | Strength | Watch out for |
|---|---|---|---|---|
| Hoshin Kanri | Deploys a few multi-year breakthroughs through every level, with catchball and PDCA | Annual plan, monthly reviews | Strong link between strategy and daily work | Can become heavy paperwork if the X-matrix becomes the goal |
| OKRs | Ambitious objectives with measurable key results, set by teams | Quarterly | Fast, flexible, popular in software | Goals can drift apart without a shared multi-year direction |
| Balanced scorecard | Measures performance across four perspectives: financial, customer, process, learning | Annual, with regular reporting | Balanced view of performance | Measures what is happening; says less about how the work gets aligned |
The three are not exclusive. Some companies use Hoshin Kanri for the multi-year direction and OKRs for quarterly team goals.
What are the most common Hoshin Kanri mistakes?
- Too many objectives. Ten breakthrough objectives are a wish list. Three to five force a choice.
- Cascading instead of catchball. If targets only flow down, teams comply but do not commit.
- Forgetting daily management. Breakthroughs are built on a stable base. If quality and delivery are slipping, fix that first.
- Skipping the monthly review. Without it, the plan is a document, not a method.
- Making the X-matrix the goal. A perfect matrix nobody uses is worse than a simple table that is reviewed every month.
- No route for ideas from the floor. The best answers to “how do we reach this?” often come from the people doing the work. If they have no way to suggest them, the plan only has leadership’s ideas.
How do employee ideas fit into Hoshin Kanri?
Catchball works between managers. Most organisations also need a way for everyone else to contribute: the operator who knows why changeovers take long, or the planner who sees the forecast problem.
A common way to do this is to turn each annual objective into a question to the whole organisation: “How could we cut late deliveries?” In Hives, each question becomes a challenge of its own. People submit ideas in about two minutes from a phone or the web, managers score them against the same criteria, and everyone sees what was decided. The ideas that go ahead become improvement priorities, and because the challenge asks the objective’s own question, the link back to the strategy stays obvious. Our guides on prioritising ideas and measuring an innovation programme cover the next steps.
Frequently asked questions
What is Hoshin Kanri in simple terms?
Hoshin Kanri is a way of turning a company’s few most important goals into work at every level. Leadership sets the direction, each level agrees how it will contribute through discussion called catchball, and progress is reviewed every month using the PDCA cycle.
What does Hoshin Kanri mean?
Hoshin means direction or compass needle, and kanri means management. In English it is usually called policy deployment or strategy deployment.
What is the difference between Hoshin Kanri and OKRs?
Hoshin Kanri deploys a few multi-year breakthrough objectives through the whole organisation, with yearly plans and monthly reviews. OKRs are usually set quarterly by teams, with measurable key results. Hoshin Kanri is stronger on long-term alignment; OKRs are faster and more flexible. Some companies use both.
What is an X-matrix in Hoshin Kanri?
The X-matrix is a one-page chart that links breakthrough objectives, annual objectives, improvement priorities, measures and owners, so anyone can see why each project exists. It is useful but optional; a simple table works for a first year.
Is Hoshin Kanri part of lean?
Yes. Hoshin Kanri is often described as the strategy layer of lean management. Lean improves the work; Hoshin Kanri makes sure the improvements serve the company’s goals.
How long does it take to introduce Hoshin Kanri?
Plan a full year for the first cycle, from setting objectives to the annual review. Most companies find the second and third years work much better, once the monthly reviews have become a habit.
Sources
- Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991
- Thomas L. Jackson, Hoshin Kanri for the Lean Enterprise: Developing Competitive Capabilities and Managing Profit, Productivity Press, 2006