On 6/2/08, Chauncey Wilson <[EMAIL PROTECTED]> wrote: > > I think that the answer depends on your goals and your audience. So > the answer could be either. If you are trying to create a "vision
Exactly. Typically, my prototypes look like clickable wireframes because most of the time my purpose in prototyping is to quickly answer the question, "does this suck or rule?" Testing a wireframey prototype is the way to do this. Now I have also done prototypes where the prototype itself was nearly indistinguishable from the existing system. There are three situations in which I do prototypes this way: 1) Is the project to add functionality to an existing system? 2) Is the functionality tightly integrated into the existing system? 3) Will the system's users freak out when they see a wireframe instead of what they're used to seeing? If the answer to any of these questions is "Yes," then I'll do a higher-fidelity prototype. If not, then it's almost always quicker, cheaper, and easier to do a lower-fidelity prototype. The information you get back will be just as good. - Fred ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
