Catchball

Definition

Catchball is the iterative back-and-forth dialogue between management levels that aligns objectives, plans, and targets. Rather than cascading goals top-down (senior management sets targets and lower levels comply) or building them bottom-up (each level proposes what it thinks it can achieve), catchball creates alignment through multiple rounds of exchange.

The metaphor is playing catch: one person throws the ball, the other catches it, considers it, and throws it back — perhaps adjusted. After several rounds, both parties hold a shared understanding of what needs to be achieved, why it matters, and how it will be accomplished. The result is genuine commitment rather than passive compliance.

Japanese Origin

Kyacchi booru (キャッチボール) is written in katakana as a borrowed English term — literally “catch ball,” referring to the children’s game of tossing a ball back and forth. Japanese management adopted this playful metaphor to describe the serious business of aligning organizational objectives. The image is apt: both parties must participate actively, and the exchange continues until alignment is reached.

How It Works

In the hoshin kanri process:

1. Senior leadership defines breakthrough objectives and high-level targets for the coming period
2. These are shared with the next level — not as orders but as proposals to discuss
3. The next level examines the objectives against their understanding of current capability, resources, and constraints
4. They respond with questions, concerns, and counterproposals: “We can achieve X if we get Y resource” or “The real constraint is Z, not what you assumed”
5. Senior leadership considers the feedback and adjusts — or explains why the original target stands
6. The exchange continues until both levels agree on objectives, targets, and the means to achieve them
7. The aligned objectives are then catchballed to the next level down, and the process repeats

What makes it different from negotiation:

Catchball is not bargaining or horse-trading. The intent is not to split the difference between what management wants and what the team thinks is possible. The intent is to surface reality — what is actually achievable, what the real obstacles are, and what resources or changes are needed. Both sides are trying to reach the best plan, not to win a negotiation.

The role of the A3:

At Toyota, catchball often happens through A3 reports. A manager asks a subordinate to develop an A3 on a particular objective. The subordinate researches, analyzes, and proposes a plan. The manager reviews it, asks questions, and sends the subordinate back to refine. This cycle may repeat several times. The A3 is both the vehicle for the dialogue and the record of the resulting agreement.

Common Mistakes

One-way cascade disguised as catchball. If senior management presents objectives and the only acceptable response is agreement, that is top-down deployment regardless of what it is called. True catchball requires that lower levels can push back, provide data, and influence the final plan. If the targets never change through the process, catchball is not happening.

Endless back-and-forth without resolution. Catchball is iterative but not infinite. After a reasonable number of exchanges, alignment must be reached and commitments made. If the process drags on without resolution, it becomes a stalling mechanism rather than an alignment tool.

Skipping levels. Catchball works between adjacent levels. Senior management catchballing directly with frontline workers — skipping middle management — creates confusion about roles and ownership. Each level catches the ball from the level above and throws it to the level below, adding their own analysis and context at each step.

Treating catchball as optional in hoshin kanri. Without catchball, hoshin kanri degenerates into traditional top-down target-setting. The back-and-forth dialogue is what distinguishes hoshin kanri from MBO (Management by Objectives) — it builds understanding and commitment that pure target deployment cannot achieve.