GR3 - Paper Prototyping
Prototype photos
Briefing
Scenario Tasks
Observations
Day 1:
User 1 Test:
-Looked hesitant without list of contacts (should change for Friday)
-Tried to click "add friends" text
-Easily used checkboxes to navigate restaurant selection
-User chose restaurant rather than type of restaurant
-User having issues using poorly implemented prototype chat box.
-Waits for friends to order (rather than trying to continue)
-Hastily thrown together chat box is causing confusion (no place to type in words).
-Organizer unsure when everyone has ordered. Needs more visibility.
User 1 Comments:
-She didn't know much about what was going on with the chat box. This is perhaps because we're missing it this iteration.
User 2 Test:
-No premise given (so see how the user would react given this interface cold turkey).
-Easily finds Indian food (checkboxes seem easy). Chooses restaurant rather than type of restaurant.
-Seems to be some guidance in choosing friends.
-Utilizing Facebook connect will allow easy searching of friends.
-Tried to order for friends in addition to himself (didn't understand social aspect, which is understandable given above)
-Wants description of food items (not in this iteration)
-Can't see what friends are ordering.
-Also having confusion with the chat box
-Computer conjures up text box for chat. Enter to talk.
User 2 Comments:
-Add description to food.
User 2 Test, take two (after hearing premise):
-Chose type of restaurant
-On the "doodle" for communal restaurant selection: "Oh, it works. Cool."
-Tried to click on numbers?
-Much easier to chat now (with added text box)
User 2 Comments, take two:
-Mentioned that a mobile interface would be cool
User 3 Test:
-Confused by only one type of food highlighted (Chris had to explain)
-Unsure of whether or not you could choose one or multiple (restaurants on initial selection). Need to make this more visible
-Chose type of food rather than restaurant (with prompting in task)
-Should really prompt users who they're adding as friends
-Confused by restaurant selection Doodle screen
-Tries to order for friends
-Doesn't know if she has to wait for everyone to decide.
-Should make visible who is actually present in the order
-Chat still failing
-Computer tries to show who has ordered and who hasn't at the top of the chat box
-"Does the sad face mean she hasn't ordered yet?"
User 3 Comments:
-A lot depends on whether or not users are there already
Summary:
-Chat box sucks.
-Restaurant selection is hazy
-Need to make visible who has ordered and who hasn't, also make easier to see who is ordering what
-Need to make social aspect more visible as well, as we had people trying to order for their friends
Day 2:
User 1 Test (little premise given; again, to see user response to lack of information):
-Seems hesitant overall
-"Where's the order button?" (On initial screen, wants to order food right away rather than just select restaurant)
-"Are they supposed to be with me right now?" (Referring to friends)
-"I think if I'm ordering with friends they'll be right next to me, not on Facebook"
-"Oh I could have just clicked [send invite]"
-Ok, we really need a better initial explanation, or more affordances for what the user is actually doing
-Was under the impression that he was just paying for *his food*, not paying for all and running an order
User 1 Comments:
-"Good for company/group meetings"
-Suggested that we have more affordances for "payer" (should indicate that organizer is the one paying)
-Didn't seem to agree with concept.
User 2 Test (Less minimalist):
-Invited friends first (rather than choosing restaurant)
-"This looks very much like the facebook thing" (in reference to add friends)
-"This seems like what I would do to pick the place, but then there's this order thing"
-"Don't know if [optional message] is some sort of chat thing"
-"Feels strange. Feels permanent." (on send invite)
(At communal restaurant selection)
-Torn between clicking "choose" and clicking check box
-Notices that his friends are starting to check boxes
-"Looks like Jenny voted twice. (oh, they can do that)"
-"I'm going to wait for people"
-Confused a bit because count looked like radio button (when it was at zero)
(At ordering)
-"I want to go family style."
-"I was planning on adding this item and then splitting this item"
-Splitting seemed to work.
-Wait, are we offering splitting to things that have already been ordered?
-Sit here and wait. Seems to be a need for check box.
-"Pressing [review and submit] will move everyone forward"
-Review and submit highlighted
-User doesn't seem to be sure what's going on elsewhere. More affordances for done?
User 2 Comments:
-Couple things that didn't seem obvious. If I was invited, done button? After the first time, totally get it. First time, wasn't inherently obvious. Basically, need more affordances for being done.
-Would get the idea with the red and green background thumbnails. However, less obvious of the color change
-In the actual menu, maybe highlight things that have been ordered?
-Fairly easy to order family style.
User 3 Test (not minimalist, w/robot):
-"I guess I want to get Indian" (clicks easily)
-"So, is there going to be a list of Indian restaurants (highlighting fail-prototype didn't include list of Indian restaurants)"
-Tries to initially choose food when viewing menu of restaurant (in initial selection phase)
-Assumes order is saved somewhere
-"Is add friends a link?"
-Tried to hit "Send invite" without adding friends
(At communal restaurant selection)
-"These are restaurants?"
-Seemed to understand after votes began to come in
(At ordering)
-"Now I can order food?"
-"So this is periodically updating? So I have to wait for this thing to be done first?" (didn't seem to get social aspect)
-No affordances for waiting until friends are done. Rather, doesn't indicate what happens if you send an order without everyone ordering.
User 3 Comments:
-Forcing to invite friends before ordering. Wanted to choose food first.
-Maybe the initial list wasn't clear?
-Confused by "Invite friends" vs "Send invite". Perhaps Send invite should be grayed out.
-Robot didn't help.