The product type has a lot to do with what specific tools and strategies are needed to manage PDue-diligence. Markets such as commercial, OEM, military, medical, nuclear, knowledge, etc. have varying demands for quality, reliability, documentation, testing, reports, certifications, traceability, etc.  What works for high volume may not work for low volume.  What works for a knowledge product may not work for a hard product and what works for software may not work for hardware:  For example, software that constantly is constantly open to hacking is a totally different product quality (and cost) problem. "Software developers already spend approximately 80 percent of development costs on identifying and correcting defects, and yet few products of any type other than software are shipped with such high levels of errors." ⁴

In any case, the following elements are general enough to be applied to product development in most any industry.

The product developer needs to take the attitude of not just being the techie responsible for implementing a product out of 'parts, material and code', but also being a product developer creating a product out of 'information'.  This attitude requires working with the marketing, production, financial and management teams and sharing responsibility for the whole product concept.