Who Invented Hoshin Kanri?
No single person invented hoshin kanri. It took shape inside Japanese companies in the 1960s, out of the Total Quality Control movement built by JUSE scholars like Shigeru Mizuno and Kaoru Ishikawa on inputs from Deming and Juran. The honest answer traces each contributor's timeline, publications, and documented influence on the companies that built the practice.
No single person invented hoshin kanri. The practice took shape inside Japanese companies in the 1960s, out of the Total Quality Control (TQC) movement, and the various origin stories that circulate online mostly assign one person credit for what a movement and several companies built in parallel.
The honest way to answer the question is to lay out each contributor’s timeline, published record, and documented influence on the companies that built the practice. That is what this article does, ending with the best-documented company record: Toyota’s.
What did the American advisers actually teach?
Two American advisers appear in every origin story, and dating what each actually taught matters, because the popular versions compress it badly.
W. Edwards Deming lectured in Japan in 1950 at the invitation of JUSE (the Union of Japanese Scientists and Engineers). What he taught was the Shewhart Cycle, a product-focused quality wheel, inside a course that was mostly statistical quality control. He did not teach PDCA; that framework was built inside Japan over the following decade and named by Kaoru Ishikawa in 1964. When Deming encountered PDCA decades later, he did not recognize it as his own work, initially calling it a corruption of the original concept and insisting on “Plan-Do-Study-Act” instead. The full history is in One Hundred Years of PDCA Thinking. Deming’s contribution to what became hoshin kanri was real but indirect: statistical discipline, cyclical thinking, and the prestige of the prize JUSE named after him.
Joseph Juran arrived in 1954 with a different emphasis: quality as a management responsibility, not a shop-floor technique. For the lineage that leads to hoshin kanri, this was the catalytic reframing. Managing the direction of a whole company with quality-control discipline is a Juran-flavored idea before it is anyone else’s.
Both men supplied ingredients. Neither designed, named, or implemented hoshin kanri anywhere.
What role did JUSE, Mizuno, and Ishikawa play?
The reconstruction work happened in Japan, and the senior figure of that era is largely missing from English-language origin stories: Shigeru Mizuno.
Mizuno was a quality and management scholar, part of JUSE’s original Quality Control Research Group from 1948 and five years senior to Ishikawa. Through the 1950s he did the intellectual work of merging the American quality tradition with general management thinking: interpreting the Deming Wheel for Japanese readers from 1952, recasting it in general-management terms by 1954, and, with Hiroshi Tomizawa in 1959, publishing the “Management Circle” paper that put the four-part management cycle in print five years before Ishikawa gave it the name PDCA in 1964. His role and influence in the 1950s quality movement are not in doubt.
Mizuno also has the only documented early adviser connection to Toyota. Toyota’s records of its TQC introduction in the early 1960s note guidance from JUSE, in which Mizuno took part. The documented subject of that guidance is TQC, the company-wide quality discipline, not hoshin kanri specifically. That distinction matters for the origin question: the outside advisers are documented at the door of Toyota’s quality movement, and the hoshin system itself was built inside.
JUSE’s broader machinery, the QC Research Group, the training courses, and above all the Deming Prize with its demanding examination discipline, is what pushed companies to systematize their management practice. Hoshin kanri is one of the things that systematization produced.
When did the companies build hoshin kanri?
Inside that movement, the practice took shape at several companies in parallel. Bridgestone appears to have initiated the practice and its name in the mid-1960s. Komatsu developed its own version in the same era. And Toyota’s record, thanks to Mikio Sugiura, the responsible manager for hoshin kanri in Toyota’s Corporate Planning Department in the late 1970s, is the best-documented of all:
| Date | Event |
|---|---|
| June 1961 | Toyota formally adopts TQC |
| 1961 | Nippon Denso, Toyota’s major supplier, wins the Deming Prize |
| July 1962 | First company-wide TQC audit: five audit groups examine management practice across the company |
| January 1963 | First written Company Hoshin, in three layers: Basic, Long-term, Annual |
| 1965 | Toyota wins the Deming Prize |
| 1967 | Hoshin document reaches six categories, organized by function |
| 1977 | Operational audit structure stabilizes: four operational audits and four plant audits per year |
| 1978 | Eiji Toyoda declares Global 10 in the New Year’s speech, the system’s most visible expression |
The most telling detail is the sequence in 1962-63. Hoshin kanri at Toyota was not designed as a framework and rolled out. The July 1962 audit exposed four specific problems: managers did not understand the purpose of company policy, long-term plans were poor, fact-based thinking was weak, and horizontal coordination between departments lagged vertical control. The first written Company Hoshin, six months later, was the countermeasure. The system was discovered as the answer to a diagnosed problem, managers rowing hard but not in the same direction, and then refined over decades.
Did Yoji Akao invent hoshin kanri?
The most repeated origin claim online, including in machine-generated answer summaries, credits Professor Yoji Akao with inventing hoshin kanri in the 1950s. The record does not support it, and the timeline shows why.
Akao belongs to the generation after the 1950s builders. He completed his doctorate in the mid-1960s, co-edited the foundational QFD volume with Mizuno in 1978 (品質機能展開, JUSE Press), and the book translated into English as Hoshin Kanri: Policy Deployment for Successful TQM appeared under his editorship in 1988 (方針管理活用の実際, Japan Standards Association; English edition 1991), a quarter century after Toyota’s first written Company Hoshin. His standing as the method’s best-known academic explainer likely seeded the “Akao invented it” claim, assigning one generation’s work to the man who later documented it.
A fair account leaves room for real influence, placed where it belongs. Hoshin kanri in Japan was never one uniform practice: companies developed their own flavors, and through his teaching and the books of the 1978–1988 period, Akao influenced later branches of Japanese practice. What the record does not support is invention. And on the Toyota branch, the fact is plain: Sugiura’s insider account of the system’s construction from 1962 onward contains no Akao role. The documented outside influence on Toyota’s quality movement came from the earlier generation, Mizuno’s, through the JUSE TQC guidance of the early 1960s.
Akao’s QFD community did contribute one artifact to Western hoshin practice: the X-matrix, the four-quadrant planning form popularized in the United States by GOAL/QPC. The X-matrix is a genuine QFD-lineage tool. It is also absent from Toyota’s hoshin kanri, which may be the cleanest way to see the difference between the documented-and-exported version of hoshin and the practice as the source companies ran it.
Did hoshin kanri come from Drucker’s Management by Objectives?
A second origin story holds that Drucker published MBO in the 1950s and Japanese companies adapted it into hoshin kanri. Here the honest answer has two halves, and the publishing timeline cuts the other way from the Akao case.
Drucker introduced “management by objectives and self-control” in The Practice of Management in 1954, and the Japanese translation (現代の経営, 1956) was widely read. His engagement with Japan was direct as well: he first visited in 1959, his executive seminars drew large audiences, and Managing for Results appeared in Japanese (創造する経営者) in 1964, the same year as the English edition. His influence on Japanese business is documented, most famously the decades-long advisory relationship with Masatoshi Ito of Ito-Yokado. So MBO was in print in Japan before hoshin kanri took shape, Drucker’s mark on Japan is real, and the timeline alone cannot rule out influence. The question is where his influence landed.
On the record, it landed under MBO’s own banner. Japan took up Drucker’s approach under its own name, 目標管理 (mokuhyō kanri), a practice centered on individual objectives and appraisal, distinct from 方針管理 in name, in content, and in methods, and Japanese companies run the two side by side. Two different names for two different practices inside the same companies is not what a parent-and-child relationship looks like. Meanwhile, the primary shapers of hoshin kanri at Toyota do not mention Drucker as a factor, while the JUSE connection is documented.
The design of the two frameworks points the same way. MBO at its best clarifies the objective to be attained, and it typically falls short on the management-methods side: how the objective will be pursued, coordinated across functions, and checked. Hoshin kanri lives precisely in that methods-and-management territory, negotiating means as well as targets through catchball and reviewing execution in depth. A practice whose distinguishing content is the part MBO lacks is a strange candidate for an MBO derivative. The fuller comparison, including the framework that genuinely does descend from MBO, is in Hoshin Kanri vs OKRs.
Who deserves the credit, then?
The credit belongs to many hands, and it should be distributed the way the record distributes it.
Deming and Juran supplied ingredients: statistical discipline and the reframing of quality as a management job. Mizuno, Ishikawa, Tomizawa, and JUSE did the reconstruction work that turned those inputs into Japan’s own management frameworks, and the Deming Prize pushed companies to systematize. Bridgestone appears to have initiated the practice and its name. And inside each company, the system was built by working managers whose names mostly do not circulate: at Toyota, the Corporate Planning staff and executives who turned a 1962 audit’s findings into a written Company Hoshin, and presidents, above all Eiji Toyoda, who personally owned and operated the system for decades.
Much of the confusion over who did what, and when, comes from the fact that hoshin kanri was never one uniform practice. Companies developed their own flavors from the start, and later teachers and authors documented and spread their own versions. Each origin story tends to describe one branch and present it as the whole tree.
An invention with many contributors, developed in parallel, refined by use: less quotable than a professor and a date, and what the sources actually support.
Frequently asked questions
Who invented hoshin kanri? No single person. Hoshin kanri took shape inside Japanese companies in the 1960s, including Bridgestone, Komatsu, and Toyota, out of the Total Quality Control movement built by JUSE scholars such as Shigeru Mizuno and Kaoru Ishikawa on inputs from Deming and Juran. It was a movement’s practice, developed in parallel, not one inventor’s design.
Did Yoji Akao invent hoshin kanri? The record does not support it. The senior quality-movement figure of the 1950s was Shigeru Mizuno; Akao completed his doctorate in the mid-1960s, co-edited the foundational QFD volume with Mizuno in 1978, and the hoshin kanri book under his editorship appeared in 1988. Akao documented and taught the method, and through his books of the 1978-1988 period he influenced later branches of Japanese practice, but Toyota’s insider record of its system’s construction shows no Akao role.
Did W. Edwards Deming teach hoshin kanri or PDCA to Japan? Neither, exactly. Deming’s 1950 lectures taught the Shewhart Cycle and statistical quality control. The PDCA framework was built inside Japan over the following decade, primarily by Shigeru Mizuno and colleagues, and named by Kaoru Ishikawa in 1964; Deming himself, encountering PDCA decades later, initially called it a corruption of his teachings. Hoshin kanri grew inside the companies practicing that TQC discipline. The full story is in One Hundred Years of PDCA Thinking on this site.
When did Toyota start hoshin kanri? Toyota adopted TQC in June 1961, ran its first company-wide audit in July 1962, and committed its first written Company Hoshin to paper in January 1963 as the direct countermeasure to four management problems the audit exposed. The company won the Deming Prize in 1965.
What company first used hoshin kanri? The practice appears to have been initiated at Bridgestone in the mid-1960s, while Toyota was independently building the mechanics of its own system from 1962 and Komatsu practiced its own version in the same era. Several TQC companies developed hoshin practice in parallel; no one company owns the origin.
Did hoshin kanri come from Drucker’s Management by Objectives? The documented record shows no MBO route. Drucker’s The Practice of Management (1954; Japanese translation 1956) was widely read in Japan, but the primary shapers of hoshin kanri at Toyota do not mention him as a factor, MBO clarifies the objective while saying little about the management methods where hoshin kanri lives, and Japan adopted MBO separately under its own name, 目標管理 (mokuhyō kanri), distinct from 方針管理 in name, content, and methods. The documented route runs through JUSE, the Deming Prize, and each company’s own innovations.
Related reading
- One Hundred Years of PDCA Thinking — the full Taylor-to-Ishikawa history, including Mizuno’s role
- Hoshin Kanri: How Direction Becomes Daily Work — the full guide to Toyota’s system
- What Does Hoshin Kanri Mean in Japanese? — the term itself
- Hoshin Kanri vs OKRs — including the framework that really does descend from MBO
- Does Toyota Use Hoshin Kanri? — Toyota’s practice today
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), the Japanese-language publication record of the postwar quality movement, and firsthand Toyota experience. AI was used in the editing of this article.