Well, it all starts with the initial product design and concludes with a Product Design Review where a predominant percentage of a product's lifecycle costs and market applicability and usefulness are determined at minimal project cost. It's also imperative and extremely cost-effective to require the stakeholders who are most experienced and knowledgeable about (and responsible for) the development, production and marketing of the pending product to be involved during the Product Design Review. It's beneficial for them to also be involved in the design if possible.

For this to be effective, a mechanism is needed to embody the product design in a form that the stakeholders can use to examine and understand all product design implications. The stakeholders can, from their various viewpoints, then debate and justify issues that represent their particular needs.

An appropriate initial boundary object, which allows intra-stakeholder understanding of the design, is the Product Design Specification (PDS). The PDS must be established right at the beginning of a new product development project. This initial foundation of communication and its critical review will help to prevent disconnects within the "intellectual-capital supply chain", which usually would create misunderstandings and problems in the ensuing development project.

A multitude of design, project and product reviews and design representations (boundary objects) may be required for various sizes and complexities of product development products. However, the Product Design Specification (PDS) and the subsequent Product Design Review can not be over emphasized as to their efficacy on the product life cycle costs, cost reduction opportunities and the product's ultimate market viability.