Electronic Product Development: How to Approach It

Electronic product development is the process of turning a functional concept into manufacturable hardware: defining requirements and architecture, designing the schematic, laying out the PCB, writing and bringing up firmware, passing EMC and safety testing, and transferring the design to a manufacturer. Most programs need two to three board revisions before production.

Electronics fail differently from mechanical parts. A mechanical mistake usually shows up as a fit problem you can see. An electronics mistake shows up as intermittent behavior at temperature, a failed emissions scan, or a component that goes end-of-life two months before launch. The stages below are organized to surface those failures early.

Before any schematic, write down what the device must do in measurable terms: power source and budget, connectivity, sensors and actuators, environmental conditions, expected lifetime, target cost and the markets it will be sold in. Market list matters immediately because it determines which certifications apply.

The schematic defines the circuit: power regulation, processor, memory, radios, sensors, protection and connectors. Component selection at this stage is a supply chain decision as much as an engineering one — choose parts with multiple sources, long lifecycle status and real availability, not just the best datasheet.

Layout is where a correct schematic becomes a working or failing product. Placement determines thermal behavior, trace routing determines signal integrity, and ground strategy largely determines whether the board passes EMC on the first attempt.

Bring-up is the first time hardware and firmware meet. Plan it as a sequence — power rails, clocks, debug interface, then peripherals one at a time — and keep a written log of every deviation. Budget real time here; teams routinely underestimate bring-up by half.

Certification is a schedule risk, not a formality. Emissions and immunity failures usually require layout changes, which means a board respin and often an enclosure change. Pre-scan at an accredited lab as soon as an integrated prototype exists — a half-day pre-compliance session is far cheaper than a failed formal test.

Design transfer is a documentation package, not an email with Gerbers. It includes fabrication and assembly files, a fully specified BOM with approved manufacturer part numbers and alternates, assembly drawings, test procedures and acceptance criteria, and the production test firmware. Choosing the right partner matters as much as the package — see our guide to selecting an electronics contract manufacturer.

These exclude tooling and certification. For how electronics fits into the wider program, see the new product development process.

Electronic product development is the end-to-end process of turning a functional concept into manufacturable electronic hardware. It covers requirements and architecture, schematic design, PCB layout, firmware development and bring-up, EMC and safety compliance testing, and design transfer to a contract manufacturer.

A simple accessory using a pre-certified module typically costs $25,000 to $60,000 in engineering. A connected consumer device with a companion app usually runs $60,000 to $180,000, and industrial or safety-certified products $150,000 to $400,000 or more, excluding tooling and certification fees.

Four to seven months for a simple device, eight to fourteen months for a connected consumer product, and fourteen to thirty months for industrial or medical hardware where safety certification dominates the schedule.

Two to three revisions before production is normal. The first board proves the architecture, the second fixes bring-up findings and EMC issues, and the third is production-intent. Budgeting for only one revision is the most common cause of schedule overrun.

For most products, yes. A pre-certified module removes the majority of radio certification cost and risk, shortens the schedule by weeks, and avoids antenna tuning work. Discrete radio designs make sense mainly at high volume where the per-unit saving outweighs the certification investment.

Compliance planning starts at stage one, when you decide which markets the product will sell in. Physical pre-compliance scanning should happen as soon as an integrated prototype exists — well before design freeze — because emissions failures usually require layout changes.

Schematics get judged on function; bills of materials get judged on availability. A design that specifies a single-source MCU with a 40-week lead time is not finished, no matter how elegant the circuit. Run a sourcing review at schematic freeze and again before layout release, and treat lifecycle status as a hard requirement alongside electrical specifications.

Layout for substitution where you can: footprints that accept two regulator families, a pin-compatible memory alternate, and passives at common values rather than exotic ones. Each of those choices costs nothing at design time and can save a respin when a part goes unavailable mid-ramp.

The most common structural failure in electronic product development is organisational: the board is designed by one group, the housing by another, and they meet at the first assembly. By then the connector is 3 mm from where the opening is, the antenna sits behind a metal bracket, and the only remaining fix is a board revision.

The practical fix is a shared mechanical-electrical model reviewed weekly during layout: a STEP export of the board into the enclosure model, and the enclosure back into the ECAD tool. It takes an hour a week and removes the most expensive revision in the program.

Bring-up is scheduled optimistically almost every time. Budget two to three weeks for a first board of moderate complexity, and make sure the tools and access points exist before the boards arrive.

Every unit needs a pass or fail decision on the line, and that decision needs a fixture. Plan for it during layout: a bed-of-nails fixture needs test pads on a 2.54 mm-friendly grid on one side of the board, plus tooling holes for alignment. Retrofitting test access after design release is a board revision and a schedule slip.

Mechanical products ship and are finished. Electronic products ship and start accruing obligations: security patches, protocol changes at the cloud provider, phone operating systems that deprecate a Bluetooth behaviour, and the bugs that only appear across ten thousand units. Budget for that from the beginning rather than discovering it in the second year.

The same discipline applies to the hardware side. Keep the bill of materials under review after launch, because component obsolescence does not pause for your production schedule, and a last-time-buy notice with a six-week response window is far easier to handle when an alternate part has already been qualified.

Work with LA NPDT: if you are moving from here to execution, start with our our product development process or talk to us about end-to-end product development.