What Is Catchball in Hoshin Kanri?
Catchball (キャッチボール) is the two-way negotiation through which hoshin targets and methods are aligned between organizational levels. It is a real term used inside Toyota, said in English and written in katakana. The dialogue continues for as many rounds as it takes until the goal and the methods are both clarified.
Catchball (キャッチボール) is the two-way negotiation process through which hoshin items are aligned between levels of an organization: direction flows down, feasibility flows up, and targets and methods are jointly shaped until each level owns its piece. It is a real term used inside Toyota, said in English and written in katakana.
Catchball is the mechanism that keeps hoshin kanri from becoming top-down target dictation. This article covers what the exchange actually negotiates, where the baseball metaphor helps and where it misleads, and the conditions the practice depends on.
- The term is genuine Toyota vocabulary, not a consulting layer added in the West
- Both targets and methods are on the table, and the rounds continue until both are clarified
- Vertical catchball depends on horizontal coordination to produce plans that can actually be executed
Where does the word catchball come from?
The word is English, adopted into Japanese business usage and written in katakana as キャッチボール, the same word Japanese uses for two people throwing a baseball back and forth. Inside Toyota, people say it in English. Several Western books have described the practice, with varying accuracy, but the term is not their invention: it is working vocabulary inside the company itself.
The image is apt as far as it goes. One level throws (a proposed direction or target), the other catches and throws back (a response, a constraint, a counter-proposal). Nobody keeps the ball.
Where the metaphor fails is important. In a game of catch, the same ball goes back and forth unchanged. In real catchball, the content changes and improves with every catch and return. Each round sharpens the goal and the methods: the receiving manager’s response surfaces constraints the sender could not see, the sender’s next throw adjusts scope or resources, and the proposal that finally settles is better than what either side started with. The exchange is not a ball being passed. It is a plan being forged.
What gets negotiated in catchball?
Three things: the targets, the countermeasures, and the resources required. The inclusion of countermeasures, the methods, is what most distinguishes the practice from ordinary target-setting.
The process begins after the president sets Company Hoshin. Department managers develop their own hoshin items in response, and those proposals go back up for review and discussion, not simply down for execution. A department-level hoshin item like “overseas engineering support activities” is a direction requiring judgment about scope, priorities, and resource allocation, not a mechanical fraction of a company number. The same negotiation then repeats between department managers and section managers.
At each handoff, the receiving manager has an obligation, not merely permission, to push back where targets are unrealistic, resources are insufficient, or the proposed methods will not work. That upward flow is the point: it surfaces information senior leaders cannot see from their position, and it converts recipients into owners.
The number of rounds is not fixed. The exchange continues until a goal and a set of methods are clarified successfully. That is the finish line, not a meeting count.
What does a catchball exchange look like?
A representative exchange, compressed to its skeleton:
| Round | Direction | Content |
|---|---|---|
| 1 | Down | Company hoshin asks the department to expand overseas engineering support next year |
| 2 | Up | Department manager proposes a scope and target, and flags that current staffing supports two regions, not three |
| 3 | Down | Executive adjusts: two regions this year, third deferred, with two engineer transfers approved |
| 4 | Up | Department manager commits to the revised target with named countermeasures and a review schedule |
Note what changed across the rounds: not just the number, but the scope, the resourcing, and the methods. Round 4’s plan did not exist in round 1. That improvement across rounds is what the practice exists to produce, and it is why a single feedback meeting stapled onto a cascade does not qualify.
Catchball also has a relative in ordinary Toyota decision-making: nemawashi, the informal one-on-one groundwork done before formal proposals. Catchball is the structured, hierarchical version of the same instinct, that commitments worth making are negotiated before they are declared.
Why does catchball depend on horizontal coordination?
Catchball runs vertically, between levels of the hierarchy. But most hoshin objectives worth having cannot be delivered by one department. A department manager cannot honestly commit to a hoshin item that requires another department’s cooperation unless some mechanism aligns the two.
At Toyota, that mechanism is the Function Meeting system: standing management forums organized by Quality, Cost, Production, Technology, and Sales/HR that cut across departmental boundaries. Global 10, Eiji Toyoda’s 1978 challenge to raise Toyota’s global production share from 7% to 10%, required Product Development, Production Engineering, Manufacturing, and Sales to coordinate on initiatives none could achieve alone.
Without a horizontal layer, catchball degrades into a series of bilateral manager-to-boss negotiations, each internally reasonable and collectively incoherent. The plans align up and down and conflict side to side, at exactly the boundaries (shared resources, handoffs, conflicting timelines) where execution lives.
Where does catchball stop?
At Toyota, the documented hoshin cascade runs from the president to department managers to section managers, and no further: there is no individual-employee hoshin. But the hoshin does not vanish below that level. It changes form. At the supervisor level, hoshin-aligned KPIs and improvement themes are carried through the FMDS floor management boards and 3 Pillar daily management activity, and team members contribute through QC circles. In effect, Toyota does have hoshin at the supervisor level, implemented through the daily management system rather than through personal hoshin documents. That nuance is easy to miss and critical: the boundary is where the paperwork stops, not where the direction stops.
Two lessons follow, and they should not be collapsed into one. First, Toyota’s boundary is Toyota’s design choice, matched to its culture, capability, and daily management maturity. Where another organization stops its catchball cascade depends on the same factors; there is no single right level. Second, the transferable principle is the change of form: at some point the cascade should become daily management rather than continue as personal strategy paperwork. Extending unchanged hoshin documents to every individual multiplies paperwork and turns a management negotiation into an appraisal-season exercise, which is one of the standard ways hoshin kanri stops working.
What are the common failures of catchball?
One round, pro forma. The cascade meeting where targets are presented and “questions are welcome” is not catchball. If nothing changed between the first throw and the final commitment, no negotiation happened.
Negotiating targets but not methods. When only the number is discussed, the exchange becomes haggling. The methods conversation is where feasibility gets tested and where the receiving manager’s knowledge actually enters the plan.
Catchball without the horizontal layer. Covered above: bilaterally negotiated plans that collide laterally.
No finish line. The opposite failure: exchanges that circulate indefinitely because nobody is accountable for reaching clarity. The rounds continue until goal and methods are clarified, and then they stop, the commitment is made, and execution begins.
Frequently asked questions
Is catchball a real Toyota term? Yes. Catchball is used inside Toyota, said in English and written in katakana (キャッチボール). It is not a Western consulting invention layered onto Toyota practice, although Western books have described it with varying accuracy.
What gets negotiated in catchball? Both the targets and the means. A manager receiving a hoshin direction responds with proposed targets, countermeasures, and resource requirements, and pushes back where targets are unrealistic or methods will not work. Negotiating only the numbers, without the methods, is not catchball.
How many rounds of catchball are there? The number of rounds is not fixed. The exchange continues until a goal and a set of methods are clarified successfully. A single pro-forma feedback meeting does not qualify, and neither does endless circulation: the exchange has a finish line, which is genuine clarity and ownership on both sides.
What is the difference between catchball and cascading targets? In a target cascade, the number flows down and accountability flows up. In catchball, the direction flows down, the feasibility assessment flows up, and the final commitment is jointly shaped. The difference shows in execution: people carry out plans they helped build with more judgment and persistence than plans they were handed.
Does catchball work without cross-functional coordination? Poorly. Catchball runs vertically, between levels, but most hoshin objectives require cooperation across departments. At Toyota, standing Function Meetings (Quality, Cost, Production, Technology, Sales/HR) handle that lateral alignment. Without some equivalent, catchball becomes a bilateral negotiation disconnected from the dependencies that determine whether the plan can be executed.
Related reading
- Hoshin Kanri: How Direction Becomes Daily Work — the full guide to Toyota’s system
- Catchball — encyclopedia entry
- What Are the 7 Steps of Hoshin Kanri? — where catchball sits in the taught models
- Nemawashi — the informal cousin of catchball
- Does Toyota Use Hoshin Kanri? — Toyota’s practice, dated and sourced
Art Smalley is president of Art of Lean, Inc. This article draws on firsthand knowledge of the term as used inside Toyota Motor Corporation in Japan and on Mikio Sugiura’s Japanese-language account of Toyota’s hoshin kanri system (Toyota Global 10). AI was used in the editing of this article.