Toyota Hoshin Kanri (方針管理) — How Direction Becomes Daily Work

What is hoshin kanri?

In English, the term goes by several names — policy deployment, strategy deployment, policy management — but none quite capture the Japanese. 方針 (hoshin): 方 (hō) means direction, 針 (shin) means needle, as in a compass needle — together, a sense of directional bearing or course. 管理 (kanri): 管 (kan) means to control or manage, 理 (ri) means with logical thought or reason. The compound resists clean translation, which is why most practitioners use the Japanese term directly.

Hoshin kanri operates at three time horizons: a permanent basic direction (基本方針, kihon hoshin), a mid-term plan of three to five years, and an annual cycle. Most Western implementations practice only the annual exercise and treat it as the whole system. At Toyota, the annual cycle only makes sense in the context of the longer-term direction it serves. The system also depends on catchball — two-way negotiation that creates ownership at each level — and a disciplined review rhythm where senior leadership's own feedback drives organizational learning.

At each level of the organization, hoshin items are management directions — policies in support of the objectives above, not simply targets to hit. At the group leader level on the production floor, those directions resolve into operational KPIs tracked through daily management. The alignment work happens in the middle layers through catchball and cross-functional coordination.

Mark Reich describes the larger relationship plainly: “Vision is where you want to go, hoshin kanri is how to get there, and daily management is building stability through continuous improvement. You need all three.”

This guide draws from two insider accounts. Mikio Sugiura's Global Ten (published in Japanese in 2017) is a firsthand record of Toyota's hoshin system from the responsible manager in Corporate Planning during the late 1970s. Mark Reich's Managing on Purpose (Lean Enterprise Institute, 2025) adds twenty-three years of hoshin practice at Toyota North America.

1Where Did Hoshin Kanri Come From?

Hoshin kanri did not originate at any single company. It emerged from the Total Quality Control (TQC) movement that transformed Japanese industry in the 1950s and 1960s, practiced at companies including Bridgestone, Komatsu, and Toyota. The roots are somewhat documented but certain nuances and contexts are not well explained in English-language accounts.

In post-war Japan, three external forces converged. In 1950, W. Edwards Deming came to Japan and introduced the PDCA cycle — Plan, Do, Check, Act — which became the foundational management discipline. In 1954, Joseph Juran arrived and advised Japanese companies to use quality control not only on the manufacturing floor but as a management tool. This was the catalytic shift: QC expanded from a shop-floor discipline into a company-wide management approach. Kaoru Ishikawa of the University of Tokyo and organizations like JUSE (the Union of Japanese Scientists and Engineers) spread QC circle practices across industries. The term “TQC” itself came from Armand Feigenbaum at General Electric, though Japanese companies transformed it into something distinct from Feigenbaum's original concept.

Toyota's Implementation

Toyota adopted TQC formally in June 1961, with Eiji and Shoichiro Toyoda directing senior executive Masao Nemoto to lead the effort. Hoshin kanri grew within the TQC infrastructure Nemoto built. Nippon Denso, Toyota's major supplier, won the Deming Prize that same year — an indication that these practices were developing across the Toyota Group simultaneously, not flowing top-down from one company.

In July 1962, Toyota conducted its first company-wide quality audit. Five audit groups examined management practices across the organization and identified four structural problems:

1. Managers did not understand the real purpose of Company Hoshin
2. Long-term plans were poor in quality
3. Fact-based thinking was persistently weak
4. Horizontal quality coordination lagged behind vertical

These findings led directly to the first formal Company Hoshin, committed to paper in January 1963. From the beginning, the system had three layers: Basic Hoshin (permanent foundational direction), Long-term Hoshin (five-year targets with three-to-five-year countermeasures), and Annual Hoshin. By 1967, it had expanded to six functional categories — Administration, Technology, Production, Quality, Cost, and HR/Safety.

In 1965, Toyota won the Deming Prize, which required and reinforced the discipline of systematic hoshin management. The operational audit structure continued to evolve, stabilizing by 1977 into a rhythm of four operational audits and four plant audits per year.

Global 10

One representative example of hoshin kanri at Toyota is the Global 10 case, which began with Eiji Toyoda's 1978 New Year's speech. Each year, the president delivered Company Hoshin to assembled managers on the first working days of January — roughly twenty minutes, nineteen double-spaced pages. Preparation was intensive. Corporate Planning would interview the president and draft a manuscript. Toyoda did not simply sign off. Mikio Sugiura, the responsible manager in Corporate Planning at the time, recalls: “I must admit I was quite surprised to find there were as much as 80 corrections with a red pen, including punctuation marks.”

In that 1978 speech, Toyoda declared what would become the organizing ambition for the next decade:

“Currently our share in the global production is 7%, but I sincerely wish to raise this to 10%. I call this challenge: ‘Global 10.’”

The trajectory had been building for years. When Toyoda became president in 1967, Toyota held 3.6% of global production. By 1978 it had reached 7.1%. After the TMC-TMS merger in 1982, it stood at 9.6%. By 1990, Toyota reached 10.6%. Global 10 was not a single-year target — it was a direction pursued across multiple hoshin cycles over nearly three decades.

Sugiura's firsthand account of this period was published in Japanese in 2017 under the pen name Masaji Shibaura. An English edition, Toyota Global 10, has not yet been published in English.

2What Are the Three Layers of Hoshin Kanri?

From its first formal articulation in January 1963, Toyota's hoshin system operated at three distinct time horizons.

Basic Hoshin (基本方針, kihon hoshin) is the permanent foundational direction of the company. At Toyota, the Basic Hoshin barely changed over fifty years. It expressed commitments like contributing to society through automobile manufacturing and respecting employees. In 1970, after the recall crisis and growing public scrutiny of the auto industry, Toyota added a line about being aware of the public nature of the car industry — a rare but meaningful update to what was otherwise a stable document. Basic Hoshin is not revisited annually. It provides the context within which everything else operates.

Long-term Hoshin (長期方針) sets targets over a three-to-five-year horizon with corresponding countermeasures. Global 10 is the most prominent example: a multi-year ambition requiring coordinated investment in overseas manufacturing, product development, supplier networks, and sales channels. Long-term hoshin targets are directional — they define where the company is heading and what capabilities it needs to build. They are reviewed and adjusted, but they do not reset each year. The content of long-term hoshin has shifted with each era's defining challenge — from globalization in the 1970s and 1980s, to quality and supply chain resilience after the 1995 Hanshin earthquake and 2011 Tohoku tsunami each devastated key supplier networks, to the 2016 structural reorganization into in-house companies under Akio Toyoda.

Annual Hoshin (年度方針) is the yearly execution plan. This is the layer most Western implementations recognize, and the only one many of them practice. At Toyota, the annual hoshin draws its meaning from the long-term and basic layers above it. An annual objective to expand overseas production capacity, for example, only makes sense as part of a multi-year globalization direction that itself serves a permanent commitment to growth through local contribution.

The three layers create a structural context that prevents annual planning from drifting into disconnected target-setting. When a department manager receives an annual hoshin item, the long-term and basic directions above it explain why that item matters and where it is heading. Without that context, annual targets become arbitrary numbers — which is what happens in most organizations that practice only the annual slice.

3How Does Company Hoshin Work at Toyota?

Company Hoshin are the president's hoshin. This is not a metaphor. At Toyota, the president personally owns the content, the language, and the delivery of the company's annual direction. The process that produces Company Hoshin reflects this ownership at every step.

Sugiura recalls the process in detail. Each year, Corporate Planning interviews the president to understand his priorities for the coming year — informed by the long-term direction, current business conditions, and results from the prior year's hoshin review. Corporate Planning drafts a manuscript for the New Year's speech, the formal vehicle through which Company Hoshin are delivered to the organization. The president then revises the draft — not as a formality. When Eiji Toyoda prepared his 1978 New Year's speech, Sugiura found eighty corrections in red pen, down to punctuation. The number of corrections halved each subsequent year as the process between president and staff matured, but the principle held: these are the president's words, not a staff document he signs.

The speech runs roughly twenty minutes, delivered to assembled department and section managers on the first working days of January. From there, the content cascades into workplaces. Senior leaders reinforce the same themes through multiple channels over the following weeks and months — formal events, training sessions, management meetings. The content does not land in a single broadcast. It is repeated and adapted across settings until it becomes the operating context for the organization.

The Cascade

Company Hoshin cascade from the president to department managers, and from department managers to section managers. At each level, the hoshin items are management directions in support of the level above — not mechanical breakdowns of a target into sub-targets. A department-level hoshin item like “overseas engineering support activities” is a direction requiring judgment about scope, priorities, and resource allocation within that domain. It serves the company-level objective but is not simply a fractional share of it.

The cascade stops at the section manager level. Below that, hoshin directions resolve into the operational KPIs that group leaders track through daily management — quality, cost, delivery, and safety metrics on floor management boards. Team members are led by supervisors who use hoshin as an operational guide. There is no individual-employee hoshin at Toyota. This is a structural design choice: the system aligns the organization through its management layers, not by assigning every person a personal strategic objective.

Eiji Toyoda's own working method illustrates what the top of the cascade looks like in practice. During the 1977 planning cycle, Sugiura walked into Toyoda's office and found three time-series graphs on the desk — domestic sales, overseas exports, and production volume. Realized figures were in blue pencil, forecasts in red. Toyoda was personally weighing the trade-off between restraining exports amid rising trade friction and supporting dealers with domestic volume. The top of the hoshin cascade is a person at a desk weighing cross-functional trade-offs that only the top can weigh — not a document generator.

4What Is Catchball in Hoshin Kanri?

Catchball (キャッチボール) is the two-way negotiation process through which hoshin items are aligned between levels of the organization. The metaphor is straightforward — throwing a ball back and forth — but the actual practice is more structured than most descriptions suggest.

The process begins at the top. After the president sets Company Hoshin, department managers receive the direction and develop their own hoshin items in response. This is where catchball starts: the department manager's proposed hoshin goes back up for review and discussion, not simply down for execution. What gets negotiated are the targets, the countermeasures, and the resources required. The goal is not compliance but ownership — a department manager who has negotiated the content of a hoshin item owns it differently than one who was handed a target.

This negotiation repeats between department managers and section managers. At each handoff, the receiving manager has the obligation to push back where targets are unrealistic, resources are insufficient, or the proposed countermeasures will not work. Catchball is the mechanism that prevents hoshin from becoming top-down dictation. It also surfaces information that senior leaders cannot see from their position — constraints, dependencies, and realities on the ground that should shape the plan.

Catchball operates vertically — between levels of the hierarchy — but it depends on horizontal coordination to function. A department manager cannot realistically commit to a hoshin item that requires cooperation from another department without some mechanism for cross-functional alignment. At Toyota, that mechanism is the Function Meeting system, described in the next section. Without it, catchball becomes a bilateral negotiation between a manager and a superior, disconnected from the lateral dependencies that determine whether the plan can actually be executed.

The distinction between catchball and conventional target-setting is practical, not philosophical. In a target cascade, the number flows down and accountability flows up. In catchball, the direction flows down, the feasibility assessment flows up, and the final commitment is jointly shaped. The difference shows up in execution: people execute plans they helped build with more judgment and persistence than plans they received.

5What Are Function Meetings and Why Do They Matter?

Most descriptions of hoshin kanri focus on the vertical cascade — company to department to section. What gets lost in nearly every Western account is the horizontal coordination that makes the vertical cascade work.

At Toyota, cross-functional coordination operates through Function Meetings (機能別会議, kinobetsu kaigi). These are standing management forums organized by function — Quality, Cost, Production, Technology, and Sales/HR — that cut across departmental boundaries. Each Function Meeting brings together managers from every department whose work touches that function, regardless of where they sit in the organizational hierarchy.

Function Meetings exist because most significant hoshin objectives cannot be achieved by any single department. Eiji Toyoda's 1978 Global 10 challenge — raising Toyota's global market share from 7% to 10% — required simultaneous and coordinated action from Product Development, Production Engineering, Manufacturing, and Sales. No department could deliver its piece independently. Product Development could design vehicles for overseas markets, but those vehicles needed Production Engineering to prepare manufacturing processes, Manufacturing to build them at quality and cost targets, and Sales to establish the distribution channels. The Function Meeting system provided the forum where these interdependencies were identified, negotiated, and tracked. Nemoto, who oversaw TQC deployment across Toyota, describes how the company assigned managing directors and senior managing directors to cross-divisional functions — outranking the divisional general managers — to ensure company-level optimization over divisional optimization.

Without horizontal coordination, a vertical cascade produces aligned-looking plans that fail in execution. Each department optimizes within its own hoshin targets, but the gaps between departments — where handoffs, shared resources, and conflicting priorities live — go unmanaged. This is the condition most Western hoshin implementations operate in. They cascade targets vertically through catchball but lack any standing mechanism for lateral alignment. The result is departmental KPIs that look well-deployed on paper but produce suboptimal outcomes at the system level.

The Function Meeting system also reinforced the operational audit process. When an audit surfaced a cross-functional problem — such as Eiji Toyoda's observation at the 1982 Tahara audit that distribution was being neglected while everyone focused on production — the Function Meeting structure provided an existing channel to coordinate the response. Within months of that audit, scattered distribution functions were consolidated into a new Head Department of Distribution Management, elevated to the same organizational rank as seven other head departments. The audit identified the problem. The Function Meeting system and executive authority enabled the organizational response.

The 2016 reorganization into seven in-house companies under Akio Toyoda tested whether this coordination mechanism could survive a fundamental restructuring of the organization itself — moving from functional divisions to product-line-based business units while preserving the cross-functional forums that hoshin depends on.

This horizontal layer is arguably the most important structural element that disappeared when hoshin kanri moved to the West. What remains in most implementations is a vertical cascade with catchball — which, without cross-functional coordination, amounts to a more collaborative version of management by objectives.

6How Does Toyota Review Hoshin Progress?

Hoshin kanri at Toyota is not a planning system that produces a document and waits for year-end results. It includes a structured review rhythm — operational audits — that connects planning to execution throughout the year.

By 1977, the review structure had stabilized into four operational audits and four plant audits per year. Operational audits are theme-driven, not comprehensive. Each year, Corporate Planning proposes four to six potential audit themes drawn from the Company Hoshin priorities and current business conditions. The president decides which themes advance. This selectivity is deliberate — the audits examine a few topics in depth rather than reviewing everything superficially.

The format is consistent. Each presenter prepares a double-sided A3 document and delivers a ten-minute presentation followed by five minutes of questions. A full audit session runs roughly two hours. The discipline of condensing a complex topic into one A3 and ten minutes is itself a management development exercise — it forces clarity about what matters and what the data shows. Nemoto describes preparing detailed PDCA checking calendars as a plant manager — scheduling which reviews he would conduct and when — to prevent the checks from being quietly dropped. The discipline of planning the checking, not just the doing, was a TQC principle that hoshin review inherited.

In the period Sugiura describes, what distinguished Toyota's operational audits from typical management reviews was the president's personal engagement in the feedback. After each audit, the president provided written feedback — and this was not delegated to staff. Sugiura confirms: “I've been asked more than once if the feedback draft wasn't written by Corporate Planning, but that was not the case — the comments were President Eiji Toyoda's own, which made them all the more valuable.”

The audit also served as a coaching mechanism. Toyoda would ask presenters: “What would you do as President?” or “What would you do if you were the responsible executive?” These questions pushed managers to think beyond their immediate role and consider the problem from the perspective of the whole organization.

The audits had organizational consequences. After a 1982 operational audit at the Tahara plant on distribution cost kaizen, Eiji Toyoda observed that everyone was focused on JIT and production inside the plants while the broader challenge of getting products to customers efficiently was being overlooked. He remarked: “It's like distribution is just a thing in the shade, but that is a big mistake... Making good products at the Gemba with low cost is the starting point of manufacturing, but it all depends on how efficiently distribution is handled.” Within months, distribution was consolidated into a new Head Department of Distribution Management on par with seven other head departments, and Toyoda directed every executive who had not seen Tahara to visit the plant.

The audit mechanism also proved its value in crisis. In June 1969, amid a national recall scandal triggered by consumer advocates and press investigations, Toyota mobilized the existing operational audit structure on the recall theme within weeks. Special committees were formed, company-wide quality audits conducted, and supplier audit processes created — all within the normal hoshin review infrastructure. Sugiura drew a clear lesson: “It was because normal-time Company Hoshin kanri was functioning relatively well that emergency hoshin kanri could function effectively company-wide in a really short time.”

The pattern repeated across later decades. When Toyota posted its first operating loss during the 2008 global financial crisis, faced a worldwide recall crisis that brought Akio Toyoda before the U.S. Congress in 2010, and when the 2011 Tohoku tsunami severed critical supplier networks for months, the response each time was routed through the existing hoshin and audit infrastructure — not through ad hoc crisis management.

The review rhythm closes the loop between planning and execution. Without it, hoshin kanri degrades into an annual planning exercise that produces a document, distributes targets, and hopes for results. The operational audit ensures that deviations are surfaced, root causes are examined, and the organization learns — not at year-end, but throughout the year.

7What Happens When Hoshin Kanri Breaks Down?

In 1978, despite rising market share and the momentum of the Global 10 declaration, Toyota faced an internal quality crisis. Over one hundred severe quality issues were reported. Dealers across the country complained about new cars arriving flawed and requiring inspection and servicing before delivery. On-road breakdowns were increasing. The responsibility was shared across design and manufacturing.

Managing Director Masao Nemoto diagnosed the root cause: managers had lost the basics of PDCA. The quality management process that was presumed to be functioning well had quietly degraded. Forms were being filled out, presentations were being given in the correct format, but the substance behind them had weakened. A review of the Deming Prize assessor feedback from years earlier confirmed the pattern. The assessors had noted:

• “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”

The warnings had been recorded. The degradation they predicted had arrived.

Toyota's response was not to redesign the hoshin forms or introduce a new framework. It was to re-educate the managers. Nemoto launched the Kanri Noryoku Program (管理能力プログラム, Kan-Pro) — a two-year management capability initiative from 1979 to 1980 targeting 760 department and section managers. Nemoto personally delivered the lectures and later described the program in his own account in The Birth of Lean. The program was built and run entirely in-house, with no external consultants. The content focused on the fundamentals: what PDCA actually requires, what a manager's role in hoshin execution means, how to think about problems based on facts rather than assumptions.

Critically, improving hoshin practice was itself designated a Company Hoshin item. The system's response to its own degradation was routed through the system itself — not through a parallel initiative or a special transformation program.

At the closing of Kan-Pro, Eiji Toyoda addressed the participants: “You have now reached the first base station. You have completed the stage of Shu, the fundamentals. As a next step, I would like you to acquire the leadership skills to control and manage your people in order to improve business results.”

The reference to 守破離 (Shu-Ha-Ri) — master the fundamentals, then make them your own, then transcend — placed the two-year program in context. It was a beginning, not a conclusion. The expectation was that managers would continue developing their hoshin capability through practice, not that a program had fixed the problem.

Mark Reich, drawing on his own experience managing hoshin at Toyota North America, frames the connection directly: “Hoshin kanri is a methodology for developing leadership capabilities on the job. It is not a random approach that may or may not work. It's a structured approach of planning and executing strategy that allows leaders to try new approaches and priorities, and to learn from those approaches through long and short PDCA cycles.”

The 1978 crisis and Kan-Pro response reveal a design principle embedded in the system: when hoshin practice degrades, the corrective action is people development, not process redesign. Most organizations facing a similar breakdown would commission a new planning template, hire a consulting firm, or adopt a different framework. Toyota re-educated its managers in the fundamentals they had stopped practicing.

8What Changed When Hoshin Kanri Moved to the West?

When hoshin kanri moved from Japan to Western organizations in the 1980s and 1990s, the transfer was partial. Several structural elements from Toyota's practice are absent from most Western implementations, and some tools were added that did not originate at Toyota.

The X-matrix has a different origin. The X-matrix (also called the hoshin matrix or deployment matrix) is the most widely associated visual tool in Western hoshin practice. It originated in the Quality Function Deployment (QFD) community, developed by Yoji Akao and popularized in the United States by GOAL/QPC. It is a legitimate planning tool, and organizations that find it useful for mapping relationships between objectives have reason to use it. It is not, however, Toyota practice. Mark Reich, who managed hoshin kanri at Toyota North America for 23 years, had never encountered the X-matrix at Toyota. When building the hoshin process in North America, he found that managers who arrived with X-matrix experience from other companies tended to equate filling out the form with aligning goals — when what they really had was management by objectives. The risk is not in using the X-matrix — it is in treating the form as the system.

Two of three layers are typically absent. Most Western implementations practice only the annual cycle. The permanent Basic Hoshin and the three-to-five-year Long-term Hoshin are either missing or collapsed into a vague vision statement that does not function as an operating layer of the management system. Without these layers, annual targets lack strategic context and reset each year without continuity.

Cross-functional coordination is rarely described. Toyota's Function Meetings — standing forums organized by Quality, Cost, Production, Technology, and Sales/HR — provided the horizontal alignment mechanism that made the vertical cascade work. This structure is absent from most English-language descriptions of hoshin kanri and, based on available observation, from most Western implementations. Without some mechanism for lateral coordination, hoshin produces departmental plans that may each align vertically to the company direction but conflict with each other at shared boundaries.

Management development was separated from hoshin. At Toyota, improving managers' hoshin capability was itself a hoshin objective. In most Western practice, hoshin is treated as a planning process, and leadership development is handled through separate programs. The connection between the two — that hoshin practice is the vehicle through which managers develop — was not part of what typically transferred.

Individual-employee hoshin does not exist at Toyota. Some Western implementations cascade hoshin targets to every employee, creating personal objectives linked to corporate strategy. Toyota's cascade stops at the section manager level. Below that, hoshin directions become the operational context for daily management — group leaders and team members work within hoshin-aligned KPIs, not personal strategic objectives.

The English translations all fall short. As described in the introduction, “policy deployment,” “strategy deployment,” and “policy management” each flatten the meaning of 方針管理 in different ways. This has contributed to a mechanistic understanding of what is fundamentally a management system. The widespread use of these translations — particularly “policy deployment” — may have made it easier for Western practitioners to treat hoshin kanri as a deployment process rather than the integrated management system described in this guide.

9What Are the Most Common Hoshin Kanri Failure Modes?

Organizations that adopt hoshin kanri frequently encounter the same set of problems. Most trace back to practicing the form of the system without the underlying management disciplines.

Too many priorities. Hoshin kanri is designed around a few vital objectives — the matters important enough to require cross-functional coordination and executive attention. When organizations load their hoshin with ten or fifteen priorities, the system loses its purpose. Everything becomes a hoshin item, which means nothing receives the focused attention that hoshin is meant to provide. At Toyota, Company Hoshin typically contained a small number of items, and the president personally decided which audit themes would advance each year.

Top-down dictation without catchball. When targets flow down without genuine negotiation, the result is compliance rather than ownership. Managers who receive targets they did not help shape have less context for making judgment calls during execution and less commitment to finding countermeasures when results fall short. The catchball process exists to prevent this — but it requires leaders who are willing to have their assumptions challenged and adjusted by the levels below them.

Review theater. Regular hoshin reviews that consist of status presentations without substantive discussion of deviations, root causes, and adjustments. The format looks correct — A3 documents, scheduled meetings, executive attendance — but the content is reporting, not learning. At Toyota, the president's personal engagement in audit feedback and his practice of asking “What would you do as President?” turned reviews into genuine problem-solving and development moments. Without that kind of engagement, reviews become ceremonies.

Form over system. Investing heavily in the planning artifact — whether an X-matrix, a set of A3 plans, or a software platform — while underinvesting in the management behaviors the artifact is supposed to support. The document is the least important part of hoshin kanri. The behaviors — catchball negotiation, cross-functional coordination, deviation response, coaching through review — are what make the system function.

No horizontal coordination. Deploying hoshin vertically through each department without any mechanism for lateral alignment. Each department's plan may look well-connected to the company direction, but the gaps between departments — shared resources, conflicting timelines, interdependent deliverables — go unmanaged.

Annual-only thinking. Treating hoshin as a yearly planning exercise without the long-term and basic layers that give annual targets strategic context. Annual priorities reset each January with no continuity of direction, making it difficult to pursue objectives that require sustained multi-year effort.

Reducing hoshin to measurable KPIs only. When hoshin items are limited to quantifiable operational metrics — cost, quality, delivery, production targets — the system loses its capacity for forward-looking direction. Hoshin at the management level is meant to include new initiatives, capability development, and strategic directions that may not have clean metrics at the outset. Establishing a new supplier quality process, developing documentation standards for overseas operations, or building cross-functional coordination on a new product line are hoshin-level work. Restricting hoshin to what can be measured on a dashboard turns it into an operational scorecard and removes the strategic and developmental dimensions of the system.

10How Does Hoshin Kanri Compare to OKRs, MBO, and Balanced Scorecard?

Hoshin kanri is frequently compared to other strategic management frameworks. The comparisons are useful but can obscure a fundamental difference: hoshin kanri is a management system, not a goal-setting methodology.

Management by Objectives (MBO) shares the intent of aligning individual effort with organizational goals. The difference in emphasis is in what gets managed. MBO as generally described focuses on the objective or outcome — the what. Hoshin kanri at Toyota places significant emphasis on both the objective and the methods by which it will be pursued. The countermeasures, the approach, and the process are part of what gets discussed in catchball and reviewed in operational audits. This emphasis on method is connected to management development: leaders develop by working through how to achieve a direction, not only by being held accountable for whether they achieved it. These are differences in emphasis, and every company's implementation varies.

OKRs (Objectives and Key Results) emphasize outcome-focused goals on quarterly cycles, designed for agility — shorter cycles, frequent resets, ambitious stretch targets where partial achievement is expected. Hoshin kanri operates on longer time horizons (annual within multi-year and permanent layers), expects targets to be met, and includes a formal review mechanism with root cause analysis when results fall short. The two frameworks address different problems: OKRs optimize for speed of adaptation, hoshin kanri for sustained strategic alignment.

Balanced Scorecard (BSC) organizes performance measurement across four perspectives — financial, customer, internal process, and learning/growth. Hoshin kanri and BSC can coexist — the scorecard can inform the metrics used in hoshin reviews. The distinction is that hoshin kanri is a management system with its own cascade, negotiation, review, and development mechanisms, while BSC is primarily a measurement and communication framework. Organizations use both for different purposes.

The common thread is that hoshin kanri as practiced at Toyota includes structural elements — catchball, horizontal coordination, operational audits with executive engagement, and embedded management development — that are distinctive to the system. Organizations that draw from multiple frameworks benefit from understanding what each one emphasizes.

11Summary and Key Takeaways

• Hoshin kanri (方針管理) is a management system for translating a few vital company objectives into aligned action at every level of the organization. English translations — policy deployment, strategy deployment, policy management — all fall short of the Japanese meaning. Most practitioners use the term hoshin kanri directly.
• The system operates at three time horizons: permanent Basic Hoshin, three-to-five-year Long-term Hoshin, and Annual Hoshin. Most Western implementations practice only the annual layer.
• Company Hoshin are the president's hoshin — personally owned, personally revised, personally delivered. The process starts with executive ownership, not staff planning.
• Catchball is the two-way negotiation that creates ownership at each level. The direction flows down, the feasibility assessment flows up, and the final commitment is jointly shaped.
• Horizontal coordination through Function Meetings (Quality, Cost, Production, Technology, Sales/HR) is the structural element most often missing from Western implementations. Without it, vertical alignment produces departmental plans that conflict at shared boundaries.
• Operational audits provide the review rhythm — theme-driven, four times per year during the period Sugiura describes, with coaching embedded at multiple levels of the organization.
• When hoshin practice degrades, Toyota's response is people development, not process redesign. The Kanri Noryoku Program (Kan-Pro) re-educated 760 managers over two years after the 1978 quality crisis.
• The X-matrix originated in the QFD community (Akao, GOAL/QPC), not at Toyota. It is a legitimate planning tool but not part of Toyota's hoshin practice.
• Hoshin items at the management level include forward-looking directions and capability development — not only measurable operational KPIs.
• The cascade stops at the section manager level. There is no individual-employee hoshin at Toyota. Below section manager, hoshin directions resolve into daily management.

12Frequently Asked Questions

What does hoshin kanri mean in Japanese?

方針 (hoshin) combines 方 (direction) and 針 (needle, as in a compass) — a directional bearing or course. 管理 (kanri) combines 管 (control/manage) and 理 (logic/reason). Common English translations include policy deployment, strategy deployment, and policy management, but none fully capture the original meaning. Most practitioners use the Japanese term.

Did Toyota invent hoshin kanri?

No. Hoshin kanri emerged from the Total Quality Control (TQC) movement across Japanese industry in the 1950s and 1960s, influenced by Deming, Juran, and Ishikawa. Companies including Bridgestone and Komatsu practiced hoshin kanri alongside Toyota. Toyota's contribution was integrating hoshin into a broader management system — connecting it to operational audits, Function Meetings, daily management, and management development.

Did Toyota use the X-matrix?

No. The X-matrix originated in the Quality Function Deployment (QFD) community, developed by Yoji Akao and popularized in the United States by GOAL/QPC. It is a legitimate planning tool used by some organizations, but it is not part of Toyota's hoshin practice. Mark Reich, who managed hoshin kanri at Toyota North America for 23 years, has stated he never encountered it at Toyota.

What is catchball in hoshin kanri?

Catchball is the two-way negotiation process through which hoshin items are aligned between organizational levels. After the president sets Company Hoshin, each level develops its own hoshin items in response and negotiates targets, countermeasures, and resources with the level above. The purpose is to create ownership through genuine dialogue, not compliance through assignment.

How many objectives should a hoshin plan have?

Hoshin kanri is designed around a few vital objectives — the matters important enough to require cross-functional coordination and executive attention. Loading the system with many priorities defeats its purpose. At Toyota, the president personally selected which audit themes would advance each year from a small set proposed by Corporate Planning.

Does every employee get their own hoshin?

Not at Toyota. The hoshin cascade stops at the section manager level. Below that, hoshin directions resolve into operational KPIs tracked through daily management. Team members work within hoshin-aligned targets managed by their supervisors, not individual strategic objectives.

What is the difference between hoshin kanri and OKRs?

OKRs (Objectives and Key Results) emphasize outcome-focused goals on quarterly cycles, designed for rapid adaptation. Hoshin kanri operates on longer time horizons (annual within multi-year and permanent layers), includes formal review mechanisms with root cause analysis, and emphasizes both the objective and the methods for achieving it. Hoshin kanri also includes horizontal coordination and management development dimensions that OKRs do not.

What is the relationship between hoshin kanri and PDCA?

PDCA (Plan-Do-Check-Act) is the foundational management cycle within hoshin kanri. At Toyota, the annual hoshin cycle itself is a PDCA loop — plan the year's hoshin, execute through the cascade, check through operational audits, and act on deviations. Each level of the organization runs its own PDCA cycle within the larger one. The year-end reflection (hansei) on the prior year's results feeds directly into the next cycle's planning.

13Sources and Further Reading

Primary Sources

• Mikio Sugiura, Global Ten (published in Japanese in 2017 as From Mikawa to the World, pen name Masaji Shibaura). Sugiura was the responsible manager in Toyota's Corporate Planning Department during the late 1970s. Chapters IV and V cover hoshin management and the Kanri Noryoku Program in detail.
• Masao Nemoto, management lectures and Kan-Pro training materials (1978–1982). Nemoto was Managing Director at Toyota and personally led the Kan-Pro initiative to re-educate 760 managers in hoshin fundamentals.

Insider Accounts

• Mark Reich, Managing on Purpose (Lean Enterprise Institute, 2025). Reich managed the hoshin kanri process for Toyota North America for 23 years and spent six years in Japan. The book provides a practitioner-oriented guide to hoshin implementation drawn from his Toyota experience. Foreword by Jeffrey Liker and John Shook.

Historical References

• Toyota Motor Corporation, Toyota: A History of the First 50 Years (1988) and the 75-Year History series
• Deming Prize records and assessor feedback (Union of Japanese Scientists and Engineers)
• Koichi Shimokawa, Takahiro Fujimoto, eds., The Birth of Lean (Lean Enterprise Institute, 2009). Chapter V: Masao Nemoto's firsthand account of TQC at Toyota, including the Kan-Pro management training program.

Related Pages on This Site

• Hoshin Kanri — encyclopedia entry
• Catchball — the alignment mechanism
• Hoshin Kanri Topics — structured knowledge claims
• Toyota 8-Step Problem Solving — the problem-solving engine under each hoshin gap
• Floor Management Development System (FMDS) — where hoshin meets daily management