Hoshin Kanri (strategy deployment)
Hoshin Kanri / Policy Deployment
Hoshin Kanri translates the company’s few breakthrough goals into committed goals, initiatives and targets at each organisational level — through dialogue (catchball) rather than decree — and couples them to a fixed follow-up cadence.
Use the method when
- →The strategy lives in slides while the day-to-day runs its own logic
- →Departments work hard — on their own priorities, which don’t sum to the strategy
- →There are more initiatives under way than the organisation has capacity to execute
Don’t use it when
- →Without functioning daily management (boards/tiers) — Hoshin needs a nervous system to couple to; build it first
- →If top management won’t take part in the monthly reviews — deployment without follow-up is merely distributed disappointment
Before you start
A real strategic direction exists (Hoshin deploys strategy — it doesn’t invent it)
Daily Management/tier structure is running, so the goals have somewhere to land
Management accepts the focus discipline: 3-5 breakthrough goals, not 15
How to do it — step by step
Choose 3-5 breakthrough goals
1-2 workshopsThe executive team distils the strategy into a few goals that require cross-cutting change (breakthrough), separate from ordinary operations (managed in daily management). Each goal: one owner on the executive team, one target metric, one target value. The test: can everyone on the executive team name the goals in the elevator?
Build the X-matrix at the top level
1 workshopThe X-matrix links on a single sheet: 3-5-year breakthrough goals → this year’s goals → improvement initiatives → metrics (KPIs) → owners. Each link is marked explicitly — the matrix’s value is that gaps and overload become visible: initiatives without goals, goals without initiatives, people with five responsibilities.
Deploy with catchball — level by level
2-4 weeksEach level receives the goals, translates to its own area and answers BACK: “this we can move, this requires that from you.” Adjustment happens BEFORE the goal is committed. Catchball takes 2-4 weeks — that is the price of ownership, and it is low compared with a year of passive compliance.
Couple to the daily management
1-2 weeksThe Hoshin goals’ metrics must be findable on the team boards — as the numbers teams can influence themselves. The escalation path for strategic deviations is the same tier chain as operations’. Strategy and operations must meet in the same room, or the strategy loses.
Run a monthly review on deviations
2 hours/month per levelA fixed monthly review per level: target against plan, deviations, root causes, adjustments — the same discipline as the board meeting, just with a longer horizon. The review is about LEARNING and adjusting (PDCA on the strategy), not about reporting nicely.
Annual cycle: reflect and restart
1 workshop/yearThe year’s end: what did we learn — about the goals, about our ability to execute, about the process itself? The learning feeds next year’s Hoshin. After 2-3 annual cycles, the deployment is a routine rather than a project — that is where the method really begins to pay off.
The classic mistakes
How it goes wrong in practice, and this is where most implementations part ways.
Too many goals
Eight breakthrough goals plus operations is a guarantee that none of them happen. Focus IS the method — every extra goal dilutes all the others.
Catchball is skipped
Deployment becomes cascade communication: the goals are “informed out”. Without the dialogue, the levels don’t own their numbers, and the review becomes a defence instead of a learning.
The X-matrix as an annual ritual
The matrix is filled in in January and gathers dust. The document is not the method — the cadence is. Without monthly reviews, Hoshin is just strategic origami.
Related standards
The standard is free. The anchoring is the craft.
The method only works when it becomes daily routines and leadership behaviour. The operations check shows in 4 minutes where your operations stand, and what should come first.