In my years working in PCBA, I've seen too many beautifully designed boards die on the word "communication."
A project from design to production involves at least six roles: designer, purchasing, PCB fab, assembly house, test engineer, and quality engineer. Every role has its own language, mindset, and priorities. As information passes between these people, it naturally distorts, gets lost, and mutates.
Below are 7 communication traps I repeatedly see on the factory floor. Behind every single one is a real story of project delays or rework.
Trap 1: "Just use standard process"
The designer thinks this is clear. When the factory receives this, the mental checklist is: Which fab's "standard"? Green solder mask or any color? White silkscreen or default? Flying probe or AOI test? Vacuum or ESD bag packaging?
"Standard process" in the designer's mind is one thing. In the factory's eyes, it's dozens of permutations.
Consequence: The factory does their "standard." You receive boards with the wrong silkscreen color, the wrong shade of green, oxidized pins from wrong packaging. You think the factory messed up. The factory thinks "you told me to do standard."
How to avoid: On your PCB order form, specify every single process parameter — board thickness, copper weight, solder mask color, silkscreen color, surface finish, test method, packaging requirement. Don't write "standard." Write actual values and options.
Trap 2: "Just let me know if you see any issues"
This is the most common phrase designers use when sending files for DFM review.
The factory opens the design, finds 8 potential risks, and sends a list back. The designer replies to 3 of them. The other 5 are forgotten. The factory waits two days, assumes "the client doesn't care about these 5," and builds the board as-is. Of those 5 issues, 2 do cause yield loss.
Consequence: The factory thinks "I asked, you didn't reply, I took it as approval." You think "I asked you to look, you should have stopped me if there was a problem." Both sides think they're right. The boards are still bad.
How to avoid: Respond to every single DFM comment, no matter how small, with either "will fix" or "won't fix, risk accepted." Don't use vague instructions like "just let me know." Use explicit language like "please confirm the following items one by one."
Trap 3: "I bought the same thing"
Purchasing sees a capacitor on the BOM specified as "10μF/25V/0805." They buy the cheapest batch from three suppliers.
Boards come back. Power ripple is out of spec. Investigation reveals the capacitor's ESR is 3x higher than the batch used on the prototype. Purchasing says "the spec is the same." But the "same spec" only covers capacitance, voltage, and package — not ESR, ESL, temperature coefficient, or lifetime.
Consequence: Entire batch scrapped. Repurchase. Reassembly. Cost overruns, schedule delays, and ultimately, the designer still takes the blame.
How to avoid: On your BOM, specify brand and full part number (including suffix). If alternates are allowed, list the exact alternate brand and part number. Don't leave room for guessing.
Trap 4: "I've always done it this way"
This is the most dangerous phrase for experienced engineers.
You design a power supply using a DCDC chip, copying a previous project's circuit. That project had a 500mA load. This one has a 2A load. The circuit looks the same, but current is 4x higher — the inductor needs to be recalculated.
You use an LDO you've used twenty times without issue. But this product's operating temperature is 20°C higher, and the thermal conditions are different.
Consequence: Boards work in the lab. But in the field at high temperature, they crash or restart. Or under full load, the inductor saturates and the supply drops out.
**How to avoid: **Recalculate key parameters for every new project. Don't trust "we did it before." The environment changed. The load changed. The thermal conditions changed. So the math changes too.
Trap 5: "I'll fix it and send it right back"
The factory finds an issue during DFM review and emails you. You reply "fixing it now" and actually send updated files within hours.
But you only fixed the PCB, forgot the BOM. Or fixed the BOM, forgot the assembly drawing. Or fixed the Gerber, forgot to update the XY coordinate file.
The factory receives your new files, assumes "everything is updated," and builds to the new files. When the boards come back, the BOM and PCB don't match — the assembly house populates the wrong parts.
Consequence: Entire batch has wrong parts assembled. Rework. Or worse — assembled wrong, goes unnoticed, and fails at the customer site.
**How to avoid: **Every time you make changes, use an "Engineering Change Notice" or version number. Clearly list which files were changed, what was changed, and why. Don't just say "I updated it." Write it down.
Trap 6: "Just test it"
When discussing test strategy with the factory, the designer says "just test it." The factory doesn't know what "it" means — power-on test? Functional test? ICT? Thermal cycling? Burn-in?
You say "test it." The factory does the cheapest option — power-on test. The boards go to the customer and fail after two days. A BGA void that power-on test couldn't detect.
Consequence: Customer complaint. Product recall. Reputation damage. You regret not specifying "ICT + functional test + thermal cycle."
How to avoid: At the order stage, clearly define the test plan. Specify test items, test standards, and sampling ratio. Don't use vague words like "test it." Use explicit descriptions like "flying probe all electrical nodes, functional test 10% of units."
Trap 7: "Make it as fast as you can"
The most common phrase, and the most misunderstood.
What you mean: The factory should work overtime, jump the queue, prioritize my boards.
What the factory hears: Fit it into the current schedule as early as possible — but every other client also said "as fast as you can."
Consequence: You expect 2 weeks. The factory schedules 3 weeks. You think they're late. They think "I did make it as fast as I could."
How to avoid: Be specific about what "fast" means to you. What's your expedite budget? What's the absolute latest you can receive? Do you need it faster and are willing to pay? Give the factory a clear deadline, not a vague "as fast as possible."
The Bottom Line: Communication Isn't "Saying" — It's "Confirming the Other Side Received the Right Information"
All 7 traps share the same root cause: you think you said it clearly, they think they understood it correctly — but you weren't talking about the same thing.
The fix is simple in theory, but requires discipline in practice:
- Use numbers instead of adjectives. Don't say "fast." Say "5-day delivery." Don't say "standard." Say "green solder mask, white silkscreen, ENIG finish."
- Use checklists instead of speech. Every time you send files, attach a checklist confirming process parameters, test requirements, packaging.
- Use confirmation instead of assumption. If the other side hasn't confirmed, follow up. Don't assume "it's fine."
- Use writing instead of phone calls. For important communication, send an email. Or follow up a call with a confirmation email.
Do these right, and your project delays and rework can be cut in half.
📬 We treat every board as if it were our own product — no explanation needed, just results.
Top comments (0)