chakachck
Monday, January 6, 2014
Tuesday, March 11, 2008
The question of prototypes
having worked for now more than a decade in the design and innovation field the question of prototypes keeps coming up again and again.
of course there are many ways of doing it but it is their purpose that I have been trying to nail. Is it a simulation for checking the principle? is it a method to check it's value with the users? is it for demonstration? etc etc.
Within the technology space where we are constantly looking for the next big wow how does one deal with prototyping. This is a question often asked mostly by people who are constantly watching the dollars drain in the spread sheets. Some time ago a manager who had been working on creating a working demo for his technology concept caught up with me and asked me if there were any shortcuts to achieve this final objective. In this case for a long time they were just trying to work out something that could be used so that they could test it out with people and basically validate the experience. Now looking back if that was the end in mind one could have easily mocked the experience with a technique usually known as the wizard of oz.
Now the question is that is there anything that was achieved by actually making a working demo that is of more value than the wizard of oz.
Then the question is why do we prototype. what are all those things that should be considered before prototyping. Are there any guides to this decision making process that can help innovation groups decide on the kind of prototyping that should be employed in their context.
So I'm going to just try to make a list of all the kinds of things that could be done and let's see where this all leads:
of course there are many ways of doing it but it is their purpose that I have been trying to nail. Is it a simulation for checking the principle? is it a method to check it's value with the users? is it for demonstration? etc etc.
Within the technology space where we are constantly looking for the next big wow how does one deal with prototyping. This is a question often asked mostly by people who are constantly watching the dollars drain in the spread sheets. Some time ago a manager who had been working on creating a working demo for his technology concept caught up with me and asked me if there were any shortcuts to achieve this final objective. In this case for a long time they were just trying to work out something that could be used so that they could test it out with people and basically validate the experience. Now looking back if that was the end in mind one could have easily mocked the experience with a technique usually known as the wizard of oz.
Now the question is that is there anything that was achieved by actually making a working demo that is of more value than the wizard of oz.
Then the question is why do we prototype. what are all those things that should be considered before prototyping. Are there any guides to this decision making process that can help innovation groups decide on the kind of prototyping that should be employed in their context.
So I'm going to just try to make a list of all the kinds of things that could be done and let's see where this all leads:
- Wizard of oz simulation (just fake the entire user experience)
- Working principle model (works but looks like something out of a garage)
- paper prototypes (wire frames on paper, good for software UIs)
- HTML prototype (actual pages that can be navigated through)
- Styrene and clay models
- Detailed model (looks like the real thing but doesn't work)
- Concept sketches (just some doodles on paper)
Tuesday, April 3, 2007
mystery of the medium
does a paper need to start up ? no
does the paper tie the individual to a certain kind of interaction with itself? no, it does not impose or demand any particular kind of action.
does the paper tie the individual to a certain kind of interaction with itself? no, it does not impose or demand any particular kind of action.
Subscribe to:
Comments (Atom)