Hoshin Kanri Strategy Deployment

Hoshin kanri translates roughly as “compass management” or “policy deployment.” Neither translation captures it. Here is what it actually does:

It takes a small number of breakthrough objectives — three to five things that must change over the next three to five years — and deploys them through an organization so that every level knows what it is working on, why it matters, and how progress is measured. Not through memos. Through a structured negotiation process (catchball) that creates genuine commitment.

What it is not

• It is not strategic planning. Strategic planning produces goals. Hoshin kanri deploys them. Most companies plan well and deploy poorly. This is the deployment system.
• It is not MBO (Management by Objectives). MBO cascades objectives downward without negotiation. Hoshin kanri negotiates upward and downward through catchball. The difference is commitment vs. compliance.
• It is not a balanced scorecard. A balanced scorecard measures. Hoshin kanri connects measurement to projects to objectives and tracks dollar savings monthly. Measurement without action is decoration.
• It is not annual. The planning cycle is annual. The tracking is monthly. The alignment check is daily (via MDI). If you only look at your X-matrix once a year, you do not have hoshin kanri — you have a poster.

The operating logic

A manufacturing plant has hundreds of things it could improve. Hoshin kanri forces you to pick the three to five that matter most, assign projects to each, measure results monthly, and resolve conflicts between them explicitly. Everything else is daily management (MDI). The discipline is saying no to everything except the breakthroughs — and then executing those breakthroughs with resources, timelines, and accountability.

The X-matrix is the single-page artifact that makes hoshin kanri visible. Four quadrants. Correlation dots at the intersections. One page forces discipline — if it does not fit on one page, you have too many objectives.

How to read the correlations

At each intersection between quadrants, you mark the strength of the relationship:

• Strong correlation — this project directly drives this objective, or this KPI directly measures this project’s output
• Moderate correlation — indirect relationship, supporting but not primary
• No dot — no meaningful connection

The correlations reveal problems. A project with no dots connecting it to any annual objective is an orphan — why are you doing it? An annual objective with no projects supporting it is aspirational — how will you achieve it? A KPI with no project connection is measuring something nobody is actively improving.

Four quadrants, four questions

• South: Where are we going? (3-5 year breakthroughs)
• West: What must we achieve this year to get there?
• North: What projects will drive those annual targets?
• East: How will we know we are succeeding?

Every project must connect to at least one annual objective. Every annual objective must connect to at least one strategic objective. Every KPI must connect to at least one project. If a quadrant has orphans, the X-matrix is telling you something is disconnected.

Most descriptions of catchball make it sound like “getting everyone’s input.” It is not. Catchball is a structured negotiation between levels of the organization where each level commits to what it can realistically deliver given the resources available.

What makes catchball work

The ball goes back and forth, not just down. Leadership says: “We need OEE above 85% by year-end.” Area managers respond: “We can get to 80% with current staffing. 85% requires a SMED project on Press 4 and backfill for the changeover team during the kaizen.” Frontline leads respond: “SMED is achievable in Q2 if we get the shadow boards fabricated by March. Press 4 operators need two days of training.”

Now leadership has a choice: fund the resources and hold people to 85%, or accept 80% without the investment. The commitment is bilateral. If leadership agrees to fund the SMED project and provide backfill, then 85% is a real commitment. If leadership does not fund it, 85% is a fantasy target that will produce resentment instead of results.

Common catchball failures

• Top-down only: Leadership sets targets and “deploys” them without negotiation. This is MBO, not hoshin. People comply but do not commit.
• Consensus-seeking: Trying to get everyone to agree. Catchball is not democratic. Leadership still decides. But they decide with information about what is actually achievable.
• Skipping levels: Plant manager talks to team leads directly, bypassing area managers. Each level has a different view of constraints. Skip a level and you miss critical resource information.
• No resource conversation: Agreeing on targets without discussing what resources are needed to achieve them. Every target requires a “with what?” conversation.

Catchball produces newspapers

The output of catchball is not a memo. It is a set of commitments: I will do X by Y date, given Z resources. These commitments become newspaper items — bilateral contracts tracked through the MDI system. If the resources do not arrive, the commitment is void. If the resources arrive and the work is not done, that is a different conversation.

Hoshin planning is annual but the execution is continuous. The planning cycle has a rhythm that repeats each fiscal year. If you do not follow the rhythm, hoshin degrades into a planning exercise that nobody references after January.

Project classification matters

Not every project on the X-matrix is the same. Classify them correctly because your savings rollup depends on it:

• Budgeted new: Planned in the annual cycle. Targets set during catchball. These are your primary hoshin projects.
• Carryover: Continued from the prior fiscal year. Savings may be partially realized. Baseline and actuals carry forward.
• Contingency: Identified but not yet funded. If a budgeted project finishes early, contingency projects absorb the freed resources.
• Unplanned/reactive: Emerged during the year in response to events (equipment failure, customer issue, regulatory change). Track them on the X-matrix so they do not consume resources invisibly.

Hoshin kanri without monthly dollar tracking is a wish list. Every project on the X-matrix must have a savings calculation method, a baseline, and monthly actuals. The monthly review is where hoshin becomes real — you see whether the projects are delivering the dollars that justify their existence.

Savings calculation methods

Different types of improvement produce different types of savings. Using the wrong calculation method produces numbers nobody trusts. Match the method to the improvement:

• Waste percentage: (Baseline% − Actual%) × Volume × Cost/Unit. For scrap reduction, yield improvement, first-pass quality.
• Time reduction: (Baseline seconds − Actual seconds) / 3600 × Volume × Labor rate. For changeover reduction, cycle time improvement.
• Headcount reduction: (Baseline HC − Actual HC) × Cost per employee. For automation, cell redesign, workflow elimination.
• Claims/quality returns: (Baseline% − Actual%) × Sales dollars. For customer quality improvement.
• Energy reduction: (Baseline usage − Actual usage) × Cost per unit. For utility optimization, compressed air leak repair.
• Direct cost: Baseline cost − Actual cost. For material substitution, supplier negotiation, freight consolidation.
• Layout/width optimization: Width reduction × Volume × Cost per unit. For printing, packaging, material utilization.
• Custom formula: User-defined with variable substitution. For anything that does not fit the standard methods.

Example: Monthly tracking table

Dollar rollup

Savings roll up through the X-matrix: projects → annual objectives → strategic objectives. The rollup is not simple addition — different metric types aggregate differently:

• Dollar savings (sum): Add across all linked projects. Waste reduction + time reduction + headcount = total dollar impact on the annual objective.
• Rate metrics (volume-weighted average): OEE, scrap rate, first-pass yield. You cannot add percentages across projects. The formula is Σ(actual × volume) / Σ(volume).
• Point-in-time metrics (latest): Cpk, Ppk, gage R&R. Use the most recent value, not an average.

Value stream mapping is the diagnostic that feeds hoshin. A current-state VSM reveals where the constraints are. The future-state map identifies what must change. The kaizen bursts on the future-state map are the candidate hoshin projects.

The pipeline: VSM → Hoshin

1. Map the current state. Cycle times, changeover times, uptime, WIP, operator count, data boxes on every process step. This is not a value stream “walk” — it is data collection.
2. Identify constraints. Where does flow break? Where is the bottleneck? Where is the highest WIP? Where is the longest changeover?
3. Design the future state. Place kaizen bursts on the future-state map where improvement is needed. Each burst is a candidate project with a specific target (reduce changeover from 28 min to 12 min, improve OEE from 62% to 85%).
4. Promote to hoshin. The kaizen bursts that align to strategic objectives become hoshin projects. They get a calculation method, a savings target, an owner, and a timeline. The burst that does not align to strategy stays in MDI as a local improvement.
5. Track realized savings. As the hoshin project executes and generates monthly savings, those savings write back to the kaizen burst on the VSM. The VSM becomes a closed-loop diagnostic — not a wall poster that never gets updated.

Estimation before commitment

Before committing resources to a hoshin project sourced from VSM, you need a savings estimate. But point estimates are dangerous — they create false precision. A “$120,000 savings target” sounds authoritative but hides uncertainty in volume, cost, and improvement realization.

Monte Carlo simulation addresses this. Run 1,000 simulations with three uncertainty sources:

• Volume volatility (±15% std) — customer demand is not constant
• Cost variation (±10% std) — material and labor costs fluctuate
• Improvement realization risk (Beta(4,2), mean ~67%) — not every kaizen delivers 100% of the target

The output is a confidence interval: median savings, probability of positive return, 5th and 95th percentile bounds. A project with $120K deterministic savings but 30% probability of positive return is a different decision than one with $80K deterministic savings and 92% probability of positive return.

Hoshin and MDI are two halves of the same system. Hoshin is the strategy. MDI is the daily execution mechanism. Separate them and both fail: hoshin becomes a planning exercise nobody references, MDI becomes activity without direction.

The connection points

• Newspapers feed hoshin. Daily MDI newspaper items that exceed local authority — that require cross-functional resources, budget, or management decision — escalate to hoshin projects. A newspaper item that says “need $15K for shadow boards and tooling for SMED” is too big for the area manager’s authority. It becomes a hoshin project with a kaizen charter, owner, and savings target.
• KPIs flow from tier meetings. The metrics on the X-matrix east quadrant (OEE, scrap rate, changeover time) are the same metrics discussed in daily tier meetings. Actuals from Tier 1 and Tier 2 boards flow up to the hoshin KPI dashboard. The X-matrix does not have its own separate data source — it reads from the same production data that MDI tracks daily.
• Leadership standard work verifies alignment. The plant manager’s LSW includes a weekly check: are the hoshin projects progressing? Are the MDI boards showing the right KPIs? Is the gap between strategic intent and gemba reality narrowing? LSW is the mechanism that prevents hoshin from floating above the operation.
• Action items cross both systems. A hoshin project generates action items with owners, due dates, and dependency chains. Those action items appear in the relevant team’s MDI newspaper. The action item lives in one place but is visible in both systems.

Why most hoshin implementations fail

They fail because hoshin operates at the strategic level and MDI operates at the tactical level, and nobody builds the bridge between them. The bridge is:

1. Hoshin projects generate action items that appear in MDI newspapers
2. MDI newspapers that exceed local authority escalate to hoshin
3. KPIs are shared — one data source, two views
4. LSW includes hoshin verification as a structured daily/weekly task

Without this bridge, you get two separate systems: a binder with an X-matrix that gets reviewed quarterly and a set of MDI boards that track daily activity without strategic direction. Both look correct. Neither produces breakthrough results.

Hoshin kanri fails in predictable ways. Recognizing the pattern early lets you intervene before the system collapses into theater.

How to diagnose a failing hoshin system

• Ask a frontline team lead: “What are the plant’s hoshin objectives this year?” If they cannot name them, hoshin is not deployed — it is filed.
• Check the X-matrix for orphan projects and unsupported objectives. If more than 20% of entries are disconnected, catchball failed.
• Look at monthly actuals. If three or more months are blank, nobody is tracking. The X-matrix is decoration.
• Check whether MDI newspapers reference hoshin projects. If they do not, the two systems are not connected.