Wishdex GR3

Briefing

Our application is Wishdex.com, a site that helps you keep wishlists, which you can use to track of items you find online, show your friends and family gifts you want, and see what your friends or celebrities are interested in. We're doing this test to get some feedback on how well we've designed the user interface. There are probably a lot of problems with the design, and we need help finding them. Keep in mind that we're testing the computer system, not you. Also, the results of this test will be kept completely confidential, and you can stop and leave the test at any time. My name is Susie, and I'll be reading out the tasks we want you to perform. This is Emily, and she will be moving around things on the screen, pretending to be the computer. This is Ashu, and he'll be taking some notes to help us remember the problems we find.

Scenario Tasks

We divided our scenario tasks into three sections corresponding to our task analysis from GR1:

1. Exploring
   1. Find interesting/popular items you may want to buy
   2. Look at what your friends are wishing for on Wishdex
   3. Find Maggie's wishdexes
2. Viewing
   1. Like an item on Maggie's wishdex
   2. Add a comment to an item on Maggie's wishdex
   3. Claim to buy the item for Maggie and view item on Amazon
3. Managing
   1. Create a new wishdex called "Birthday Wishlist"
   2. Add new item (a laptop case) to this wishdex from an Amazon URL
   3. Edit name of item
   4. Move "Crazy Shoes" from "Shoes" wishdex to "Birthday Wishlist"
   5. Share "Birthday Wishdex" with your mom

Observations

Summary of Important Observations

1. Meaning of "claiming an item" (Task 3c, Users #1-#6)
   All of the users who tested our design were unsure what the "Claim It" button did on the page for an item in a friend's wishdex. Some thought that it referred to telling the friend they were going to buy the item for themselves, which was in fact the exact opposite of what we wanted the button to indicate. The distinction between "buy it" and "claim it" was also unclear to some users. This confusion was also clear because many users asked what the checkmark button did when hovering over an item during the managing tasks.
2. Distinction between different wishdexes (Task 2a, Users #4, #6)
   Two of the users did not understand when first viewing a friend's page that the categories at the top indicated different wishdexes. They were more likely to have a single wishdex and putting all of the items they want into it, and therefore did not expect a friend to have multiple wishdexes on their page. It was also not clear that the categories were different wishdexes created by the user instead of being divisions of one wishdex created by the backend system.
3. Buttons did not seem clickable (variety of tasks, Users #2, #4, #5)
   Our designs made frequent use of large images as buttons for tasks such as going to a person's wishdexes, opening a wishdex, or going to an item page. It was often not clear that these images were clickable. This may have been an issue with the paper medium, but there are also probably issues with the design that could have increased their affordances for clicking.
4. Textboxes did not seem editable (Tasks 3a, 3c, Users #1, #3)
   Our designs also used text areas that would become editable if clicked on but seemed to be plain text before this. This was an especially an issue with adding a wishdex, because some users tried clicking on the plus button next to the textbox for the wishdex's name without entering a name first. Again this may have been an issue with the medium, but the design could have provided more affordances.

All Observations

Prototype iteration

We decided to use our second round of prototyping to explore a different approach to the viewing and exploring tasks that involved panes for navigation (inspired by the "Finder" design from GR2). However, we did perform iteration between user tests during each round for each of the important observations summarized above.

1. Meaning of "claiming an item"
   The