A tier-1 supplier receives a new quality directive from a major customer: reduce PPM defect rates by half within the fiscal year. The supplier's commercial director reviews the mandate, confirms the target with corporate leadership, and signs the annual quality agreement. Procurement logs the commitment. The supplier quality manager files the document. Six months later, the customer's supplier development engineer arrives to audit progress and finds minimal improvement.
The failure occurred at the supplier interface, the boundary where strategic intent crosses from one organisation to another. The customer deployed the objective through a contract amendment, not a structured negotiation. The supplier accepted the commercial terms without translating the target into specific engineering requirements, process capability upgrades, or capital investments. Neither party engaged in genuine catchball.
Across two decades implementing ISO 9001, IATF 16949, and AS9100 systems in automotive and aerospace, I have seen this pattern repeatedly at the supplier boundary. The traditional internal catchball process described in Hoshin Kanri literature stops at the factory wall. What crosses to the supplier is a purchase order, a PPAP requirement, or a quality agreement — a one-way transmission dressed up as deployment.
The Contract Is Not the Conversation
Quality agreements and PPAP submissions are essential compliance instruments, but they are the output of strategy deployment, not the mechanism. When a customer transmits a defect reduction target through a commercial document, the supplier's quality function receives a number without context. The supplier's quality engineer cannot connect a fifty-percent PPM reduction to specific failure modes because the customer provided no failure mode breakdown, no field return analysis, and no prioritisation of which defect categories matter most.
The result is dispersed effort. The supplier attacks every defect mode equally because the target was never refined through bilateral dialogue. Resources allocated to cosmetic defects consume the same engineering bandwidth as functional failures. A PPAP package gets resubmitted with updated control plans, but the underlying process capability remains unchanged because nobody negotiated the specific capital investment required to move Cpk from 1.0 to 1.33 on the critical characteristic.
Genuine cross-company catchball requires the customer to throw the strategic target with its operational context: the field data, the warranty cost analysis, the specific voice-of-customer complaints driving the mandate. The supplier catches that data, pulls their own 8D records and PFMEA, and throws back a counter-proposal that identifies which failure modes they can realistically address, what resources they need, and what timeline the constraints of their current production system allow.
Engineering and Procurement as Catchball Conduits
The customer's procurement function is typically the first point of contact for the supplier, yet procurement is the least equipped to negotiate quality strategy. Procurement understands price, lead time, and volume commitments. When procurement transmits a quality target, the conversation defaults to commercial terms: penalty clauses, warranty caps, and chargeback thresholds. The strategic quality intent is buried under contractual risk allocation.
Functional cross-company catchball requires the customer's engineering and supplier quality functions to engage directly with the supplier's engineering and quality teams. Procurement facilitates the commercial framework, but the technical negotiation must happen between practitioners. The customer's design engineer must explain why a specific tolerance is critical to the final assembly. The supplier's process engineer must explain why that tolerance demands a fixture redesign and a three-month lead time.
Horizontal catchball within each organisation must precede the cross-company dialogue. Before the customer throws a target, their own engineering, quality, and procurement teams must align internally on what is feasible. I have audited facilities where the customer's purchasing department committed a supplier to a zero-defect target that the customer's own engineering team had not yet validated for design maturity. The supplier was set up to fail before the first catchball round occurred.
Cross-Company Catchball Round at the Supplier Interface
- 01Internal alignment (customer)Customer's engineering, quality, and procurement define the target with field data and resource constraints.
- 02Strategic throw with contextCustomer transmits the target, failure mode data, and warranty analysis through a joint review session, not a contract amendment.
- 03Supplier catch and analysisSupplier's quality and engineering teams pull 8D records, PFMEA, and process capability data to assess feasibility.
- 04Counter-proposal with constraintsSupplier returns a specific execution plan identifying achievable defect reductions, capital needs, and timeline.
- 05Joint agreement and resource commitmentBoth parties finalise the refined target, investment plan, and measurement cadence with documented accountability.
Where Asymmetric Power Distorts the Dialogue
Cross-company catchball is structurally harder than internal deployment because the two parties hold unequal power. A major OEM can impose quality targets on a tier-1 supplier through commercial leverage. The supplier's quality manager, aware that the contract renewal is pending, is unlikely to push back honestly on an unrealistic target. The catchball round becomes a compliance ritual where the supplier tells the customer what the customer wants to hear.
This power asymmetry destroys the counter-proposal mechanism that makes catchball functional. If the catcher cannot safely reject or modify the throw, the process is pure theatre. The supplier signs the quality agreement, commits to the PPAP update, and returns to the floor knowing the target is unachievable. When the next audit reveals the gap, both parties express surprise — but neither invested in the honest dialogue that would have surfaced the constraint months earlier.
Functional cross-company catchball requires the customer to explicitly authorise pushback. The customer's supplier quality engineer must open the session by stating that the target is preliminary, that operational constraints will shape the final commitment, and that a counter-proposal identifying infeasible elements is expected. This framing converts the meeting from a mandate delivery into a negotiation, which is the precondition for any genuine strategy deployment.
If your supplier catchball happens through a signed quality agreement, you have compliance theatre, not deployment.
Diagnosing Interface Failures Through Layered Audits
The most reliable diagnostic for cross-company catchball failure is a layered process audit that examines both the customer's deployment record and the supplier's execution record side by side. VDA 6.3 process audits, when conducted at the supplier, typically focus on the supplier's internal controls. But the gap lives at the interface: the customer's quality plan says one thing, the supplier's control plan says another, and neither party has reconciled the difference.
I have audited plants where the customer's quality plan specified one hundred percent inline inspection of a critical characteristic, while the supplier's control plan relied on a sampling plan at a downstream station. The PPAP submission confirmed the sampling approach, and the customer approved it. No catchball round ever reconciled the discrepancy because the dialogue never happened — the document exchange masked the disagreement. The audit finding was not a supplier deficiency; it was a deployment failure at the interface.
The corrective action in these cases is not another form or an additional signature. It is a joint review session where both parties open their quality plans, PFMEAs, and control plans simultaneously, compare them characteristic by characteristic, and document the negotiated agreement. This is catchball in its functional form: two engineering teams refining a shared understanding of the process until both sides commit to the same operational reality.
Compliance Exchange vs. Functional Cross-Company Catchball
Document-based compliance
- Customer transmits targets via quality agreement or purchase order
- Supplier signs acceptance without modifying scope or timeline
- PPAP and control plans are exchanged but never jointly analysed
- Progress reviewed only at scheduled audits or when PPM targets are missed
Functional catchball
- Customer and supplier teams meet in joint sessions with field data and 8D records
- Supplier proposes resource, design, and timeline modifications based on capability data
- Both parties reconcile quality plans and PFMEAs characteristic by characteristic
- Targets are reviewed and adjusted monthly based on agreed performance metrics
Sustaining the Dialogue Beyond the Initial Agreement
Cross-company catchball is not a one-time event completed during contract negotiation or PPAP submission. The operational reality at the supplier changes continuously: tooling wears, raw material sources shift, and workforce turnover erodes process knowledge. A quality target negotiated in January may be invalid by June because the production system that supported the agreement has fundamentally altered.
The customer's supplier quality function must establish a cadence for recurring catchball rounds tied to the operating rhythm, not the audit calendar. Monthly reviews should examine whether the agreed counter-proposals are holding, whether new failure modes have emerged that change the defect distribution, and whether the resource commitments from both parties have been fulfilled. If the supplier committed to a fixture redesign and the customer committed to extended testing support, both actions must be tracked with the same discipline applied to production delivery.
The organisations that sustain cross-company catchball effectively treat the supplier interface as an extension of their own Hoshin Kanri process. The strategic priority flows through the same bilateral negotiation mechanism regardless of whether the execution team sits in the same building or on another continent. The contract defines the legal relationship; the catchball dialogue defines the operational one.
The Cost of Skipping the Negotiation
The most expensive failure mode in supplier quality deployment is the silent acceptance of an unachievable target. When a supplier signs a quality agreement knowing the commitment is unrealistic, the downstream costs compound silently. The supplier allocates partial resources, chases the wrong defect modes, and submits improvement plans that look credible on paper but lack the engineering substance to change process capability. The customer receives periodic reports showing marginal progress and interprets the trend as gradual improvement rather than evidence of fundamental misalignment.
When the audit or the field failure finally exposes the gap, the corrective action cycle is exponentially more expensive than the original catchball round would have been. An 8D investigation, a containment action, a supplier escalation, and a revalidation of the entire PPAP package consume more engineering hours than five structured negotiation sessions ever would. The rework cost is measured not just in warranty claims but in the diversion of quality engineering talent away from prevention and into firefighting.
The investment in cross-company catchball — the joint sessions, the data exchange, the counter-proposal cycles, the willingness to revise the target based on operational evidence — pays its return by eliminating this rework. It is the difference between a supplier relationship built on shared understanding and one built on documents that neither party genuinely believes.