New Product Introduction for Electronics
What NPI Covers
New product introduction is the process that takes a design from the engineer’s bench to a repeatable production line, and its output is a product that can be built at the target cost and quality by people who did not design it. It is a sequence of gates rather than a single event, and each gate asks whether the evidence is sufficient to spend the next increment of money. The programme that skips a gate usually pays for it later, at a much higher price, because the problem moves from a bench to a shipment.
Phase Zero: Requirements and Manufacturability
The earliest useful work is the review of the design against what can be manufactured. A design for manufacture review examines the stackup and the material, the panel utilisation, the component selection against availability and lifecycle, the placement and the clearances, the thermal path and the test access. Its purpose is to find the items that will cost money later, while they cost only a design change. Doing this review after the layout is complete is useful; doing it during the layout is far cheaper, because the same finding can be absorbed into the current revision.
Prototype and Engineering Builds
The first physical builds exist to answer questions that no simulation can settle. An engineering build typically uses a small quantity, sometimes with parts that are not the final ones, and its goal is to prove the electrical function, the thermal behaviour and the mechanical fit. The record of what was different and what was changed by hand is as important as the build itself, because it defines the delta to the next revision. A prototype that is built without a record of its deviations cannot be used as a baseline.

Design Verification and Validation
Verification asks whether the product was built correctly against its specification; validation asks whether the specification describes what the customer needs. The two are different and both are necessary. Verification covers the electrical performance across voltage, temperature and load, the mechanical and environmental requirements, the electromagnetic behaviour and the reliability testing that the market demands. Validation brings the customer’s use case and the field conditions into the lab. A product that passes verification but fails validation is a product that was specified incorrectly, and the earlier that is discovered, the cheaper it is to correct.
Pilot Build and Process Qualification
The pilot build is the first run on the production line, using production tooling, production programs and production operators, and it is where the manufacturability of the design is truly tested. It should be run at a rate that resembles production rather than at a comfortable pace, because the problems that appear at rate are different from the problems that appear at one unit per hour. The pilot produces the process data: the first pass yield by station, the defects and their Pareto, and the settings that have to be controlled. Its output is a frozen process rather than a set of boards.
Gates and the Decision to Ship
Each phase ends at a gate where the evidence is reviewed and a decision is made. The gate should ask specific questions: is the design frozen, is the supply chain secured, is the process capable, is the test coverage adequate, are the open deviations acceptable, and is the cost within target. A gate that is passed on optimism rather than evidence is worse than no gate at all, because it converts an open question into an assumption that everyone then relies on. Where a gate is passed with exceptions, the exceptions should be listed with an owner and a date.
Documentation and Handover
A product is not introduced until someone else can build it without the design team. That means a released BOM and approved vendor list, a controlled set of drawings and programs, a work instruction that a new operator can follow, an inspection plan that states what is checked and how it is judged, and a test procedure with limits. The handover also includes the lessons: the list of what went wrong in the pilot and what was changed, kept where the next project can find it. The programmes that capture this become faster on every product that follows.
Supply Chain Readiness
A product cannot be introduced on a design alone; it needs a supply chain that can deliver it. Readiness means that every part has a qualified source, that the long lead and single sourced items are identified and either second sourced or bought out, that the lifecycle status of each device is known, and that the quantities the forecast calls for can actually be obtained. Where a part is on allocation or approaching end of life, the correct time to discover it is during the review rather than in the first production month. Supplier readiness is a gate item, not an administrative step.

FAQ
What is NPI? The process that takes a design from a prototype to a repeatable production line, through a sequence of reviewed phases.
When should design for manufacture begin? During the layout, not after it, so that findings can still be absorbed into the revision.
Why run a pilot build? To prove the design on the real line, at a realistic rate, and to produce the process data that locks the settings.
What is the difference between verification and validation? Verification checks the product against its specification; validation checks that the specification matches what the customer needs.
What must be handed over? A released BOM and AVL, controlled drawings and programs, work instructions, an inspection plan and a test procedure with limits.
Conclusion
NPI is how a design becomes a product, and its value is in the gates that force evidence before spending. Review early, build to learn, pilot to lock the process and document to hand over. Manufacturing readiness belongs to PCB manufacturing, the pilot line sits in SMT PCB assembly, and the verification that follows is part of PCBA testing. The first pass of a new design is supported by prototype PCB assembly in 2026.



