Phase 0: Feasibility Analysis
The goal of this phase is to identify existing technology to achieve the intended high-level function. If technology can be purchased as opposed to developed, the scope of subsequent development phases changes.
Simply put, product development companies research and assess the probability that the current technology can be used to reach the intended functionality of the product. By doing this, the development efforts are reduced, which in financial terms represent a great reduction in development costs.
Moreover, if the technology is not yet available, then the assessment can result in longer development cycles and the focus moves into creating the new technology (if humanly possible) that can accomplish the functionality of the product.
This is an important part of the in any product development process because it is safer and financially responsible to understand the constraints that a product can have prior to starting a full development cycle. A feasibility study can cost between 7 -15 thousand dollars. It might be sound very expensive for some, but when it is much better than investing $100k+ to end up with a product that no manufacturer is able to produce.
Phase 1: Specification or PRD (Product Requirements Document) development
If your product is feasible, congratulations! you are a step closer to creating your product and you can move into documenting what is going to go into the product itself, aka the guts (product objective, core components, intended end-user, aesthetics, User interphase, etc).
In this phase, product design and engineering focus on documenting the critical functionality, constraints, and inputs to the design. This is a critical step to keep development focused, identify the high-risk areas, and ensure that scope creep is minimized later.
This document will help you communicate the key features of your product and how they are supposed to work to all members of your team. This will ensure that you keep everyone involved on the same page.
Without one, you are more likely to stay off track and miss deadlines. think about the PRD as your project management breakdown structure (BDS)
Phase 2: Concept Development
Initial shape development work identifies options for form, as well as possible approaches for complex mechanical engineering challenges. Initial flowchart of software/firmware also happens here, as well as concept design level user interface work. Aesthetic prototypes may be included in this Phase, if appropriate. Prototype in this phase will not typically be functional.
Phase 3: Initial Design and Engineering
Based on decisions made at the end a concept development phase, actual product design and engineering programming can start. In this phase, Level 1 prototypes are often used to test approaches to technical challenges.
Phase 4: Design Iteration
This part of the project is where we focus on rapid cycles, quickly developing designs and prototypes, as the depth of engineering work increases. This phase can include Level 2 and 3 prototypes, typically through multiple cycles. Some products require as many as twenty prototype cycles in this phase. Others may only require two or three.
Phase 5: Design Finalization / Optimization
With all assumptions tested and validated, the design can be finalized and then optimized for production. To properly optimize for production, product design and engineering teams take into account the target production volumes, as well as the requirements of the manufacturer. Regulatory work may start in this phase.
Phase 6: Manufacturing Start and Support
Before production starts, tooling is produced, and initial units are inspected. Final changes are negotiated with the manufacturer. Regulatory work also should wrap up in this phase.