Catchball

1. Validating strategic feasibility through operational reality: High-level strategic targets are tested against actual machine capacities, labor constraints, supplier lead times, and process capabilities. This testing prevents organizations from committing to external obligations that cannot be supported by internal systems.
2. Establishing resource commitments and operational ownership: Because frontline leaders and team members participate in defining the methods, counter-proposals, and resource requirements, they take psychological and operational ownership of the targets. Concurrently, executive leaders are held accountable for providing the specific capital, tooling, cross-functional support, and training hours negotiated during the cycle.

Upon receiving this draft target, the value stream team conducted a single-minute exchange of die analysis on the process. The team's direct investigation revealed the following operational realities:

• Baseline state: Current changeover duration averaged 40 minutes.
• Immediate internal-to-external conversion: The team identified that 12 minutes of setup preparation could be moved outside of the machine stoppage window through standardized work and pre-staging materials. This change lowered the baseline stop time to 28 minutes without capital investment.
• Technical limitation: Reaching the 20-minute target required eliminating an additional 8 minutes of internal adjustments while the machine was stopped. This reduction was physically impossible with existing tooling fixtures unless two operators worked in parallel and specific mechanical guides were replaced with quick-release mechanisms.
• Resource requirement: The team drafted a counter-proposal indicating they could achieve the 20-minute target only if leadership provided a second die cart and funded 16 hours of structured operator training on external setup routines.

Leadership reviewed the counter-proposal, verified the operational data, and approved the purchase of the second die cart along with the allocated training time. The result was a feasible, resourced, and owned target that successfully reduced changeover time to the 20-minute threshold within the designated quarter.

Manufacturing

In an industrial manufacturing environment, corporate leadership established a goal to reduce total product lead time by 20% to defend market share against aggressive new competitors.

Through the catchball process, plant managers and value stream leaders audited equipment changeover logs, internal transport times, and work-in-process buffers. Their analysis demonstrated that existing tooling limitations and furnace cool-down cycles capped lead-time improvements at 15% under current operational parameters. Achieving the full 20% would require substantial capital allocation for modern quick-change tooling.

Plant management submitted a counter-proposal detailing these findings. Following three structured rounds of catchball, corporate leadership and plant management agreed to an 18% lead-time reduction target paired with a defined capital expenditure schedule that phased in tooling upgrades over two fiscal quarters. This compromise allowed the facility to meet delivery targets without exceeding corporate capital ceilings.

Administrative and service functions

Catchball is equally applicable to service organizations, transactional workflows, and corporate shared services. In one administrative scenario, a chief financial officer proposed an across-the-board 10% operational budget reduction for all corporate departments to protect operating margins during an economic downturn.

Rather than implementing arbitrary head-count reductions that would degrade service levels, departmental managers engaged in catchball cycles with the finance group:

• The accounts payable department analyzed transaction logs and identified that 30% of invoice processing time was spent resolving supplier billing discrepancies manually.
• The department countered that an across-the-board budget cut would increase invoice backlogs, leading to late-payment penalties.
• The counter-proposal demonstrated that if the executive team approved an electronic data interchange standardization project with the top twenty vendors, operational processing hours could be reduced permanently by 14%, exceeding the CFO's target while maintaining internal service-level agreements.

Through factual operational modeling, the department avoided arbitrary cuts and secured the cross-functional support needed to redesign its process.

What communication tool is used to document catchball negotiations?

Catchball exchanges are typically documented using an A3 problem-solving report. Teams use standard A3 sections—such as current conditions, root-cause analysis, countermeasures, and implementation plans—to anchor discussions in verified gemba data rather than subjective impressions. This shared format ensures that both leadership proposals and frontline counter-proposals are evaluated against objective operational facts.

How does catchball differ from ringi and nemawashi?

Nemawashi is the informal groundwork and stakeholder consultation that precedes decision-making, while catchball provides the formal, transparent governance structure within which those discussions happen. Catchball also differs from the traditional ringi system, which relies on circulating static, bottom-up administrative documents for management approval seals. Instead, catchball establishes an active, two-way negotiation between executive strategy and operational feasibility before any final document is signed.

What should an operational team do during catchball if a proposed target is not achievable?

The operational team conducts direct observation and time studies at the gemba to quantify baseline capabilities and identify technical or physical bottlenecks. They then submit a counter-proposal detailing the performance gap, the maximum output possible under current conditions, and the specific process improvements or capital resources required to hit the draft target. Leadership and frontline managers then enter structured negotiation rounds to adjust the target's magnitude or supply the necessary resources.

How do organizations prevent catchball from becoming an endless negotiation loop?

Organizations avoid protracted negotiations by setting strict cycle-time limits and predefined escalation pathways. A standard countermeasure is capping catchball cycles at a maximum of three iterations across a four-week planning window. These boundaries force decisive alignment between operational reality and strategic goals without paralyzing organizational execution.

How does catchball prevent unfunded strategic mandates?

Catchball treats agreed targets as a binding mutual contract, meaning frontline execution is contingent upon leadership delivering promised organizational support. To maintain accountability, leadership commitments—such as equipment upgrades, tooling, or operator training hours—are tracked directly on visual management boards alongside operational metrics. If leadership fails to supply the negotiated resources, the agreement is broken and the target must be formally reassessed.