Catchball in Hoshin Planning

Catchball is the back-and-forth dialogue in hoshin planning where goals and plans are tossed between management levels like a ball, up and down the organization, until targets, methods, and resources are negotiated into commitments people actually own. It turns top-down direction into two-way agreement.

Most strategy deployment fails in the handoff. Leadership sets a target, cascades it down as a number, and the floor receives a demand it had no part in shaping and no real belief in. Catchball is the fix for that handoff. Instead of throwing a target over the wall, each level throws it, then listens: the receiver pushes back with what is realistic, what it will take, and what obstacles stand in the way, and the ball comes back up. A goal that survives a few rounds of catchball is no longer an order; it is a commitment, and commitments get met at a rate orders never do.

What Is the Catchball Process?

Catchball is a structured, iterative dialogue used within hoshin kanri to align goals and plans across levels of an organization. The name captures the mechanic: a proposed objective is tossed down to the next level, which catches it, examines whether it is achievable and how, and tosses back its response, questions, counterproposals, resource needs, and obstacles it can already see. Senior managers set the direction; the teams who will do the work shape the how, the timing, and the targets they can honestly stand behind. The exchange repeats until both sides agree on a plan neither could have written alone. The Lean Enterprise Institute describes it as a dialogue in which, once major goals are set, planning becomes both top-down and bottom-up, a conversation between senior managers and project teams about the resources and time available and needed to hit the targets.

It is closely tied to nemawashi the lean practice of building consensus and pre-agreement before a decision is finalized, and both exist for the same reason: a decision that people helped shape is a decision they will carry out. Catchball is where the abstract direction of the business meets the concrete reality of the floor, and the two get reconciled before anyone commits resources.

Why Does Catchball Matter for Strategy Deployment?

Because top-down targets without dialogue produce compliance at best and quiet sabotage at worst. When a number lands on a team that had no say in it, one of three things happens: they miss it and feel it was never fair, they hit it by cutting a corner nobody sanctioned, or they nod in the meeting and do what they were already doing. Catchball breaks that pattern by forcing the target through a reality check before it is locked. The team gets to say "that is achievable if we solve these two obstacles and get this fixture," and now the target and the plan to reach it exist together. Ownership is the whole point: people execute plans they helped build with an energy they never bring to plans handed to them. This is the same principle that underpins a healthy lean culture where respect for people means trusting the folks closest to the work to shape how it gets done.

Catchball also surfaces problems early, while they are still cheap. The obstacles a team raises during the exchange are the obstacles that would otherwise appear as missed milestones six months later. Hearing them up front lets leadership adjust the target, reallocate resources, or sequence the work differently, before the plan is set in concrete.

How Do You Run a Catchball Session? A 7-Step Method

1. Set clear direction first. Leadership defines the few true priorities, the "true north" and the small number of breakthrough objectives for the year. Catchball negotiates the how and the how-much, not the whether; without clear direction, the exchange becomes an unfocused wish list.
2. Draft, then throw down. Each level proposes draft targets and the means to reach them to the level below, framed explicitly as a starting point open to challenge, not a finished order.
3. Catch and pressure-test. The receiving team examines the target against reality: Is it achievable? What method would we use? What obstacles do we already see? What resources, time, and support would it take?
4. Throw it back with substance. The team returns its response, agreement where it fits, counterproposals where it does not, and a clear statement of what it needs. Silence is not agreement; a real catch always comes back with something.
5. Iterate until aligned. Repeat the exchange as many rounds as it takes, usually two or three, until the target, the method, and the resources form a plan both sides believe in. Do not rush to close.
6. Confirm ownership and commit. Once aligned, each level commits to its part in writing, often on an X-matrix or bowling chart, so the agreement is visible and specific rather than a vague nod.
7. Review and adjust on a cadence. Catchball is not a one-time event. Through the year, plan-do-check-act reviews reopen the dialogue when reality diverges from the plan, and the ball starts moving again.

What Does a Catchball Exchange Look Like in Practice?

Take a real-shaped example. Leadership sets a breakthrough objective: cut customer complaints on Product A by 40 percent this year. That direction is thrown down to the value-stream manager, who catches it, looks at the complaint data, and sees that most complaints trace to two defect modes on one line. She throws back a counterproposal: 40 percent is reachable, but only if two things happen, a fixture redesign that needs capital, and time to build real standard work on the problem operation. That response goes up; leadership agrees to fund the fixture but asks whether the timeline can be pulled in. The value-stream manager throws the target down again, now to the frontline team, who catch it and raise the last obstacle: the current inspection step misses one of the defect modes entirely. With that surfaced, the team proposes adding a check, the plan firms up, and everyone commits. Notice what happened: the original 40 percent survived, but the plan to reach it was written by the people who could see where it would break. That is catchball doing its job.

What Is the Difference Between Catchball and Just Getting Buy-In?

Buy-in is asking people to agree to a plan already written; catchball is letting them change it. That is not a small distinction. In a buy-in meeting, the target is fixed and the conversation is about persuasion, so the honest objections stay unsaid because raising them looks like resistance. In catchball, the target is explicitly negotiable within the boundaries of the direction, so objections are the point, not a problem. The team that catches the ball is expected to throw it back with changes. This is why catchball produces plans that are more accurate, not just more accepted: the people who know where the process actually breaks are given real authority to reshape the plan around those breaks. Buy-in gets you compliance; catchball gets you a better plan and the ownership to run it.

Where Does Catchball Fit With the Rest of Lean?

Catchball connects the strategy layer to the daily work. The targets it settles become the objectives that kaizen events and daily improvement chip away at; the standards those improvements produce, captured as standard work are how gains are held; and the gemba walks leaders run are partly a live continuation of catchball, checking on the floor whether the agreed plan is holding against reality. It is the negotiation engine inside hoshin kanri, and hoshin is the thread that keeps floor-level improvement pointed at what the business actually needs rather than at whatever is loudest this week. Get catchball right and improvement stops being random; every project on the floor traces back to an agreed priority.

How Do You Keep Catchball From Becoming a Rubber Stamp?

The failure mode is catchball in name only, where the ball is thrown down, caught, and thrown straight back with "sounds good" because pushing back feels unsafe or pointless. Two things prevent it. First, psychological safety: if the last team that raised a hard obstacle got overruled and remembered for it, no one throws the ball back with anything real. Second, visible follow-through: when a team's counterproposal actually changes the plan, everyone learns the exchange is genuine, and the next round gets more honest. Leaders should treat a catch that comes back with no changes as a warning sign, not a win. A whole cascade of instant agreement usually means the dialogue is theater. The Lean Enterprise Institute's own materials on strategy deployment stress this two-way, resource-and-reality dialogue precisely because the top-down-only version is the common failure (Lean Enterprise Institute, Strategy Deployment). This works far better when the plan and its check-ins live somewhere everyone can see. That is the pattern Harmony deploys on running floors: targets, standards, and daily checks become live station-level capture, so the agreed plan and how it is actually tracking are visible the same shift, not buried in a binder (live floor visibility). Pair it with disciplined production scheduling so the commitments made in catchball line up with what the plant is physically able to run.