A handful of prototype boards, hand-soldered or assembled in a low-volume run with extra attention from a technician, can hide problems that only surface at production volume — a footprint that's technically correct but hard for automated placement to handle reliably, or a design with no way to verify a board is fully functional without a slow manual bring-up procedure. Design for Manufacturing (DFM) and Design for Test (DFT) are the disciplines that close that gap, and they're far cheaper to apply during design than to retrofit after a production run reveals the problem.
DFM: designing for how the board actually gets built
- Component placement and orientation consistency — parts oriented consistently (all polarized components facing the same direction, for instance) reduces placement errors and speeds up automated optical inspection
- Adequate spacing for automated assembly — components placed too close together can cause solder bridging or make automated pick-and-place unreliable, even if they fit fine on paper
- Panelization-aware design — boards assembled in panels need appropriate tab/mouse-bite placement and enough margin for depaneling without stressing nearby components
- Fab-realistic tolerances — trace widths, via sizes, and spacing that match what the actual fabrication house can reliably produce, not generic minimums that increase cost or reduce yield at that specific fab
- Component availability at volume — a part that's available in prototype quantities isn't guaranteed to be available (or reasonably priced) at production volume; sourcing risk needs evaluation before committing to a part in the design
DFT: designing so a bad board can be caught, not debugged
At prototype scale, a non-functional board gets manually debugged by an engineer with a scope and a schematic. At production scale, that approach doesn't work — testing needs to be fast, largely automated, and capable of distinguishing a good board from a bad one without requiring deep diagnostic work per unit. Designing for test means building that capability into the board itself, not hoping a generic test procedure will catch problems.
Practical DFT elements
- Test points on key nets — power rails, reset lines, communication buses, and other diagnostically useful signals, accessible to a bed-of-nails fixture or probe without requiring board disassembly
- Boundary-scan (JTAG) support where the design's ICs support it, enabling automated interconnect testing without physical probe access to every pin
- A built-in self-test routine in firmware that can be triggered during production test to exercise sensors, radios, and peripherals and report pass/fail, rather than requiring an external test engineer to manually verify each function
- Programming and debug interfaces accessible without full enclosure assembly, so firmware flashing and functional test can happen at the right point in the assembly process
The cost asymmetry that makes this worth doing early
A DFM or DFT gap caught during design review costs a layout change. The same gap caught after tooling is committed, or worse, after a production run has started, costs a redesign, a re-tooling cycle, and — for DFT gaps specifically — potentially higher per-unit test cost for the life of the product if no better testing method gets retrofitted. The asymmetry between catching this early versus late is large enough that a dedicated DFM/DFT review pass before committing to production tooling is standard practice, not an optional step.
How we approach this
DFM and DFT considerations get reviewed as part of the same design pass as the electrical and layout work, not as a separate gate right before production. See our embedded hardware work for how this fits into taking a design from prototype to a manufacturable product.