Establish a controlled incident scope
Ask quality and engineering teams to identify the relevant batches, specifications, production periods and known effects. Distinguish a non-conformity, a suspected safety implication and a confirmed risk. Specialists determine the applicable actions and notifications. Communications should preserve these distinctions rather than collapse every issue into either 'minor defect' or 'major crisis'.
Map who needs which information
A direct customer, integrator and final manufacturer may have different responsibilities and access to end users. Identify the contractual and operational communication routes with the relevant advisers. Do not assume the Taiwanese supplier should publicly contact every downstream user itself. Equally, ensure that confidentiality is not used as an excuse for failing to escalate verified safety information through the proper channels.
Support decisions during uncertainty
Prepare a factsheet with confirmed findings, current investigation, validated instructions and the next update point. If a containment action is still under technical review, do not invent one. Customers may need to plan production; explain what can be confirmed and who can discuss the operational implications. Keep a record of which version each partner received.
Align public and customer-facing statements
A brief public statement may legitimately contain less detail than a confidential technical notice, but the two must not contradict one another. Avoid denying a problem simply because its full scope is not known. Taiwan headquarters and European teams should share approved terminology and a single route for material changes to the account.
Prepare for pressure from multiple programmes
Use a hypothetical defect affecting two customers with different production schedules to rehearse prioritisation. The response team should determine technical priorities while communications tracks unanswered requests, approved updates and escalation. Avoid treating the loudest media coverage as the sole guide to action. Operational consequence and safety assessment must remain visible in the decision process.
Document corrective follow-through
When the investigation permits, explain corrective actions and their verified scope. Do not claim that a root cause is confirmed before the responsible specialists approve it. Deliverables include an incident communication matrix, partner notices, spokesperson brief and review process. Belief System supports coordination and clarity alongside quality, legal and account teams, without taking over technical product decisions.
Sources and reference points
Reference sources checked on 9 October 2026. The proposed methods and hypothetical situations are Belief System analyses. Your advisers determine the rules applicable to your project.
Continue your preparation
- A Taiwanese automotive supplier approaches European OEMs: how to build credibility before the pitch
- Taiwanese charging technology in Europe: communicating a partnership beyond the hardware
- A European automotive trade show: how a Taiwanese supplier can earn attention with substance
Prepare your European market entry
Public affairs · Media relations · Reputation & crisis management · GEO & AI visibility