A few breakthrough goals. Cascaded so every shift knows their part.
Hoshin kanri is the lean planning system that connects strategy to the shop floor. The literal Japanese translation is something like "direction management," and the Western version is usually called policy deployment. The point of the method is that a small number of breakthrough goals at the top of the company should reach every workstation in a form people there can act on. Most shops have a strategic plan and a daily work rhythm and nothing in between. Hoshin kanri is what fills that gap.
"Strategy that doesn't reach the bench is just a slide. Hoshin kanri is the cascade that gets it there."
Hoshin kanri starts with the top of the organization picking a small number of breakthrough objectives, usually three to five, and usually framed against a three to five year direction. Those objectives are then translated into annual plans. Each annual plan has owners, supporting initiatives, and a small set of measurable indicators. The annual plan then cascades to departments, where each department picks the initiatives they will contribute to and the actions their teams will run. Each layer specifies its piece in enough detail that the next layer down can act on it.
What separates hoshin kanri from a normal top-down plan is the iterative dialogue between layers, called catchball. When leadership proposes an annual objective, departments push back with what is actually feasible given current capacity and constraints. Leadership adjusts. Departments cascade their own piece to teams, and teams push back on what they can realistically commit to. The back and forth takes longer than a memo and produces a plan everyone agrees with, which is the whole point.
The one-page document many shops use to hold this together is the x-matrix, which puts long-term breakthroughs, annual objectives, key metrics, and owners in a single visual. The x-matrix is a tool, not the system. A shop can practice hoshin kanri without an x-matrix if their cascade is clear enough; a shop with a beautiful x-matrix and no catchball dialogue is just doing top-down planning with a fancy template.
Imagine a 60-person sheet-metal fabricator running parts for HVAC and lighting OEMs. The owner has a three-year direction of cutting lead time in half to win more short-run work. Without hoshin kanri, the owner shares that goal at the holiday party and goes back to expediting. Lead times do not change.
With hoshin kanri, the owner picks "cut lead time from six weeks to three" as the annual breakthrough. Operations commits to two contributing initiatives: a setup reduction program on the main brake and a kanban link with the powder coater. The kitting team commits to standardizing kit pull times. The shipping team commits to a daily release routine instead of weekly batches. Each team has a piece they can name and a metric they update on the morning board. Six months in, lead time is at four and a half weeks and still trending down because every team is rowing in the same direction.
That is hoshin kanri at small scale. Not a binder. A plan everyone can recite.
Hoshin kanri is the strategic planning system; the x-matrix is the one-page tool many practitioners use to hold the cascade together. The communication discipline inside the cascade is catchball, the iterative dialogue that aligns commitments up and down. The directional north the breakthroughs point toward is true north, the long-term ideal state that gives every annual objective its purpose. The shop-floor routines that turn the plan into daily work usually live inside a daily management system.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.
.svg)
.svg)
%201.svg){kind=logo}
.png)
.svg)
.svg)
