Hoshin KanriJapanese: 方針管理 — "compass / policy management"

Hoshin kanri (方針管理) translates literally as "direction / compass-needle management" — hoshin meaning "shining metal pointing direction" (i.e. compass needle) and kanri meaning "management / control". The English-language convention is "strategy deployment" or "policy deployment"; both are accurate. The originator was Bridgestone Tire in the mid-1960s, building on TQC ideas from Deming and Juran; Toyota systematised it; Hewlett-Packard adopted it in 1986 and was the first major Western company to run it end-to-end; Yoji Akao's 1988 (English 1991) edited volume Hoshin Kanri: Policy Deployment for Successful TQM made it accessible globally.

The premise is operational, not philosophical: most strategy fails not because the strategy is wrong but because it never reaches the people who would execute it, in a form they can act on. Hoshin kanri is the operating system that fixes that. It is the bridge between the executive offsite ("we will be the lowest-cost producer by 2029") and the operator at the line ("my team's job this quarter is to reduce changeover time on Line 3 from 42 to 25 minutes"). Without the bridge, the strategy is shelfware; with the bridge, the strategy becomes daily work.

Hoshin kanri is structured as nested time horizons, each decomposed into the next. The canonical four-level cascade:

The discipline is the constraint at each level. The 3-5 breakthrough rule at the True-North level forces real choice — you cannot have 12 strategic priorities, because if everything is strategic nothing is. The annual hoshin reduces further: this year, we will deliver these 3-5 breakthroughs, and we will say no to everything else (or schedule it for a future year). The department level then translates strategic intent into operational metrics owners can move; the team level translates operational intent into experiments operators can run.

The X-matrix is the visual artefact that puts a level of hoshin onto a single sheet of paper (or single screen). Pat Lancaster of Lantech and later Thomas Jackson codified the modern 4-quadrant form. The four arms of the X represent four interlocking lists:

1. South — 3-5 year breakthrough strategies ("what are we trying to become?")
2. West — annual objectives / this year's breakthroughs ("what must we deliver this year to move toward becoming that?")
3. North — annual tactics / improvement priorities ("what are the specific work-streams that deliver this year's breakthroughs?")
4. East — KPIs + improvement targets ("how do we know it worked?")

The connecting cells of the matrix show which 3-5 year strategy each annual objective serves, which annual objective each tactic supports, and which KPI measures each tactic. A right-hand column lists named owners — every tactic has exactly one accountable owner. The result is a single sheet that can be read in 5 minutes and that links daily work to long-term direction with no ambiguous mapping. The X-matrix is posted at every visual-management board in the plant; the area-level X-matrix nests inside the site X-matrix which nests inside the company X-matrix.

Catchball (or nemawashi-by-iteration, after Liker's Principle 13) is the process that turns a draft hoshin into a real commitment. It is the antidote to the typical strategy cascade — leadership decides, mid-management is told, frontline is informed — which reliably produces compliance without ownership. Catchball is iterative negotiation between levels until each level genuinely owns its commitments and each level above genuinely trusts the commitment will be met.

The mechanics: leadership drafts the annual hoshin. Each department director receives the relevant slice and is asked: is this achievable? What support do you need? What constraints will prevent it? What would you propose instead if anything? The director catches the ball, examines it, throws it back with edits, counter-proposals, and resource requests. Leadership catches the ball, adjusts, throws it back. The ball gets thrown 2-4 times — typically over 2-4 weeks — until both sides agree. Then the director runs the same process with their managers, who run it with their team leaders. The cascade is iterative; the destination is genuine commitment.

1. Round 1 — Leadership drafts; departments respond with feasibility, constraints, proposed adjustments. Often the most painful round; departments push back on aggressive targets, leadership pushes back on conservative ones.
2. Round 2 — Adjusted draft; departments commit to negotiated targets + identify resource needs. Leadership commits to providing or arbitrating resource conflicts.
3. Round 3 — Departments cascade to managers + team leaders; teams propose kaizen experiments + improvement projects. Bottom-up reality check against top-down intent.
4. Round 4 — Final hoshin; X-matrices published at every level; visual boards updated; monthly review cadence scheduled.

Hoshin kanri is PDCA at strategy scale. The annual cycle:

1. October-November (PLAN) — Leadership reviews True North, evaluates progress on multi-year breakthroughs, identifies next-year focus. Drafts annual hoshin: 3-5 breakthroughs + tactics + KPIs + draft owner assignments.
2. November-December (PLAN — catchball) — Multi-round catchball with departments, managers, team leaders. X-matrices finalised at every level. Visual boards updated. Monthly review cadence scheduled.
3. January-November (DO) — Departments + teams execute. Team-level kaizen experiments run weekly/monthly using PDCA. Department-level tactics tracked monthly. Resource conflicts arbitrated by leadership.
4. Monthly (CHECK) — Each level reviews its X-matrix monthly. Status colour-coded green/yellow/red against the year-to-date plan. Yellow + red items trigger root-cause analysis + course-correction, not blame. The point of the monthly review is to surface problems early enough to act, not to punish.
5. Quarterly (CHECK + ACT) — Deeper quarterly review with cross-functional perspective. Persistent reds may trigger formal re-planning. Emerging opportunities or threats may add tactics. New problems get formal CAPA + change-control treatment.
6. October-November (ACT + next-year PLAN) — Year-end review: what did we deliver? what did we miss? why? What did we learn about our own planning + execution discipline? Lessons feed directly into next year's planning cycle. The continuous-improvement loop closes.

The monthly review is the load-bearing habit. A hoshin that is planned in December and re-examined the following October is a hoshin that died sometime in March. The monthly rhythm — short, structured, focused on the X-matrix, owned by leadership not delegated — is what keeps the system alive.

Regulated manufacturers have explicit obligations that map cleanly onto the hoshin cycle. The hoshin operating system is the natural home for these obligations — running them as a single integrated discipline rather than as parallel compliance bureaucracy:

1. ICH Q10 §3.1 — Continual improvement of the PQS: "The pharmaceutical company should identify and implement appropriate process performance and product quality improvements". The annual hoshin is the documented identification + selection mechanism, with monthly review providing the implementation tracking.
2. ICH Q10 §3.2.4 — Continual improvement of process performance + product quality: this is essentially a description of bottom-up kaizen + improvement projects, which the hoshin operating system organises and aligns to strategic priorities.
3. ICH Q10 §2.7 + 21 CFR 820.20 — Management responsibility: the annual hoshin review + monthly cadence is direct evidence of management review of suitability + effectiveness of the QMS. Far stronger evidence than a single annual management review meeting.
4. ISO 13485 §5.4.1 — Quality objectives: "top management shall ensure that quality objectives, including those needed to meet applicable regulatory requirements and requirements for product, are established at relevant functions and levels". The X-matrix cascade is exactly this: quality objectives established at site, department, team levels.
5. ISO 9001:2015 §6.2 — Quality objectives + planning to achieve them: same pattern; hoshin is the planning discipline that delivers §6.2 compliance as a by-product.
6. 21 CFR 211.180(e) — Records reviewed annually: the hoshin year-end + planning cycle naturally pulls in annual product reviews + APR / PQR data as inputs to the next year's priorities.
7. EU GMP Chapter 1 §1.5 — Senior management has the ultimate responsibility to ensure an effective PQS is in place: the hoshin operating system makes this responsibility visible, measurable, and reviewable rather than aspirational.

• Number of breakthrough objectives in the annual hoshin — should be 3-5; >7 is the death-by-priorities anti-pattern; <3 may indicate lack of strategic ambition.
• X-matrix coverage — fraction of departments + areas with current X-matrix posted at visual board; <90% means the system is not fully deployed.
• Catchball rounds completed — 2-4 rounds per cycle indicates real negotiation; 1 round indicates cascade-disguised-as-catchball; >5 rounds indicates the draft was too rough or leadership not aligned.
• Monthly review attendance — fraction of scheduled monthly reviews held with named owners present; <85% indicates the cadence is collapsing.
• Year-end delivery rate — fraction of annual hoshin breakthroughs delivered to target; 70-80% is healthy; 100% suggests targets too soft; <50% suggests planning + catchball broken.
• Time from problem surface to course-correction — for yellow/red items, median days from monthly-review identification to documented countermeasure; trending up means the system is becoming bureaucratic.
• Department-level participation — number of named kaizen experiments per team per quarter that link explicitly to an annual hoshin tactic; the load-bearing measure of bottom-up engagement with top-down direction.
• Year-on-year improvement on the True-North metrics — the multi-year-arc measure; trending toward the 3-5 year breakthrough vision is the ultimate validation.

Mistake 1 — too many breakthroughs

The most common failure: leadership cannot say no, the annual hoshin lists 10-15 breakthroughs, and within 4 months everything is yellow because attention is fragmented. Discipline: 3-5 maximum, publicly schedule the rest for future years, and accept the political cost of de-prioritising sponsors' pet projects.

Mistake 2 — skipping catchball

Leadership issues the annual hoshin as a top-down directive because catchball is uncomfortable + time-consuming. Departments comply on paper, report green on targets they never believed in, and the year ends with the breakthrough undelivered. The 4 weeks of catchball at the top of the year is the difference between strategy and shelfware.

Mistake 3 — monthly reviews that become status theatre

Reviews degenerate into 60-minute slide-decks where every status is reported green or "on track" regardless of reality, because reporting red invites criticism. Fix: leadership explicitly rewards early surfacing of red, treats red as opportunity for help rather than failure, and demands countermeasures rather than explanations. A culture where red is safe to report is a culture where hoshin works.

Mistake 4 — X-matrix as decoration, not operating document

The X-matrix is created at the start of the year, posted at the visual board, and never referred to again. Daily decisions still come from email, ad-hoc meetings, and the loudest voice in the room. Fix: monthly reviews are run from the X-matrix; kaizen proposals must reference an X-matrix tactic; visual boards are updated monthly with status colours. The matrix must be the operating document, not the wall art.

Mistake 5 — confusing hoshin with budgeting

Hoshin kanri and the annual operating budget are different artefacts with different purposes. The budget is the financial commitment; the hoshin is the improvement commitment. Both belong, but conflating them produces hoshins that are really thinly-disguised cost-cutting targets, which destroys engagement. Discipline: separate the two cycles, link them where appropriate (resource allocation for hoshin tactics) but never substitute one for the other.

Mistake 6 — no bottom-up component

The annual hoshin is purely top-down: leadership decides, cascades, monitors. There is no mechanism for frontline teams to surface improvement ideas or to flag that a hoshin tactic is impractical at their level. Fix: catchball must include frontline, and team-level kaizen must be the unit of execution. Hoshin without kaizen is a planning system without an execution system.

Mistake 7 — never re-planning when reality changes

A major customer is lost in February; a regulatory action requires a rebuild of a process in May; a competitor announces in August. The annual hoshin is treated as immutable, and the organisation works on yesterday's priorities while the world changes. Discipline: quarterly review is the formal opportunity to re-plan; major events trigger ad-hoc re-planning. The annual hoshin is the plan, not the strait-jacket.

V5 ships hoshin kanri infrastructure that makes the practice operational and that integrates the regulated obligations (ICH Q10, ISO 13485 §5.4, 820.20) into a single living artefact rather than parallel compliance bureaucracy.

• X-matrix workspace — visual, configurable 4-quadrant editor at site / department / team levels with explicit nesting; per-cell linking shows which strategy each objective supports, which objective each tactic delivers, which KPI measures each tactic.
• Catchball workflow — draft hoshin routes through configurable catchball cycles with named participants per round; comments, counter-proposals, resource requests captured in audit trail; each round explicitly closed before next opens.
• Annual cycle calendar — auto-scheduled monthly + quarterly review cadence per X-matrix level with reminders + meeting agenda templates + status-colour rollup from kaizen execution data.
• Kaizen experiment linkage — every kaizen suggestion + experiment + event can be tagged to a hoshin tactic; dashboards show per-tactic kaizen activity, fraction of tactics with active kaizen, kaizen-without-tactic flags.
• Visual board export — X-matrix renders as printable + kiosk-visible visual board with current status colours; updated automatically as monthly reviews record status; deployable to every area visual-management board.
• Regulated overlay — X-matrix doubles as ISO 13485 §5.4 quality-objectives register + ICH Q10 §3.1 continual-improvement plan + 820.20 management-review input; investigator-visible export bundles everything inspectors ask for.
• Monthly review record — every monthly review captures attendees, status updates, decisions, countermeasures, action items with owners + due dates; auto-routes commitments and tracks follow-through; satisfies management-review documentation requirements as a by-product.
• Year-end retrospective — structured year-end review template captures delivery rate per breakthrough, root-cause for misses, lessons-learned, and feeds directly into next-year planning cycle with auto-population of prior-year baseline.
• Cross-area visibility — site-level dashboard surfaces hoshin status across all areas + departments; identifies stalled tactics, resource conflicts, areas without engagement; gives leadership the cross-cutting view that prevents departmental siloing.
• Coaching-kata integration — Toyota-kata improvement-kata + coaching-kata supported as the team-level execution discipline that runs underneath the hoshin tactics; leadership coaches the kata, not the outcome.
• Part 11 + Annex 11 audit trail — every X-matrix edit, catchball round, monthly review, status colour change is captured in the regulated audit trail with timestamps + e-signatures where required.
• Mobile-safe — entire hoshin surface designed for iPhone (≤390 px CSS width); leaders can run monthly reviews from the floor + capture status during gemba walks.

How is hoshin kanri different from strategic planning?

Most strategic planning produces a plan and stops; hoshin kanri produces an operating system. The plan is one artefact; the X-matrix cascade, the catchball process, the monthly review cadence, the kaizen execution linkage, the year-end retrospective are the operating system that makes the plan happen. The discipline is in the cycle, not the document.

How long does it take to implement hoshin kanri?

Year 1 is awkward: leadership is learning to choose 3-5 breakthroughs, departments are learning catchball, teams are learning to link kaizen to tactics. Year-end delivery rate is often 40-50%. Year 2 is functional: catchball is genuine, monthly review is honest, delivery rate hits 60-70%. Year 3 is mature: the cycle is muscle memory and the organisation is genuinely executing strategy. Premature pessimism in year 1 is the most common reason organisations abandon it.

Does hoshin kanri work in regulated pharma / device manufacturing?

Yes, and in fact regulated obligations make it more rather than less applicable. ICH Q10 §3.1 explicitly requires continual improvement of the PQS, ISO 13485 §5.4 requires quality objectives at relevant functions + levels, 820.20 requires management responsibility for QMS effectiveness. The hoshin operating system delivers all three as a by-product of running the business well, rather than as parallel compliance bureaucracy.

What's the relationship between hoshin kanri and kaizen?

Complementary: hoshin sets strategic direction top-down; kaizen executes improvement bottom-up. Without hoshin, kaizen produces lots of small improvements that don't add up to strategic change. Without kaizen, hoshin produces strategic targets with no operational mechanism to deliver them. The mature plant runs both as a single integrated system.

How does hoshin compare to OKRs (Objectives + Key Results)?

OKRs (Doerr / Grove / Intel / Google) are conceptually similar — top-down breakthrough objectives cascaded with measurable key results — but typically lighter on the operating system. Hoshin has the X-matrix (visual artefact), catchball (negotiated commitment), monthly review (recurring cadence) as named, taught disciplines. OKRs more commonly degenerate into 'set them quarterly, forget them until quarter-end'. The two are compatible; teams that find OKRs working at strategic level often benefit from adopting hoshin operational disciplines (catchball + X-matrix + monthly review) without renaming.

How does V5 support hoshin kanri?

X-matrix workspace at site/department/team levels + configurable catchball workflow + auto-scheduled monthly + quarterly review cadence + kaizen experiment linkage to tactics + visual board export + regulated-overlay (ISO 13485 §5.4 / ICH Q10 §3.1 / 820.20) + monthly review record + year-end retrospective + cross-area visibility dashboard + coaching-kata integration + Part 11 audit trail + mobile-safe at iPhone width.

What if leadership won't commit to the discipline?

Honest answer: hoshin doesn't work without leadership commitment, and there is no substitute. The catchball requires leadership time, the monthly review requires leadership presence, the year-end retrospective requires leadership honesty about misses. If leadership isn't willing, start smaller — a single department running its own hoshin can demonstrate the discipline + the results, which is often what unlocks site-wide leadership commitment in year 2.