Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

-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:

Wiki Markup
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.

Wiki Markup
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.

Prototype iteration