Hoshin Kanri, Explained: Cascading Goals Without Losing the Strategy

Hoshin kanri is a method for turning a few long-range goals into agreed annual goals at every level of a company, and then checking them on a fixed rhythm. It came out of Japanese quality management, where it is also called policy deployment. Its distinctive move is catchball: goals are passed down, questioned, adjusted and passed back up until each level has agreed what it will deliver and how it will be measured.

Most companies already cascade goals in some form. The leadership team sets priorities, departments are told about them, and individual objectives appear in the review form. What hoshin kanri adds is the part most cascades skip: the negotiation in the middle, and the check that the pieces still add up to the strategy.

What hoshin kanri means

The name is usually translated as something close to "direction management." Hoshin carries the sense of a compass needle or a heading; kanri means management or control. The point of the name is that the whole organization should be steering by the same heading.

The method grew up in Japanese manufacturers in the decades after the Second World War, as part of the wider total quality movement. It borrowed the Plan–Do–Check–Act cycle from quality management and the idea of agreed objectives from management by objectives, then combined them into an annual planning discipline. Yoji Akao's writing on policy deployment did much to bring it to English-speaking managers, and it is still most common in manufacturing and healthcare, though nothing in it is specific to either.

Three ideas sit at its core:

1. Few goals. A small number of breakthrough objectives that would change the company, not a long list of everything worth doing.
2. Every level translates. Each layer works out what it must deliver for the goals above to be met, in its own terms.
3. Regular checking. Progress is reviewed monthly or quarterly against the plan, and the plan is corrected, not just reported on.

The parts of hoshin kanri

A full hoshin kanri cycle has five layers, usually laid out on one sheet.

The X-matrix

The sheet that holds all of this is called the X-matrix. Picture a square divided into four sections around a central X. Breakthrough objectives sit on one side, annual objectives on the next, improvement priorities on the third and metrics on the fourth. The corners between them are small grids where dots mark which item supports which. A final column lists the people responsible.

The X-matrix is useful because it is a single page and because the dots expose gaps. An annual objective with no improvement priority beneath it is a wish. A priority with no metric is a project that cannot fail. A priority that supports none of the annual objectives is someone's favorite initiative, and a good moment to ask why it is on the list.

It is also intimidating. A fully populated X-matrix can carry dozens of dots and takes practice to read. Many companies that try hoshin kanri give up at this stage, which is a shame, because the idea underneath is simpler than the diagram.

Catchball: goals are negotiated, not handed down

Catchball is the back-and-forth between levels that turns a top-down instruction into an agreed commitment. Leadership "throws" a goal to the level below. That level works out what it would take, what it would need, and what it cannot do with what it has, then throws it back with questions and a counter-proposal. The ball goes back and forth until both sides agree.

A short example. Leadership sets an annual objective: raise on-time delivery from 89% to 95%.

1. Leadership to Operations: "We need 95% on time by year end. What will it take?"
2. Operations back: "We can reach 93% with better route planning. Getting to 95% needs a second dispatcher, or we stop accepting same-day orders after 2 p.m."
3. Leadership back: "No new headcount this year. Can you get to 95% if Sales moves the cut-off?"
4. Operations, with Sales: "Yes, if the cut-off moves to noon and Sales owns telling customers. We'll own route planning and the on-time measure. Sales owns the share of orders placed before noon."
5. Agreed: two department KPIs, two owners, one company objective, and a decision about the cut-off that would never have surfaced in a one-way cascade.

That fourth step is the reason catchball exists. The original goal belonged to one department; the negotiation showed it needed two.

Why cascading goals break between organization and department

Most cascades do not fail at the top or the bottom. They fail in the middle, where the company's priorities are supposed to become each department's measures. Three things go wrong there.

The number is copied, not translated. The company says "grow recurring revenue," and every department is given "recurring revenue" as a goal. Nobody in Finance or Operations knows what to do differently on Monday. The translation step, the one that turns a company priority into a different measure for each function, is the work. The way the levels should relate is laid out in company, department and individual KPIs.

Departments relabel what they were already doing. Asked to support the strategy, each department looks at its existing plan and finds a way to describe it in the strategy's words. The cascade looks complete, and nothing has changed.

Nobody throws the ball back. Goals arrive with no chance to say "we cannot do this with what we have." Capacity problems stay hidden until the third quarter, when they show up as missed targets.

The result is that the strategy becomes hard to see from inside the company. Sull, Sull and Yoder, writing in MIT Sloan Management Review in 2018, found that only 28% of executives and managers responsible for executing strategy could name three of their company's strategic priorities. A cascade that copies numbers downward, without a conversation, is one of the ways that happens. Another is a leadership team that agrees in the room and means different things outside it, the problem described in leadership alignment.

A plain-language hoshin kanri for a 50–500 person company

You do not need an X-matrix, a policy deployment office or a new vocabulary to get most of the value. For a company of 50 to 500 people, a lighter version works, built around four plain questions asked in this order:

1. Where are we now? An honest read of the current numbers and last year's results.
2. Where are we going? The two or three changes that matter most over the next few years.
3. What could affect us? The risks, constraints and outside forces that shape what is realistic.
4. What must we deliver? This year's objectives, each turned into KPIs for the organization and for every department, with one owner each.

Run it like this:

The single sheet is your X-matrix with the hard parts removed. Each department KPI names the organization KPI it serves. If one serves nothing, ask why it is there. If an organization KPI has nothing beneath it, it has no plan.

The method for writing each KPI is in how to create KPIs; this article is about how they connect. If it helps to do the first pass with someone outside the company in the room, that is what our free working session is for.

How the four questions map onto hoshin kanri

The mapping is close enough that a company running the four questions every year, with a genuine catchball step, is doing hoshin kanri in everything but name.

What to keep and what to skip

Keep: few goals, translation at each level, the back-and-forth, one page, and a fixed monthly or quarterly check where corrections are decided.

Skip, at least at first: the full correlation grid, separate "bowling charts" for every metric, and any terminology your managers would need a glossary for. The vocabulary is a means. A team that argues usefully about whether Operations can reach 95% has learned the important part.

If you want to see the line from strategy to each department as a picture rather than a table, a strategy map does that job, and pairs well with the one-page sheet above.

Frequently asked questions

What is catchball in hoshin kanri?

Catchball is the negotiation between levels of the organization when goals are set. A goal is passed down, the receiving level replies with what it would take and what it cannot do, and the goal goes back and forth until both sides agree. It turns an instruction into a commitment and surfaces capacity problems early.

Is hoshin kanri the same as OKRs?

No, though they share ideas. Both limit the number of goals and connect levels of the organization. Hoshin kanri is an annual planning discipline with multi-year objectives, a formal negotiation step and a regular check cycle; OKRs are usually quarterly and lighter on how goals are negotiated between levels.

What is an X-matrix?

The X-matrix is the one-page sheet traditionally used in hoshin kanri. It links long-range objectives, annual objectives, improvement priorities, metrics and owners, with small grids showing which item supports which. Its value is that gaps become visible on one page.

Does hoshin kanri work outside manufacturing?

Yes. It started in manufacturing and is common in healthcare, but the core ideas of few goals, translation at each level, catchball and a regular check apply to any company. Service businesses often do well with a lighter version that keeps the negotiation and drops the heavier diagrams.

How long does a hoshin kanri planning cycle take?

For a company of 50 to 500 people, the planning itself can usually be done in a few weeks: one or two leadership sessions, a round of department drafts and a catchball session. The checking runs all year, monthly or quarterly.