What the name means
Hoshin kanri is usually translated as "policy management" or "direction management". Hoshin suggests a compass needle pointing the way; kanri means management or control. The method emerged in Japanese industry in the 1960s, building on Deming's PDCA and management by objectives, and was adopted by Toyota and later by many Western lean organisations.
Core principles
- Focus on the vital few. A small number of breakthrough objectives, typically three to five, rather than a long wish list.
- Catchball. Each level proposes how it will contribute, the level above responds, and the plan is negotiated until targets and means are agreed. Plans are built with people, not handed to them.
- Targets and means. Every objective is paired with the specific initiatives that will deliver it.
- PDCA on the plan itself. Progress is reviewed monthly, gaps trigger countermeasures, and the annual review feeds next year's plan.
- Separation from daily work. Hoshin covers breakthrough change; routine performance is managed through daily management.
Typical hoshin kanri cycle
- Set or revisit the long-term vision, often three to five years.
- Define breakthrough objectives for the year.
- Deploy objectives to each level through catchball.
- Agree improvement priorities, owners and measures, often summarised on an X-matrix.
- Execute through projects and A3s.
- Review monthly using bowling charts and countermeasure sheets.
- Conduct an annual reflection (hansei) and start the next cycle.
Common mistakes
- Too many objectives, so nothing gets real resources.
- Top-down cascading without genuine catchball.
- Building the X-matrix and then never reviewing it.
- Loading routine KPIs into hoshin instead of daily management.
Hoshin kanri vs strategy deployment
Hoshin kanri is the specific lean methodology, with its own vocabulary, tools and review rhythm. Strategy deployment is the broader term for any structured way of turning strategy into aligned work. Many organisations use "strategy deployment" as the plain-English name for a hoshin-style approach, but not every strategy deployment process includes catchball or X-matrices.