...
- Check messages to see if anyone has responded to your listing.
...
Observations
User 1
When User 1 first opened the user interface to complete his first task of giving a toy, he started by filling in his name and description until the “Condition” field tipped him off. As designers, we had assumed that the user would automatically know that we only cared about the toy’s information rather than the user himself’s information. Next, User 1 was curious as to what the box on the right entailed until he guessed that it might have to do with a picture, and he wished allowed that there was a placeholder picture. When the user saw the “add toy” option, he thought it would act like a submit and suggested using “Add Another Toy.” The user was also really confused with the difference between what a single item and a collection of items entails such as “Is a deck of cards a collection?”
For the second task, it was unclear to the user whether the images would dynamically change or there needed to be a submit button for the search. This was probably a result of the fact that the prototype could not change fast enough for the user to realize it was dynamically changing. The user had trouble figuring out how the drag-and-drop worked since clicking the image already showed more detailed information, so he did not think to drag the photo.
The “New” button was confusing to the user as to what exactly it would entail. Messaging was unclear to the user even though it was modeled after Facebook’s messaging feature.
User 2
When registering toys on the website, User 2 put his contact information in the description field of the list toys interface. This was unexpected as we expected people to use the messaging feature, but not being exposed to the product like we were, the user thought the description was the appropriate place to put the contact information. He also was a bit confused about there not being a placeholder image for the image box that is filled after selecting a URL or file from disk to populate it.
...
- Field names unclear
- Confused by browse/URL since there was no picture placeholder
- Add toy looks like it behaves like submit
- Single vs Collection
- No clear all option
User 2
- User wanted to put contact info in description
- User wanted a picture placeholder but was able to assume function
- User wanted a button that says “any” for age
- User wants submit confirmation for donation
- “Any” condition for dropdown filter
- Drag and drop not obvious
- Feedback on hover for shopping cart
- What does clicking on cart do
- Confirmation that message was sent
- Notification on envelope for unread messages
User 3
- Where is remove button on toy listings page?
- Can I submit toys of different types at once?
- Checkout is confusing...
- User tried clicking shopping cart (does nothing)
- Can I cancel order after placing it?
Summary
- Make age range a drop down
- “Add toy” label changed to “Add another toy”
- Distinguish single toy vs collection of toys better
- Add clear filters button
- Delete new button in message window
- Add send button in message window
- “Any” field in toy condition search filter
- Affordances for cart on drag and drop
- Add to cart button as well in receive page
- More clear remove button on add toy listings page
- Distinguish which message is going to which user for which item on requesting items
- Change name of “checkout” button