Hoshin kanri (方針管理) is Toyota's system for aligning an organization around a vital few breakthrough objectives. The records below state what the term means, where the practice came from, how it works through catchball and operational audits, how Toyota actually ran it, the examples and failure modes that reveal its discipline, and why it matters — drawn from Mikio Sugiura's insider account, Mark Reich's practitioner guidance, and the LEI Lexicon.
Hoshin kanri is written 方針管理 and means managing toward a needle-point direction
Hoshin kanri (方針管理) combines 方針 — 方 (direction or way) and 針 (needle, as in a compass needle) — with 管理 (management or control). The characters together describe a compass needle pointing the way to proceed, then managing the whole organization toward it. Art Smalley translates the term as "managing with a needle-point type of focus pointing out the ways to proceed."
Art Smalley, Art of Lean; Global Ten (Mikio Sugiura) — artoflean.com/reference/hoshin-kanri
"Policy deployment" is a flat translation that loses the meaning of hoshin kanri
The common English rendering of hoshin kanri as "policy deployment" or "strategy deployment" drops the compass-needle metaphor at the center of the Japanese term. The Japanese 方針 is a direction to steer toward, not a policy to push down; "deployment" imports a one-way, top-down flavor the original does not carry. Art Smalley flags the translation as inadequate to what the practice actually is.
Art Smalley, Art of Lean — artoflean.com/reference/hoshin-kanri
Hoshin kanri is a living management system, not annual planning
Hoshin kanri is a strategic management practice rooted in PDCA that aligns an organization vertically and horizontally around a few breakthrough objectives. It uses disciplined two-way dialogue (catchball) between levels to connect senior-leadership intent with frontline reality. It is not top-down goal cascading, not annual planning, and not a once-a-year document that sits in a binder.
Mark Reich, Managing on Purpose (LEI, 2025); Global Ten (Mikio Sugiura) — artoflean.com/reference/hoshin-kanri
Toyota's Company Hoshin had three nested layers, of which the annual layer is only one
At Toyota the Company Hoshin was structured in three layers: Basic Hoshin (the permanent direction and reason for being), Long-term Hoshin (5-year targets and 3-5 year countermeasures), and Annual Hoshin (the current year's targets and key countermeasures). Most managers — even inside Toyota — only ever see the Annual Hoshin, which is why hoshin is so often mistaken for annual planning. Strip away the Basic and Long-term layers and the strategic coherence that makes hoshin work disappears.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota's Basic Hoshin barely changed for over fifty years
Toyota's 1963 Basic Hoshin — the company's fundamental direction — remained essentially unchanged for more than fifty years, until the 2016 reorganization into in-house companies. The Basic Hoshin is not a goal to be achieved and checked off; it is the enduring direction the company is trying to become. Its stability is the point: it gives every annual cycle a fixed reference.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Hoshin kanri turns PDCA while daily management turns SDCA
Hoshin kanri runs on PDCA — each cycle is meant to change the level of performance and reach a standard that did not exist before. Daily management (nichijo kanri) runs on SDCA — Standardize-Do-Check-Act — whose job is to hold the current standard and restore it when the process drifts. Breakthrough runs on PDCA; maintenance runs on SDCA; the two wheels turn together, with PDCA raising the standard and SDCA locking it in.
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/daily-management
Toyota's hoshin practice begins with Check and Act, not Plan — Sugiura calls it CA-PDCA
Sugiura describes Toyota's actual kanri circle as CA-PDCA: a problem-solving cycle revolved one and a half times, starting with Check and Act — grasping the current situation and acting on causes — before arriving at a credible Plan. Most Western PDCA instruction begins with Plan as if the planner faces a blank page; the CA half-turn first establishes what is actually happening. This applies at both scales: macro for the Company Hoshin and micro for shop-floor kaizen.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/pdca
CAPDCA is the hoshin-context application of PDCA, not a replacement for it
CA-PDCA does not replace PDCA. It corrects a teaching failure: PDCA taught as a pure forward cycle beginning with Plan misses the half-turn of Check-and-Act on the current state that any credible Plan must rest on. At the annual Company Hoshin scale, this shows up as starting each cycle with reflection (hansei) on the prior year before setting the new year's plan.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/pdca
Toyota's Company Hoshin originated from a failed 1962 audit, not a designed system
Toyota's Company Hoshin was a discovered practice, not a polished export. Toyota introduced company-wide TQC in June 1961, and the first company-wide audit in July 1962 found that managers did not share a common understanding of the company's direction. The written Company Hoshin institutionalized in January 1963 was a direct response to the weaknesses that audit exposed — Toyota's answer to "our managers are rowing, but not in the same direction."
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
The 1962 audit surfaced four problems hoshin was built to fix
The July 1962 company-wide audit — in which all executives and TQC instructors toured departments listening to managers describe their business management — surfaced four structural problems: lack of understanding of the real purpose of the Company Hoshin, poor quality of long-term plans, persistent failure to develop the habit of thinking based on facts, and weak horizontal coordination between departments. These four are the same problems hoshin is still designed to fix in organizations today.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Cross-functional alignment was a design goal of Toyota hoshin from the start
The fourth problem from the 1962 audit — weak horizontal coordination — was significant enough that the second company-wide audit was organized by function rather than by department. Quality and cost were audited across Product Planning, Product Design, Production Preparation, Purchasing, Production, and Sales. Horizontal cross-functional alignment was built into Toyota hoshin from its earliest form, not added later.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota's first Basic Hoshin in 1963 addressed world leadership, quality, and cost together
The three Basic Hoshin items committed to paper in January 1963 were: develop Toyota into a world leader by gathering resources from within and outside the company; further Toyota's reputation as a quality leader through the spirit of "Good Products, Good Thinking"; and contribute to Japan's economy through high-volume production and competitive prices. Even in this earliest form, Toyota hoshin covered the whole business — it was never a quality-only framework.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota won the 1965 Deming Application Prize
The Deming Prize Committee voted in October 1965 to present the Deming Application Prize to Toyota Motor Co., and the award ceremony was held in November 1965 at the Imperial Hotel in Tokyo, with W. Edwards Deming in attendance. The award came roughly four years after company-wide TQC began in 1961 and two years after the Company Hoshin was committed to paper in 1963. The Deming pursuit was the crucible in which Toyota's hoshin and audit disciplines were forged, and its assessor feedback was later mined to design the Kan-Pro management re-education program.
Toyota Motor Corporation, Toyota 75-Year History; Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/hoshin-kanri
By 1967 Toyota's Company Hoshin had six components
By 1967 the Company Hoshin had grown to six elements: Basic Hoshin, annual slogans, long-term targets (5 years), long-term countermeasures (3-5 years), annual targets, and annual countermeasures. Hoshin was also categorized by function — General Administration, Technology, Production, Quality, Cost, HR, and Environment-Health-Safety. The document was printed on brownish medium-quality paper and distributed to each department and section manager: a working document, not a glossy strategic plan.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Hoshin kanri emerged in 1960s Japan as the answer to the shortcomings of MBO
Hoshin kanri developed in Japan in the 1960s at the intersection of several influences, including Peter Drucker's Management by Objectives, introduced in his 1954 The Practice of Management. The Japanese found MBO alone fell short: it produced negotiated targets, metric gaming, and blame when objectives were missed. Hoshin retained Drucker's emphasis on objective-driven management while transforming the process through PDCA discipline, catchball dialogue, and integration with frontline problem-solving.
Hoshin Kanri — Lean Lexicon, LEI; Peter Drucker, The Practice of Management (1954) — artoflean.com/reference/hoshin-kanri
JUSE added planning and strategy to the Deming Prize criteria in 1958
In 1958, influenced by Drucker's work on long-term planning, the Japanese Union of Scientists and Engineers (JUSE) added planning and strategy to the criteria for the Deming Application Prize. This created a concrete incentive for Japanese companies to develop systematic strategic management integrated with their quality-control methods, and was the institutional catalyst that pushed companies to formalize what became hoshin kanri.
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/hoshin-kanri
Bridgestone Tire is credited with first formally adopting the term hoshin kanri
Bridgestone Tire is widely credited as the first company to formally adopt the term "hoshin kanri." In 1965 Bridgestone published the results of a study it had conducted of hoshin kanri activities at various companies — effectively the first hoshin kanri manual — documenting what had been emerging as a practice across multiple Deming Prize-winning firms. Komatsu, which won the Deming Prize in 1964, also contributed to refining the methodology.
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/hoshin-kanri
Yoji Akao codified hoshin kanri for Western audiences in 1991
Professor Yoji Akao published Hoshin Kanri: Policy Deployment for Successful TQM in 1991, the seminal academic treatment that codified the methodology and brought it to a Western audience through Productivity Press. According to Akao, the concepts of control items and hoshin kanri were born during Japanese companies' transition from Statistical Quality Control to company-wide Total Quality Control between 1961 and 1965.
Yoji Akao, Hoshin Kanri: Policy Deployment for Successful TQM (1991) — artoflean.com/reference/hoshin-kanri
Mikio Sugiura is the authoritative insider source on Toyota hoshin kanri
Mikio Sugiura joined Toyota in 1958 and was the responsible manager of the Corporate Planning Department for the 1977 hoshin cycle. He documented Toyota's hoshin system from the inside in Global Ten, published in Japanese in 2017 under the pen name Masaji Shibaura and forthcoming in English from LEI. He witnessed and participated in the President's audits, the New Year's speech drafting, the TMC-TMS merger, the 1969 recall response, and the founding of the Kan-Pro program.
Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/hoshin-kanri
Mark Reich is the foremost English-language authority on practicing hoshin kanri
Mark Reich spent 23 years at Toyota starting in 1988, including six years in Japan, and managed Toyota's North American hoshin kanri process. His book Managing on Purpose (LEI, 2025) gives detailed practical guidance on strategy development, catchball dialogues, integration with daily management and A3 problem-solving, and the leadership behaviors the system requires.
Mark Reich, Managing on Purpose (LEI, 2025) — artoflean.com/reference/hoshin-kanri
Catchball is the disciplined two-way dialogue that distinguishes hoshin from MBO
Catchball is the back-and-forth dialogue between management levels that aligns goals, plans, and targets before anything is finalized. The level above sets direction — the what and the why; the level below proposes means — the how — and pushes back where targets are unrealistic. Both commit only after genuine understanding. It is the mechanism that distinguishes hoshin from MBO, OKRs, and ordinary goal-cascading.
Mikio Sugiura, Toyota Global 10 (Ch. 4); Mark Reich, Managing on Purpose — artoflean.com/reference/catchball
The term catchball is written in katakana from the children's game of playing catch
Catchball (キャッチボール, kyacchi booru) is a borrowed English term written in katakana, referring to the children's game of tossing a ball back and forth. The senior level throws an objective; the next level catches it, examines it, proposes how it would actually achieve it, and throws back questions and pushback; the senior level adjusts and throws again. The exchange continues until both sides commit because both sides understand.
Catchball — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/catchball
Catchball is not communication, negotiation, or a single meeting
Catchball is not communication, which moves an already-made decision downward — catchball is how the decision gets made. It is not adversarial negotiation, since both parties want a shared answer that works rather than a higher or lower target. And it is not a single meeting: it is a series of exchanges across days or weeks, including informal ones, with the ratifying meeting only the visible tip.
Mikio Sugiura, Toyota Global 10 (Ch. 4); John Shook, LEI — artoflean.com/reference/catchball
Real catchball must change something — catchball that moves nothing is theater
Three questions reveal whether catchball is real: can the level below explain in their own words why the objective matters; did anything change because of pushback from below; and did the senior level adjust support, capacity, or priorities in response to what they heard. If every objective set at the top arrived at the bottom unchanged, no real catching happened. If the answer to a lower level's constraints is "they just have to figure it out," the catch was rejected, not received.
Mikio Sugiura, Toyota Global 10 (Ch. 4); Art Smalley, Art of Lean — artoflean.com/reference/catchball
Nemawashi comes before the hoshin document, not after it
At Toyota a great deal of behind-the-scenes dialogue — nemawashi — happens before anything is formally written down: one-on-one conversations, sketches, quiet pushback, adjustments made before the meeting where the plan is "presented." The formal hoshin document on the brownish A4 paper is the last step, not the first. People who have not lived hoshin invert this order, drafting the form first and then "communicating" it — which is not catchball.
Mikio Sugiura, Toyota Global 10 (Ch. 4); John Shook, Managing to Learn — artoflean.com/reference/nemawashi
The catchball process within hoshin kanri is nemawashi applied to strategy
The catchball process is a structured form of nemawashi — goals and plans passed back and forth between levels, each providing input and adjusting until alignment is reached. Nemawashi (根回し, "going around the roots") is the broader Japanese practice of building consensus through informal one-on-one discussion before a formal decision; catchball is that same discipline applied specifically to strategic planning.
John Shook, Managing to Learn (2008); Toyota Way 2001 — artoflean.com/reference/nemawashi
Catchball works between adjacent levels; skipping levels breaks ownership
Catchball happens between adjacent levels of the organization. Each level catches the ball from the level above, adds its own analysis and context, and throws it to the level below. Senior management catchballing directly with frontline workers — skipping middle management — creates confusion about roles and ownership. The same person is often catcher and thrower in the same cycle, which is what makes hoshin different from a simple top-down cascade.
Catchball — Lean Lexicon, LEI; Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/catchball
The vertical cascade translates direction into work at each level, not just smaller numbers
The vertical cascade runs Company Hoshin to Plant Manager Hoshin to Department Manager Hoshin to Section Manager Hoshin. At each level the hoshin from above is translated into that level's context using a standard shape: goal, action item, target, action plan, and audit plan. A plant manager's hoshin is not the company hoshin written smaller — it is the plant manager's expression of what the plant must do for the company hoshin to be achieved.
Mikio Sugiura, Toyota Global 10 (Ch. 4); LEI Lexicon — artoflean.com/reference/hoshin-kanri
Even at Toyota the cascade went abstract in the middle layers
Toyota's own internal audits found the roll-out into Department and Section Manager Hoshin lacked uniformity, with action plans that lacked concreteness on deadlines. Department Manager Hoshin tended to be somewhat abstract while Section Manager Hoshin were developed concretely — the top is concrete and the bottom is concrete, but the middle goes abstract. This abstraction gap is the most common cascade breakdown, and it is structural rather than a personal failing.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
A concrete hoshin can be acted on Monday morning; an abstract one can only be repeated
A practical test applies at any level: can someone two levels below the writer read this hoshin and know what to do differently on Monday morning? If yes, it is concrete; if they can only repeat the words back, it is abstract. The further down the cascade, the more concrete the hoshin must become — by the section-manager level, every line should map to actual work the team will do.
Art Smalley, Art of Lean; Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/hoshin-kanri
Concrete hoshin was easy for plants and hard for support staff
Sugiura noted that formulating concrete plans was straightforward for the plants but far from easy for support staff departments. Manufacturing has natural concrete units — takt time, defect rate, downtime — that lend themselves to clear targets. Support functions such as HR, IT, finance, engineering, and purchasing struggle more and tend to drift toward activity-counting (trainings delivered, audits run) rather than outcomes (capability built, problems solved).
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Art Smalley's rule is to over-communicate the hoshin by a factor of five
Art Smalley's guidance: "Plan on over-communicating your hoshin contents by a factor of five and you will be close to the level that is probably required." Most managers communicate the deployed hoshin once, at the planning meeting, and assume the message has landed; it has not. Meaning does not transfer in a single pass, especially when the message is abstract or the consequences of getting it wrong land months later.
Art Smalley, "Houshin Kanri Advice," Art of Lean — artoflean.com/reference/hoshin-kanri
Hoshin deploys both vertically and horizontally; without the horizontal it is just cascaded KPIs
Most Western treatments focus almost entirely on the vertical cascade and miss half the picture. Vertical deployment translates direction down the hierarchy; horizontal deployment coordinates across functions in service of company-level objectives. At Toyota the horizontal mechanism was as load-bearing as the vertical one. Without horizontal coordination you have cascaded KPIs, not hoshin.
Mikio Sugiura, Toyota Global 10 (Ch. 4); Mark Reich, Managing on Purpose — artoflean.com/reference/hoshin-kanri
Toyota coordinated hoshin horizontally through cross-functional Function Meetings
At Toyota, hoshin implementation was checked and followed up through Function Meetings, organized by management theme rather than by department: Quality and Cost Function Meetings (the oldest and most central), Production Function Meetings, Technology Function Meetings A and B, and Function Meetings for Sales, HR, and Public Relations. The next year's hoshin was drawn up based on reflections from these meetings — because alignment was largely complete there, little additional consensus-building was needed by the time Corporate Planning compiled it.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Function Meetings made cross-functional decisions, not status reports
A real cross-functional body translates company objectives into function-coordinated initiatives, surfaces conflicts before they hit the floor, and jointly reviews progress on problems that span functions. "Reduce development lead time" is not deployed to Engineering alone; it is translated jointly with Manufacturing, Product Planning, Purchasing, and Sales into an initiative they all own pieces of. Function Meetings are working sessions where cross-functional decisions get made, not meetings where departments take turns presenting status.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Cross-presenting hoshin A3s is a smaller-scale version of Function Meetings
Michael Ballé describes a practical version that scales below Toyota's full structure: department heads cross-present problem-solving A3s to each other, explaining how they will overcome obstacles to their hoshin targets. Each department learns what its colleagues are trying to achieve, what obstacles they face, and where they need help — or where they should stop hindering without realizing it. Without regular cross-presentation, departments pursue their own objectives without regard for impact on the full value stream.
Michael Ballé, "What are the pitfalls of implementing hoshin kanri?" (LEI Lean Post, 2016) — artoflean.com/reference/hoshin-kanri
Engineering releasing changes on a fixed rhythm illustrates horizontal hoshin coordination
Ballé's concrete example: an engineering department realizes that frequent random engineering changes make it hard for suppliers to support a milk-run program. Engineering then chooses to release part-design changes on a regular rhythm rather than in unexpected batches, giving suppliers space to adapt. This decision is invisible from inside Engineering's own hoshin — it only becomes visible in the cross-presentation with the functions it affects.
Michael Ballé, "What are the pitfalls of implementing hoshin kanri?" (LEI Lean Post, 2016) — artoflean.com/reference/hoshin-kanri
Eiji Toyoda declared the "Global 10" challenge in his 1978 New Year's speech
In his January 1978 New Year's speech, President Eiji Toyoda set the objective of raising Toyota's global production share from 7% to 10% of a projected 45-million-car world market, naming it "Global 10." This single hoshin objective drove coordinated initiatives across every function — sales expansion, production capacity, product development, cost reduction, and overseas manufacturing — and is the clearest illustration that Toyota hoshin was always about total business direction, not quality alone.
Mikio Sugiura, Toyota Global 10 (Ch. 1) — artoflean.com/reference/hoshin-kanri
Global 10 broke into six key cross-functional countermeasures
The Global 10 challenge was followed by six key countermeasures: enhancing Toyota-wide cooperation across TMC and TMS; putting a basic technology research structure in place; developing attractive products and reducing lead time; ensuring development of great cars in fuel economy, weight saving, and reliability; securing a solid position in global markets; and intensifying cost-reduction efforts. None of these is a frontline KPI, and none lives inside a single department — each required Product Planning, Engineering, Manufacturing, Sales, and Purchasing to change how they coordinate.
Mikio Sugiura, Toyota Global 10 (Ch. 1) — artoflean.com/reference/hoshin-kanri
The Global 10 number sat with the President privately for over a decade before declaration
The Global 10 idea predated its 1978 public declaration by years. Sugiura recounts that Eiji Toyoda spoke of achieving 10% of global car production as early as 1967, and the 1971-73 COP (Creative Operation Program) Committee discussed global-share targets under the cover label "Global α%" to prevent leaks. In the 1978 speech Toyoda said it "has long been my wish to raise this to 10%" — textual evidence the ambition had been private for over a decade.
Mikio Sugiura, Toyota Global 10 (Ch. 1) — artoflean.com/reference/hoshin-kanri
Global 10 was declared in 1978 and achieved in 1990 — twelve years of execution
Toyota's global production share moved from 3.6% when Eiji Toyoda became President in 1967, to roughly 7% at the 1978 declaration, to 9.6% by the 1982 TMC-TMS merger, to 10.6% by 1990. The harder work came after the declaration, not before: navigating the 1981 US Voluntary Restraint Agreement, building the NUMMI joint venture in 1984-85, and establishing independent North American production. A numeric ambition owned by the President set the company's direction for more than a decade.
Mikio Sugiura, Toyota Global 10 (Ch. 1) — artoflean.com/reference/hoshin-kanri
The Long-term Countermeasure to shorten development lead time produced the LASRE engine
Toyota's 1978 Long-term Countermeasure #4 — "Shorten the lead time from development of attractive products to start of production" — drove Engine Engineering to create the LASRE engine concept (Light-weight, Advanced, Super-Response Engine) and an entirely new approach to engine development. A single line in the Long-term Hoshin set off a multi-year engineering program, illustrating how the long-term layer reaches into concrete technical work.
Mikio Sugiura, Toyota Global 10 (Ch. 4); Art Smalley, Art of Lean — artoflean.com/reference/hoshin-kanri
Toyota's annual hoshin carried specific production-volume and cost targets, not just quality goals
Toyota's annual targets included concrete numbers across functions: production-volume targets such as "100,000 cars/month" in 1967 and "2,000,000 cars/year" in 1970, cost-reduction targets by model, R&D capacity targets, and market-share objectives — alongside quality goals. Hoshin at Toyota was the management of the whole enterprise toward its most critical objectives, with quality one important dimension among several.
Hoshin Kanri — Lean Lexicon, LEI; Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/hoshin-kanri
Production volume at Toyota was the President's exclusive decision, worked by hand
Annual production-volume targets — the numbers that shaped supplier planning, personnel, and capital investment across the Toyota Group — were the President's exclusive decision. Sugiura describes walking into Eiji Toyoda's office during the 1977 planning cycle and finding three time-series graphs laid out for domestic sales, overseas exports, and production, with realized volumes in blue pencil and forecasts in red. The President was balancing trade-friction concerns against dealer demand by hand, before the decision went out to the departments.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
At Toyota the Company Hoshin is the President's Hoshin
Sugiura states the ownership principle directly: the Company Hoshin is the President's Hoshin. Even when the content is devised by staff, and even when some components were opposed by some middle managers, what has been debated and decided as a company must be executed. The President's role is to articulate the direction in a way that enrolls the organization in the challenge.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
The President's annual New Year's speech was the primary vehicle for delivering the hoshin
At Toyota the President's annual New Year's speech delivered the Company Hoshin, treated as a major leadership act rather than a formality. Eiji Toyoda's 1978 manuscript ran about 19 double-spaced A4 pages and roughly 20 minutes, and he personally revised it with as many as 80 red-pen corrections including punctuation. After the speech, a printed summary was distributed and department managers conveyed it at their workplaces — the official roll-out of the year's hoshin.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Hoshin is a document and a ritual; the ritual has to be performed well
At Toyota hoshin kanri is both a written artifact and a ritual that activates it. The written Company Hoshin is the formal document; the President's New Year's speech is the ritual that brings it alive. Sugiura's account — the 80 red-pen corrections, the manuscript iterating to fewer corrections each year, the attentive delivery — shows that ceremonial delivery done perfunctorily does not carry the same weight. Bad ritual is as unsuccessful as no ritual.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Top management's intentions do not transfer automatically; they must be repeated across channels
Sugiura records the principle directly: the intentions of top management are not automatically understood by all employees, so messages must be repeated time and again in many different ways. Toyota's "youthfulness" theme from 1976-77 reappeared in the 1978 New Year's speech, the Bonus Grant Ceremony, and the 1979 Spring Greeting Event. A single announcement does not land; the message is built up through structured repetition across multiple ceremonial channels.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota's annual slogans responded to current reality, not generic positivity
At Toyota the annual slogan accompanying the Basic Hoshin framed what the year was about. "Toyota-wide Quality Assurance" was held as an annual slogan for 25 years with yearly changing subtitles: after the 1969 recalls, "Be mindful of the public nature of the car industry"; after the oil crisis, "Building the Toyota of the future in times of drastic change." A slogan that can be applied to literally any year is wallpaper; a good one tells the organization where to spend attention.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
The annual hoshin cycle has a rhythm of reflection, commitment, mid-year review, and year-end learning
A workable annual cycle runs roughly: Q4 reflection and drafting of next year's direction with initial nemawashi; year-end and new-year formal commitment with catchball at each level; a substantive mid-year review; and an end-of-year reflection that feeds the next Q4. The annual cycle is not a fresh planning exercise each January — it is the next iteration of an ongoing direction, the current-year expression of the long-term arc.
Mikio Sugiura, Toyota Global 10 (Ch. 4); Mark Reich, Managing on Purpose — artoflean.com/reference/hoshin-kanri
A real mid-year review changes the plan; a status review only ratifies it
Most organizations schedule a mid-year hoshin review and use it to report status against targets while nothing changes. A working mid-year review names gaps honestly, asks why the plan is not working rather than only what the recovery action is, reallocates support to functions that need it, and adjusts the plan when the diagnosis demands it. Locking in January's plan and refusing to adjust because "we committed" is not PDCA — real PDCA includes the Check and the Act.
Art Smalley, Art of Lean; Mark Reich, Managing on Purpose — artoflean.com/reference/hoshin-kanri
The operational audit is the Check step of hoshin PDCA, and is distinct from a review
The operational audit is the Check in the hoshin PDCA cycle. A review is a status meeting where the owner presents progress and leadership confirms the plan. An audit is an investigation: the auditor, typically senior leadership, goes to the gemba, examines documents, talks to people two levels below the presenter, and forms an independent judgment of whether the deployed hoshin is actually being executed and whether reported progress reflects reality. Reviews are what most companies run; audits are what hoshin requires.
Mikio Sugiura, Toyota Global 10 (Ch. 4); Art Smalley, Art of Lean — artoflean.com/reference/hoshin-kanri
Toyota's audit system evolved from a 1962 TQC status check to focused countermeasure audits
Toyota's audit mechanism evolved over decades. The 1962 first company-wide audit checked TQC status; from 1968 the focus shifted to the specific key countermeasures of the Company Hoshin, performed by senior executive officers with four to six audit themes per year decided by the President; and from 1977 "operational audits" became audits of annual key countermeasures, running about four times per year. The audits became progressively more specific to what the company was actually trying to achieve.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota's audit format was one double-sided A3, ten minutes presenting, five minutes Q&A
Toyota's operational-audit documents were on medium-quality A3 paper printed double-sided, with each presenter taking ten minutes plus five minutes of Q&A, so an audit typically ran about two hours. The format is austere by design: the A3 forces concise causal reasoning, ten minutes forces the presenter to lead with what matters, and five minutes of Q&A forces the auditor to ask the right question.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
The President's audit feedback was his own words, which is why it carried weight
At Toyota the President's written feedback at the close of each audit was his own — Sugiura was asked more than once whether Corporate Planning had drafted it, and the answer was no, which made the comments all the more valuable. When senior leaders write their own audit comments, the audit is real; when they sign comments drafted by staff, the audit is theater. The audit themes were proposed by Corporate Planning, but when executives diverged the President made the final decision.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota auditors asked presenters "What would you do as President?"
When a department manager proposed a change outside their own authority during an audit, senior participants would ask "What would you do as President?" or "What would you do if you were the responsible executive?" The question surfaces system-level issues above the presenter's role, tests leadership readiness, and signals that rising to senior-level thinking is part of what the audit is for — making the audit a development mechanism, not just a review.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
The 1982 Tahara Plant audit moved Distribution from a scattered function to a peer Head Department
During a 1982 operational audit following the TMC-TMS merger, a production manager presented kaizen on distribution costs at the Tahara Plant, located about 60 km from headquarters where transport took four times as long as at the Nishi-Mikawa plants. Eiji Toyoda responded that treating distribution "like a thing in the shade" was a big mistake, recalling that postwar Toyota raised productivity through distribution kaizen when it had no capital. Within months Distribution was promoted into a new Head Department of Distribution Management, ranked alongside seven other head departments.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
A 1974 energy-saving audit reported 480 million yen per month and launched the F-3 Program
A 1974 Company Hoshin item was "resource/energy-saving measures." Kaizen examples were reported at monthly cost meetings, an Energy-Saving Countermeasures Committee was established in May, and a September operational audit on the theme reported savings of 480 million yen per month. The President's feedback directed that energy saving must not harm quality, safety, or cost, and the effort fed into the 1978 launch of the F-3 Program for fuel economy and future technology.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
The 1980 Dyna market-share audit led Toyota to create a separate Truck Department
In a 1980 President's audit, a product-planning chief investigator presented "Increasing market share of Dyna," whose domestic share had fallen to fourth. The President's follow-up question — whether truck sales techniques should match passenger cars and whether after-sales service had issues — surfaced that the real problem was the sales-channel structure, not the product. This led to TMS establishing a new Truck Department in 1981 and the 1982 Company Hoshin item "Comprehensive roll-out of truck sales countermeasures."
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota's hoshin and audit system did not prevent the 1978 quality crisis
Toyota's hoshin and audit machinery did not prevent the 1978 quality crisis: unprecedented dealer complaints, over 100 severe quality issues, and increasing on-road breakdowns. Masao Nemoto's diagnosis was that managers had forgotten the basics of PDCA — the forms were intact but the discipline behind them had decayed. The lesson is that when audits start producing the same surface answers year after year, the issue is rarely the audit format; the management practice has decayed and audits have become ceremony.
Mikio Sugiura, Toyota Global 10 (Ch. 4-5) — artoflean.com/reference/hoshin-kanri
Toyota's response to the 1978 crisis was to re-educate managers, not redesign the forms
Toyota's response to the 1978 quality crisis was the Kanri Noryoku Program (Kan-Pro), a two-year management re-education for roughly 760 department and section managers, with Nemoto personally delivering four lectures to 650 of them. The response was not to redesign the hoshin forms but to re-educate and coach the managers. When the practice degrades — and it will — the answer is re-education and coaching, not new templates.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/hoshin-kanri
The Kan-Pro program appeared in Toyota's own Company Hoshin as a long-term countermeasure
Improving how managers did hoshin was itself a Company Hoshin item: Kan-Pro appeared as Long-term Countermeasure #7, "The improvement of executive and operational management skills." Hoshin is not a system you deploy and then operate — it requires continuous development of the managers who run it, and Toyota treated that development as a hoshin objective in its own right.
Mikio Sugiura, Toyota Global 10 (Ch. 5); Hoshin Kanri — Lean Lexicon, LEI — artoflean.com/reference/hoshin-kanri
Kan-Pro's curriculum was designed from ten-year-old Deming Prize assessor feedback
To design Kan-Pro's content, Nemoto had Corporate Planning analyze the decade-old documentation of Deming Prize and Japan Quality Control Award assessor feedback. The most-heard complaint was "the Kanri circle is not revolved well," followed by "presentations are framed as a QC story" with execution missing underneath, "unclear linkage of activities to Company Hoshin," reports focused only on operational matters, and reports whose primary message was lost. Toyota mined what outside experts had already told it rather than inventing the curriculum.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/hoshin-kanri
Kan-Pro was delivered in-house so that the executive trainers would improve too
Chairman Hanai directed that managers be educated in-house under Nemoto, without external trainers, because the current executives had themselves been trained by the Deming Prize effort and should transmit that knowledge. Eiji Toyoda added that board members coaching their subordinates could likewise improve their own management skills. The in-house choice was a governance decision, not cost-cutting: external trainers would have preserved the skill asymmetry, while internal trainers closed it by the act of delivering.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/hoshin-kanri
Kan-Pro registered one "priority coaching item" per manager as its accountability mechanism
Each manager in Kan-Pro selected one priority coaching item — typically their most important Department Manager Hoshin item — and registered it with Corporate Planning. That single topic became the focus of mid-year and end-of-year audits by executives in both program years, with section managers selected by lot audited similarly. The choice-plus-accountability structure forced specificity that generic manager training would not have produced.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/hoshin-kanri
Kan-Pro's closing principle was "let us hear about your struggles"
At Kan-Pro's conclusion, executives told managers that kanri presentations are not the same as operational audits — too often the actual management the manager performed does not stand out. They wanted honest accounts of struggle and resolution: kanri "is not all gloss and shine; it is rough-cut," and "stories with bells and whistles are not what we want to hear." A presentation that names the troubles faced, what was done, what was solved, and what remains is the useful artifact, not a polished success narrative.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/hoshin-kanri
A Kan-Pro survey found 91% of managers rated it beneficial, weakest on technical-skill transfer
Sugiura reports honest program results: 91% of the 760 managers surveyed rated Kan-Pro beneficial, with the strongest gains in creating presentation documents (89%) and drafting a kanri story (86%), and the weakest in accumulation of specific technical skills (31%). The program succeeded at generic management discipline — presentation, the kanri circle, the QC story — and was weak at domain-specific expertise transfer. Sugiura documents the weak number alongside the strong ones.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/hoshin-kanri
The QC Story is Toyota's standardized eight-step problem-solving presentation format
The QC Story is Toyota's standardized eight-step format: reason for picking the topic, setting a target, grasping the current situation, analyzing causes, designing countermeasures, executing countermeasures, checking results, and recurrence prevention with standardization. The same structure is used by shop-floor QC circles and by department-manager hoshin presentations, which lets people across levels share a common narrative skeleton and makes presentations mutually legible both vertically and horizontally.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
In hoshin work Toyota sets ambitious targets before grasping the current situation
Sugiura names a deliberate difference between QC-circle and hoshin practice at the target-setting step. Conventional teaching grasps the current situation first and sets a target after, but doing so often produces less ambitious, current-state-anchored targets. For hoshin, where Company Hoshin roll out to department and section levels, it is best to set ambitious targets first — pushing the organization beyond incremental reasoning from the current condition.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
"One A3, ten minutes" is a rehearsal discipline, not just a format
Kan-Pro formalized a presentation discipline that had evolved at TMC since the 1960s: one A3 sheet, ten minutes presenting, five minutes Q&A, with a bell rung at ten minutes. The value comes from the rehearsal and preparation the format forces, not the format itself — Nemoto had emphasized rehearsal since the Deming Prize era. Between mid-year and year-end audits, time overruns dropped dramatically and hesitation markers ("er," "um") fell off, evidence the rehearsal discipline worked.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/a3
A3 became Toyota's standard audit format only in the 1980s, after 20 years of office use
A3-size sheets had been used at TMC since the 1960s for office-work rationalization, but Sugiura is precise that it was only from the 1980s — through Kan-Pro — that A3 came to be used at operational audits for its readability. A3 is a Kan-Pro-era enshrinement of a longer-running office-work practice, not a Toyota origination of the 1950s. Sugiura also notes the cost: unifying everything onto one A3 can curtail the reporter's creativity and takes real effort to prepare.
Mikio Sugiura, Toyota Global 10 (Ch. 5) — artoflean.com/reference/a3
Hoshin kanri works only with daily management and A3 problem solving alongside it
Hoshin kanri is one of three integrated components of a Toyota-style management system: hoshin (strategic alignment around breakthrough objectives), daily management (operational execution and standard maintenance), and A3 problem solving (structured improvement connecting the two). Hoshin without daily management is strategy that never reaches the floor; daily management without hoshin is operational excellence without direction; problem solving is how gaps between plan and actual get closed at every level.
Mark Reich, Managing on Purpose (LEI, 2025); Global Ten (Sugiura) — artoflean.com/reference/hoshin-kanri
Gains from hoshin must be handed off to daily management or they regress
The hoshin process depends on stable daily management as its foundation — breakthrough objectives cannot be deployed to teams that cannot maintain basic standards. Equally, gains achieved through hoshin initiatives must be handed off to daily management (SDCA) to sustain them, or the improvements regress. Trying to make hoshin work in an organization with no daily-management discipline is balancing one leg of a three-legged stool.
Mark Reich, Managing on Purpose; LEI Lexicon — artoflean.com/reference/daily-management
The A3 is the natural working format for hoshin: hoshin is the skeleton, A3 the muscle
Hoshin kanri provides the organizational structure and strategic alignment — the skeleton — while A3 problem-solving provides the movement and action — the muscle. Hoshin objectives are often captured on A3s documenting the gap, root-cause analysis, target condition, countermeasures, and review plan; hoshin reviews surface problems and A3s solve them. Both are expressions of PDCA at different scales: hoshin at the organizational and annual scale, A3 at the project and problem scale.
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/a3
Hoshin kanri connects Challenge to daily work through True North
Hoshin kanri is the mechanism that translates Toyota Way Challenge — forming a long-term vision and pursuing ambitious goals — into annual objectives and concrete actions at every level. Challenge supplies the why, the long-term direction; True North gives that challenge a fixed ideal direction such as zero defects and zero inventory; and hoshin kanri supplies the how, the mechanism for focusing effort. Challenge sets the horizon beyond what incremental kaizen alone can reach.
The Toyota Way, Toyota Motor Corporation — artoflean.com/reference/challenge
Hoshin is set to a vital few breakthrough objectives, not ten to fifteen priorities
Hoshin kanri begins with an honest assessment of the critical few challenges an organization must address. If you have more than three or four hoshin objectives, you have too many — you are trying to do everything instead of focusing. Companies that deploy ten to fifteen "hoshin objectives" have created an elaborate goal-setting bureaucracy, not a management system; if everything is a hoshin priority, nothing is.
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/hoshin-kanri
Mark Reich recommends starting hoshin "inch-wide, mile-deep"
Mark Reich's recommendation for starting hoshin is "inch-wide, mile-deep": pilot in one division or plant, demonstrate results, then scale, rather than attempting an organization-wide rollout from day one. Leadership involvement is non-negotiable — without the leader's engagement, understanding, and proactive support, hoshin cannot succeed; the continuous-improvement function can support but cannot replace leader responsibility.
Mark Reich, Managing on Purpose (LEI, 2025) — artoflean.com/reference/hoshin-kanri
The most common Western failure is treating hoshin as top-down goal deployment
The single most common Western failure is taking senior management's targets and cascading them downward without genuine catchball, producing Management by Objectives with Japanese terminology — precisely what Toyota moved away from. As the LEI Lexicon notes, the misconception is that hoshin is a top-down deployment process akin to MBO; in reality, practiced consistent with Total Quality Management, hoshin is equally top-down and bottom-up.
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/hoshin-kanri
Toyota hoshin has no individual-employee cascade — it stops at the supervisory layer
At Toyota the hoshin cascade stops at the assistant-manager and group-leader supervisory layer; it does not deploy to individual team members. Team members are led by supervisors who use the hoshin as an operational guide, and individual operators participate in improvement through QC circles rather than personal hoshin. The common Western assumption of a personal hoshin for every employee does not match Toyota practice.
Global Ten source notes, Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/hoshin-kanri
Hoshin is not MBO, OKRs, Balanced Scorecard, or strategic planning as usually practiced
Hoshin kanri is frequently confused with adjacent frameworks but differs from each. MBO is top-down target-setting with individual accountability; OKRs are quarterly goal-setting; Balanced Scorecard is a measurement framework; and typical strategic planning produces a document that sits on a shelf. Hoshin is a multi-year, two-way management practice with organizational learning that produces aligned action changing daily work — not a measurement framework or a planning artifact.
Jeffrey Liker and John Shook, LEI; Mikio Sugiura, Toyota Global 10 — artoflean.com/reference/hoshin-kanri
Technical hoshin is MBO with Japanese terminology; real hoshin is a socio-technical process
Liker and Shook frame the central failure mode: technical hoshin is advanced objective-setting — fill out a template, cascade targets, track metrics, run a quarterly review — which is what most Western companies actually do, and is MBO with Japanese terminology. Real hoshin is a socio-technical process requiring collaborative planning at all levels, robust problem-solving capability, coaching and on-the-job development, and individual ownership through causal reasoning. If people fill out forms without changing how they think, manage, and solve problems, it is paperwork, not hoshin.
Jeffrey Liker and John Shook, "Hoshin Kanri as a Foundational Piece of a Lean Management System" (LEI Lean Post) — artoflean.com/reference/hoshin-kanri
Two things kill hoshin momentum: weak PDCA and tool-based implementation
Art Smalley names two failures that kill hoshin most reliably. The first is failure to truly embrace PDCA management — easier to talk about than to do; without rigorous check-and-adjust cycles, performance goes sideways with excuses. The second is tool-based implementation — embracing forms, charts, and templates without the underlying management discipline. Posting hoshin charts on the wall does not make you better at hoshin, just as posting the periodic table does not make you better at science.
Art Smalley, "Houshin Kanri and PDCA Management," Art of Lean — artoflean.com/reference/hoshin-kanri
Annual-planning collapse is the most common structural failure of hoshin
The most common structural failure is treating hoshin as annual planning, with the Basic and Long-term layers absent and the whole exercise reduced to "what are this year's targets?" When this happens, direction shifts year to year with no continuity, annual targets feel arbitrary, managers learn that priorities change every January and stop investing, and the strategic coherence hoshin exists to produce disappears. The Annual Hoshin makes sense only as the current-year expression of a longer arc.
Mikio Sugiura, Toyota Global 10; Art Smalley, Art of Lean — artoflean.com/reference/hoshin-kanri
Deploying outcome targets without means is MBO; deploying activities without goals is activity-counting
Two opposite failures often appear in the same organization. Goals without means deploys outcome targets — "reduce defects 30%" — with no specification of how, so the lower levels are told to figure it out; this is MBO. Means without goals deploys activities — "complete 12 kaizen events," "deliver 8 A3s" — with no connection to outcomes, so activity-counting replaces outcome-chasing. Real hoshin pairs goals with means and lets catchball reconcile the senior leader's direction with the lower level's proposed approach.
Mikio Sugiura, Toyota Global 10; Art Smalley, Art of Lean — artoflean.com/reference/hoshin-kanri
Hoshin loses credibility when targets are routinely missed and nothing changes
Michael Ballé puts it directly: hoshin only makes sense if objectives are met, and if goals are missed by far the exercise becomes pointless and loses credibility. When targets are routinely missed by 30% or more with no resource reallocation, no coaching, and no honest re-planning, the organization learns that hoshin commitments are not real, and future cycles get more polished and less honest. The fix is not lower targets but real support — gemba walks, capability building, removed obstacles — when targets are at risk.
Michael Ballé, "What are the pitfalls of implementing hoshin kanri?" (LEI Lean Post, 2016) — artoflean.com/reference/hoshin-kanri
Assigning a level targets it has no authority to influence is a subtle hoshin failure
A subtler failure is giving a level targets it cannot influence — Sales handed a margin target controlled by Product Pricing, or Manufacturing handed a quality target controlled by Engineering. The level either hits the target by accident or does not, but cannot meaningfully act on it. This emerges when senior leaders deploy outcomes mechanically by org chart rather than to the level that owns the lever; the fix is to deploy to the lever-owner or to create a cross-functional initiative with shared accountability.
Mikio Sugiura, Toyota Global 10; Art Smalley, Art of Lean — artoflean.com/reference/hoshin-kanri
Skipping the Check and Act degenerates hoshin into an annual planning exercise
Many organizations do the Plan and Do phases of hoshin but treat Check and Act as optional. Without rigorous review and adjustment, hoshin degenerates into an annual planning exercise that gathers dust. The learning happens in the Check — when actual results are compared to targets, root causes are analyzed, and countermeasures are developed; when targets are missed, the question is not "who failed?" but "what did we learn and what will we do differently?"
Hoshin Kanri — Lean Lexicon, Lean Enterprise Institute — artoflean.com/reference/hoshin-kanri
Hoshin used well is a counterweight to "Big Company Disease"
Ballé draws out that Toyota recognized growth inescapably brings "Big Company Disease": the company focuses more on internal processes than customer preferences, directors solve their own problems at the expense of colleagues, leaders select pandering middle managers, and legacy technologies block new ones. Used well, hoshin is one of the strongest tempering forces against this drift; used as a transactional planning technique, it can accelerate the disease by adding another layer of corporate ritual. Real hoshin should make the organization feel more honest and aligned, not more processed.
Michael Ballé, "What are the pitfalls of implementing hoshin kanri?" (LEI Lean Post, 2016) — artoflean.com/reference/hoshin-kanri
Toyota's normal-time hoshin discipline is what let it respond fast to the 1969 recall crisis
When the 1969 US recall crisis hit — triggered by Ralph Nader's activism, the National Traffic and Motor Vehicle Safety Act, and press coverage of concealed defects — Toyota did not improvise a crisis mechanism. The normal-time hoshin ritual absorbed the crisis: a Special Recall Committee on June 17, a company-wide quality audit targeting suppliers and internal functions within weeks, and the addition of "Being aware of the public nature of the car industry" to the 1970 Basic Hoshin. Sugiura's principle: because normal-time hoshin was functioning well, the crisis version could scale company-wide in a really short time.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Toyota extended hoshin discipline across legal company boundaries to affiliates and dealers
Toyota extended hoshin-style review discipline beyond its own legal boundary. Informal Executive Meetings (IEMs), coordinated by the Related Business Research Office established in 1973, brought President-led review to five or six affiliated companies per year, with Vice-President-level Mini-IEMs for about seven more. Dealer QC followed in 1981: Nemoto personally trained 60 TMS area managers and QC and hoshin activity reached about 400 dealers, eventually 90% of dealers within three years, with 12,000 QC circles operating at peak.
Mikio Sugiura, Toyota Global 10 (Ch. 4-5) — artoflean.com/reference/hoshin-kanri
TMC and TMS had different hoshin cultures, bridged by renaming "audit" as "exchange business reports"
Before the 1982 merger, Toyota Motor Company (manufacturing) used department-level hoshin reviewed through operational audits, while Toyota Motor Sales did not roll hoshin to the department level and reacted allergically to the word "audit." Managing Director Masao Nemoto preserved the practice while accommodating the receiving culture's language, proposing that the two companies "exchange business reports" instead of conducting an "audit." The substance of audit discipline crossed the boundary under a different name — accommodation, not dilution.
Mikio Sugiura, Toyota Global 10 (Ch. 4) — artoflean.com/reference/hoshin-kanri
Hoshin kanri exists to develop strategic and problem-solving capability, not just to hit targets
The ultimate purpose of hoshin kanri is not to hit targets but to develop an organization's strategic thinking and problem-solving capability at every level — each cycle should leave the organization better at managing itself. Hoshin creates the context and direction that enables frontline workers to solve problems that matter; when people understand how their daily improvement connects to strategic objectives, their problem-solving becomes both more motivated and more targeted.
Mark Reich, Managing on Purpose (LEI, 2025); LEI Lexicon — artoflean.com/reference/hoshin-kanri
Without hoshin an organization drifts strategically; without daily management it builds on sand
The two systems are complementary and inseparable. Without hoshin, an organization runs well day-to-day but drifts strategically, never making the breakthrough improvements needed to compete in a changing environment. Without daily management, an organization has ambitious strategic goals but lacks the operational foundation to execute them — it is building on sand. An organization that integrates hoshin, daily management, and problem solving achieves far greater results than one with only one of them.
Mark Reich, Managing on Purpose (LEI, 2025); LEI Lexicon — artoflean.com/reference/daily-management
In functional silos, leaders default to local optimization; the senior leader uses hoshin to find the best overall plan
In functional silos, leaders default to short-sighted goals, conflicting action items, and myopic metrics, each optimizing locally. The senior leader's role is to use hoshin to arrive at the best overall strategy, tactical plans, and metrics for total success — not to let each silo optimize for itself. This is why the senior leader's personal engagement is non-negotiable and cannot be delegated to a staff function.
Art Smalley, Art of Lean; Mark Reich, Managing on Purpose — artoflean.com/reference/hoshin-kanri