Why Does Hoshin Kanri Not Work?
Hoshin kanri does not work when an organization deploys the planning form without the management system behind it: weak daily management underneath, no real review mechanism, too many priorities, skipped catchball, and targets cascaded to individuals. Toyota's own 1978 breakdown and the Kan-Pro response give an instructive case study to learn from.
Hoshin kanri does not work when an organization deploys the planning form without the management system behind it. The recurring causes: weak daily management underneath, a review process reduced to status reporting, too many priorities, skipped catchball, and targets cascaded to every individual. The document is a piece of paper. Actual ability lives inside people and processes.
This article covers the failure modes in detail, including the searched variants of this question: why hoshin kanri fails, its disadvantages, and what happened the one time Toyota’s own hoshin kanri degraded. The 1978 experience and the Kan-Pro response give an instructive case study to learn from.
Why does hoshin kanri fail in most organizations?
The failure modes below recur across industries. Most trace to one root: practicing the form of the system without the management disciplines underneath it.
| Failure mode | What it looks like | What the countermeasure actually is |
|---|---|---|
| No daily management underneath | Hoshin improvements evaporate after the champion moves on | Build stable daily management (SDCA) before and alongside hoshin (PDCA) |
| Review theater | Monthly status meetings, green/yellow/red charts, no consequences | Reviews with real questioning and real decisions; Toyota added an executive audit layer on top |
| Too many priorities | Ten to fifteen “breakthrough” objectives, everything is a hoshin item | A vital few; at Toyota the president selects 4–6 audit themes per year |
| Catchball skipped or fake | Targets flow down, no negotiation of methods or feasibility | Two-way negotiation of both targets and means until each level owns its piece |
| Cascading unchanged to individuals | Every employee gets personal hoshin paperwork | At some level, change form: carry hoshin content through daily management, not personal strategy documents |
| Form over system | The X-matrix or template is polished; the behaviors are absent | Treat the document as the least important part of the system |
No daily management underneath. Hoshin kanri and daily management are symbiotic, not separable. Hoshin runs a PDCA cycle aimed at future-oriented breakthroughs. Daily management runs an SDCA cycle (Standardize-Do-Check-Act) that holds the operational foundation stable. Toyota-lineage sources on the FMDS daily management system are explicit about what happens when an organization runs only hoshin: improvements become one-time events that stop when a champion or manager transfers, because nothing standardizes the change into daily routines. The daily management layer also feeds the hoshin: problems accumulated on daily management boards through the year become candidate themes for the next cycle’s policy. An organization with no daily management has cut both the roots and the return loop.
Review theater. A hoshin review that consists of status presentations is a calendar entry, not a check. Toyota reviews hoshin through the year like any disciplined practice, and in the era Sugiura documents it added an audit layer on top: four to six themes per year, selected by the president, presented on a double-sided A3 in ten minutes plus five minutes of questions, with the president’s written feedback composed in his own words. The audits had consequences. A 1982 audit observation about neglected distribution led, within months, to a new Head Department of Distribution Management ranked alongside seven other head departments. When review has no power to change plans, resources, or the organization itself, deviation from the hoshin costs nothing, and the system knows it.
Too many priorities. Hoshin kanri exists to concentrate the organization on a vital few objectives that need cross-functional coordination and executive attention. Load it with fifteen priorities and it becomes the corporate to-do list, which the organization already had.
Catchball skipped or performed. When targets flow down without genuine negotiation, managers receive numbers they had no hand in shaping. Ownership does not survive that. Real catchball negotiates both the targets and the means, and it continues for as many rounds as it takes until the goal and the methods are clarified. A single pro-forma feedback meeting is not catchball.
Cascading unchanged to individuals. Some implementations push personal hoshin objectives to every employee. Toyota’s documented cascade stops at the section manager level, but the direction does not stop there: it changes form, carried to the supervisor level as hoshin-aligned KPIs and improvement themes on FMDS daily management boards, with team members contributing through QC circles. Where the cascade should stop in another organization depends on culture, capability, and daily management maturity. The failure mode is not cascading deep; it is cascading unchanged, so that strategy paperwork multiplies, focus dilutes, and hoshin becomes a personal-appraisal exercise.
Form over system. The planning artifact, whether an X-matrix, a set of A3s, or a software platform, is the least important part of hoshin kanri. A hoshin document by itself accomplishes nothing. It can provide direction, a cascade of goals, and methods, but without the ability to execute and solve problems, none of it progresses.
What happened when Toyota’s own hoshin kanri weakened?
Hoshin kanri degraded at Toyota itself, once, and the episode is worth knowing in detail because of what Toyota did about it.
In 1978, Toyota’s business position was strong: domestic market share approaching 40%, and the Global 10 ambition freshly declared in Eiji Toyoda’s New Year’s speech. In the same period, the company experienced an unprecedented wave of more than one hundred severe quality problems, split roughly equally between design and manufacturing. Dealers complained about new cars arriving flawed. On-road breakdowns were increasing.
Managing Director Masao Nemoto diagnosed the root cause: managers had lost the basics. Forms were filled out and presentations followed the correct format, but the management substance behind them had hollowed. Deming Prize assessor feedback from years earlier had already warned of exactly this pattern:
- “The Kanri circle is not revolved well”
- “Presentations are framed as a QC story” (form without substance)
- “Unclear linkage of activities to Company Hoshin”
- “Reports focus on operational matters only, with no consideration of who did what and what the role of a manager should be”
Toyota’s response was not a new planning template, a new form, or an outside consulting firm. It was the Kanri Noryoku Program (管理能力向上プログラム), known as Kan-Pro: a two-year re-education of all 760 department, deputy department, and section managers in management fundamentals, launched after the 1978 crisis and built and delivered entirely in-house. Nemoto personally gave the core lecture series. The program standardized the audit format still associated with Toyota today, one double-sided A3 presented in ten minutes with the time limit enforced by a bell, and required every manager to register a priority item that executives audit-checked at mid-year and year-end.
Two details show the system’s character. First, improving hoshin practice was itself made a Company Hoshin item: the system corrected itself through its own mechanism, not through a parallel transformation program. Second, at Kan-Pro’s closing, Eiji Toyoda told the 760 managers they had completed only Shu, the fundamentals stage of Shu-Ha-Ri (守破離), and the real work of applying the capability lay ahead.
The case is worth studying as much for what Toyota did not do as for what it did. It did not redesign the hoshin forms, adopt a new framework, or bring in outside help. It re-taught 760 managers how to manage.
Why does hoshin kanri need problem-solving capability underneath?
A top-down hoshin plan reads well in theory, and a strategy plan is a good idea in any company. But hoshin kanri only progresses at the speed of the organization’s ability to execute and solve problems. Direction, cascaded goals, and methods on paper do not accomplish anything in isolation. The ability that moves them lives inside people and processes.
This is why Toyota’s own crisis response took the shape it did. The 1978 breakdown was not a planning failure; the plans existed and the market results were strong. It was a capability failure in the management layer, so the countermeasure was aimed at the management layer. It is also why bolting hoshin onto an organization with weak problem-solving produces so little: every gap the hoshin surfaces needs someone able to close it, and closing gaps is problem solving, practiced at every level, on a stable daily management base.
Why is hoshin kanri difficult?
Because it makes four demands most planning approaches do not: sustained senior executive time, existing management capability, patience with an annual and multi-year rhythm, and more than one cycle to mature. Each of these, unmet, produces the failures described above.
It consumes senior executive time, by design. At Toyota the president personally owns the Company Hoshin, edits the New Year’s speech in his own hand, selects audit themes, sits through audits, and writes feedback personally. An executive team unwilling to spend that time will run a delegated version, and delegated hoshin loses the properties that make the system work.
It presumes capability that most organizations have not built. PDCA discipline, fact-based problem solving, and stable daily management are prerequisites, not products, of hoshin kanri. Installing the annual cycle first and hoping the capabilities follow inverts the order.
It runs on an annual and multi-year rhythm. The system is built for sustained direction: annual hoshin inside three-to-five-year hoshin inside a permanent basic direction. Decisions that must move in weeks move through daily management or normal line authority, not through the hoshin cycle.
It takes more than one cycle to work. The first year of any hoshin implementation is an exercise in discovering how weak the catchball, review, and problem-solving muscles are. Organizations that expect a transformation from the first annual cycle abandon the system before it can compound.
These four demands are why the failure modes at the top of this article recur. An organization that does not meet them does not get a smaller version of hoshin kanri. It gets the form without the system.
Frequently asked questions
Why does hoshin kanri not work? The most common causes: no stable daily management underneath it, a review process reduced to status reporting, too many priorities, catchball skipped or performed as theater, targets cascaded to every individual employee, and treating the planning form (often an X-matrix) as the system. A hoshin document by itself accomplishes nothing. Direction and cascaded goals only progress when people can execute and solve problems.
What is the failure rate of hoshin kanri? No credible published failure-rate statistic exists for hoshin kanri. Claims of specific percentages trace to general strategy-execution surveys, not to studies of hoshin implementations. What can be said from experience: implementations that deploy the annual planning form without daily management, problem-solving capability, and a real review mechanism do not produce durable results.
Did hoshin kanri ever fail at Toyota? It degraded seriously once. In 1978, Toyota experienced over one hundred severe quality problems while its market position was strong. Deming Prize assessors had already warned that “the Kanri circle is not revolved well.” Toyota’s response was Kan-Pro, a two-year program in which Managing Director Masao Nemoto personally re-educated all 760 department and section managers in management fundamentals. The fix was capability development, not a new planning template.
Is hoshin kanri too top-down? Not as Toyota practices it. Targets and methods are negotiated through catchball until each level owns its piece, the documented cascade stops at the section manager level, with the direction carried below through daily management rather than personal objectives, and daily management feeds shop-floor reality back into the next cycle’s hoshin. Implementations that skip these elements do become top-down target dictation, and that is one of the standard failure modes.
What are the disadvantages of hoshin kanri? Four main ones: it requires sustained senior executive time, it presumes management capability in PDCA and problem solving that many organizations have not built, it operates on an annual-and-multi-year rhythm that does not suit every business decision, and it takes more than one cycle to work well. Organizations unwilling to invest in those prerequisites will get a planning ritual, not a management system.
Related reading
- Hoshin Kanri: How Direction Becomes Daily Work — the full guide to Toyota’s system
- What Are the 7 Steps of Hoshin Kanri? — the taught model versus the practiced system
- Operational Audits: The Missing Feedback Loop in Hoshin Kanri — the review leg most implementations lack
- How to Implement Hoshin Kanri — the build sequence that avoids these failures
- Daily Management and FMDS — the foundation layer hoshin depends on
- Is Hoshin Kanri a Lean Tool? — what kind of thing hoshin kanri actually is
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 experience. AI was used in the editing of this article.