Strategy Deliver

Hoshin Kanri

Hoshin kanri is a planning cadence that connects company goals to the daily work of individual people.

The questionWhich few things must change this year, and does every level know its part in them?

Also called policy deployment, policy management, strategy deployment, and hoshin planning. Hoshin kanri is Japanese for policy management.

Process · Japanese quality movement, 1960s

Set directionReview last year, list candidate priorities
Breakthrough objectivesTwo to four, each with an owner
CatchballNegotiate up and down the levels
Deploy on a pageMeans, targets, measures, owners
ReviewMonthly, then the year-end close

Simplified annual cycle of hoshin kanri, from direction setting through monthly review and the year-end close.

When to use it

The company has a dozen or more stated priorities, every function can show it is working on one of them, and the main gap is not closing.
Strategy is approved each year, and by March nothing in the plants or branches has changed because of it.
The client is operations-heavy and already runs standard daily management and structured problem solving, such as A3 reports and daily huddles.
Leaders want middle managers to commit to targets they helped shape, instead of receiving them from above.

When to avoid it

Daily management is weak. Targets will land on units that cannot hold today's standards, so build that discipline first, with 5S or PDCA basics.
The engagement is a single strategy choice. Hoshin is an annual management system, and it takes more than one cycle to work well.
Leadership wants targets cascaded without hearing back. That is management by objectives under another name, and plain target setting costs less.
The organization is small enough that the CEO talks to everyone every week. The machinery will cost more than it saves.

Overview

Hoshin kanri is an annual cycle that turns a few company priorities into specific work at every level and reviews progress every month. It supports one choice: which small number of changes the organization will put management attention behind this year, and who owns each part.

Two features set it apart from ordinary target cascading. Objectives are negotiated down and back, so lower levels can change what is asked of them before they commit. And it covers change only, since the routine work of holding current standards runs through daily management. It is slow to learn, and the first cycle is usually rough.

The elements

Breakthrough objectives

The small number of changes that get management attention this year, commonly two to four. Each has a measurable target and a named executive owner. Anything that only maintains current performance stays out.

Catchball

The negotiation of objectives up and down the organization. Leaders draft, the next level tests what it would take, names obstacles and resource needs, and sends the draft back changed. It repeats until each level can say what it will do and what it needs. If the ball returns unchanged, no catchball happened.

Deployment page

One page per level or site that links the objective to local means, targets, measures, and owners. The X-matrix is a common layout, a grid that cross-references objectives, priorities, metrics, and people. Toyota-style practice leans on A3 reports instead. The layout is a tool, and the content is what matters.

Review cadence

Progress checks monthly or quarterly, and an annual review at year end. The reviews look at gaps against target and their causes, then agree on countermeasures. The annual review also asks whether the process itself worked.

Daily management

The counterpart that runs alongside. Hoshin changes a standard, and daily management holds the standard once it exists. Hoshin deployed into a unit with no daily management has nothing to land on.

What it is not

Management by objectives with a Japanese name. MBO centers on individual objectives and appraisal. Hoshin centers on a few company-level changes, deployed across functions through two-way dialogue.
An annual planning document. The plan matters less than the monthly reviews. Without them it is a binder.
A list of everything the company will do. Routine work belongs to daily management, and hoshin holds only change.

The steps

Review last year and set direction

Start from the long-range direction, usually three to five years, and the results and unfinished gaps from the last cycle. Look for gaps that more than one function would have to close. The output is a short list of candidate priorities.
Choose the breakthrough objectives

Cut the candidates to the few that matter most. Write each one with a measure, a target, and an executive owner. If you end up with ten objectives, you have a goal list and not a hoshin.
Run catchball

Take the draft down one level, collect what that level would need and what it cannot do, and revise. Repeat to the front line. Record what changed and why, because changes are the evidence that the dialogue was real.
Deploy on a page

Each level writes its means, targets, measures, and owners on one page, in X-matrix or A3 form. Check that every page traces upward to an objective and that nothing is orphaned or duplicated across functions.
Review monthly, then close the year

Compare results to target, find causes for gaps, and agree on countermeasures. At year end, review what worked, what did not, and how the process itself ran. That review feeds next year's first step.

In practice

The chief operating officer's draft objective read: cut order-to-delivery time from 19 days to 12 by year end. Three plant managers answered within a week. One pointed to a tooling bottleneck that only her plant had. Another said he could reach 12 days only by building inventory, and the finance team would not allow that.

Catchball changed the objective. It became 14 days for the forty highest-volume items, with inventory held flat, and the tooling bottleneck became a corporate-funded project. Each plant then wrote one page with its own means, owner, and monthly measure. At the March review two plants were behind, and the meeting spent its time on causes and countermeasures. The original target would have been missed with no one having said why.

What you leave with

Two to four breakthrough objectives with measures, targets, and executive owners.
A deployment page for each function or site, showing its own means, targets, and owners.
A record of what changed during catchball and why.
A review calendar, with a standing agenda of results against target, causes of gaps, and countermeasures.
An annual review that sets next year's starting point.

Failure points

Too many objectives

Each function lobbies for its own item. The result is a long list that no one can review monthly, and the gap that matters most gets the same attention as the minor ones.

Catchball that returns the ball unchanged

Leaders ask for feedback and then restate the original targets. Lower levels learn that comments are ignored, so they stop commenting and comply. The plan shows agreement that does not exist.

Deployment without daily management

The units cannot hold their standards, so every objective competes with firefighting. Breakthrough work loses to the day's problems.

Reviews that report status

Red, yellow, and green are presented and nobody asks why. Without causes and countermeasures, the monthly review is a reporting meeting, and the process stops producing learning.

Template before thinking

The X-matrix is filled in before the objectives are debated, and the grid looks complete. It records choices nobody made.

The failures above are usually Synthesis & Story: the work was done, but it never became one clear message a client could act on.

Origin

Hoshin kanri grew out of Japan's shift in the early 1960s from statistical quality control to company-wide quality control, in firms competing for the Deming Prize. Bridgestone Tire and Toyota are usually credited with formalizing it, and Komatsu refined it. Accounts differ on who first used the term, and there is no single founder. Yoji Akao, a quality professor, edited the 1991 Productivity Press book that gave Western readers a common vocabulary.

The plan-do-check-act cycle is the shared base. Management by objectives is often listed as an ancestor, but Japanese companies adopted Drucker's version under a different name and practiced it separately, so sources disagree on how much it shaped hoshin. The term is generic, and consultancies sell their own versions under names such as strategy deployment, so check what a given vendor's version includes before you compare.