Strategy deployment explained
Strategy deployment is how a plant picks a few big goals for the next three to five years, agrees who will reach them, and checks progress every month. It is also called hoshin kanri or policy deployment.
Matt Savas · Reviewed October 2026 · About 7 minutes
What strategy deployment is
Strategy deployment is a plan for the few changes a plant most needs to make. Leadership sets three to five breakthrough objectives for the next three to five years. A breakthrough objective is a change the plant cannot reach through daily improvement alone. Each objective gets a target for this year. Each department turns its share into a few improvement priorities, and every priority gets one owner and one metric. Once a month, the owners review their numbers on a bowling chart.
The Japanese name is hoshin kanri (方針管理). Hoshin means direction and kanri means management. The targets at each level are set through catchball. A leader proposes a target, and the level below replies with what it can do and what it needs.
Strategy deployment needs daily management in place first. Daily boards keep today's work at standard. Strategy deployment changes the standard. When a target is reached, the new level moves to the daily boards and the plan makes room for the next objective.
Why most plant plans fail
Most plants already have goals. The trouble starts after the planning meeting.
- The plan holds 20 or 30 goals, so none of them gets real effort.
- Targets come down from the top, and nobody below is asked whether they can be met.
- Each goal has a number but no plan for how to reach it.
- Goals that cross departments have no single owner.
- Progress is checked once a year, when it is too late to change course.
Strategy deployment answers each of these. It keeps the list short, asks the people who will do the work, names one owner for each target and checks progress every month.
How to run your first cycle
- 1Set three to five breakthrough objectivesAbout three months before the year starts, the leadership team picks the few changes the plant needs in the next three to five years. Each one gets a number, a date and one owner.
- 2Pick this year’s target for eachEach objective gets one target for the coming year. Keep the list short. Write down what you will stop doing to make room for it.
- 3Run catchball down and upEach leader takes a target to the level below and asks how they would reach it. The team replies with what it found, what it can commit to and what it needs. Departments agree what they need from each other. Expect two or three rounds over six to eight weeks. The plan is done when each owner says they can deliver it.
- 4Set priorities with owners and metricsEach department turns its share into a few priorities. Every priority gets one owner, one metric, a starting value, a year-end target and a target for each month. Put each level’s plan on one page.
- 5Review every month on a bowling chartA bowling chart has one row for each metric and one column for each month, with the target and the actual in each cell. Spend the meeting on the misses. Every miss gets a reason. Two misses in a row get an A3 with a countermeasure. Keep the target and change how the team works toward it.
- 6Reflect at the end of the yearIn the last two months, each owner writes down what was reached, what was missed and why, and what went wrong in the planning. This reflection (反省, hansei) is the first input to next year’s plan. Reached targets move to daily management. Missed ones carry over, or leadership decides to drop them.
Write each priority's plan and each countermeasure on the free A3 tool. To keep the monthly review from getting skipped, put it in each manager's leader standard work.
One plant’s first year
The plant in this example is made up. It has 300 people who machine and assemble hydraulic valves. Leadership set three objectives for 2027 to 2029. Each has one owner and a target for 2027.
After catchball, the departments agreed on five priorities for 2027. Each has one owner and one metric. Most priorities serve more than one objective. The cell 2 changeovers help delivery and output at the same time.
● strong link, ○ some link. The letters match the objectives above. An X-matrix shows the same links on one sheet.
Catchball on one target
Here is how objective B reached the shop floor. On-time delivery depends on small batches, and small batches depend on short changeovers. So the plant's 92% delivery target became a changeover target for the machining department. Machining then passed its share to the cell 2 team.
The changeover target did not start at 30 minutes. Plant leadership first asked for 20. The number came out of catchball.
- DownPlant to machining: we need 92% on time. Can cell 2 changeovers drop to 20 minutes, so you can run smaller batches?
- UpMachining to plant: 20 minutes needs a quick-clamp fixture we can’t pay for this year. We can reach 30 with standard work and tools set out before the stop. We need two kaizen weeks from maintenance.
- AcrossMachining to planning: shorter changeovers only help if the schedule stays frozen five days out.
- DownMachining to the cell 2 team: help us get from 90 to 30 minutes.
- UpCell 2 team to machining: half the time goes to finding tools and waiting for the first-piece check. A tool cart gets us to 45 by June. Getting to 30 needs an inspector at the cell within 10 minutes.
- Agreed45 minutes by June and 30 by December. Quality commits to first-piece checks within 10 minutes. Planning freezes the schedule five days out. Maintenance gives two kaizen weeks in the spring. The fixture goes into next year’s budget request.
The monthly review
Each month the plant reviews its bowling chart. Here are the first six months for four of its metrics.
- Delivery missed in February and March. The operations manager wrote an A3. It traced the misses to a casting supplier that shipped late. Purchasing added that supplier to its monthly reviews, and by April delivery was back on target.
- Customer defects missed in April and May. The quality manager's A3 traced most of the escapes to a valve model launched in March with no error-proofing for its seal. A fixture that will not close unless the seal is in place brought June back under target.
- OEE missed three months in a row. The engineering manager's A3 found that the cells skipped the weekly two-hour maintenance window whenever they fell behind. The plant manager made the window fixed, so it runs even when the cells are behind. June beat the target.
Each owner kept the year's target and changed how the team worked toward it.
Common mistakes
- Too many objectives. If everything is a priority, the monthly review turns into a reading of 40 numbers. Keep three to five objectives at the top and one to three priorities for each team.
- Skipping catchball. The team that does the work knows what stands in the way. If nobody asks them, the plan rests on guesses and the targets get missed.
- Sharing a metric between departments. When three departments share a metric, no one person answers for it. Name one owner and list who supports them.
- Reviews that only report. If a missed month gets a comment and no countermeasure, nothing changes before the next review. Ask the owner for an A3.
- Putting daily work in the plan. Keeping the line at standard belongs on the daily boards. Strategy deployment is for the few changes daily management cannot make.
Frequently asked questions
- What is strategy deployment?
- Strategy deployment, also called hoshin kanri, is a way to run a plant’s few most important changes. Leaders pick three to five breakthrough objectives for the next three to five years. Each level turns its share into its own targets through catchball. Every target gets one owner and one metric, and the owners review progress every month.
- Is strategy deployment the same as hoshin kanri?
- Yes. Hoshin kanri is the Japanese name. Hoshin means direction and kanri means management. Strategy deployment and policy deployment are the common English names for the same method.
- What is catchball?
- Catchball is the back-and-forth that sets each level’s targets. A leader proposes a target and explains why it matters. The team below replies with what it can commit to and what it needs. Departments also agree what they need from each other. The plan is done when each owner says they can deliver it.
- Do I need an X-matrix?
- No. An X-matrix is one sheet that shows how the objectives, yearly targets, priorities, metrics and owners connect. Plain tables that show the same links work as well and are easier to read. The links and the catchball matter more than the format.
- How is hoshin kanri different from OKRs?
- OKRs are usually set by each team every quarter and scored at the end. Hoshin kanri picks a few objectives for the whole organization each year. It agrees how each target will be reached, and it reviews progress every month so a miss gets a countermeasure while there is still time.
- How is it different from daily management?
- Daily management keeps today’s work at standard with daily boards, huddles and standard work. Strategy deployment changes the standard. When a target is reached, daily management takes over the new level.
- How long does the first cycle take to set up?
- Plan on about three months before the year starts. Leadership sets the objectives in the first month. Catchball takes six to eight weeks. The last weeks go to writing the owners, metrics and monthly targets onto one page for each level.