R3 - Paper Prototyping

e did 2 round user-testing. We choose to focus on our Dual-Window Design for user testing.

Prototype photos - Round 1

Design Sketch -

Here is the briefing we gave to users: Purpose of application: To explore the food options safely using our menu.

You are a "chicken vegetarian", someone who is a vegetarian, except that you eat chicken.You are also allergic to peanuts

Scenario Tasks

Here are the tasks we gave to users, one after another.

1. Enter the dietary restrictions to the interface.

2. Browse the menu for an item that you can safely eat.

3. You realize today is a special day so you want to eat burgers.

Total number of users tested: 6

Restrictions
- Unclear whether checking item 'includes' or 'excludes' it
- Item preference selection inconsistent between 'restrictions' menu
- 'Partial checkbox' for partially-restricted item groups is unclear
- Some food categories were obvious (chicken is obviously under 'protein'), some were not (is 'peanuts' under grains?)
- Users appeared to understand that checking an 'item group' meant checking everything beneath it
- Right-pointing arrow to indicate 'folded accordion' was well-understood
Groups
- Not clear if checking 'vegetarian' is reversible
- Some users simply selected 'vegetarian' and did not attempt to 'de-select' chicken
Item browsing
- Not clear at first that this is *not* an ordering system, just a menu system
- Not immediately clear what selecting 'happy face' did (reordered preference list, moved preferred items towards the front)
- One user wanted to be able to 'dislike' food; not sure if that would cause even more confusion
- Use of 'neutral' face to indicate lack of restriction/preference is confusing; suggest happy face (and excited face for preference)
- Some users thought X/neutral face/happy face meant 'amount of ingredient in food'
- User are not sure how to deselect an item.

Unify preference/restriction editing menu
- Instead of X/neutral face/happy face, use 'disgusted' face/happy face/excited face
- Use clearer categories than 'grains/fat/protein' (where are peanuts?)
- Drop check-box interface entirely
  - Perhaps preserve 'restrict all' button?
- Use same interface for 'edit
Clarify how to switch between menu and restrictions
- Big, eye-catching arrow
- 'Directional' for consistency; the menu is to the 'right' of the preference restrictions
Remove ability to edit 'generic' preferences from menu viewing; only list selected items. Decrease UI clutter
Using 'leading' phrases to indicate what to do: "what can't you eat?", etc.
Add 'undo' button to indicate actions are reversible; grayed out when no actions are possible

Modified Revisions - (Wei added / feel free to edit)

Ignore the "preference" option and focus on the restriction - to avoid confusion.
Put the restriction and the menu on the same page - improve visibility, enable direct manipulation
Add Language Option Button - to overcome language barrier issue.
Add registration option / Save button, in case the user wants to build a profile - Improve efficiency .
- If the user click the save button, she sees a sign-up/login page, which enable her to save the restrictions to her account .
Strike through the ingredient when it's checked/clicked, also change the color of the chosen ingredient to red - add visual cue to the chosen restriction ingredients.
Use small user-friendly pop-out window, while darkening the rest of the page - To let the user to check the ingredients more thoroughly. ** small window contains: *** with list of full ingredient
- - input field for possible special instructions
  - a big green "Add item" button,
Add "Saved Item" column. - Let user review what has been saved** When user save an item, it will show up on the "Saved Item" column.
- Show price for each item, and also show subtotal,tax and total price.
- Remove option (a red cross icon) shows up when an item is clicked.
- Add a green Print button.