Bringing goals to the floor with Hoshin Kanri: catchball
In brief
A goal handed down as an order is never owned on the floor. Catchball is throwing the goal back and forth at every level until both sides own it. This step of Hoshin Kanri and the manager's duty to listen.
23 October 2026 · 4 min read
Sample company · demo dataX-matrix
The Lean Enterprise Institute lexicon defines Hoshin Kanri as a strategy deployment method that spreads the company's goals through every layer in the same direction and follows them with the PDCA cycle. The step most often skipped is catchball: senior management proposes a goal, the next layer weighs it against its own conditions and either accepts it or throws it back with reasons. The ball travels until both sides own the goal.
Why it must be thrown back
If a goal only comes down from above, one of two things happens: the floor says “impossible” and the goal stays on paper, or it is accepted in silence and found unmet at year end. Catchball prevents both. When the lower layer throws the goal back it says “for this goal we need this resource, this project, this time”; the upper layer either gives the resource or corrects the goal. The Lean Enterprise Institute's definition of nemawashi describes a similar principle: a proposal is matured by talking to everyone involved before formal approval.
Top down: long-term goal, annual goal, project, indicator.
Bottom up: capacity, obstacle, resource need, counter-proposal.
Agreement: a written goal, an owner, an indicator and a review calendar.
The manager's job is to listen
In catchball the manager's role is not to persuade but to listen. The ball coming back from the floor is the best information management has about whether the goal is realistic. A manager who reads a returned goal as resistance gets no ball back next year; nobody throws it back, everyone accepts and no goal is met. Respect for people here becomes a way of setting goals: the goal is written with the person who will meet it.
Monthly follow-up: what happens off target
The annual Hoshin plan lives through monthly review. Each indicator is compared with its target month by month; an off-target month is not an accusation but an opportunity for a countermeasure. The countermeasure has an owner, a date and a verification of its own. At year end the matrix is rebuilt and catchball starts again.
How to run catchball
Senior management proposes three to five goals; ten goals means no goals.
Each unit translates the goal into its own language: “reduce scrap” becomes “reduce setup loss at station two” for a line.
The unit writes the project, resource and indicator the goal needs and throws the ball back.
Senior management provides the resource or corrects the goal; the agreed goal is written down.
The same loop repeats one layer down; the goal travels all the way to the team on the floor.
Common mistakes
The most common mistake is turning catchball into a presentation round: goals are explained, questions are taken, nothing changes. The second is taking a returned ball personally. The third is bringing the goal to the floor while keeping the indicator at the centre; if a team does not know what it measures, it cannot own the goal. The fourth is quietly changing the goal mid-year; a changed goal needs catchball again. What these mistakes share is that listening was skipped.
Sample company · demo dataScorecards
How it is done in Gemy
The Hoshin X-matrix shows a unit's strategy for one year in a single table: long-term goals to the south, this year's goals to the west, improvement projects (Kobetsu, records, actions) to the north, indicators to the east. The corner cells are relationships; a goal or project nobody is linked to stands out.
The Bowling Chart shows progress for each annual goal and the target / actual values of linked indicators month by month; from an off-target month you open the indicator page and an action. A month without data is not counted as zero.
The matrix and Bowling Chart download as one A3 PDF; work the person cannot see is printed as “Hidden source”.
The matrix owner edits their matrix; if a role is limited to a unit, only that unit's and its sub-units' matrices are visible. The feature is a module the company switches on.
Catchball itself is not a screen; it is a conversation between a manager and the team. The matrix only holds the agreed result.
In short
Hoshin Kanri spreads a few goals through every layer in the same direction; catchball makes sure those goals are owned through conversation rather than handed down as orders. The goal is written with the person who will meet it; a returned ball is information, not resistance. In monthly follow-up an off-target month is not a matter for blame but an opportunity for a countermeasure. The manager's job is to listen rather than persuade; a team that is not listened to does not throw the ball back next year, it accepts in silence and no goal is met.
Takt time is the customer's pace; Yamazumi stacks each station's load against that pace. Calculating takt, reading the chart, the balancing sequence and how to explain balancing to the operator.
Autonomous maintenance means the person who knows the machine best, the operator, takes over its daily care. The content of the first three steps, the abnormality tag, the CIL standard and the division of work between operator and maintenance.
Kamishibai checks with short cards, at regular intervals, whether a standard is being followed on the floor. The structure of a card, the layers, good and bad question examples and the path of a red card.
7 November 2026 · 5 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.