...
We briefed the users by presenting our problem statement from previous GR’s, and presented the users with the following tasks: *
- User Account
...
- Sign up for a ContactLens account
...
- Add 2 or 3 contacts
...
- Connect with one of those contacts via twitter and email
...
- Edit some contact information and make notes
...
- Sample account
...
- Explore the grid to filter and search for contacts
...
- Find “Victor Pontis”
...
- Find Beta users
...
- Adjust the size of a few contacts
We ran into some of the following usability problems *
- Learnability
...
- All 3 users weren't able to figure out what to do after the signup page (should’ve authenticated Twitter account
...
- , 1 and 3 attempted to change password)
- User 1 attempted to use comma delimited tags, while user 2 tried space delimited tags
...
- Users 1 and 3 didn’t realize you have to save tags using the “Save contact” button
...
- User 1 didn’t find resizing intuitive
...
- User 1 didn’t notice the tag search as separate from the name search
...
- Users 2 and 3 weren't sure what to do about “add contact” or “grid”
...
- User 2 found “add contact” to be out of place next to grid, thought it should be next to filters
...
- User 3 thought history was tied to interaction medium
- Safety
...
- User 1 found that confirming leaving a page without saving was necessary
...
- Users 1 and 2 needed to authenticate, but didn’t and ran into errors when trying to engage with customers
...
- Efficiency
...
- User 1 was interested in last contacted date search
...
- User 1 wanted resizing in place
...
- User 2 wanted to search by content, such as emails
- User 3 wanted to read whole tweets
- User 3 expressed concerns that tweets were not automatically linked
- User 3 wanted to relate size of card on grid to priority, as well as metadata (ie tags)
Reflection
One of the major lessons learned through implementing ContactLens was the balance of breadth and depth. Because of the vast number of APIs we were accessing, we quickly realized that we would not be able to implement a fully functional product in the timeline given. One of the difficult design decisions was to leave several of the APIs unimplemented. However, there was a large sunk engineering cost in the first week of the project setting up the product to be ready for use with all of the APIs.
...