“IDEO”
prototypes have various forms. According to an article written by two apple computer employees, Houde and Hill (1997), prototypes prototype the “role,” “look and feel,” or “implementation” of the final products. This suggests that designers should be able to make different forms of prototypes for one product idea (i.e., 3D space planning application).
One step further, prototypes serve different objectives. Last summer, when I visited IDEO, I found a series of boards which describe why designers build prototypes; they do so for “inspiration,” “experimentation (evolve),” or “validation (specify).” This further suggests that different forms of prototypes serve different purposes for one product idea (i.e., Swiffer cleaner).
Given that there are different forms and different objectives of prototypes, do designers need different forms of prototypes for their objectives? For instance, are the “role” (or functional) prototypes more appropriate when designers “think” about their final products but less appropriate when designers “specify” their final products, compared to the “look and feel” (or aesthetic) prototype?
so this can be exactly what becomes of darwanism