In my previous article we covered the advantages of a phase and gate structure for new product development. Now we can discuss some proposed phase names for a new product development or product life cycle (PLC) process.
An organization may have an existing PLC process ‘baked-in’ to their culture and process documentation. Accordingly, there’s a wide range of PLC phase names, all of which are likely acceptable and based on solid reasoning.
In the interest of examining a PLC process, listed below are some proposed product life cycle phases:
Note that each phase is outcome-based, with the outcome focused on the product, increasing levels of design maturity and reduced design and manufacturing process risk. A gate review at the end of each phase should be able to answer the following questions:
From a risk mitigation standpoint, we want to avoid investing in detailed design of an inadequate design concept, avoid formally verifying a design that’s still evolving, we want a fully qualified design before production, etc.
Also, we’re keeping our “eye-on-the-ball” by focusing on an increasingly mature product/deliverable (good design concept, complete design, verified/validated design) in addition to enabling the ongoing business decision to (continue to) invest in the product.
Flexibility can be built-into this framework as needed, however. If the risk is low to formally verify aspects of the design before it’s full detailed, then that’s entirely acceptable. We can also assign milestones and deliverables according to these phases (for example, product requirements completed by the end of the concept phase).
Establishing and applying product life cycle process can significantly reduce risk, improve alignment of resources and enable project planning and governance.