Hoshin Kanri 方針管理
How a whole organization points itself at the same few goals — not by handing plans down, but by throwing them back and forth until everyone owns them. Play it through inside a hospital.
Hoshin looks like other goal systems on the surface. The difference is how the plan is made, how few things you chase, and what it’s trying to grow. Pick a method you know and compare.
Done well, OKRs can borrow hoshin’s habits — real input, fewer bets, honest reviews. The contrast here is with how these methods usually run in practice.
A system-level objective just landed on your desk. You’re the ops director — your job isn’t to deliver the plan, it’s to develop the person who will. Watch what happens depending on how you throw the ball.
Catchball is the two-way conversation that replaces a top-down plan — and the reason a matrix isn’t needed. Alignment comes from the discussion, not a filled-in form.
The plan Priya now owns is one node in a fractal. Drill down — click through the levels and watch a three-year vision turn into something a frontline team can act on this week.
Same shape at every scale — the “how” at one level becomes the “what & why” at the next, linked by dialogue rather than a matrix.
A department’s hoshin isn’t only the corporate objectives handed down. Leaders are expected to place their own bets — to run their patch like it’s their own company. Filter 4 West’s board to see the two kinds of objectives.
Now execute. Advance the year month by month and watch the summary scorecard fill in. When a metric goes red, you don’t rewrite the plan — you open a countermeasure and go and see for yourself on the unit.
The discipline: plan, do, check, adjust — a red month means investigate and counter, not quietly abandon the goal.
When an objective is achieved, you “hand it to daily management.” But what is that? Hoshin and daily management are two different engines — you need both. Tap each to see its job.
Vision says where to go, hoshin kanri gets there in leaps, and daily management holds each gain and inches it forward in between. You need all three.
Everything you just made — the hoshin, the A3s, the scorecard — hangs together on one wall in the obeya (“big room”). Once a month the team stands here and walks each objective top to bottom. Pick a board and watch a single goal break down into A3s.
The obeya makes the whole system visible in one place: direction at the top, each objective broken into a strategy A3 and frontline problem-solving A3s, all tracked on the scorecard — and reviewed together, monthly.
Hoshin chases three things at once — and this is the one that makes it different from a goal tracker. Every objective, every A3, every round of catchball is also a person being developed on the job.
Breakthrough results
Focus the whole company on the vital few and actually move them.
Alignment
Vertical and horizontal — everyone pulling the same direction.
Developed people
Leaders and problem-solvers grown through the work itself.
The quiet purposeFrequently asked
- What does “hoshin kanri” actually mean?
- Hoshin means fundamental direction, objective, or policy; kanri means management or control. Together, hoshin kanri is the management system an organization uses to set its mid- and long-term direction, then annually build alignment — both vertically (top-to-bottom) and horizontally (across departments) — behind that direction, manage execution to it, and develop people along the way. The common English translation “policy deployment” is often considered misleading, because it sounds purely top-down when the practice is meant to be equally bottom-up.
- What is catchball in hoshin kanri?
- Catchball is the structured back-and-forth discussion that turns a proposed objective into a plan people actually own. Vertical catchball runs between a leader and their team — direction and “why” flow down, while the team’s thinking, frontline findings, and input flow back up. Horizontal catchball runs across departments to agree what support each team needs from the others. It’s less a one-time event than an ongoing, overlapping conversation that keeps weaving through the planning cycle — and it is the mechanism, not a form, that creates real alignment.
- Why doesn’t this guide use the X-matrix?
- The X-matrix is a popular Western hoshin template, but many practitioners argue it gets in the way. Real alignment comes from face-to-face problem-solving, not from filling in a grid, and a complex matrix can quietly turn into a check-the-box exercise. A simpler alternative is a one-page table linking each objective to its activities, targets, one lead, and its supporting departments — held together by catchball. The more complicated the tool, the harder it is to build the genuine understanding that alignment actually depends on.
- How is hoshin kanri different from setting annual goals?
- Ordinary annual goals are usually assigned from above and then policed. Hoshin kanri creates accountability through ownership instead: the team develops the plan itself through catchball, the organization focuses on the “vital few” breakthrough objectives rather than a long list, and the year runs as a full PDCA cycle — plan, do, check, adjust — with monthly obeya reviews, a midyear reflection, and a year-end evaluation. It also names one lead per objective who leads by responsibility rather than authority, using it as a deliberate way to develop that person.
Related
Founder of Kaizumi, an AI-powered Lean training platform. More about Matthew →
Updated July 2026 · Cedar Valley Health, its units, and all figures are a fictional illustration, created for teaching.