Hoshin Kanri: X-Matrix, Catchball & MES Data Layer

What is Hoshin Kanri?

Hoshin Kanri (方針管理) is the Japanese strategy deployment method that translates a company's 3–5 year vision into annual breakthrough objectives, then cascades those objectives down to every level of the organisation — until the machine operator on the night shift can explain how their daily targets connect to the CEO's strategy. The literal translation is "compass management" (hoshin = compass/direction, kanri = management/control). Toyota, Danaher and most world-class manufacturers use it. Most mid-market manufacturers do not — and the gap shows up as a disconnect between what the boardroom decides and what the shop floor delivers.

How does Hoshin Kanri work? The 7-step process

The secret of Hoshin Kanri is not in the steps — it is in Step 4: catchball. Objectives are not pushed down; they are negotiated up and down. The production manager receives a target, proposes how to achieve it, and pushes back if the target is unrealistic. The COO adjusts. This negotiation process ensures that targets are ambitious but achievable — and that the people who must deliver them believe the targets are theirs.

What is the X-matrix and how does it connect strategy to execution?

The X-matrix is the single-page visual that makes Hoshin Kanri tangible. It fits on one A3 sheet and maps four dimensions in a cross-shaped layout:

• South: 3–5 year breakthrough objectives (long-term strategy)
• West: Annual objectives (this year's targets derived from the strategy)
• North: Top-level improvement priorities / projects (the initiatives that will deliver the annual objectives)
• East: KPIs / targets to measure progress (the metrics that show whether it is working)

The intersections (the dots in the matrix) show which objective connects to which project connects to which KPI. If a project has no connection to a strategic objective — why are you doing it? If a strategic objective has no project assigned — how will it be achieved?

In a manufacturing context, the X-matrix typically looks like this:

Every X-matrix quadrant depends on reliable data. And that is exactly where most Hoshin implementations break down in mid-market manufacturing: the strategy exists on paper, but the shop floor KPIs are collected manually, updated weekly and debated in monthly meetings. By the time someone notices that OEE is not trending toward 68 %, the quarter is over.

How does Hoshin Kanri compare to MBO, OKR and Balanced Scorecard?

The critical difference: Hoshin Kanri is the only method that explicitly includes catchball (bidirectional negotiation) and connects strategy directly to daily management on the shop floor. MBO sets goals and checks them once a year. OKR sets goals and checks them quarterly. Hoshin sets goals, negotiates them with the people who must deliver, tracks them monthly (or even daily via shopfloor management) and reflects annually.

Why does Hoshin Kanri fail without real-time data?

Hoshin Kanri has two failure modes. The first is strategic: the wrong objectives are chosen. The second — and far more common in mid-market manufacturing — is operational: the right objectives are chosen, but progress is not tracked in time to correct course.

The monthly bowler chart review (Step 6) is where Hoshin lives or dies. If the bowler chart is filled with manually collected data that is 2 weeks old, the review becomes a retrospective — not a management intervention. The plant manager learns in March that the February OEE target was missed. The root cause is cold. The countermeasure is delayed.

An MES closes this gap:

• Breakthrough objectives are data-grounded from the start. When the COO defines "OEE from 62 % to 75 %," the 62 % comes from automated MES measurement — not from an Excel estimate that nobody trusts. The target is credible because the baseline is credible.
• Catchball is evidence-based. When the press shop team pushes back on a 30 % changeover reduction target, they can show actual changeover time distributions from the MES: "Our average is 38 minutes, but 40 % of changeovers are under 25 minutes. The variance is driven by die complexity, not operator skill. We can commit to 25 % reduction by standardising the top 5 die families." That is a different conversation than "we think 30 % is too aggressive."
• Monthly reviews become weekly — or daily. The MES dashboard shows OEE, changeover time, FPY and scrap in real time. At Meleghy Automotive (6 plants, bidirectional SAP integration), the COO can see whether the annual Hoshin targets are on track across all plants — not once a month from a PowerPoint, but every day from a live dashboard.
• Annual reflection is honest. At year-end, the MES provides the complete data trail: what actually happened, when, on which machines, during which orders. Neoperl's approach — PLC alarm correlation with quality defect tracking — meant that the annual reflection could pinpoint exactly which improvement projects delivered results and which stalled.

SYMESTIC's production metrics module provides exactly the KPI layer that Hoshin Kanri requires: OEE, downtime, changeover time, scrap rate — automatically calculated, historically traceable and available across multiple plants in a single dashboard.

FAQ

How many breakthrough objectives should a Hoshin plan contain?
Three to five. Maximum. Hoshin is about focus, not comprehensiveness. Toyota typically runs 2–3 Hoshin objectives per year. If you have 10 objectives, you have a wish list, not a strategy. The rule of thumb: if every department is working on more than 2 breakthrough projects simultaneously, the organisation is overloaded and none of them will finish.

Can a small manufacturer (50–250 employees) use Hoshin Kanri?
Yes — and it is often easier because the management layers are fewer. In a small plant, the COO can do catchball directly with the shift leaders. There is no middle-management translation layer. The X-matrix fits on one page and everyone in the management team sees it daily. The critical success factor is not company size; it is data quality. Without reliable OEE and downtime data, Hoshin degenerates into target-setting without feedback.

What is the relationship between Hoshin Kanri and Kaizen?
Hoshin Kanri sets the direction. Kaizen (continuous improvement) is the execution engine. Hoshin defines the breakthrough objectives — "reduce changeover time by 25 %." Kaizen events, PDCA cycles and DMAIC projects are the methods used to achieve them. Without Hoshin, Kaizen is directionless — teams improve random things. Without Kaizen, Hoshin is a strategy document that stays on the wall. Together, they form the management system that Toyota calls "True North."

How does Hoshin Kanri connect to shopfloor management?
Shopfloor management is the daily rhythm of Hoshin execution. The morning meeting at the shopfloor board reviews yesterday's KPIs (which come from the MES), identifies deviations and assigns countermeasures. Those KPIs are the same ones that appear on the Hoshin bowler chart. Shopfloor management is the daily heartbeat; the monthly Hoshin review is the strategic pulse check. Both need the same data source — and that source is the MES.

Related: Kaizen · Lean Production · Gemba · Shopfloor Management · OEE Explained · DMAIC · MES: Definition & Functions · SYMESTIC Production Metrics

About the author

Christian Fieg

Head of Sales at SYMESTIC. Six Sigma Black Belt. Led Hoshin-driven improvement programmes across 30+ plants at Johnson Controls (900+ machines, global MES rollout). Author of OEE: Eine Zahl, viele Lügen. · LinkedIn