As a locker owner, i want to be guided through the process of setting it up
Note: The following wireframes have Singly in the header, but this is generic functionality for Lockers, regardless of where they're hosted.
- Browser support
- Chrome (latest stable)
- Firefox (latest stable)
- Safari (latest stable)
- Selenium Test(s)
- Start to finish with installing all services (Facebook, Google Contacts, Twitter, GitHub, Flickr) using test OAuth tokens.
- Test using bad tokens
- Test with bail out
- Backend Tests
- Connector Endpoints
- Collection Endpoints
-
HTML matches Wireframes (roughly)
-
User Test with working prototype with 5 social web users (facilitator asks each participant to complete an action). This process is based on Steve Krug's approach defined in "Rocket Surgery Made Easy".
- Video camera captures the user's reactions, as well as what they're doing on the screen.
- Welcome: Facilitator welcomes participant with pre-defined script (5m, p70)
- Questions: Questions are asked about participant (2m, p73)
- The Tour: User is presented with a brief home page tour (3m, p75)
- The Tasks: Facilitator asks user to complete the task of completing the wizard (5-35m, p76)
- Probing: Facilitator provides participant time to go back and probe the process they just went through in order to get more feedback about what they're thinking (5m, p78)
- Wrapping Up: Ask "Does that seem like a worthwhile way to spend XXX minutes?", and thank them for their time and help (5m, p79)
Just doing a 5-person survey isn't enough to adequately get feedback this particular feature. In addition, we want to address the following approaches in the future, and will need infrastructure / 3rd party help in order to complete them.
Less in-depth with fixed response options, which is used to get statistical data for analysis.
- Start to Finish Conversion ("what percentage of people get through the process?")
- Start to Finish Conversion funnel breakdown (mixpanel?)
- Eye Tracking Survey with 10 people (do the users follow what is expected?)
More in-depth information for a few scenarios with focus groups. No statistical tests, less generalizable.
- Feedback Army Questionare (25)
- Locker Project Community Questionare
- Informal in person at Singly (new user is tasked to "setup a locker for the first time" and asked to speak aloud)
In order to satisfy proper user testing, we will need the following services most likely.
- Feedback Army
- Google Analytics
- Get Satisfaction?
- GazeHawk?
- Mixpanel?
- Olark?
We're going to want to have a way for people to opt in to a program to measure the above metrics. How do we do this? Is this technically feasible for non-hosted lockers?
-
John Britton:
-
Martha Denton:
-
Jasmine Trabelsi:
-
High level feedback (with a more thorough and robust set of notes following the completion of the 5 usability tests):
- People were receptive to the service avatars for their simplicity
- 3 of 3 subjects were confused by the spinning wheel. They all thought they had to wait around for it to finish spinning.
- Showing node.js was confusing, even for John Britton (Twilio's ex-hacker extraordinare)
- People had guesses as to what "contacts," "links" and "photos" might be, but they lacked certainty.
- No one wanted to read the copy on the front page regarding what a locker is. Everyone just wanted hit, "Let's get started." I had to ask them to read the copy.
- 3 of 3 subjects were most uncomfortable adding Facebook.
- Folks had no idea what to do when they first got the mainly white page after connecting a service. One refreshed, one moved it down below.