Engineering Expertise

A practical reference for enterprise R&D leaders running a hardware program: deliverables, gate criteria, durations, and the pitfalls that consistently cause timeline slip.

Most enterprise product programs do not fail at the engineering. They fail at the process. The product development process is the structured sequence of phases that connects a rough product idea to a launched, manufacturable product, and the discipline of running it well is what separates programs that ship on time from programs that quietly slide a quarter at a time.

This article is the execution reference: what happens in each phase, what each phase produces, how to know when a phase is done, how long each phase typically runs, and the failure modes that cause slippage. It is built for R&D leaders who are inside an active program right now.

For the broader engagement context, including when to bring in an external partner and how to evaluate one, see our Complete Guide to Product Development Consulting and our guide to choosing a product development firm.

What Is the Product Development Process?

The product development process is the structured sequence of phases that turns a product idea into a manufacturable, launch-ready product. The standard enterprise framework runs five execution phases (discovery, concept, design, prototyping, and pilot production) inside a broader seven-stage business cycle (ideation through commercialization). Each phase produces a defined deliverable that the next phase consumes, and phase-gate reviews catch problems before they compound downstream.

Two frameworks appear consistently in industry literature:

• The 5-phase execution arc covers the engineering and manufacturing path from concept through pilot production. This is what an internal R&D team or a product development consultancy actually runs day-to-day.
• The 7-stage business cycle covers the full path from raw idea through full commercialization. This is the framework a product manager or business sponsor uses to track a program from portfolio approval to launch.

The 5-phase arc fits inside stages 3 through 6 of the 7-stage cycle. Most of the rest of this article focuses on the 5-phase execution arc because that is where most enterprise R&D leaders need depth.

What Are the 5 Phases of the Product Development Process?

The 5 phases of the product development process are discovery and requirements, concept and architecture, detailed design and engineering, prototyping and validation, and design for manufacturability and pilot production. Phase 1 frames the problem; phase 5 ships the first verified production-quality units.

Brief overview of each phase before the full walkthrough below:

• Phase 1: Discovery and Requirements. The team frames the problem, captures constraints, and defines success metrics.
• Phase 2: Concept and Architecture. System architecture, concept generation, and feasibility studies. The riskiest elements are identified and ranked.
• Phase 3: Detailed Design and Engineering. Mechanical CAD, electrical schematics, PCB layout, firmware, and analysis. The design becomes manufacturable on paper.
• Phase 4: Prototyping and Validation. Physical builds, test campaigns, FMEA, and design iteration. The design becomes manufacturable in practice.
• Phase 5: Design for Manufacturability and Pilot Production. DFM and DFA reviews tighten the design for scale, and the pilot run produces the first verified production-quality units.

What Happens in Each Phase of the Product Development Process?

Each phase has a defined objective, a set of activities, deliverables, gate criteria, a typical duration, and a recurring pitfall. While each project, firm, and customer will necessitate unique caveats or adjustments, the following phases outline general guidelines.    

Phase 1: Discovery and Requirements (2 to 8 weeks)

Objective: define what the product must do, for whom, under what constraints, and how success will be measured. Discovery is the right phase for surfacing a wrong idea, before sunk cost makes course correction expensive. It is also where the constraints that will dominate every later phase are most easily set.

What happens: the team gathers stakeholder requirements, captures cost and mass constraints, identifies regulatory exposure, maps the supply chain dependencies, and runs an Analysis of Alternatives so the program does not lock into the first concept that survives the kickoff meeting. User research happens here when the product is consumer-facing.

Deliverables: a requirements specification, a constraints map (cost, mass, regulatory, supply chain), a stakeholder map, a target product profile, and a documented Analysis of Alternatives. Together these become the contract between the engineering team and the business sponsor.

Gate criteria: the requirements specification is signed by engineering, product management, and operations. Cost and timeline targets are committed. Top three risks are identified and have owners.

Common pitfall: phase 1 ends with the requirements spec but without alignment on trade-offs. Six weeks later in phase 3, the business sponsor pushes back on a design choice that follows directly from a constraint nobody objected to in phase 1. The corrective is an explicit trade-off log during phase 1, with decisions captured and dated.

Phase 2: Concept and Architecture (3 to 10 weeks)

Objective: produce a system architecture and a concept set that has been pressure-tested against the phase 1 requirements. Phase 2 is where the program either commits to a feasible path or sends the riskiest elements back to the drawing board before sunk cost makes a course correction expensive.

What happens: system architecture is drafted at the block-diagram level. Concepts are generated against the requirements (typically 3 to 6 concepts in early ideation, narrowed to 1 to 2 through scoring). Feasibility studies confirm the riskiest elements. Bottom-up and parametric design approaches are applied where the constraints are sharp.

Deliverables: system architecture document, concept scoring matrix, feasibility study results, preliminary bill of materials (BOM v1), and a risk register with the top 5 to 10 program risks ranked by impact and likelihood.

Gate criteria: one concept is selected with documented rationale. Top three technical risks have mitigation plans. The preliminary BOM tracks within the cost target. The phase 3 work plan is scoped and resourced.

Common pitfall: the team falls in love with the first elegant concept and skips the scoring matrix. The corrective is the discipline of running at least three concepts through a documented scoring matrix even when one looks obviously right.

Phase 3: Detailed Design and Engineering (8 to 24 weeks)

Objective: take the selected concept and architecture and design the product in full engineering detail. Phase 3 is typically the longest phase and the one most internal R&D leaders associate with the bulk of the engineering work.

Engineers dive into the technical aspects of designing the product. Mechanical CAD in SolidWorks handles solid and surface modeling. Electrical schematics and PCB layout move into Altium Designer, Eagle, or KiCad. Firmware is written in C and C++, targeting microcontrollers like STM32, RP2040, Teensy, and PIC. Finite element analysis runs in ANSYS or SolidWorks Premium Simulation. Computational fluid dynamics is added where thermal or hydraulic systems are involved. Signal acquisition and PID feedback control configuration are handled in LabVIEW where instrumentation depth is needed.

“When you can do everything under one roof and all parts of the process are done in one place, it really streamlines the communication because you know who is responsible for each part of the project,” says Scott Romich, Mechanical Engineer at Bravo Team. The discipline coverage in phase 3 is what determines whether the design closes cleanly or fragments across handoff seams.

Deliverables: complete CAD model with full part-level detail, electrical schematics, PCB layout files, firmware source code, FEA and CFD analysis reports, design verification test plan, BOM v2 with sourcing notes, and a manufacturability assessment.

Gate criteria: design is complete to the level needed for prototyping. All requirements from phase 1 trace to design elements. Analysis confirms structural, thermal, and electrical performance against targets. The design verification test plan is approved.

Common pitfall: phase 3 runs over because requirements drift mid-design and the change-control process is informal. The corrective is a formal change-control process that requires sign-off on requirement changes after phase 1 gate.

Phase 4: Prototyping and Validation (4 to 16 weeks)

Objective: build physical units and test them against the design verification plan. Phase 4 is where assumptions meet reality, and the rate of iteration in this phase is the single largest predictor of program duration.

What happens: physical builds run through internal prototyping capability or the prototyping partner’s facility. Mechanical parts come off 3D printers and CNC machines. PCBs are fabricated and assembled. Firmware is loaded onto target hardware. Test campaigns run against the design verification test plan. FMEA is conducted on the assembled prototypes. Factory Acceptance Tests and Site Acceptance Tests are run where applicable. High-speed video captures mechanism behavior where verification cannot be done with static measurements.

“We eliminate lead times [caused by] outsourcing. And we eliminate redoing work or making mistakes because we can consult with the people who will take over further down the line early on,” says Stuart Draughn, Electrical Engineer at Bravo Team. The compounding effect of avoided handoffs is the largest source of iteration speed.

Deliverables: validated prototype units, completed FMEA, test results against the design verification plan, design refinements based on test outcomes, and an updated BOM (v3) reflecting any sourcing changes uncovered in fabrication.

Gate criteria: prototype units meet all design verification requirements. FMEA risks are mitigated or accepted with documented rationale. Manufacturing partner has reviewed the design and confirmed feasibility at pilot scale.

Common pitfall: prototypes pass functional testing but reveal manufacturability problems too late to fix without a major redesign. The corrective is engaging the manufacturing partner in phase 3, not phase 4.

Phase 5: Design for Manufacturability and Pilot Production (4 to 12 weeks)

Objective: tighten the design for production at scale and run the first pilot batch. Phase 5 is where the program transitions from engineering ownership to operations ownership, and the quality of that handoff determines how well the product scales.

What happens: DFM and DFA (design for assembly) reviews tighten the design for production economics. Tolerance analysis is finalized. Manufacturing process documentation is produced. Pilot production runs through the manufacturing partner with engineering oversight. The pilot run produces the first verified production-quality units and confirms cycle times, yield, and first-pass quality against targets.

“We ensure design for manufacturability from the very start. We pull in all the people that are going to be on the project from the very beginning. Whether that be mechanical engineers, software engineers, electrical engineers, technicians, or machinists that are going to be actually building the parts,” says Reid Wiemer, Director of Project Engineering at Bravo Team. “By doing that, we get all of the feedback up front.”

Deliverables: final design package, manufacturing process documentation, pilot production batch (typically 10 to 100 units), pilot run report with yield and cycle time data, and a manufacturing transfer package to the operations team or contract manufacturer.

Gate criteria: pilot units meet first-pass quality targets. Cycle time and yield are within the production economic model. Manufacturing process is documented and transferred. Engineering and operations have signed the production readiness review.

Common pitfall: pilot production reveals that the design is unmanufacturable at the target cost because DFM was treated as a phase 5 activity rather than a phase 3 discipline. The corrective is DFM integration into every phase from concept onward.

What Are the 7 Stages of the Broader Product Development Cycle?

The 7 stages of the broader product development cycle are idea generation, idea screening, concept development and testing, business case and strategy, product design and development, test marketing and validation, and commercialization and launch. Together they map the path from raw insight to a launched, supported product. The 5-phase execution arc fits inside stages 3 through 6.

The 7-stage cycle in brief:

1. Idea Generation. User research, market signals, internal innovation pipelines, and adjacencies surface candidate concepts.
2. Idea Screening. Concepts are evaluated against strategic fit, technical feasibility, and resource availability. Most are killed here, deliberately.
3. Concept Development and Testing. Surviving concepts are sharpened into testable propositions through user interviews, prototypes, and feasibility studies.
4. Business Case and Strategy. The team builds the financial model, defines the launch plan, and aligns leadership on go or no-go criteria.
5. Product Design and Development. Engineering design, prototyping, validation, and DFM. This is where the 5-phase execution arc lives.
6. Test Marketing and Validation. Pilot runs, beta deployments, and limited launches confirm production readiness and market acceptance.
7. Commercialization and Launch. Full production, distribution, marketing, and post-launch support.

For the framework-level discussion, see the PDMA NPD body of knowledge, the industry reference maintained by the Product Development and Management Association.

What Causes Product Development Processes to Slip?

Five recurring failure modes account for most timeline slip in enterprise product development programs: late requirements changes, supply chain dependencies discovered during DFM, prototype iteration loops that run longer than scoped, untested assumptions that surface during validation, and slow phase-gate decisions on the customer side. Each has a corrective that prevents it from recurring.

1. Late requirements changes after phase 1 gate. Requirements that change in phase 3 or later cascade through every downstream phase. The corrective is a formal change-control process with explicit cost and timeline impact assessment for every change request after phase 1 gate.

2. Supply chain dependencies discovered during DFM. A component on a 26-week lead time discovered in phase 5 adds 26 weeks to the program. The corrective is engaging supply chain in phase 2 to flag long-lead-time items during architecture, not after design freeze.

3. Prototype iteration loops that run longer than scoped. A program scoped for three prototype iterations that runs to six iterations adds the duration of three additional iterations to the timeline. The corrective is explicit iteration budgeting in phase 3 planning and a clear escalation path when the budget is exceeded.

4. Untested assumptions that surface during validation. A subsystem performance assumption that fails in phase 4 testing triggers a phase 3 redesign. The corrective is feasibility studies and proof-of-concept testing in phase 2 for any subsystem performance assumption that is not backed by prior art.

5. Slow phase-gate decisions on the customer side. A phase gate that requires four weeks to schedule the review meeting adds four weeks to the program. The corrective is scheduling the phase-gate reviews at the start of the program, not when the deliverables are ready.

How Does a Product Development Consultancy Fit Into Your Process?

A product development consultancy typically owns phases 2 through 5 (concept through pilot production) and integrates with internal teams on phase 1 (requirements) and the broader business cycle (commercialization). The integration model matters more than where the line is drawn. The work has to flow through phase gates on a shared cadence with named owners on both sides.

Three common integration models:

• Full execution. The consultancy owns phases 2 through 5 end-to-end, with the internal team owning phase 1 requirements and phase 6+ commercialization. This is the most common model for programs where the internal team is fully consumed by other priorities.
• Phase-specific. The consultancy owns one or two phases (typically phase 3 detailed design or phase 5 DFM and pilot), with the internal team running the others. This works when the internal team has gaps in specific disciplines.
• Embedded. The consultancy engineers are embedded inside the internal team and follow the internal program structure. This is closer to staff augmentation than to a true consultancy engagement, and is best reserved for sustained capacity gaps.

For a deeper look at the build-versus-buy decision and how to structure the integration, see product engineering consulting vs. in-house teams.

How Bravo Team Runs the Product Development Process

Bravo Team is a tech-enabled, people-first engineering partner with mechanical, electrical, software, and machining disciplines under one roof. The process discipline reflects the model: phase-gate reviews with the client-partner present, requirement traceability through every phase, FMEA conducted during phase 4, and DFM integrated from phase 2 onward.

The single-roof discipline coverage matters most in phases 3 and 4. Mechanical CAD changes that affect PCB layout get resolved across desks instead of across firm boundaries. Firmware engineers sit ten feet from the EE engineers whose hardware they are controlling. Machinists give DFM feedback in phase 2, not phase 5. The compounding effect of avoided handoffs is the largest source of timeline acceleration in a single-roof firm.

Case Study: Connected Access Device for the Outdoor Rental Market

A hardware startup in the outdoor rental market entered an engagement with Bravo Team with a working proof-of-concept and a fixed pilot launch date. The product was a connected storage device: a weatherproof enclosure housing a fail-secure electronic lock, four independent access paths (mobile app, admin dashboard, RFID badge, and manual key), and cloud connectivity for real-time status reporting and remote control. Missing the pilot window meant losing the first live venue validation. There was no schedule flexibility.

Phase 1 requirements work captured the non-negotiable constraints: a weight ceiling, an IP rating for outdoor exposure, extended runtime under worst-case load, and a fail-secure lock that remains closed on power loss.

Phase 2 architecture resolved the system-level decisions: a dual-board electronics approach, dual-battery power architecture, cloud-synced firmware, and a weatherproof enclosure designed around the electronics.

Phase 3 detailed design produced two custom PCBs (one covering power management and wireless communication, one driving the lock and e-paper display), embedded firmware built around a real-time device-state model synced to the cloud, and a mechanical enclosure engineered for outdoor conditions with passive cooling and tool-free battery access. The mechanical and electrical teams iterated across desks, not across firm boundaries, resolving enclosure geometry and PCB layout constraints in hours rather than days.

Phase 4 validation bench-verified every subsystem against defined pass/fail criteria for wireless range and power draw before design freeze. The final unit came in at approximately 23 pounds, within the client-partner’s weight ceiling, with every subsystem independently confirmed.

The engagement delivered a complete design package: schematics, PCB layouts, CAD models, and a full bill of materials. The client-partner’s manufacturing team received everything needed to carry the design into production without revisiting the electronics or firmware. That is the phase-gate model producing the outcome it is built for: each phase generating the specific artifacts the next phase needs to proceed.

Frequently Asked Questions

What are the 7 stages of the product development process?

The 7 stages of the product development process are idea generation, idea screening, concept development and testing, business case and strategy, product design and development, test marketing and validation, and commercialization and launch. The 5-phase execution arc (discovery, concept, design, prototyping, pilot) fits inside stages 3 through 6 of the 7-stage cycle.

What is the difference between product development and product design?

Product design is a discipline inside the broader product development process. Design focuses on the form, function, and engineering of the product itself. Product development covers the full process of taking a product from idea to launched, manufacturable production, including discovery, business case, design, prototyping, validation, manufacturing, and commercialization.

How long does the product development process take?

Concept to pilot production typically runs 6 to 18 months for enterprise hardware products, 3 to 9 months for software-only products, and 12 to 36 months for regulated products (medical devices, aerospace, food contact). Regulatory burden, not engineering complexity, is the largest variable. Phases overlap, so sequential addition of per-phase ranges overstates total duration by 20 to 30 percent.

What is stage-gate in product development?

Stage-gate (also called phase-gate) is the practice of breaking the product development process into defined phases separated by review meetings where the program is approved to proceed, sent back for rework, or killed. Stage-gate is the discipline that prevents scope drift and surfaces problems early enough to fix them without redesign. ISO 9001 design control formalizes stage-gate practice in regulated industries.

What is the difference between the product development process and the product life cycle?

The product development process covers the path from idea to launched product. The product life cycle covers what happens after launch, including production scaling, market growth, maturity, decline, and end-of-life. The two frameworks meet at launch.

Who is responsible for the product development process inside an enterprise?

Responsibility typically rotates by phase. Product management owns phase 1 requirements and the business case. Engineering owns phases 2 through 5 execution. Operations owns the manufacturing transfer at phase 5 gate. Marketing and sales own commercialization. A program manager coordinates across phases.

What tools are used in the product development process?

Common tools include SolidWorks (mechanical CAD and FEA), ANSYS (FEA and CFD), Altium Designer, Eagle, and KiCad (PCB design), C and C++ in Code Composer Studio, Microchip Studio, STM32CubeIDE, and Arduino IDE (firmware), LabVIEW and MATLAB (signal acquisition and analysis), and project management tools for phase-gate tracking. The specific stack varies by product category and team preference.

What is a phase gate and how does it work?

A phase gate is a structured review meeting at the end of each phase of the product development process. The review covers whether the phase deliverables were produced, whether they meet the gate criteria, and whether the program is approved to enter the next phase. Phase gates have explicit go, no-go, or rework outcomes documented at the time of the meeting.

Start the Conversation

If you are scoping a product development program and want to pressure-test the process plan, start with a 30-minute conversation. The goal is to understand where your internal team is stretched, what the launch needs to look like, and whether a partnership with Bravo Team would meaningfully accelerate the outcome.

Talk to an engineer →