Lean teams use hoshin kanri to focus improvement effort on what matters most. It keeps the number of priorities small and links daily work to strategy. Tools like the X-matrix and A3 make the links and owners visible.
Where it comes from
Hoshin kanri developed in Japanese companies alongside total quality management and the PDCA cycle. Lean organizations outside Japan later adopted it too.
At a glance
A simplified X-matrix
Swipe sideways to see the whole diagram.
How to apply Hoshin Kanri
- 1
Set breakthrough objectives
Define a few long-term goals tied to the organization's direction. Limit them so resources are not spread too thin.
- 2
Translate into annual objectives
Choose this year's objectives that move toward each breakthrough goal. Make each one measurable.
- 3
Play catchball
Pass the objectives down and across the organization for feedback. Teams propose how they will contribute and what they need.
- 4
Assign improvement priorities and owners
Define the projects and metrics that will deliver each objective. An X-matrix shows how goals, projects, metrics and owners connect.
- 5
Execute and review monthly
Track progress on visual boards or A3s. Hold regular reviews that focus on gaps and countermeasures, not blame.
- 6
Reflect and reset each year
Run an annual reflection on what worked and why. Use the lessons to set the next cycle of objectives.
Worked example (illustrative)
A mid-size manufacturer sets a three-year goal to cut customer lead time in half, from about 20 days to 10. This year's objective is 16 days. Through catchball, each of its three plants proposes two projects, such as quicker changeovers and pull replenishment, with an owner and a monthly target. The bowling chart shows Plant B at 19 days in March and April against a target of 18. Its A3 review finds the changeover project short of people, so a second technician joins it, and Plant B is back on plan from May.
Common mistakes
- Setting too many priorities, so nothing gets enough attention.
- Pushing targets down without real catchball, which kills ownership.
- Reviewing only at year end instead of monthly, missing chances to adjust.
When Hoshin Kanri is not the right tool
Hoshin kanri adds most where several levels must align on a few breakthroughs. A small company with one leadership team may need only a simple plan and monthly review.
It also needs a working daily management system to carry goals to the front line.
Hoshin kanri meaning
Hoshin kanri is a Japanese term often translated as policy deployment. Hoshin means direction, like a compass needle, and kanri means management or control.
It is a method for choosing a few breakthrough goals and aligning every level of the organization to them. In English it is also called hoshin planning.
The hoshin planning process
Leaders set a long-term vision and a few breakthrough objectives. They turn these into annual objectives and a short list of improvement priorities.
Each level agrees its part through catchball, a back-and-forth discussion instead of orders. The plan is often summarized on an X-matrix.
Monthly reviews check progress and adjust the plan. The yearly cycle then repeats, like one large PDCA loop.
Bowling charts
A bowling chart lists each metric with a target and an actual result for each month. Cells turn red or green, so misses stand out.
Each red cell needs a countermeasure, often worked through on an A3. In the worked example, Plant B's two red months led to one A3 and one countermeasure: a second technician on the changeover project.
The X-matrix guide shows how plans and charts connect. Hoshin kanri software can hold the matrix and the charts once paper gets crowded.
Objectives, activities and measures
Hoshin plans go wrong when finished activities are reported as results. Keep three kinds of information apart, shown here for an illustrative goal of faster customer onboarding:
| Type | What it checks | Onboarding example |
|---|---|---|
| Outcome measure | Whether the intended result is improving | Days from signed order to completed onboarding |
| Process measure | Whether a part of the work that drives it is changing | Share of sales handoffs received with complete information |
| Activity milestone | Whether an agreed action is done | Revised intake form tested with the pilot team |
Outcome measure
Whether the intended result is improving
Onboarding example: Days from signed order to completed onboarding
Process measure
Whether a part of the work that drives it is changing
Onboarding example: Share of sales handoffs received with complete information
Activity milestone
Whether an agreed action is done
Onboarding example: Revised intake form tested with the pilot team
Training everyone on a new intake form is a milestone. If customers still wait as long, the result hasn't moved. For each key measure, write the definition, baseline, target, data source, owner and how often it is reported, plus what is counted and what is left out.
Watch how measures can flatter. A delivery goal tracked against the latest revised date can look healthy while customers keep waiting; keep the original promise date visible. Pair each outcome with a balancing measure, such as complaints or repeat contacts, so the team can see whether it improved the experience or just moved the work.
Catchball questions that lead to decisions
Catchball runs up and down between levels and across functions. These questions keep it from turning into endless discussion:
- What evidence explains the current gap? Not opinions about it.
- Which part of the result can this team move directly? And which part depends on someone else.
- What must another function provide first? Name it, and agree it with them.
- Which current commitment changes to free the capacity? A plan that adds work without removing any is not agreed.
- What should be tested before the approach is fixed? A small trial beats a confident rollout.
Set a point where the responsible leaders confirm the objective, resources, owners and open assumptions. Record where a team supports the goal but questions the method or the timing; that is useful challenge, not resistance. The X-matrix guide shows an illustrative catchball exchange.
A review record for each priority
Each priority's monthly review answers the same five questions, illustrated here for an onboarding project in its third month:
Priority: faster customer onboarding
Month 3 review
- 1. Expected
- Onboarding down from 21 days to 17 by month three.
- 2. Actual
- 19 days. Complete handoffs rose from 55% to 80%.
- 3. Explanation
- Handoffs improved but elapsed time didn't follow. Supported: two approvals still wait for one manager. Still a guess: whether customers' own paperwork adds delay.
- 4. Response
- Test removing one approval for standard orders; sample ten orders for customer-side delays.
- 5. Follow-up
- Operations lead reports both at the next review.
The record keeps reporting tied to decisions and keeps uncertainty visible. A team can say it doesn't yet know why a result changed and still commit to a specific study.
Before the first planning cycle
The Lean Enterprise Institute suggests starting with a pilot. Check these first:
- Leadership ownership: A responsible leader will take part in choosing priorities, in reviews and in resource decisions. An improvement specialist can support, not replace, that role.
- A real challenge: The pilot tackles a genuine business problem, not a demonstration of the template.
- Evidence: Teams can describe the current state and admit the gaps in their data.
- The right people: Everyone who affects the result can help plan the work.
- Freed capacity: You have decided what to stop, delay or simplify.
- A review rhythm: An agreed time and place to study results and clear blockers.
- A learning record: Decisions, assumptions and lessons kept for the next cycle.
One connected objective with honest reviews teaches more than a large plan whose owners can't explain its logic. Train people on the pilot's real problem: writing objectives, running catchball, choosing measures and reviewing a missed target without jumping to the fix.
Rollout traps
Traps that tend to appear in the first year:
- 1
Starting with the template. A polished X-matrix can't make up for a weak strategic choice. Define the problem and priorities first.
- 2
Calling everything strategic. Keep routine work in daily management and save hoshin for the few changes that need joint breakthrough effort.
- 3
One owner, no support. Name one accountable lead, but write down what other functions have committed, instead of relying on goodwill.
- 4
Only green reports. Keep bad news visible and tie it to a study. A review should help the team respond, not reward a good presentation.
- 5
Moving the goal to match the result. Fixing a wrong assumption is fine; lowering a target because progress is hard is not. Record the reason either way.
- 6
Gains left inside the project. Decide who keeps the improved process running and who responds when it drifts.
| Practice | What it handles | What it is not for |
|---|---|---|
| Strategy | Which customers, capabilities and problems to focus on | Expecting a matrix to make the choice |
| Hoshin kanri | Linking a few priorities to yearly goals, owners and reviews | Holding every task in the business |
| Project management | Tasks, dependencies and milestones inside one initiative | Judging whether the initiative moves the strategic result |
| Daily management | Keeping work stable and holding gains | Breakthrough change |
| KPI reporting | Evidence for decisions | Being the management process itself |
Guides on this topic
- OKRs: how to write, run and score objectives and key resultsOKRs explained: what an objective and key result are, the quarterly cycle, OKR vs KPI, writing testable key results, illustrative examples for marketing, product and support, scoring, committed and stretch goals, a first-cycle plan and mistakes.Read the guide
- Nemawashi: how to prepare a decision before the meetingNemawashi explained: what the word means, how to run the consultation in six steps, questions to ask, how to track where people stand, how it differs from ringi and formal approval, examples, risks and a readiness checklist.Read the guide
- Hoshin kanri X-matrix: how to build and read oneThe hoshin kanri X-matrix in plain language: what goes in each section, how to read it, a filled example, catchball, the monthly review and a free X-matrix template.Read the guide
- Obeya: how a big room helps teams see and decide togetherThe obeya room explained: where it came from, what goes on the walls, how a review runs, how it differs from dashboards and status meetings, how to build a first room, virtual and hybrid setups, and how to tell whether it works.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Yoji Akao (editor), Hoshin Kanri: Policy Deployment for Successful TQM (Productivity Press, 1991)
- 2.Thomas L. Jackson, Hoshin Kanri for the Lean Enterprise: Developing Competitive Capabilities and Managing Profit (Productivity Press, 2006)