Catchball in Hoshin Kanri: How Strategy Deployment Cascades Goals

Catchball in Hoshin Kanri is a structured back-and-forth negotiation in which leaders throw a proposed objective to the level below, who catch it, test it against reality, and throw back their own targets, constraints, and counter-proposals until both sides commit. The name comes from the mental image of playing catch: the goal is never simply handed down and enforced, it is passed repeatedly between levels until it lands as something the receiving team believes is achievable and worth owning. Hoshin Kanri (often translated as policy deployment or strategy deployment) is the lean planning system that aligns a factory's few vital annual breakthrough objectives with the daily work on the floor. Catchball is the mechanic that keeps that cascade honest, because a target nobody negotiated is a target nobody defends.

Why catchball exists at all

Traditional cascades fail in a predictable way. Executives set a number, middle managers relay it, and the line receives an order it had no hand in shaping. When the number turns out to be impossible (or trivially easy), nobody flags it, because flagging it feels like insubordination. The plan then quietly dies in the gap between the boardroom and the machine.

Catchball attacks that failure directly. By requiring each level to catch a proposal, stress-test it, and return a considered response, it does three things at once:

• Surfaces reality early. The people closest to the equipment know the real cycle times, changeover pains, and staffing constraints. Catchball forces that knowledge into the plan before it is frozen.
• Builds genuine ownership. A goal you helped shape is a goal you will fight for. Commitment replaces compliance.
• Aligns means with ends. Leaders own the "what" and "why"; teams own the "how" and "how much is realistic." The dialogue reconciles the two.

This is the same logic behind the PDCA cycle that underpins all of Hoshin Kanri: plan collaboratively, do, check, and adjust rather than dictate and hope.

How the cascade actually flows

Hoshin Kanri deploys through nested levels, and catchball happens at every handoff. A typical annual cascade moves through four rounds:

1. Throw down. Leadership proposes a breakthrough objective and a rough target, framed around the "true north" the business is chasing this year.
2. Catch and analyze. The receiving level examines the target against current capability, resources, and competing priorities. They gather data rather than react emotionally.
3. Throw back. The team returns a counter: a committed target they can defend, the resources they need, the risks they see, and any assumptions leadership got wrong.
4. Reconcile and commit. Both sides converge on a number and the supporting actions, then the objective cascades one level deeper and the game repeats.

The tool that records this is the X-matrix, which links objectives to strategies, to annual improvement priorities, to the metrics that prove progress. Catchball is what fills the matrix with numbers people actually believe.

A worked example: cascading an OEE target

Suppose plant leadership sets a breakthrough objective to lift plant-wide Overall Equipment Effectiveness from 62 percent to 75 percent this year. Here is how catchball turns that headline into a defensible plan.

Round 1 (throw down): Leadership asks the packaging value stream for +13 OEE points, distributed evenly, so roughly +1 point per month.

Round 2 (catch and analyze): The value stream lead breaks OEE into its three factors. Current state is Availability 80 percent, Performance 85 percent, Quality 91 percent, which multiplies to about 62 percent. A Pareto analysis of downtime shows 70 percent of lost availability comes from changeovers and unplanned stops on one filler line. A flat +1 per month ignores that concentration.

Round 3 (throw back): The team returns a sharper counter. They commit to lifting Availability from 80 to 90 percent by attacking changeovers and stops (0.90 times 0.85 times 0.91 equals about 70 percent), which alone delivers +8 points. Reaching the full 75 percent needs Performance up to 90 percent too (0.90 times 0.90 times 0.91 equals about 74 percent, with quality gains closing the last point). They ask for two things: budget for a quick-changeover project and a reliable downtime data feed, because their current numbers are hand-logged and untrusted.

Round 4 (reconcile): Leadership accepts the phased curve (front-loaded availability wins, performance later) and funds the data feed. The committed target is now owned, sequenced, and tied to a root cause rather than a wish. Supporting maintenance actions link to the plant's CMMS so preventive work reduces the very stops that cap availability.

Roles and the rules of a good throw

Catchball only works if the exchange stays disciplined. A few rules separate real negotiation from theatre:

• Data beats opinion. A counter-proposal must be backed by evidence: cycle-time studies, downtime logs, scrap rate trends. "It feels too aggressive" is not a throw.
• Leaders defend the why, not the how. Once the objective's intent is clear, the receiving team owns the method. Micromanaging the "how" kills ownership.
• Constraints are stated openly. If a target collides with the plant's real bottleneck, say so; the theory of constraints is usually a better guide to where gains are possible than an even split across lines.
• Silence is not agreement. A level that returns no counter has not caught the ball, it has dropped it. Push back and ask for the analysis.

Common pitfalls that break the game

Catchball degrades in recognizable ways. Watch for these:

• Pseudo-catchball. Leadership announces the number, invites "feedback," then ignores it. Teams learn the dialogue is fake and stop investing in it.
• Endless throwing. Without a decision deadline, rounds multiply and nothing commits. Cap the exchange (often two to three rounds per level) and force closure.
• Sandbagging. Teams lowball targets to guarantee they hit them. The antidote is transparent baselines and a shared "true north" that makes easy targets obviously inadequate.
• No measurement backbone. If the numbers being negotiated are unreliable, the whole exchange is guesswork. This is why deploying against trustworthy, automatic metrics matters more than the negotiation ritual itself.

Structured problem-solving methods such as A3 problem solving pair naturally with catchball, giving each committed objective a one-page home for its analysis, countermeasures, and follow-up.

Where Fabrico fits

Catchball lives or dies on the quality of the data each level throws back. If Availability, Performance, and Quality are argued from hand-written logs, negotiations collapse into opinion. Fabrico is the real-time data foundation that removes the guesswork. Its real-time OEE and production monitoring give every level the same trusted numbers, and its computer vision can capture machine states even where there is no PLC to tap, so the micro-stops and changeover losses that dominate the example above are actually visible. When a team commits to lifting availability, Fabrico's field-ready CMMS (work orders, assets, preventive scheduling, and spare parts) turns that commitment into scheduled maintenance that attacks the root-cause stops, and dashboards then show whether the negotiated curve is being met month by month. Because Fabrico is EU-built with EU data residency, the whole deployment stays on a compliant footing. Explore the OEE and production monitoring and CMMS capabilities to see how the data foundation supports a Hoshin cascade.

Frequently Asked Questions

Is catchball the same as top-down or bottom-up planning?

Neither, and that is the point. Catchball is deliberately bidirectional. Leadership owns the strategic intent and initial targets (a top-down signal), while the teams doing the work own the feasibility, method, and committed numbers (a bottom-up correction). The final plan is the reconciled product of both directions, which is why it commands more genuine commitment than a purely top-down order or a purely bottom-up wish list.

How many rounds of catchball are normal before committing?

Most levels settle in two to three rounds: an initial throw down, a data-backed counter, and a reconciliation. More than that usually signals a missing baseline, an unclear objective, or unstated constraints rather than healthy debate. Setting an explicit decision deadline for each level keeps the exchange from spiraling into indecision while still leaving room for a real negotiation.

Does catchball only apply to annual Hoshin objectives?

The formal ritual is tied to the annual strategy deployment cycle, but the underlying habit scales down. The same catch-analyze-throw-back pattern works in monthly reviews, in weekly tiered huddles, and in one-off improvement events where a target needs to be reconciled with floor reality. Teams that internalize catchball tend to negotiate goals more honestly at every cadence, not just once a year.

Ready to give every level of your Hoshin cascade the trusted, real-time numbers that make catchball work? Book a Fabrico demo and see how live OEE and a field-ready CMMS turn negotiated targets into measured progress.