canmove, Confirmed users
227
edits
Pancake/French Toast/Prototyping: Difference between revisions
Pancake/French Toast/Prototyping (view source)
Revision as of 17:28, 13 August 2012
, 13 August 2012Here's how
(Formatting) |
(Here's how) |
||
| Line 18: | Line 18: | ||
That's what a prototype's job is. It lets you test design assumptions with real users before expending engineering and financial capital on a potentially wrong assumption. | That's what a prototype's job is. It lets you test design assumptions with real users before expending engineering and financial capital on a potentially wrong assumption. | ||
== Method == | |||
Here's how we plan on testing Pancake prototypes. | |||
# '''Create an interactive prototype in Keynote'''. Keynote is extremely low cost in terms of time and effort, meaning an entire prototype can be changed or scrapped if found wanting. | |||
# Ask a volunteer to sit down with you for 15 minutes. | |||
# Optional: talk a bit about project background. Avoid specifics. '''Need to make sure we don't interfere with user impressions here''' | |||
# **NEED UR SCRIPT** talk to Diane? | |||
# Have the volunteer click through the interactive prototype. Take a think-aloud approach, asking user to talk about what they are seeing as they go. | |||
# Afterwards, give the user a crayon and paper. Ask them to draw what they just saw. | |||
# Ask user how they might use an app like this. '''Need to make sure we don't interfere with user impressions here''' | |||
Experiment goal: | |||
* Find out if design metaphors and app concepts make sense | |||
* Discover how real users reason about the app | |||
* Discover from sketches if we're emphasizing the right things in the designs | |||