The most expensive errors in cross-border product development are not technical failures. They are translation failures — and we do not mean language.
A North American brand sends a product brief to a manufacturing partner. The brief specifies a “soft backsheet.” The manufacturer reads the brief, nods, and produces samples. The samples arrive. The backsheet grammage has been reduced — making the material thinner and more flexible. But it does not feel softer. If anything, the thinner film feels flimsier and cheaper. The brand rejects the samples. The manufacturer is confused. They made it softer. They have the data to prove it — lower bending stiffness, reduced thickness. By every measurable parameter in their quality system, the backsheet is objectively softer than the original.
Both parties are correct. Neither understood the other. And the project just lost six weeks.
Language Translation Is the Easy Part
When brands think about communication challenges with overseas manufacturing partners, they think about language. Mandarin to English, or vice versa. This is the most visible barrier and, paradoxically, the least important one. Professional translators can handle language. Google Translate, for all its limitations, can handle language. The barrier that actually kills timelines is not linguistic — it is engineering semantic.
Engineering semantics refers to the meaning embedded in technical terms that appears identical across languages but carries fundamentally different operational definitions depending on which quality system, test standard, and manufacturing context the speaker inhabits.
“Softness” is a consumer perception metric in a Western brand’s product development framework. It encompasses tactile feel, drape, acoustic properties (does the material crinkle?), and visual appearance. It is measured subjectively through consumer panels and objectively through instruments like the Kawabata Evaluation System or Handle-O-Meter — instruments that many manufacturing facilities do not possess.
“Softness” in a typical manufacturing quality system is operationalized as bending stiffness, measured on equipment the factory does have, using a test protocol the factory runs daily. When the factory receives a brief requesting “softer” material, they optimize for lower bending stiffness — because that is what “softness” means in their measurement framework. The result is technically softer by their definition and perceptibly worse by the brand’s definition.
This is not a miscommunication. It is a systematic gap between two internally consistent but mutually incompatible systems of meaning.
The Three Most Dangerous Terms
In our practice bridging Western brands and manufacturing partners, three terms produce the most consistent and costly misalignment.
“Absorption speed” sounds unambiguous. Liquid enters the product; you measure how fast. But the test methodology varies dramatically. Strike-through time measured by a Lister test at a specified pour rate produces a different number than free-swell absorption rate measured gravimetrically. A brand requesting “faster absorption” based on their internal testing protocol may receive samples optimized against a different test — samples that perform better by the manufacturer’s measurement and worse by the brand’s measurement. The conversation then spirals into a debate about whose test is correct, when the actual issue is that neither party established measurement alignment before development began.
“Breathability” compounds the problem because it conflates two distinct physical properties: moisture vapor transmission rate (MVTR) and air permeability. A backsheet can have high MVTR (allowing water vapor to escape) while having low air permeability (blocking airflow). A brand requesting “better breathability” may mean either or both, and the manufacturing response — typically increasing micropore density or adjusting film stretching parameters — affects these two properties differently and sometimes inversely. Improving one can degrade the other, and without explicit alignment on which property the brand is actually prioritizing, the iteration cycle produces oscillating results.
“Rewet” is perhaps the most treacherous because the test methodology space is vast. Rewet can be measured after a single insult or multiple sequential insults. Under static load or dynamic compression. After a specified rest period or immediately. Using a standardized filter paper weight or a proprietary absorbent medium. Two laboratories testing the same product with different rewet protocols can produce results that differ by an order of magnitude. When a brand specifies a rewet target without specifying the exact protocol — down to pour volume, pour rate, rest time, compression weight, compression duration, and measurement substrate — the number is effectively meaningless as a manufacturing target.
Why “Better Translation” Is Not the Answer
The instinct when confronting these gaps is to invest in better translation — hire a bilingual engineer, provide more detailed briefs, add more specification lines. This helps, but it addresses the symptom rather than the disease.
The disease is the absence of a shared specification framework that both parties have explicitly agreed maps specific words to specific test methods, instruments, and acceptance criteria. In engineering disciplines with mature cross-border collaboration history — automotive, aerospace, semiconductor — these shared frameworks exist as industry standards. In the hygiene products industry, they largely do not. Each brand and each manufacturer operates within their own specification ecosystem, and the translation between ecosystems is left to the people in the middle to figure out ad hoc.
The solution is to build what we call a specification bridge before development begins. A specification bridge is a document — typically one to two pages per critical parameter — that explicitly maps:
The brand’s term and its intended meaning in consumer-experience language. The equivalent manufacturing parameter and its operational definition. The specific test method, instrument, and protocol that both parties will use as the shared reference. The acceptable range expressed in units both parties can directly measure. And the known interaction effects — cases where improving this parameter may degrade another parameter the brand cares about.
Building the specification bridge requires an investment of one to two weeks at the start of a development program. Skipping it — which most programs do, under timeline pressure — typically costs four to eight weeks of iteration cycles later in the program when specification misalignment surfaces in sample rejections, reformulations, and repeated testing.
The Human Infrastructure Gap
Beyond terminology, there is a structural communication gap that bilingual documents alone cannot solve. Development programs require real-time technical dialogue — the kind of conversation where an engineer says “we tried your specification and the web keeps tearing at the calendar” and the brand’s product team needs to understand not just what happened but why, and what the viable solution options are.
This dialogue requires someone who can operate in both engineering languages simultaneously — not sequentially translating, but thinking in both frameworks and identifying where the concepts diverge. This is a rare skill set. Fluent bilingualism is common. Bilingual engineering fluency — the ability to understand that “calendar tearing” refers to a specific mechanical failure mode at a specific point in the nonwoven production process, and to translate its implications for the brand’s performance requirements — is not.
The absence of this human infrastructure is the single largest hidden cost in cross-border product development. It does not appear on any project budget. It manifests as extended timelines, repeated sample iterations, specification documents that grow longer with each revision cycle without converging on alignment, and a pervasive sense on both sides that the other party “does not understand what we need.”
They understand. They are just measuring a different thing.
Simon Gong | Founder & CEO, Corio Hygiene Innovation Team
