Hoshin Kanri is a strategy deployment method that aligns breakthrough objectives, annual priorities, metrics, ownership, and review routines across the organization.

Back to BoK Index
Strategy DeploymentLeadershipAlignment

Definition

Hoshin Kanri, often translated as policy deployment, is a management system for translating strategic direction into aligned objectives, projects, metrics, and review routines. It connects long-term vision with annual priorities and daily execution.

Hoshin is not only a planning document. It is a catchball process where leaders and teams negotiate priorities, capability, constraints, ownership, and measures before execution.

History

Hoshin Kanri developed in Japanese quality and Lean management practice as organizations needed stronger alignment between strategy and improvement work. It is associated with total quality management, Toyota-style management, and policy deployment systems.

The method became valuable because isolated improvement projects often fail to move strategic results unless they are connected to priorities, resources, and review discipline.

When to Use

Use Hoshin Kanri when strategy is unclear, improvement resources are scattered, departments work at cross-purposes, or breakthrough objectives need disciplined execution. It is useful for Lean transformation, quality strategy, safety improvement, growth priorities, and multi-site deployment.

It should be used when leadership is willing to make tradeoffs. A Hoshin plan that includes every wish list item is not deployment; it is overload.

Step-by-Step

  1. Clarify long-term direction and breakthrough objectives.
  2. Select a small number of annual priorities.
  3. Define measurable targets and leading indicators.
  4. Use catchball to align feasibility, ownership, and resources.
  5. Translate priorities into projects, process metrics, and local plans.
  6. Set review cadence using monthly and quarterly management routines.
  7. Escalate barriers and adjust countermeasures based on evidence.
  8. Close the year with learning, reflection, and next-cycle planning.

Examples

  • Quality strategy: A business deploys a warranty-reduction breakthrough into supplier quality, design validation, and service feedback projects.
  • Lean deployment: A site aligns value stream improvements, leader standard work, and daily management routines.
  • Safety: Executive safety goals cascade into ergonomic risk reduction and high-hazard standard work.

Common Pitfalls

  • Creating too many priorities.
  • Skipping catchball and forcing top-down targets.
  • Confusing project activity with strategic progress.
  • No monthly review discipline.
  • Using lagging indicators only.
  • Failing to stop lower-priority work.

Related Tools

Further Reading