This issue is more problematic and contributes a lot to the misunderstanding of the product design review.

The design process generates the blueprint (i.e., design concept), which must be embodied in some negotiable, tangible form: e.g., a written document, CAD representation, web-based representation, model, etc. This detailed embodiment of the design is what some call the Product design Specification (PDS). The PDS outlines as much 'global', qualitative information about the product as can be knowable and assessable and it provides the criteria against which the design can be evaluated by the stakeholders. The PDS should not limit or constrain the implementation solutions or subsequent development processes because this action may, itself, constrain the design review.

The PDS is one of a set of what can be classified as Boundary Objects⁶ - "concrete objects used to communicate and transform understanding across differences in expertise, organizational norms and time frames..."

Boundary Objects are used as "conscription devices, they enlist and organize group participation. As boundary objects, they facilitate the reading of alternative meanings by various groups involved in the design process. The use of a boundary object is then described as a means of representing, learning about and transforming knowledge to resolve the consequences that exist at a given boundary."

Here, the boundary is the knowledge and experience interface between the various disciplines (e.g., design, hardware, software, production, finance, sales, service, regulatory, etc.), which collectively create and implement a product development project. Other boundary objects used in this manner are shown below in figure 2.

Thus the PDS, being the initial the boundary object in a product development project, is used for common reference by the stakeholders to convey precise information across the various technical, departmental, cultural, etc. boundaries that separate the stakeholders. The PDS can be composed of pictures, storyboards, Wikis, models, competitor's samples, written documents, computerized renderings (2D, 3D, and anime), etc. Establishing and maintaining the mutual intelligibility of the boundary objects is critical to the efficiency and success of a project and it is the project manager's responsibility.

So, what does a product design blueprint (or PDS) contain that qualifies it as a boundary object? It's mostly qualitative declarations describing all of the relevant market, functional, performance and 'consumer charisma' attributes that a product requires, according to the product stakeholders - as best as can be established or assessed. The more complete the PDS, the less probability that as the product evolves it will stray from resolution and agreement of the original concept.

For more details about the PDS click on: