Catchball

Catchball is the conversation mechanic that turns lean planning from a memo into a commitment. The idea is straightforward: when a leader sets a goal, they do not throw it over the wall to the team that has to deliver. They toss it back and forth, with pushback and revision, until both sides agree on something realistic. The metaphor is a ball passed between players; the practical reality is two or three rounds of meetings and side conversations that produce a plan everyone can defend.

"A goal handed down is something to comply with. A goal caught and tossed back is something to own."

How catchball works

A catchball cycle usually has three to four rounds. In round one, leadership proposes a goal, often a one-page brief: here is what we want to achieve, here is why, here is the rough number. Instead of asking for commitment, they ask for feasibility analysis. The receiving team studies the work: what would it actually take to hit this, what assumptions are baked in, what are the constraints. Round two is the team coming back with a counter: we can commit to 80 percent of this if you remove this blocker, or we can commit to all of it on a three quarter timeline.

Round three is the leader adjusting. Sometimes the constraint named by the team is real and the goal flexes to match. Sometimes the constraint can be removed (different vendor, more capacity, a different sequence) and the original goal stays. Sometimes leadership pushes back and asks the team to look again at a specific assumption. By round three or four, the goal and the plan to hit it are both adjusted into something both sides genuinely sign up to.

The discipline that holds catchball together is honesty in both directions. The team has to push back when the goal is unrealistic instead of nodding and quietly missing. Leadership has to actually listen and revise instead of going through the motions. Both habits are hard to build but they compound. After two or three annual cycles, teams know that pushback gets a real response, and they put more thought into the pushback. Leadership learns where the real constraints are and gets better at setting goals that stretch without breaking.

Where catchball fits on the shop floor

Imagine a 45-person fabrication shop where the owner has decided next year's breakthrough is "cut lead time from four weeks to two." Without catchball, the owner announces it at the company meeting and assumes operations will figure it out. Three months in, lead time has not budged because the team is busy and the goal feels like a slogan.

With catchball, the conversation goes differently. The owner shares the goal in October with the operations lead. The ops lead spends two weeks looking at the constraints: setup times on the main brake, the powder coater's three week backlog, the kitting queue. They come back with a counter: we can commit to two and a half weeks by Q3 if you fund a setup reduction project on the brake and let us renegotiate the powder coat schedule. The owner agrees to fund the project and takes the supplier conversation themselves. The shipping lead, in their own catchball with operations, commits to a daily release schedule instead of weekly batches.

By the end of October, the company has an annual plan with three teams who each negotiated their piece. The plan is realistic. The teams own it because they shaped it. Lead time actually drops because everyone is rowing in the same direction.

Common mistakes with catchball

• Performative catchball. A meeting called "catchball" where the goal is already locked is just a memo with extra steps. The team learns within one cycle.
• Too many rounds. Three to four rounds is the limit. Beyond that, catchball stops being alignment and starts being avoidance.
• No revision authority. If the leader cannot actually change the goal in response to pushback, there is no catchball. There is just venting.
• Letting the team set the bar. Catchball is not surrender. Leadership has to push back when feasibility analysis is too cautious.
• Skipping nemawashi. A catchball meeting that opens with surprises rarely lands. Quiet one on one conversations beforehand prepare the ground.

Catchball and related Lean tools

Catchball is the communication discipline that makes hoshin kanri cascades real. Its quieter cousin is nemawashi, the practice of building consensus one on one before a public decision. The one-page artifact that catchball conversations often revise is the x-matrix, which holds the breakthrough objectives, annual goals, and owners in one place. The forums where catchball plays out on a smaller daily scale are usually tiered meetings, the layered standups that connect the shop floor to operations to leadership.