Definition
Hoshin kanri is a strategic management method that aligns an entire organization — vertically from the CEO to the front line, and horizontally across departments — around a small number of breakthrough objectives. It achieves this through structured PDCA (Plan-Do-Check-Act) thinking applied at the strategic level, combined with a rigorous two-way dialogue process called catchball (キャッチボール) that connects leadership intent with frontline reality.
The Lean Enterprise Institute defines hoshin kanri as “a strategic framework for building sustained high performance and producing results through structured plan-do-check-act (PDCA) thinking.” More specifically, it helps organizations “define a structure and standards for establishing and executing strategic initiatives throughout the organization.”
Hoshin kanri is not a planning exercise that happens once a year and sits in a binder. It is a living management system — one that structures how an organization thinks about strategy, solves problems, develops people, and reviews progress on an ongoing basis.
Japanese Origin
The word hoshin (方針) combines two characters: 方 (hō) meaning “direction” or “way,” and 針 (shin) meaning “needle” — specifically a compass needle. Together, 方針 means “compass needle pointing the direction,” which in Japanese is used to mean “policy” or “guiding principle.” The metaphor is precise: a compass needle that shows the way to proceed.
Kanri (管理) combines 管 (kan) meaning “pipe” or “conduit,” and 理 (ri) meaning “reason” or “logic.” Together, 管理 means “management” or “control” — the systematic oversight of a process.
So hoshin kanri literally means “managing the compass needle” — ensuring that every part of the organization is oriented in the same direction. Art Smalley has noted that the term essentially means “managing with a needle-point type of focus pointing out the ways to proceed.”
History and Origins
Hoshin kanri did not emerge from a single source. It developed in Japan during the 1960s at the intersection of several influences:
CCS management courses (1949-1950) — Before any of the better-known quality experts arrived, Homer Sarasohn and Charles Protzman of the Civil Communications Section (CCS) of the American occupation had been running management seminars for Japanese executives since 1949. Their courses covered industrial management fundamentals, systems thinking, quality as a management responsibility, and the integration of customer satisfaction into product development. Early graduates included the founders of Sony and what later became Toshiba Corporation. These CCS courses were the first postwar channel through which American management thinking entered Japan, predating both Deming and Drucker’s influence.
W. Edwards Deming and statistical quality control (1950) — Deming was invited to Japan by JUSE in 1950 to teach statistical quality control. What he presented was the Shewhart Cycle — a product-focused wheel of design, manufacture, sell, and research — not the PDCA cycle as it is commonly attributed. The Japanese honored him by calling it the “Deming Wheel,” but the transformation of this product-focused cycle into the general-purpose PDCA framework was accomplished over the following decade by Japanese thinkers, most notably Shigeru Mizuno and Kaoru Ishikawa. Deming’s contribution to hoshin kanri was indirect: his insistence on statistical thinking and continuous improvement through cyclical learning influenced the culture from which hoshin emerged, but he did not provide the management framework or the PDCA terminology.
Peter Drucker and Management by Objectives (1954) — Drucker’s The Practice of Management introduced MBO — the idea that organizations should set clear objectives and manage toward them. Drucker’s books were translated into Japanese and widely read. His influence on Japanese management thinking about goal-setting and long-term planning was substantial. However, the Japanese found that MBO alone fell far short of expectations: it created a culture of negotiated targets, metric gaming, and blame when objectives were not met. Hoshin kanri was, in significant part, Japan’s answer to the shortcomings of MBO — retaining Drucker’s emphasis on objective-driven management while fundamentally transforming the process through PDCA discipline, catchball dialogue, and integration with frontline problem-solving.
Joseph Juran and management’s quality responsibility (1954) — Juran shifted the conversation from statistical methods to management’s responsibility for quality. His emphasis on planning, organizing, and controlling quality as a management function — not merely a technical one — strengthened the management interpretation of the improvement cycle and contributed directly to the thinking that would become hoshin kanri.
JUSE and the Deming Prize criteria (1958) — In 1958, influenced by Drucker’s work on the importance of long-term planning, the Japanese Union of Scientists and Engineers (JUSE) added planning and strategy to the criteria for the Deming Application Prize. This was a pivotal moment: it created a concrete incentive for Japanese companies to develop systematic approaches to strategic management integrated with their existing quality control methods. JUSE’s role in shaping hoshin kanri cannot be overstated — it was the institutional catalyst that pushed Japanese companies to formalize what would become hoshin kanri.
The transition from SQC to TQC (1961-1965) — According to Yoji Akao, the concepts of control items and hoshin kanri were born during the period when Japanese companies transitioned from Statistical Quality Control (SQC) to company-wide Total Quality Control (TQC). This transition occurred between 1961 and 1965 in companies whose quality achievements earned them the Deming Prize.
Bridgestone Tire (1964-1965) — 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 they had conducted about hoshin kanri activities at various companies — effectively the first hoshin kanri manual. This documented what had been emerging as a practice across multiple Deming Prize-winning companies.
Toyota’s adoption (1961-1965) — Toyota introduced company-wide TQC in June 1961. In July 1962, the first company-wide quality audit identified critical problems: lack of understanding of the Company Hoshin’s purpose, poor long-term plans, insufficient fact-based thinking, and weak horizontal coordination between departments.
In January 1963, the Company Hoshin was explicitly committed to paper for the first time. According to Mikio Sugiura, who was in Toyota’s Corporate Planning Department, the Company Hoshin consisted of three levels — Basic Hoshin, Long-term Hoshin, and Annual Hoshin. The Basic Hoshin contained three items:
- Develop Toyota into a world leader by gathering resources from within and outside the company.
- Further Toyota’s reputation as a quality leader through devoting ourselves to the spirit of “Good Products, Good Thinking.”
- Contribute to the development of Japan’s economy by achieving a high-volume production system and competitive prices for our products.
Even in this earliest form, the Basic Hoshin addressed world leadership, quality, and production volume and cost — it was never a quality-only framework. In October 1965, Toyota was awarded the Deming Application Prize.
By 1967, hoshin was categorized by function — General Administration, Technology, Production, Quality, Cost, HR, and Environment-Health-Safety — and the structure evolved to six components: Basic Hoshin, Annual Slogans, Long-term Targets (5 years), Long-term Countermeasures (3-5 years), Annual Targets, and Annual Countermeasures. Annual targets included specific production volume targets (“100,000 cars/month” in 1967, “2,000,000 cars/year” in 1970), cost reduction targets by model, R&D capacity targets, and market share objectives alongside quality goals.
Komatsu and other refinements — Komatsu, which received the Deming Prize in 1964, also made significant contributions to refining hoshin kanri methodology. The versions developed at Bridgestone, Toyota, and Komatsu informed each other and the broader practice.
“Global 10” and the 1978 New Year’s Speech — In his January 1978 New Year’s speech to all managers, President Eiji Toyoda articulated what would become one of Toyota’s most ambitious hoshin objectives. After reviewing six key countermeasures spanning cooperation, technology, product development lead time, quality, and global markets, he said: “Currently our share in the global production is 7%, but I sincerely wish to raise this to 10%. I call this challenge: ‘Global 10.’” This single hoshin objective — achieving 10% of projected worldwide production of 45 million cars — drove coordinated initiatives across every function: sales expansion, production capacity, product development, cost reduction, and overseas manufacturing. Global 10 is the clearest illustration that hoshin at Toyota was always about total business direction, not quality alone.
The Kan-Pro Program and Sugiura (1979) — In the late 1970s, Toyota’s rapid growth raised concerns about declining TQC enthusiasm and inadequate development of younger managers. After the annual senior management reshuffle of September 1978, Managing Director Masao Nemoto took responsibility for overseeing the Corporate Planning Department and assigned Mikio Sugiura to help address the problem. They created the Kan-Pro program (管理能力プログラム, Kanri Nōryoku Program — Management Capability Program), adopted at the year-end board meeting and designed as a two-year initiative that trained roughly 1,000 department and section managers. Kan-Pro appeared in the Company Hoshin itself as Long-term Countermeasure #7: “The improvement of executive and operational management skills.” By the time Kan-Pro concluded, Toyota’s corporate-wide hoshin kanri process of annual planning, management, and review was firmly established. The program also made the A3 process standard across the company — as Sugiura wrote, “Everybody became familiar with using the A3 process when documented communication was needed.”
Operational audits as the “Check” of hoshin — A critical element of Toyota’s hoshin system was the operational audit (業務監査), conducted approximately four times per year by senior executives. Audit themes were proposed by the Corporate Planning Department and decided by the President. Department managers presented on A3 paper (10 minutes presentation, 5-8 minutes Q&A). The President provided written feedback after each audit. As Sugiura noted: “As the Company Hoshin is the President’s Hoshin, so the operational audits are the President’s audits.” These audits provided the rigorous “Check” step that distinguishes hoshin kanri from ordinary strategic planning.
Sugiura documented this entire history in Global Ten (グローバルテン, published September 2017), an insider account of Toyota’s hoshin management system based on his decades in the Corporate Planning Department.
Yoji Akao’s codification (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.
How Toyota Uses Hoshin Kanri
Toyota’s practice of hoshin kanri is deeply integrated with the rest of its management system. Based on the writings of Mark Reich — who spent 23 years at Toyota starting in 1988, including six years in Japan, and who managed Toyota’s North American hoshin kanri process — the practice operates as follows:
Scope: the entire business, not just quality. A common misconception — reinforced by hoshin kanri’s origins in the TQC movement — is that hoshin is a quality management tool. At Toyota, hoshin has been organized across seven functional categories since 1967: General Administration (Planning, Purchasing, Sales, Information, Public Affairs), Technology, Production, Quality, Cost, HR, and Environment-Health-Safety. The Company Hoshin routinely included production volume targets by model, cost reduction targets, market share objectives, R&D capacity goals, and overseas production plans — alongside quality goals. The “Global 10” aspiration is the clearest example: a hoshin objective targeting 10% global market share that drove coordinated initiatives across every function. Quality is one important dimension, but hoshin kanri is fundamentally about managing the whole enterprise toward its most critical objectives.
Annual planning cycle — Senior management establishes strategic and tactical goals based on the company’s long-term vision and current business challenges. These are structured as three levels: basic hoshin (long-term direction), long-term hoshin (3-5 year objectives), and annual hoshin (this year’s priorities). Goals emerge from deep analysis of the gap between where the company is and where it needs to be.
Catchball (キャッチボール) — This is the defining characteristic that distinguishes hoshin kanri from Western MBO. The term comes from the children’s game of tossing a ball back and forth. In practice, it means that objectives do not simply flow downward. Top executives draft initial goals and “toss” them to the next level. Those managers examine what it would take to achieve the goals, identify obstacles and resource needs, and “toss back” their analysis. Goals are refined through this dialogue. The middle managers then engage their teams in the same way. The process continues until there is genuine alignment — not just compliance — at every level.
As Art Smalley has described it, the process at Toyota “is a mixture of top down methods and goal setting with heavy interaction and input from affected parties. There is a lot of behind the scenes dialogue going on with this process.”
Cascading with context — At each level, the objectives are translated into specific actions appropriate to that level’s scope. A plant-level objective becomes department objectives, which become team objectives. Each level understands not just what they must achieve but why it matters and how it connects to the broader strategy.
Rigorous PDCA review — Once goals and action plans are set, they are reviewed with discipline: quarterly, monthly, weekly, and sometimes daily depending on the topic and level. This is not a once-a-year plan that gathers dust. The review cadence is what keeps the system alive — it surfaces problems early and forces countermeasures.
Horizontal alignment — Hoshin kanri does not only align vertically (top to bottom). It also creates horizontal alignment across departments and functions, ensuring that supporting groups are coordinated toward the same objectives. This is achieved through cross-functional A3s and shared targets.
Mark Reich and Managing on Purpose
Mark Reich, a Senior Lean Coach at the Lean Enterprise Institute who spent 23 years at Toyota starting in 1988 (including six years in Japan), is the foremost English-language author and teacher on hoshin kanri. His book Managing on Purpose (LEI, 2025) provides detailed, practical guidance on how to conduct the hoshin process — strategy development, catchball dialogues, integration with daily management and A3 problem-solving, and the leadership behaviors required to make the system work.
Reich’s key insights:
Three interacting systems. Hoshin kanri works in concert with daily management (nichijo kanri) and problem-solving (primarily through A3 thinking). Hoshin defines the breakthrough direction, daily management maintains standards and sustains gains, and problem-solving closes the gaps. An organization that integrates all three achieves far greater results than one with only hoshin or only daily management.
Enabling frontline problem-solving. Rather than being a top-management-only activity, hoshin creates the context and direction that enables frontline workers to solve problems that matter. When workers understand how their daily improvement work connects to strategic objectives, their problem-solving becomes both more motivated and more targeted.
Building vertical and horizontal alignment. From his Toyota experience, Reich learned that hoshin kanri builds alignment in both directions — connecting top management to the front line vertically, and coordinating across departments horizontally — thereby engaging everyone in achieving business objectives.
Hoshin Kanri and Daily Management (Nichijo Kanri)
One of the most important distinctions in Japanese management — and one of the most commonly missed by Western practitioners — is the relationship between hoshin kanri (方針管理) and nichijo kanri (日常管理, daily management).
Hoshin kanri addresses breakthrough objectives — the 2-4 vital strategic priorities where the organization must close a significant gap or make a fundamental change. These are the things that require focused, cross-functional effort beyond normal operations.
Nichijo kanri addresses maintaining and incrementally improving standards — the daily discipline of running the business, maintaining quality, meeting delivery commitments, and solving routine problems. This is the ongoing management of the fundamentals.
The two are complementary and inseparable:
- Without hoshin, an organization runs well day-to-day but drifts strategically — it never makes 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.
- The hoshin process depends on stable daily management as a foundation. You cannot deploy breakthrough objectives to teams that cannot maintain basic standards.
- Gains achieved through hoshin initiatives must be handed off to daily management to sustain them. Otherwise, improvements regress.
Connection to A3 Thinking
The A3 format is the natural companion to hoshin kanri. The Lean Enterprise Institute describes the relationship this way: hoshin kanri provides the skeleton — the organizational structure and strategic alignment — while A3 problem-solving provides the muscle — the movement and action.
In practice:
- Hoshin objectives are often captured on A3s — a hoshin A3 documents the gap, root cause analysis, target condition, countermeasures, and review plan for a strategic initiative.
- A3 problem-solving executes hoshin objectives — as gaps are discovered during hoshin reviews, A3s are opened to address them. The A3 process brings PDCA discipline to the execution of strategic priorities.
- Hoshin reviews surface the problems; A3s solve them. The two processes form a continuous loop.
This connection is not accidental. Both hoshin kanri and A3 thinking are expressions of PDCA at different scales — hoshin at the organizational/annual scale, A3 at the project/problem scale.
Implementation Guidance
Start with genuine strategic thinking. Hoshin kanri is not about deploying this year’s budget targets. It begins with an honest assessment of the critical few challenges the organization must address. If you have more than 3-4 hoshin objectives, you have too many — you are trying to do everything instead of focusing.
Invest heavily in catchball. This is where most implementations fail. Real catchball requires that leaders genuinely listen to feedback from lower levels and modify objectives based on frontline reality. If leaders “catch” the ball and throw it back unchanged, it is not catchball — it is command and control with extra steps.
Build daily management first or in parallel. Do not attempt hoshin deployment into an organization that lacks basic daily management discipline — standardized work, visual management, regular problem-solving at the team level. The hoshin objectives will have no foundation to land on.
Use A3s as the working format. Capture hoshin plans, team objectives, and problem-solving on A3s. This enforces PDCA discipline, creates a visual artifact for review, and develops thinking capability in every person who writes one.
Establish a review cadence and keep it sacred. Monthly and quarterly reviews of hoshin progress are non-negotiable. These reviews are where the system generates learning. When targets are missed, the question is not “who failed?” but “what did we learn and what will we do differently?”
Develop people through the process. The ultimate purpose of hoshin kanri is not to hit targets — it is to develop an organization’s strategic thinking and problem-solving capability at every level. Each cycle should leave the organization better at managing itself.
Common Mistakes
Treating it as top-down goal deployment. This is the single most common Western failure. Companies take senior management’s targets and cascade them downward without genuine catchball. The result is Management by Objectives with Japanese terminology — precisely what Toyota moved away from. As the LEI Lean Lexicon notes, “one common misconception is that hoshin kanri is a top-down ‘deployment’ process akin to Management By Objectives. In reality, hoshin kanri, when practiced consistent with the philosophy of Total Quality Management, is a process that is equally top-down and bottom-up.”
Too many objectives. If everything is a hoshin priority, nothing is. The entire point of hoshin is to focus the organization on a vital few breakthroughs. Companies that deploy 10-15 “hoshin objectives” have created an elaborate goal-setting bureaucracy, not a management system.
Separating hoshin from daily management. Organizations that treat hoshin as a strategy exercise disconnected from daily operations find that nothing changes on the ground. Hoshin and nichijo kanri must be integrated — the same leaders, the same review structure, the same PDCA discipline.
Skipping the Check and Act. 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. The learning happens in the Check — when actual results are compared to targets, root causes are analyzed, and countermeasures are developed.
Confusing hoshin kanri with strategic planning. Western strategic planning typically produces a document. Hoshin kanri produces a living management system. The plan matters less than the process of alignment, dialogue, review, and learning that hoshin creates. Companies that focus on perfecting the hoshin document while neglecting the management behaviors are missing the point entirely.
Failing to invest in problem-solving capability. Hoshin kanri depends on problem-solving. When gaps between targets and results emerge (and they will), the organization must be able to conduct rigorous root cause analysis and develop effective countermeasures. Without A3-level problem-solving skill distributed across the organization, hoshin reviews become status update meetings instead of learning events.