The process you use to develop your strategic plan is as important as the plan itself. Many organizations adopt Hoshin Kanri -- also called Hoshin Planning, Strategy Deployment, or Policy Deployment -- to integrate daily management with the strategic breakthroughs needed to propel the organization forward.

Hoshin Kanri was developed by Professor Yoji Akao in Japan in the 1950s and became a cornerstone of the Toyota Production System. The term translates roughly to "direction management" or "compass management." The idea is deceptively simple: leadership defines a small number of breakthrough objectives, then aligns every level of the organization around achieving them -- connecting long-term strategy to annual goals to daily improvement work.

Simple in concept. Hard in practice. According to research by Norton and Kaplan (The Balanced Scorecard), 90% of organizations fail to execute their strategies. A separate study found that 95% of employees are unaware of or don't understand their company's strategy. Hoshin Kanri exists to close both of those gaps.

An important element of Hoshin Kanri is catchball -- the structured two-way dialogue between leadership and employees that ensures strategic objectives are both communicated effectively and refined based on input from all levels. Leaders "throw" the strategic direction; teams "catch" it, pressure-test it against reality, and throw back feedback. The plan improves with each cycle.

Without catchball, strategy deployment becomes top-down command-and-control -- and the 90% failure rate applies. With it, employees understand how their daily work connects to breakthrough objectives, and leaders get ground-truth feedback before committing resources to the wrong priorities. For a deeper guide to the practice, see What Is Catchball in Lean?.

Here are the seven steps typically followed in the Hoshin Kanri process:

Step 1: Establish the Vision and Assess the Current State

Before setting new objectives, understand where you are. Review your organization's mission, vision, and values. Are they still aligned with where the organization needs to go? Assess current performance against existing strategic goals. Where did you hit targets? Where did you fall short, and why?

This step also means honestly evaluating organizational capability. Do you have the skills, systems, and leadership bandwidth to pursue a breakthrough objective? Most hoshin failures start here -- with objectives that ignore current-state constraints.

Step 2: Develop Breakthrough Objectives

Breakthrough objectives are the three-to-five-year goals that require genuine transformation -- not incremental improvement. Entering new markets, fundamentally redesigning a service delivery model, achieving a step-change in quality or safety performance.

Discipline matters here. Most organizations try to pursue too many breakthrough objectives simultaneously, diluting focus and resources. Three to five is the right range. If everything is a breakthrough priority, nothing is.

Step 3: Define Annual Objectives

Break each breakthrough objective into what must be accomplished this year to stay on track. If the three-year goal is to launch a new service line, this year's objective might be completing market research and defining requirements. If the five-year goal is zero preventable harm, this year's objective might be reducing falls by 30%.

Annual objectives should be measurable and owned. Each one needs a clear metric, a target, and a person or team accountable for achieving it.

Step 4: Cascade Goals Throughout the Organization

This is where hoshin kanri diverges from conventional strategic planning. Goals don't simply flow downward through the hierarchy. Through catchball, they move up and down -- leadership sets direction, teams pressure-test feasibility, and the plan adjusts based on ground-truth feedback.

Each level of the organization translates the annual objectives into tactics relevant to their scope. A hospital's annual objective to reduce discharge delays becomes the pharmacy team's objective to cut medication reconciliation turnaround time. A manufacturer's annual quality target becomes each production line's specific defect reduction goal.

The cascading process ensures two things: alignment (everyone is working toward the same breakthrough objectives) and ownership (every team knows exactly what they're responsible for and why it matters).

Step 5: Execute Annual Objectives

With goals set and cascaded, teams execute. This is where strategy meets daily management. The improvement methodologies your organization already uses -- Kaizen events, PDSA cycles, A3 thinking, DMAIC -- become the vehicles for achieving the annual objectives.

The key distinction from conventional execution: hoshin kanri connects each improvement project back to the strategic objective it supports. A Kaizen event on the discharge process isn't just "a Kaizen event" -- it's directly tied to the annual objective of reducing length of stay, which supports the breakthrough goal of becoming the region's highest-performing health system. That line of sight from daily work to strategic direction is what makes hoshin kanri different from a list of goals that sits in a binder.

Step 6: Monthly Reviews

Monthly reviews are the accountability mechanism. Without them, the strategic plan becomes a document that gets enthusiastic attention in January and gathers dust by March. The review cadence ensures that:

Progress is measured against the targets established in Step 3. If a metric is off track, the team identifies why and adjusts tactics -- not just reports the variance.

Obstacles are surfaced early. Problems that would take months to discover through quarterly reporting become visible in weeks.

Resources are reallocated based on reality, not the assumptions made during planning.

The review should be structured, not a status meeting. Use the x-matrix (see The Benefits of Using an X-Matrix for Strategy Deployment) to keep the conversation anchored to objectives, metrics, and owners.

Step 7: Annual Review

At year end, assess progress toward breakthrough objectives. What annual objectives were met? Which fell short, and what got in the way? Are the breakthrough objectives still the right ones, or have conditions changed?

The annual review feeds directly back into Step 1 -- establishing the new year's vision and current-state assessment. Hoshin kanri is a cycle, not a linear process. Each year's review sharpens the next year's plan.

Common Hoshin Kanri Mistakes

The failure modes are consistent across organizations:

Too many breakthrough objectives. If you have twelve "breakthrough priorities," you have zero. Limit breakthrough objectives to three to five. Everything else is important but not breakthrough-level.

Cascading without catchball. Pushing goals downward without the two-way feedback loop produces plans that look good on paper and fail on the floor. If frontline teams weren't involved in pressure-testing the plan, they won't own it.

No review discipline. The plan launches with energy in January and stalls by Q2 because nobody scheduled the monthly reviews. Without a cadence of measurement and course correction, hoshin kanri becomes an annual planning exercise, not a management system.

Confusing hoshin with the annual budget process. Hoshin kanri is about strategic breakthroughs, not financial forecasting. Organizations that merge the two end up with a budget dressed up in strategy language.

Failing to connect improvement work to objectives. If your Kaizen events, PDSA cycles, and A3s aren't explicitly linked to annual objectives, improvement is happening but not in service of the strategy. That's activity without alignment.

Declaring victory at the plan stage. A beautifully crafted x-matrix pinned to the conference room wall is not strategy deployment. Deployment means the plan is being executed, measured, and adjusted -- daily, by real people, on real problems.

How KaiNexus Supports Hoshin Kanri

Hoshin kanri requires infrastructure that most organizations try to build from spreadsheets, slide decks, and shared drives. It works for a quarter, then falls apart as the volume of objectives, metrics, and improvement projects overwhelms the manual tracking.

KaiNexus was designed for this. Breakthrough objectives cascade into annual goals, which cascade into improvement projects -- all connected, all trackable, all visible. The x-matrix lives in the platform, not in a static file. Monthly reviews are informed by real-time data, not reconstructed from memory. And catchball happens inside the system: feedback is documented, ownership changes are tracked, and leaders can see where the process stands at any moment.

For multi-site organizations, KaiNexus aggregates strategy deployment across every facility. Leadership sees which sites are on track, which are stalled, and what cumulative impact the strategic initiatives are producing -- without waiting for quarterly reports to arrive.

For a real example, see how Tirlan scaled strategy deployment with KaiNexus -- replacing Excel-based tracking that consumed the CI team's time with a platform that gave leadership real-time visibility across every department.

See how KaiNexus supports strategy deployment or talk to our team.

Frequently Asked Questions

What is Hoshin Kanri?

A strategic planning methodology that aligns an organization's breakthrough objectives with annual goals and daily improvement work. Developed in Japan in the 1950s by Professor Yoji Akao, it uses structured two-way communication (catchball) and visual management (the x-matrix) to connect strategy to execution at every level.

What is the difference between Hoshin Kanri and strategy deployment?

They're the same thing. "Hoshin Kanri" is the Japanese term. "Strategy deployment" and "policy deployment" are English translations. Some organizations use one term, some use another. The methodology is identical.

What is the x-matrix in Hoshin Kanri?

A visual tool that maps the relationships between breakthrough objectives, annual goals, improvement projects, metrics, and owners on a single page. It makes the entire strategic plan visible and helps leaders see whether daily improvement work is aligned with long-term objectives. For a detailed breakdown, see The Benefits of Using an X-Matrix.

How does catchball work in Hoshin Kanri?

Leaders propose strategic direction. Teams review it, test it against operational reality, and send back feedback. The plan improves with each cycle. Catchball ensures alignment isn't just top-down -- it's informed by the people who will execute the work. See What Is Catchball in Lean? for the full guide.

How many breakthrough objectives should we have?

Three to five. Breakthrough objectives represent transformative change that requires concentrated organizational focus. More than five dilutes attention and resources. Start with fewer and add as your organization's hoshin capability matures.

How long does it take to implement Hoshin Kanri?

The first planning cycle takes one to three months, depending on organizational size. But hoshin kanri is a management system, not a one-time project. Most organizations see the first cycle as a learning experience and hit their stride in year two or three as the review discipline, catchball practice, and cascading process become habitual.

What software supports Hoshin Kanri? Purpose-built improvement platforms like KaiNexus support the full hoshin lifecycle: x-matrix visualization, goal cascading, catchball tracking, monthly review dashboards, and impact measurement. Spreadsheets and slide decks are common starting points but typically break down as the number of objectives, projects, and sites grows.