Sketches in Product Requirements Documents
Defining product requirements is a critical part of the product development process. One study, by Ashok Gupta published an article in California Management Review claimed that 71% of all problems that are encountered in the product development process are the result of a failure to identify requirements. The difficulty in doing this arises from the multi disciplinary nature of product development. Each discipline (Marketing, Engineering, Manufacturing) has its own specialized language used to discuss their unique product requirement objectives. This hinders a collective agreement on requirements. Best practices aim to solve this problem. There are a host of techniques for product requirements gathering, and specification writing, for example, VOC, Voice of the Customer. But, the results of the techniques are still subject to interpretation and the biases of the individual reader. One additional step helps to clarify the results; it very useful to verify relevant findings by including sketches of the physical attributes identified in the VOC study in the requirements document. The sketches make very clear what the attributes are in a universal neutral visual language. Marketing and Engineering see the sketched images and interpret them the same way. The product requirements document allows people within a company to understand what a product should do and how it should work. Sketches are a very effective addition to that document and the product development process.
- 0Comments
- Trackbacks (0)
- Permalink




Comments
Post has no comments.