What is strategy deployment?

Strategy deployment — hoshin kanri, also called policy deployment — is the discipline of turning a few multi-year breakthrough objectives into aligned action at every level of a company. Each level translates the objective above it into something it can honestly commit to, so a corporate goal like “halve warranty cost” becomes a department’s monthly plan, a team’s weekly goals, and finally a target on one machine. Done well, everyone can trace what they do this week back up to why it matters.

Is strategy deployment the same as hoshin kanri?

Yes — they name the same method. “Hoshin kanri” is the original Japanese term (roughly “direction management”); “strategy deployment” and “policy deployment” are the common English translations. All three describe the same practice: a small number of vital objectives, cascaded and negotiated down through the organization and reviewed on a regular rhythm, rather than a long list of goals assigned from the top.

What is catchball in strategy deployment?

Catchball is the back-and-forth that turns a proposed objective into a plan people actually own. Direction and the “why” flow down; the team’s findings, constraints, and counter-proposals flow back up; and departments negotiate sideways over what they need from each other. It takes real time — often about a quarter for a plan to settle — which is exactly why the top of the cascade cannot change quickly: if the objective moves faster than catchball can propagate it, alignment never finishes.

Why does review cadence change as the strategy cascades down?

Because each level must be checked at the rate its reality actually changes. A five-year vision barely moves, so reviewing it monthly would be noise; the factory floor changes by the hour, so checking a machine’s defect rate once a year is blindness. Deeper in the organization means a faster clock — daily or hourly on the floor — and higher up means a slower one. This guide makes that coupling visible: the corporate card sits nearly still while the floor strobes.

How does a floor problem connect back to the corporate objective?

Through the same thread, in reverse. When a floor metric goes red, the fast daily clock catches it before the slower weekly and monthly boards can — and the operator’s A3 (a one-page problem solve) names the physical root cause and a countermeasure. If the fix holds, the levels above never need to know; if it recurs, it escalates one “gear” up. That is the cascade working as a nervous system, not just an org chart: direction flows down, and reality flows back up.

Does hoshin kanri need an X-matrix?

No. The X-matrix is a popular Western template, but many practitioners find it gets in the way — a complex grid can quietly become a check-the-box exercise, while real alignment comes from the face-to-face negotiation of catchball. A simpler one-page table linking each objective to its activities, targets, a single lead, and its supporting departments works well, and it is closer to how the cascade in this guide actually behaves.

Strategy deployment · Hoshin kanri

The thread from one objective to one machine

Strategy deployment (hoshin kanri) is how a company turns a few multi-year objectives into aligned action everywhere — each level translating the one above into what it can actually commit to, until the plan reaches a single operator at a single machine. Most diagrams draw that as a static tree. This one adds the thing a tree can’t hold: the clock. Scroll down the cascade and watch review cadence speed up with depth — the corporate objective nearly still, the factory floor strobing — because each level must be checked at the rate its reality actually changes.

Also called: hoshin kanripolicy deploymentcatchballobjective → floor cascade

↓Scroll to descend the four levels — corporate (yearly) → departments (monthly) → goals (weekly) → floor (daily).

✦Click any card to make it the thread. The levels below re-cascade to its children.

▦The navigator (bottom-right) jumps to any objective, department, goal, or metric.

●A red floor cell opens its A3 — the one-page problem solve the fast clock triggered.

⊞“The whole thread” pulls back to show all four clocks at once — still at the top, strobing at the floor.

↔Swipe sideways (trackpad) to pan across a level when a row runs off screen.

Good to know

Frequently asked

What is strategy deployment?: Strategy deployment — hoshin kanri, also called policy deployment — is the discipline of turning a few multi-year breakthrough objectives into aligned action at every level of a company. Each level translates the objective above it into something it can honestly commit to, so a corporate goal like “halve warranty cost” becomes a department’s monthly plan, a team’s weekly goals, and finally a target on one machine. Done well, everyone can trace what they do this week back up to why it matters.
Is strategy deployment the same as hoshin kanri?: Yes — they name the same method. “Hoshin kanri” is the original Japanese term (roughly “direction management”); “strategy deployment” and “policy deployment” are the common English translations. All three describe the same practice: a small number of vital objectives, cascaded and negotiated down through the organization and reviewed on a regular rhythm, rather than a long list of goals assigned from the top.
What is catchball in strategy deployment?: Catchball is the back-and-forth that turns a proposed objective into a plan people actually own. Direction and the “why” flow down; the team’s findings, constraints, and counter-proposals flow back up; and departments negotiate sideways over what they need from each other. It takes real time — often about a quarter for a plan to settle — which is exactly why the top of the cascade cannot change quickly: if the objective moves faster than catchball can propagate it, alignment never finishes.
Why does review cadence change as the strategy cascades down?: Because each level must be checked at the rate its reality actually changes. A five-year vision barely moves, so reviewing it monthly would be noise; the factory floor changes by the hour, so checking a machine’s defect rate once a year is blindness. Deeper in the organization means a faster clock — daily or hourly on the floor — and higher up means a slower one. This guide makes that coupling visible: the corporate card sits nearly still while the floor strobes.
How does a floor problem connect back to the corporate objective?: Through the same thread, in reverse. When a floor metric goes red, the fast daily clock catches it before the slower weekly and monthly boards can — and the operator’s A3 (a one-page problem solve) names the physical root cause and a countermeasure. If the fix holds, the levels above never need to know; if it recurs, it escalates one “gear” up. That is the cascade working as a nervous system, not just an org chart: direction flows down, and reality flows back up.
Does hoshin kanri need an X-matrix?: No. The X-matrix is a popular Western template, but many practitioners find it gets in the way — a complex grid can quietly become a check-the-box exercise, while real alignment comes from the face-to-face negotiation of catchball. A simpler one-page table linking each objective to its activities, targets, a single lead, and its supporting departments works well, and it is closer to how the cascade in this guide actually behaves.

Hoshin kanri Catchball Nemawashi A3 problem solving Hoshin kanri guide A3 problem solving guide PDCA guide

Matthew Savas

Founder of Kaizumi, an AI-powered Lean training platform. More about Matthew →

Updated July 2026 · Aster Mobility, its people, and every figure are illustrative, created for teaching. The method — a few vital objectives, cascaded and negotiated through catchball, each level reviewed at the rate its reality changes — follows the hoshin kanri tradition (Jackson, Hoshin Kanri for the Lean Enterprise, and the Lean Enterprise Institute).

Frequently asked

Related