Hoshin Kanri Explained: Turning Strategy Into Plant Goals

By Mirko Peters · 2026-11-11

Hoshin kanri turns a few strategic objectives into aligned goals at every level. See the X-matrix, catchball, seven steps and how a plant can run it yearly.

Hoshin kanri is a method for turning the few most important goals of a company into aligned goals and actions at every level, with regular reviews. It is also called policy deployment or strategy deployment. This guide is for operational excellence managers who have a strategy on paper and a plant that works on something else. You will learn the parts of hoshin kanri, how the X-matrix and catchball work, and how a plant can run it through a year without drowning in slides.

Key points

• Hoshin kanri, also called policy deployment or strategy deployment, aligns the whole organisation with a few strategic objectives through an annual plan with regular reviews.
• Hoshin means direction and kanri means management, so the method is about managing direction, not about filling a template.
• The X-matrix puts breakthrough objectives, annual objectives, initiatives and metrics on one page, and shows which items support each other.
• Catchball is a two-way dialogue about targets, time and resources between levels, so goals are agreed and not simply handed down.
• A plant keeps hoshin kanri alive by linking it to daily tier meetings and PDCA, with weekly, monthly and annual reviews.

What hoshin kanri means

Hoshin is Japanese for policy or direction, and kanri means management. The Gemba Academy glossary glosses the term as the management of objectives, or "how do we manage our direction?". The Lean Enterprise Institute (LEI) describes strategy deployment as a management process that aligns functions and activities, both vertically and horizontally, with the strategic objectives. A specific plan, typically annual, sets goals, actions, timelines, responsibilities and measures.

The point is to close the gap between strategy and execution, so that the strategic plan shapes daily work and the plant's KPIs show whether it does. Many plants have a strategy that lives in a presentation and a set of daily priorities that live on the shop floor. Hoshin kanri connects the two. It limits the number of priorities, makes each one concrete, names who is responsible, and checks progress at fixed times. It also helps align several levels of the organisation behind the same strategic goals, from the executive team to the line, and it gives continuous improvement a direction: the plant improves what supports the objectives first.

LEI notes that in a lean conversion the process may start top-down. Once the major goals are set, it should become both top-down and bottom-up. In a mature organisation, each part proposes actions to senior management. That is why hoshin kanri is not a once-a-year slide deck: it is a management system with an iterative rhythm, and a core part of lean management.

The X-matrix: strategy on one page

The X-matrix, also called the hoshin kanri matrix, is a one-page template. Gemba Academy describes it as a spreadsheet that lays out cascading goals, priorities and projects. Another guide, from the vendor Teamguru, describes the four lists around the centre this way:

• Breakthrough objectives for the next three to five years.
• Annual objectives, meaning what will be achieved this year.
• Improvement initiatives, meaning how the annual objectives will be achieved.
• Metrics and targets, meaning what will show that progress is happening.

A column assigns each initiative to a named owner. The corners of the matrix show the links between the lists. An item with no link to anything else is a gap. For example, an initiative that supports no annual objective is activity without direction. The two sources place the lists in slightly different quadrants, so do not worry about the exact layout. What matters is that every initiative connects to an objective and a metric.

Keep the matrix small. The Teamguru guide suggests three to five items per quadrant. Gemba Academy gives a general guideline of fewer than five breakthrough objectives and recommends two or three.

Catchball: how goals travel up and down

Catchball is the discussion that makes hoshin kanri more than a cascade of orders. LEI defines it as a dialogue between senior managers and project teams about the time and resources available and needed to reach the targets. Gemba Academy adds that upper management shares the strategy, middle managers add their views and tactics, and frontline staff share operational insights. The stated aim is to reduce waste from poor communication by building agreement on how to reach the goals.

In practice, a plant manager receives a corporate objective, and drafts the plant's version. The plant manager then plays it to the area leaders, who respond with what they can do, what they need and what they doubt. The plant manager adjusts, and plays it back up if the resources do not fit. Two or three rounds are often enough. The result is buy-in: the people who must deliver the target helped to shape it.

LEI also points out the benefit: the process matches resources to projects, so only projects that are desirable, important and achievable are authorised. This guards against launching many initiatives that stall for lack of cross-functional agreement and resources.

Hoshin planning in seven steps: a yearly rhythm

Gemba Academy lists seven steps of hoshin planning. The following version adapts them to a plant year. The calendar is our own suggestion.

1. Define mission, vision and key metrics. Confirm what the plant is there to do and how you measure it.
2. Choose breakthrough objectives. Pick two or three long-term goals, such as delivery reliability or lead time.
3. Set annual objectives. Gemba Academy recommends using an A3 document for this step. Each objective needs a measure and a target.
4. Deploy with catchball. Agree the initiatives, owners and resources with each area.
5. Review. Gemba Academy calls for reviews weekly, monthly and annually, to find gaps and reset targets.
6. Solve problems. Use the PDCA cycle on initiatives that miss their targets.
7. Reflect and learn. At the year end, ask what worked and what the next plan should change.

The weekly and monthly reviews need a place. Many plants use their tier meetings for this: a short daily or weekly meeting at each level, where the team looks at the metrics and the actions. A tier meeting turns the objectives into day-to-day operations, because the numbers on the board are the same numbers that sit in the X-matrix.

If your plant is new to the method, start small. Run the first cycle with one breakthrough objective and one value stream, and keep the X-matrix to a single page. Hold the weekly review for 15 minutes. After one year, add the second objective. A small first cycle teaches the leaders how to run catchball and how to read the matrix, and it avoids the fatigue that comes from a large plan nobody believes in.

Example: from a plant goal to a line goal

This is an illustrative example, not a real plant. Assume the company strategy includes a breakthrough objective: "Be the most reliable supplier in our market within four years". The plant turns it into an annual objective: raise on-time delivery from 88 per cent to 93 per cent this year.

The plant chooses three initiatives:

• Cut the changeover time on the two constraint machines by 25 per cent. Owner: production manager.
• Introduce a daily tier meeting on every line with the on-time delivery board. Owner: lean manager.
• Fix the five most frequent causes of missing material. Owner: logistics manager.

Each initiative gets a metric: changeover minutes, meetings held and actions closed, and missing-material events per week. On the line, the team leader sees the line's share of the target on the board. The monthly review shows that changeover time is on track while material shortages are not, so the plant manager moves resources. The numbers are invented. The logic is real: one objective, three initiatives, named owners, metrics and a review rhythm.

Common mistakes

• Too many objectives. A long list is a to-do list. Hoshin kanri works because it says no.
• Cascading without catchball. If targets arrive as orders, teams comply on paper and ignore them in practice.
• No link to daily work. If the tier meeting and the X-matrix show different numbers, the plan dies by March.
• Using it as a yearly event only. Without weekly and monthly reviews, the plan is forgotten until the next planning round.
• Missing owners. An initiative without a named person has no one to ask.
• Confusing it with kaizen. Kaizen improves what is in front of the team, step by step. Hoshin kanri chooses which few improvements matter most this year.

How software can help

Software can hold the X-matrix, link each initiative to its metric and owner, and show the status of every objective in one view. It can pull the metric values from the ERP or the shop floor so that nobody retypes them. A plant dashboard that shows planned versus actual values for the metrics supports the monthly review. Software does not replace the conversation in catchball. It only keeps the results visible.

Next step

Write down your plant's one to three annual objectives on a single page, and check that each has a metric and a named owner. Then hold your first catchball round with your area leaders. That is how a plant starts with hoshin kanri.