Communication Best Practices
Clear communication with a Chinese factory prevents more defects than any inspection. The best QC system in the world cannot fix a specification that was lost in translation.
Factory communication is the most underrated skill in hardware development. A founder who communicates clearly with their factory gets fewer defects, faster samples, and proactive problem-solving. A founder who communicates poorly gets exactly what they asked for — not what they wanted — and finds out too late. The gap between these outcomes is not about Chinese language ability. It is about how you structure information, confirm understanding, and document decisions.
For hardware founders, factory communication happens across multiple channels: email, WeChat, video calls, spec documents, and in-person visits. Each channel has its own strengths and failure modes. Mastering the patterns that work — and avoiding the ones that produce misunderstandings — is a force multiplier for everything else in your supply chain.
Always communicate specifications in writing with visual references. A written spec (dimensions, tolerances, materials, surface finish, color code) paired with annotated photos or CAD screenshots is dramatically clearer than either alone. The spec provides precision. The visual provides intuition. Together they eliminate 90% of the ambiguity that causes first-sample failures. Never send a spec by voice message. Never approve a change verbally. If it is not written, it did not happen.
Use closed-end confirmation questions, not open-end ones. "Do you understand this tolerance requirement?" invites "Yes, no problem." Instead, ask: "What tolerance can you hold on this dimension?" or "Please confirm the maximum warpage you can guarantee on this part." Closed-end questions verify understanding. Open-end questions invite face-saving agreement. After every specification discussion, ask the factory to repeat back the key requirements in their own words — this catches misunderstandings that "yes" would hide.
Document every change with a revision log and redline drawings. When something changes — a dimension, a material, a surface finish — do not just mention it on WeChat. Issue a revised drawing with the change clouded (circled) and the revision clearly labeled (Rev B, Rev C). Keep a simple change log: date, what changed, who approved it, and which version is now current. This seems bureaucratic until the factory produces 1,000 units to Rev A because nobody told the night shift about Rev B.
WeChat is the default communication channel with Chinese factories, but it is a double-edged sword. It is fast, casual, and ubiquitous — great for quick confirmations, photos of issues, and relationship building. It is terrible for technical specifications, because messages scroll away, files expire, and there is no audit trail. Use WeChat for daily coordination. Use email or a shared document system (Google Drive, Notion, or similar) for all specifications, approvals, and decisions that need to be referenced months later.
Communication failures that ruin production
Assuming "yes" means understanding
In Chinese business culture, "yes" often means "I heard you," not "I understand and agree." The factory may say yes to avoid losing face or appearing uncooperative, then proceed with their own interpretation. Verify with closed-end questions.
Sending a spec once and assuming it stuck
The person who received your spec three months ago may no longer be on the project. The production line supervisor may have a printed version from two revisions ago. Re-send the current spec before every production run.
Using idioms, slang, or culturally specific references
"This feels premium" or "make it pop" or "Apple-level quality" means nothing across a language barrier. Describe the specific attribute: surface roughness under Ra 0.8, no visible parting line flash over 0.1 mm, gap between parts under 0.3 mm.
Relying on machine translation for critical specs
Google Translate and Baidu Translate are adequate for "The shipment will arrive Tuesday" and dangerous for "The tolerance on dimension A is +0.05/-0.02 mm." Numbers, technical terms, and tolerance syntax get mangled. Include both English and metric specs, and reference ISO/GB standards where applicable.
What founders should remember
Specs in writing, decisions in writing, changes in writing
If a factory claims you never told them about a change, the only defense is a dated email with the revised drawing attached. No verbal agreement counts. No WeChat voice message counts. Written records.
Confirm receipt and understanding separately
After sending a spec, ask: "Please confirm you received this drawing" (receipt). Then ask: "Please confirm the tolerance on dimension A is achievable" (understanding). These are different questions and both are necessary.
Build a relationship, not just a transaction
A factory contact who considers you a friend will flag problems early, recommend better approaches, and prioritize your order. This does not replace documentation — it supplements it. Both are needed.