How to Implement Hoshin Kanri
Implement hoshin kanri by building capability before ceremony: stable daily management and problem solving first, and on that foundation the elements of the system together, a layered written hoshin, catchball deployment, horizontal coordination, and a real review mechanism. The document can be drafted in weeks. The working system is a multi-year capability build.
Implement hoshin kanri by building capability before ceremony: stable daily management and problem-solving skill come first, and on that foundation the elements of the system are built and matured together, a layered written hoshin, deployment through catchball, horizontal coordination, and a real review mechanism. The document can be drafted in weeks. The working system is a multi-year capability build.
That distinction, between producing the artifact and building the system, is the single most important thing to understand before starting. Hoshin kanri provides direction, a cascade of goals, and methods. By itself, in isolation, it accomplishes nothing: the document is a piece of paper, and the ability that moves it lives inside people and processes.
What must be in place before starting hoshin kanri?
Two capabilities, and they are prerequisites, not products, of the implementation.
Stable daily management. Hoshin kanri and daily management are symbiotic halves of one management system. Hoshin runs PDCA aimed at future-oriented breakthroughs; daily management runs SDCA (Standardize-Do-Check-Act) to hold the operational foundation stable. Toyota-lineage sources on the FMDS daily management system are explicit about the failure sequence when hoshin runs alone: improvements become one-time events that stop when the responsible manager transfers, because nothing standardizes the gains into daily routines. Daily management also feeds the hoshin: problems accumulated on daily management boards through the year become candidate themes for the next cycle’s policy.
Problem-solving capability in the management ranks. Every gap a hoshin surfaces needs someone able to close it, and closing gaps is problem solving. An organization whose managers cannot run PDCA on real problems will execute hoshin as form-filling, because form-filling is what remains when capability is absent.
An organization missing both should build them first and defer the hoshin cycle. That advice is unfashionable and correct: deploying strategy through an organization that cannot execute produces an annual ritual and a residue of cynicism that makes the eventual real implementation harder.
Where do you start with hoshin kanri?
From check and act, not from a blank-page plan. Sugiura describes Toyota’s thinking pattern as CA-PDCA: a management cycle revolved one and a half times, where grasping results and acting on the current state precede a credible plan.
Toyota’s own system began exactly this way. A company-wide audit in July 1962 diagnosed four management problems, and the first written Company Hoshin, in January 1963, was the countermeasure. The system started as an answer to an honest diagnosis, not as a vision workshop.
The transferable starting point is the same reflection: what did we intend this year, what actually happened, and what few gaps matter most. The first hoshin grows out of those answers.
What are the elements of a working hoshin kanri system?
Hoshin kanri is not implemented by completing a numbered sequence. Problem solving has steps; a management system has elements, and the elements are built and matured together across cycles rather than checked off in order. What follows is descriptive, not a checklist.
A written hoshin in layers, holding a vital few objectives. The first Toyota hoshin document had three layers: Basic Hoshin (the permanent direction), Long-term Hoshin (three-to-five-year targets and countermeasures), and Annual Hoshin (this year). Even a first-cycle version should distinguish the permanent, the multi-year, and the annual, because that structure is what keeps annual targets from becoming disconnected numbers. Keep the objectives few: hoshin kanri concentrates the organization on the matters that need cross-functional coordination and executive attention, and a first hoshin with ten priorities is the old plan with new vocabulary. Resist starting with an X-matrix: the form is not Toyota practice, and polishing an artifact is the classic early substitute for building the system.
Deployment through catchball, with a deliberate boundary. Targets and methods are negotiated at each level through catchball, with as many rounds as it takes to clarify the goal and the methods. Decide deliberately where the documented cascade stops. Toyota stops it at the section manager level, but the direction continues below in changed form: supervisor-level hoshin content is carried through FMDS floor management boards and daily management, not personal hoshin documents. The right stopping level for another organization depends on culture, capability, and daily management maturity. What transfers is the change of form, not the exact level: at some point the cascade should become daily management rather than more strategy paperwork.
A horizontal coordination layer. Most hoshin objectives cross departmental boundaries. Toyota coordinates through standing Function Meetings organized by Quality, Cost, Production, Technology, and Sales/HR. An implementation needs at least a deliberate equivalent: named cross-functional forums for the objectives that require them.
A review leg with questioning and consequences, not status theater. Regular reviews through the year, plus real executive examination. Toyota’s documented model paired its regular reviews with theme-driven operational audits: a few themes per year chosen by the president, presentations on a double-sided A3 in ten minutes plus five minutes of questions, and executive feedback written in the executive’s own words. The format is copyable from the first cycle, and the discipline of one A3 and ten minutes is itself a management development exercise. What takes years is the questioning skill and organizational trust that make the audit a learning event rather than an inspection. Details: Operational Audits: The Missing Feedback Loop in Hoshin Kanri.
Management development inside the system, not beside it. When Toyota’s own hoshin practice degraded in 1978, the company’s response was Kan-Pro: a two-year re-education of all 760 department and section managers in management fundamentals, personally led by Managing Director Masao Nemoto, with improving hoshin practice itself designated a Company Hoshin item. The system is maintained by developing the people who run it.
None of these elements is completed and left behind. The first annual cycle exercises all of them weakly; the second and third cycles are where catchball sharpens, the coordination forums find their rhythm, and the audits start producing learning instead of nervousness. The elements mature together, which is precisely why hoshin kanri resists reduction to a fill-in sequence.
What do the key terms mean?
A working glossary for an implementation team:
| Term | Meaning |
|---|---|
| Hoshin (方針) | Policy, direction, course of action; the ordinary Japanese word for policy |
| Kanri (管理) | Management, control |
| Basic Hoshin | The permanent foundational direction; at Toyota it barely changed over fifty years |
| Long-term Hoshin | Three-to-five-year targets and countermeasures |
| Annual Hoshin | This year’s goals and measures |
| Catchball (キャッチボール) | Negotiation of targets and methods between levels, continuing until both are clarified |
| Function Meeting | Standing cross-functional forum (Quality, Cost, Production, Technology, Sales/HR) |
| Operational audit | Theme-driven executive review on A3, ten minutes plus questions, with personal executive feedback |
| Daily management (日常管理) | The SDCA stability layer hoshin depends on |
| CA-PDCA | Toyota’s cycle sequencing: check and act on current reality before planning |
| Hansei (反省) | Structured reflection; each annual cycle opens with it |
How long does hoshin kanri take to implement?
Be suspicious of short answers. The planning document can be drafted in weeks, and a first annual cycle can be run within a year. Neither is the system.
Toyota’s own timeline is the honest benchmark. TQC adoption in June 1961. First company-wide audit in July 1962. First written Company Hoshin in January 1963. Deming Prize in 1965. The document reached its six-category mature structure in 1967, and the audit rhythm stabilized into its lasting form in 1977, fourteen years after the first hoshin. And even then the capability required maintenance: the 1978 quality crisis showed the management fundamentals had eroded, and Kan-Pro spent two years rebuilding them.
No Western implementation needs to retrace that full history; the design is now known, and Toyota was inventing it. But the shape of the timeline transfers: expect the first cycle to be an unflattering diagnostic of your catchball, coordination, review, and problem-solving muscles, expect the second and third cycles to be where the system starts working, and treat any promise of a working hoshin system in a few months as a description of paperwork.
What are the most common implementation mistakes?
The full failure catalog is covered in Why Does Hoshin Kanri Not Work? The implementation-specific short list:
- Starting with the form. Buying templates or software and calling the configuration an implementation
- Skipping the prerequisites. Deploying strategy through an organization that lacks daily management and problem-solving capability
- Too many objectives in cycle one. The surest sign that the leadership team has not actually chosen
- Cascading to individuals. Turning a management negotiation into appraisal paperwork
- Review as reporting. Status meetings with traffic-light charts instead of audits with questions and consequences
- Declaring victory after the plan. The plan is the cheapest part; the system is catchball, coordination, review, and adjustment through the year
What is the best book on implementing hoshin kanri?
For the mechanics of the annual cycle, the best how-to guide in print, in my assessment, is Mark Reich’s Managing on Purpose (Lean Enterprise Institute, 2025). Reich managed the hoshin kanri process at Toyota North America for 23 years, and the book works through the annual cascade, catchball, and review rhythm at a practical level of detail.
Know its scope going in. The book is strongest on the annual cascade. It gives lighter treatment to the permanent Basic Hoshin and long-term layers, and it does not cover the shop-floor deployment systems, FMDS and 3 Pillar activity, that carry hoshin content below the management layers at Toyota. For those parts, pair it with the hoshin kanri guide and the FMDS material on this site.
Frequently asked questions
How long does it take to implement hoshin kanri? A first annual cycle can be run within a year, and the planning document itself can be drafted in weeks. But the working system is a multi-year capability build. Toyota conducted its first company-wide audit in 1962, wrote its first Company Hoshin in 1963, and its audit structure did not stabilize into mature form until 1977. Claims that hoshin kanri can be implemented in a few months describe the paperwork, not the system.
What should be in place before starting hoshin kanri? Two capabilities: stable daily management (standards exist, deviations are visible and responded to) and working problem-solving skill in the management ranks. Hoshin kanri surfaces gaps; people and processes must be able to close them. A hoshin document by itself accomplishes nothing.
Do you need an X-matrix to implement hoshin kanri? No. The X-matrix originated in the QFD community and is not part of Toyota’s practice. Toyota runs hoshin kanri on a written policy document in three layers, catchball dialogue, cross-functional Function Meetings, and disciplined A3-based review.
Do you need software to implement hoshin kanri? No. Toyota built and ran the system on paper: a written hoshin document, A3 reports, and face-to-face review. Software can store and share the artifacts, but the system lives in the negotiation, coordination, and review behaviors, none of which a platform provides.
What is the best book on implementing hoshin kanri? For the annual cascade, catchball, and review rhythm, Mark Reich’s Managing on Purpose (Lean Enterprise Institute, 2025) is the best how-to guide in print. Reich managed the hoshin kanri process at Toyota North America for 23 years. It gives lighter treatment to the permanent Basic Hoshin layer and does not cover shop-floor FMDS and 3 Pillar deployment, so pair it with fuller treatments of those layers.
Where should a company start with hoshin kanri? Start from check and act, not from a blank-page plan: reflect honestly on the current year, identify the few gaps that matter most, and build the first hoshin from that reflection. Toyota’s own system began with a diagnosis, the 1962 company-wide audit, and the first written Company Hoshin in 1963 was the countermeasure.
Related reading
- Hoshin Kanri: How Direction Becomes Daily Work — the full guide to Toyota’s system
- Why Does Hoshin Kanri Not Work? — the failure modes this sequence is designed to avoid
- What Is Catchball in Hoshin Kanri? — the deployment mechanism in depth
- Operational Audits: The Missing Feedback Loop in Hoshin Kanri — the review leg
- Daily Management and FMDS — the foundation layer
Art Smalley is president of Art of Lean, Inc. This article draws on Mikio Sugiura’s firsthand Japanese-language account of Toyota’s hoshin kanri system (Toyota Global 10), Japanese source material on Toyota’s FMDS daily management system, and firsthand Toyota and consulting experience. AI was used in the editing of this article.