---
title: "Why 'yes' doesn't always mean yes"
date: "2026-06-15"
tag: "Working in China"
excerpt: "Most manufacturing disasters I've seen weren't technical — they were communication failures. After 13 years here, this is how I keep 'yes' from becoming a $40,000 surprise."
series: "field-notes"
seriesOrder: 2
faq:
  - q: "What does \"yes\" mean in a factory conversation?"
    a: "In a lot of factory conversations, \"yes\" doesn't mean \"I agree and I will do that.\" It can mean \"I understand the words you said,\" or \"I don't want to lose face by saying no,\" or \"we'll figure it out later.\""
  - q: "How do I avoid misunderstandings with a factory?"
    a: "The fix is to stop asking yes/no questions. You're replacing a comfortable \"yes\" with evidence."
  - q: "How should I specify requirements to a factory?"
    a: "Adjectives don't survive translation. If a requirement can't be inspected, it isn't a requirement — it's a wish."
  - q: "What is a golden sample?"
    a: "Before a production run, get one unit made and approved that becomes the reference."
---

The hardest part of manufacturing in China usually isn't the manufacturing. It's making sure that what you *think* you agreed to is what the factory *thinks* you agreed to. Those two things drift apart more easily than you'd believe, and by the time the gap shows up, it's sitting in a shipping container.

## "Yes" often means "I heard you"

In a lot of factory conversations, "yes" doesn't mean "I agree and I will do that." It can mean "I understand the words you said," or "I don't want to lose face by saying no," or "we'll figure it out later." If you ask "Can you hold this tolerance?" and get an instant yes, you've learned almost nothing.

The fix is to stop asking yes/no questions. Ask *how*:

- Not "Can you do this finish?" but "Show me a sample of this finish you've done before."
- Not "Will it be ready by the 20th?" but "Walk me through the schedule — when does tooling finish, when does the first article come off?"
- Not "Do you understand?" but "Tell me back what we just agreed."

You're not being difficult. You're replacing a comfortable "yes" with evidence.

## Put the spec in pictures and numbers

Adjectives don't survive translation. "Premium," "smooth," "sturdy," "a nice blue" — these mean different things to everyone in the chain. Numbers and references survive: a Pantone code, a dimension with a tolerance, a photo with the bad part circled, a physical golden sample everyone signs off on.

> If a requirement can't be inspected, it isn't a requirement — it's a wish.

## The golden sample is your contract

Before a production run, get one unit made and approved that becomes *the* reference. Everyone keeps a copy. When a dispute comes up later — and it will — you're not arguing about adjectives, you're holding up the sample you both agreed to. It's the single highest-leverage hour you can spend.

## Be present, or have someone who is

A lot of drift happens in the gap between your timezone going to sleep and the factory's day starting. Decisions get made on the floor without you. Having someone on the ground who can walk over, look at the actual part, and have the conversation in the local language closes that gap before it becomes a remake.

That's the real job: not catching problems after they ship, but being close enough that they never ship at all.

Working on something like this? [Get in touch](/contact/).