Org, people & execution
Hoshin Kanri
A Japanese policy-deployment system that turns a handful of breakthrough objectives into aligned targets and means at every level of the organisation, negotiated through catchball, executed alongside daily management and held on course by structured review.
Also known as Policy deployment, Hoshin planning, Strategy deployment. First set out by Japanese TQC practice of the 1960s; codified by Yoji Akao in 1965; the primary source is cited in full below.
Where this is contested
Bridgestone Tyre is usually credited with coining the term in its 1965 study of Deming Prize winners, but the practice emerged collectively from 1960s Japanese TQC, with Akao, Mizuno and Yokogawa Hewlett-Packard all central to its codification, and no single institutional originator can be cleanly credited.
- Format
- Process / loop
- Level
- Corporate · Business unit · Team
- Best for
- Plan execution · Prioritise · Allocate resources
- Decision stage
- Plan · Execute · Review
- Difficulty
- Advanced
- Time to apply
- A full annual cycle; expect two to three cycles before the process matures.
Plate · The model
The components
Set the direction
Senior leadership distils the mid-term vision into a small number of breakthrough objectives and this year's annual objectives, accepting that choosing few means refusing many.
Signals of strength
Three to five breakthroughs, not a dozen · Objectives are derived from the mid-term vision, not from last year plus ten percent · Leadership can name what was deliberately left off the list
Cascade through catchball
Iterative negotiation of targets and means between organisational levels, each level answering with what is achievable and what it needs, until commitments are owned rather than imposed.
Signals of strength
Targets change during deployment as feedback flows upward · Teams state what they will stop doing to create capacity · Each level's X-matrix or plan links visibly to the one above
Execute with daily management
Running hoshin improvement work alongside stable daily management, so breakthrough projects draw on protected capacity rather than competing with firefighting.
Signals of strength
Hoshin actions appear on the same boards and cadences as routine work · Process stability is measured, and slippage triggers countermeasures · Improvement capacity is explicitly budgeted, not assumed
Review and adjust
Monthly checks and an annual reflection that treat gaps as problems to be solved with countermeasures, and that turn what the year revealed into next year's plan.
Signals of strength
Reviews examine means as well as numbers · Misses produce root-cause analysis, not blame or silence · The annual reflection demonstrably changes the next cycle's objectives
When it earns its keep
- Strategy is agreed at the top but keeps dissolving on the way down, with departments pursuing local goals that do not add up to the plan.
- The organisation has too many priorities and needs a disciplined mechanism for choosing three to five breakthrough objectives and saying no to the rest.
- You run an operations-led business with working daily management, and want annual strategy connected to it rather than sitting in a separate slide deck.
- Middle managers comply with targets they privately think are impossible; catchball exists precisely to surface that negotiation before the year starts.
And when it doesn't
- The direction itself is undecided. Hoshin kanri deploys a strategy; it does not generate one. Do the strategic thinking first with tools built for it.
- A start-up or small team that can align in one room. The cascade machinery adds cost that only pays off across organisational layers.
- The environment shifts faster than an annual cycle can track. A yearly hoshin with monthly reviews will lag; shorter-cycle approaches such as OKRs may fit better.
- Daily management is broken. If basic process stability and routine measurement do not exist, deploying breakthrough objectives onto them multiplies noise, not progress.
How to run it
Before starting, gather the inputs the analysis depends on:
- A mid-term vision (typically three to five years) from which this year's breakthrough objectives can be derived.
- An honest picture of current performance and capacity, so targets are negotiated against reality rather than hope.
- A working daily management system: stable processes, routine measures and local problem-solving to carry the load of normal operations.
- Leadership time and patience for catchball, since the negotiation rounds are the mechanism, not an overhead to be compressed.
- A review cadence with real consequences, monthly at minimum, plus an annual reflection that feeds the next cycle.
- 1
Set the mid-term vision and choose breakthroughs
From the long-term direction, senior leadership selects three to five breakthrough objectives for the next three to five years, then derives this year's annual objectives from them. The discipline is scarcity. A hoshin with twelve priorities is a budget, not a strategy.
- 2
Draft the deployment on an X-matrix
The X-matrix, an A3 form popularised in the West by Jackson, arranges long-term breakthroughs, annual objectives, improvement priorities, targets and owners around a central X so the correlations between them stay visible on one page. Each level of the organisation drafts its own, linked to the level above. Treat it as a thinking aid; the correlations matter, the form does not.
- 3
Cascade through catchball
Objectives and means are thrown back and forth between levels like a ball: leadership proposes a target, the receiving team responds with what is achievable, what resources it needs and what it would have to stop doing, and the target or means are revised. Several rounds are normal. Catchball is what separates hoshin kanri from target-setting by decree; skip it and you have built a fax machine for orders.
- 4
Execute alongside daily management
Hoshin projects run on top of, and depend on, routine daily management (nichijo kanri): stable processes, visual boards, tiered meetings and local problem-solving. Daily management keeps the business running; the hoshin consumes the improvement capacity it frees up. Where daily management is weak, hoshin work is quietly cannibalised by firefighting.
- 5
Review monthly and adjust
Each owner reviews progress against targets and means on a regular cadence, using plan-do-check-act on the deployment itself. Misses trigger root-cause analysis and countermeasures, including revising the plan, not just exhortation to try harder.
- 6
Reflect annually and feed the next cycle
The year closes with structured reflection (hansei), often including a senior leadership diagnosis of how well the process itself worked at each level. What was learned about the organisation's real capacity becomes an input to next year's objectives, which is what makes hoshin kanri a loop rather than an annual event.
Reading the result
A linked set of deployment plans, typically X-matrices, connecting breakthrough objectives to annual targets, improvement priorities and named owners at each level, plus a running review record showing progress, countermeasures and what the annual reflection changed.
- Read the linkage first: every team-level improvement priority should trace to a breakthrough objective, and every breakthrough should have live means beneath it. Orphans at either end mean deployment has failed somewhere.
- Judge catchball by how much targets moved during deployment. If every number survived the cascade untouched, negotiation did not happen.
- In reviews, weight the means over the metrics. A green number with no working countermeasure history is less trustworthy than a red one with honest analysis attached.
A worked example
A corrugated packaging manufacturer deploys a 48-hour lead-time breakthrough
A UK corrugated packaging manufacturer with three plants makes boxes and point-of-sale displays for food and e-commerce customers. Standard lead time is five days; e-commerce customers increasingly demand two. The board adopts hoshin kanri to deploy a three-year breakthrough objective: reliable 48-hour order-to-despatch on standard grades, without margin erosion.
- Set the direction
- The board considers three candidate breakthroughs (lead time, energy cost, new-market entry) and commits to lead time alone, judging it the one customers will switch suppliers for. The year-one annual objective is set at 72 hours on the two highest-volume grades, with 48 hours reserved for years two and three. Energy work is explicitly deferred.
- Cascade through catchball
- The operations director proposes corrugator changeover targets to each plant. The Yorkshire plant throws the ball back: the target is achievable only with tooling investment and a freeze on a minor product family that forces long changeovers. Two rounds later the target is eased for Q1, the tooling is funded, and the product family is rationalised. Each plant drafts an X-matrix linking its priorities, including changeover reduction and a finished-goods scheduling rule, to the group objective.
- Execute with daily management
- Hoshin actions join the existing tiered meeting structure: changeover times tracked on cell boards daily, escalated at the plant meeting weekly. Daily management earns its keep in month four, when a corrugator reliability problem starts consuming the improvement capacity; because routine stability is measured separately, the plant can show the hoshin work is stalling for a nameable reason rather than quietly reporting green.
- Review and adjust
- The monthly review finds despatch performance stuck despite faster changeovers. Root-cause analysis locates the constraint downstream in the finishing department, which no plan had touched. The deployment is adjusted mid-year to add a finishing flow project, and the annual reflection records the lesson: the original cascade deployed targets to the corrugators because they were the obvious asset, not because they were the constraint. Year two's objectives are set against a constraint analysis first.
The read. Year one ends at 80 hours on the target grades against a 72-hour objective: a miss, honestly recorded, with a countermeasure trail that found the real constraint. The process worked precisely where an imposed target would have failed, in the catchball that bought the tooling and the review that moved effort to finishing. The 48-hour breakthrough remains credible because the plan now reflects the plant the company actually has.
Pitfalls
- Deploying too many objectives. The method's power is scarcity; a hoshin carrying every department's wish list aligns nothing.
- Running catchball as a briefing. One-way cascade with sign-off theatre produces compliance without commitment, and the plan fails silently in month two.
- Worshipping the X-matrix. Filling in the form becomes the work, correlations are asserted rather than tested, and the A3 ossifies into bureaucracy.
- Deploying breakthroughs onto broken daily management, so hoshin projects compete with firefighting for the same people and lose.
- Reviewing metrics without means. A review that only asks 'are we green?' teaches managers to manage the colour, not the process.
- Treating the annual reflection as optional. Without hansei feeding the next cycle, hoshin kanri degrades into annual target-setting with Japanese vocabulary.
What the critics say
Western transplants often fail because firms adopt the forms without the underlying TQM disciplines. Witcher and Butterworth's longitudinal studies of Japanese-owned UK subsidiaries found the method depends on mature daily management, nemawashi-style consensus habits and patient review routines that most Western adopters lack, so the cascade becomes conventional MBO under a new name.
Witcher, B. J. and Butterworth, R. (2001) 'Hoshin Kanri: Policy Management in Japanese-Owned UK Subsidiaries', Journal of Management Studies, 38(5), pp. 651-674; Witcher, B. J. (2002) 'Hoshin kanri: a study of practice in the UK', Managerial Auditing Journal, 17(7), pp. 390-396.
The X-matrix invites bureaucratisation. It is a later codification, popularised through Jackson's Western treatment rather than universal Japanese practice, and lean practitioners themselves warn that organisations mistake completing the matrix for doing the deployment, generating correlation symbols and review packs while the negotiation and problem-solving the matrix was meant to support never happen.
Jackson, T. L. (2006) Hoshin Kanri for the Lean Enterprise. New York: Productivity Press.
The annual cycle assumes a stability many markets no longer offer. Where conditions shift quarterly, a yearly deployment with monthly checks can lock the organisation onto a stale hoshin, and the method offers little native guidance on when a breakthrough objective itself should be abandoned mid-cycle.
Sources and further reading
- Akao, Y. (ed.) (1991) Hoshin Kanri: Policy Deployment for Successful TQM. Cambridge, MA: Productivity Press (Japanese original 1988).
- Witcher, B. J. and Butterworth, R. (2001) 'Hoshin Kanri: Policy Management in Japanese-Owned UK Subsidiaries', Journal of Management Studies, 38(5), pp. 651-674.
- Jackson, T. L. (2006) Hoshin Kanri for the Lean Enterprise: Developing Competitive Capabilities and Managing Profit. New York: Productivity Press.
- Lean Enterprise Institute, Lean Lexicon: 'Hoshin Kanri'. ↗