Hoshin Kanri
Hoshin Kanri (literally 'compass needle management' or 'direction management') is a Japanese strategic management methodology developed in the 1960s and refined at Toyota, Bridgestone, and other leading manufacturers before spreading globally. It provides a rigorous process for translating long-term organisational vision into annual priorities and cascading those priorities through every level of the organisation — ensuring that daily work directly contributes to breakthrough strategic objectives. The methodology is built around two key artefacts: the X-Matrix (also called the Hoshin Planning Matrix), which on a single page maps the relationships between 3–5 year breakthrough objectives, annual priorities, improvement projects, and measurable targets; and the A3 catchball process, which is the iterative up-and-down communication mechanism by which leadership proposes direction and frontline teams respond with capacity, concerns, and refinements before committing. Unlike traditional top-down planning, Hoshin Kanri's catchball process incorporates a genuine negotiation that builds alignment and shared ownership. In a workshop, the X-Matrix is used to create the strategic deployment plan: you populate the four arms of the matrix (Breakthrough Objectives at south, Annual Priorities at west, Improvement Projects at north, Targets and Metrics at east) and then mark the strength of relationships between each pair using symbols. Blank relationships on the matrix are as important as strong ones — they reveal strategic activities with no measurable outcome or objectives with no concrete initiative supporting them.
Facilitation script
- 1
Orient the group to the X-Matrix: walk through the four arms — Breakthrough Objectives at south, Annual Priorities at west, Improvement Projects at north, Targets at east — and demonstrate the relationship symbols (filled circle, open circle, triangle).
20 min - 2
Define Breakthrough Objectives: ask 'What must be fundamentally different about this organisation in 3–5 years?' Push past incremental answers and capture 3–5 genuinely transformational statements.
30 min - 3
Derive Annual Priorities: ask 'What are the 3–5 most critical things we must accomplish THIS year to make progress toward those breakthroughs?' Force choices — not all strategic work makes the list, only the vital few.
30 min - 4
Identify Improvement Projects: for each annual priority, capture the concrete, bounded initiatives or kaizen events that will deliver it, each with a named owner.
20 min - 5
Define Metrics and Targets: for each annual priority, agree leading and lagging measures with specific numerical targets and time horizons.
20 min - 6
Map relationship strengths between adjacent arms using the symbols, then scrutinise the blanks: name every orphaned priority with no project driving it and every project with no measurable outcome.
25 min - 7
Review for balance and coherence: step back from the completed matrix, ask whether the organisation is taking on too much, and iterate on anything structurally broken.
15 min - 8
Plan the catchball process: agree how the matrix goes to the next level down and how teams' responses on capacity and concerns will be negotiated before final commitment. Book the monthly Hoshin Review before the room empties.
20 min
Tips
Hoshin Kanri fails most often because organisations fill the matrix in a day and skip catchball. The value of the method is the dialogue, not the document.
Limit breakthrough objectives to 3–5 maximum. More than that signals an inability to prioritise, which is the core problem Hoshin is designed to solve.
Annual priorities must be genuinely chosen from the full backlog of strategic work — not everything. If every strategic activity is labelled a priority, none are.
The relationship matrix is diagnostic: many blanks mean strategy and execution are disconnected. Strong relationships everywhere means the matrix is just cataloguing what already happens, not focusing on what must change.
Pair Hoshin with a regular monthly review cadence (often called the Hoshin Review). The matrix is useless without a structured review and course-correction process.
Common pitfalls
Filling in the X-Matrix in a single day and skipping catchball — leadership leaves with a document while every level below it has no ownership of the plan
Labelling every strategic activity an annual priority — if everything is a priority nothing is, and the room ends the workshop carrying the same overload it arrived with
Gliding past blank relationship cells to finish on time — orphaned priorities and unmeasured projects sail through unchallenged, which is precisely what the matrix exists to catch
Accepting a matrix that shows strong relationships everywhere — it is cataloguing what already happens instead of forcing choices about what must change, and participants sense the exercise was theatre
Closing without scheduling the monthly Hoshin Review — with no course-correction cadence the plan drifts within a quarter and the matrix is quietly abandoned
Variations
For smaller organisations or teams, a simplified two-arm version (Objectives → Projects → Metrics) can replace the full X-Matrix. For agile environments, Hoshin principles can be applied at a team level with OKRs substituting for the formal matrix structure. Toyota applies Hoshin at every level from the CEO to the shop floor — in knowledge work organisations, three levels (executive, department, team) is typically sufficient.
Where it fits
When to use it
Annual strategic planning where a leadership team must narrow a long backlog of strategic work down to a vital few priorities
Cascading corporate strategy to business units and departments so that daily work visibly connects to 3–5 year breakthrough objectives
Lean transformations and continuous improvement programmes that need kaizen activity aligned to strategy rather than scattered across the organisation
Post-merger integration or turnaround situations where focus on a handful of priorities matters more than comprehensive planning
When strategy documents exist but execution is disconnected — the X-Matrix's blank relationship cells expose exactly where the chain breaks
When not to use it
The organisation has no settled 3–5 year vision yet — run a Strategy Map or vision workshop first, because the X-Matrix deploys strategy, it doesn't invent it
A single team needs quarterly priorities — an OKR workshop delivers the goal-to-metric link with far less ceremony
Leadership won't commit to catchball and a monthly Hoshin Review — without the dialogue and review cadence the matrix becomes shelf-ware
The people in the room lack authority to commit resources to improvement projects — the matrix only binds if decision-makers fill it in
You have less than two hours — populating and relationship-coding all four arms takes 120–240 minutes even with strong pre-work
Related methods
Frequently asked questions
What is hoshin kanri?▾
Hoshin kanri — literally 'compass needle management' or 'direction management' — is a Japanese strategic planning methodology developed in the 1960s and refined at Toyota and Bridgestone. It translates an organisation's 3–5 year vision into a vital few annual priorities and cascades them through every level, so that daily work directly contributes to breakthrough objectives. Its two key artefacts are the X-Matrix, a one-page strategy deployment map, and catchball, a structured negotiation between leadership and frontline teams.
What is the X-Matrix in hoshin kanri?▾
The X-Matrix (also called the Hoshin Planning Matrix) maps an entire strategy on a single page using four arms: breakthrough objectives at the south, annual priorities at the west, improvement projects at the north, and targets and metrics at the east. The strength of each relationship between adjacent arms is coded with symbols — filled circle for strong, open circle for some, triangle for possible. The blanks are as diagnostic as the marks: an annual priority with no project driving it is orphaned, and a project with no measurable outcome is unfocused.
What does catchball mean in hoshin planning?▾
Catchball is the iterative, up-and-down communication process in which leadership proposes direction and frontline teams respond with capacity, concerns, and refinements before anyone commits. Unlike traditional top-down cascading, it is a genuine negotiation that builds alignment and shared ownership of the plan. Hoshin kanri fails most often when organisations fill in the X-Matrix in a day and skip catchball — the value of the method is the dialogue, not the document.
How many objectives should a hoshin kanri plan contain?▾
Limit breakthrough objectives to 3–5 for the whole organisation, and derive 3–5 annual priorities from them. More than that signals an inability to prioritise, which is the core problem hoshin kanri is designed to solve. Improvement projects and metrics then attach to those vital few priorities, not to everything the organisation does.
How is hoshin kanri different from OKRs?▾
Both link goals to measurable outcomes, but hoshin kanri adds the X-Matrix's explicit relationship mapping between multi-year objectives, annual priorities, projects, and metrics, plus the formal catchball negotiation across organisational levels. OKRs are lighter-weight and can substitute for the formal matrix at team level in agile environments. In knowledge-work organisations three levels of deployment — executive, department, team — is typically sufficient, whereas Toyota applies hoshin from the CEO to the shop floor.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Hoshin Kanri into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Yoji Akao / Toyota Production System.