Z515 Spring 2015

Prototype scenarios, not designs

One of the things I found the most interesting in these readings was the authors’ advocating for prototyping a part of your design and not the whole thing. I found this interesting because this is one of the major principles which people tend to forget. And this goes against the principle of ‘build early, fail often’. If you sit down to prototype everything before testing your design with users, you would never be able to finish testing early and letting go of our design would be more difficult.

Hence prototyping should be created around user scenarios and not designs. If you can select the major user scenarios, and create prototypes in the form of sketches, storyboards or interactive wireframes, you would not have to prototype everything, which will give you a chance to fail early and fail often.

Advertisements
This entry was written by ugupta2014 and published on April 13, 2015 at 1:40 pm. It’s filed under Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: