Catchball is a structured two-way dialogue used in Hoshin Kanri to develop alignment around important objectives.
Instead of leaders simply cascading goals downward, Catchball allows goals, measures, methods, resources, and feasibility to move back and forth between levels.
The metaphor is simple: one person throws the idea, another catches it, considers it, improves it, and throws it back.
Why Catchball matters
Strategy often fails because goals are assigned without enough understanding of operational reality.
A leadership team may define an objective that sounds reasonable but ignores resource constraints, process capability, competing priorities, timing, technical dependencies, or local knowledge.
Catchball exposes these issues before execution begins.
Catchball inside Hoshin Kanri
Hoshin Kanri connects long-term direction with breakthrough objectives, annual priorities, measures, and execution.
Catchball strengthens that process by creating dialogue between levels.
Leadership may propose reducing customer lead time by 30 percent.
The value-stream team may identify that the largest delay comes from engineering approval, meaning production alone cannot deliver the target.
The objective can then be refined with better ownership and cross-functional action.
What gets discussed
Catchball may address objective wording, target level, measurement method, ownership, resources, timing, risks, dependencies, and proposed countermeasures.
The goal is not consensus on every detail.
The goal is informed alignment.
Catchball is not negotiation to lower the target
A weak Catchball process becomes: “The target is too hard, so reduce it.”
That misses the point.
The discussion should use evidence.
Ask what process condition prevents the target, what capability is required, which resources are missing, what tradeoffs exist, and what countermeasures are possible.
Connect strategy to the Gemba
Catchball prevents strategy from becoming disconnected from the work.
Teams close to the process contribute knowledge that may not be visible at executive level.
This is consistent with Gemba and Respect for People.
People are expected to think about the system, not simply receive targets.
Use PDCA after alignment
Catchball improves the plan, but execution still requires learning.
PDCA helps teams test whether the chosen actions actually move the strategic measure.
If the hypothesis fails, the organization should learn and adjust rather than hide the gap.
Common mistakes
One-way cascading, endless discussion, treating pushback as resistance, failing to clarify ownership, and ignoring cross-functional dependencies all weaken Catchball.
Practical sequence
- Define the strategic objective.
- Share the desired outcome and rationale.
- Ask the receiving level to assess feasibility.
- Identify constraints and dependencies.
- Refine measures and ownership.
- Agree on the contribution required at each level.
- Confirm resources and support.
- Execute using PDCA.
- Review actual performance.
- Repeat the dialogue when assumptions change.
The practical lesson
Catchball turns strategy deployment into a learning process.
It improves both commitment and quality of thinking before the organization commits resources to execution.