...
| Wiki Markup |
|---|
{html}<a href="javascript:showhide('design2');" id="design2show">Show this user test</a>{html} |
| Wiki Markup |
|---|
{html}<div id="design2" class="hidable">{html} |
User 1 - Observations:
Task 1:
clicks Tickets
clicks text box, enters informations, tabs to go to next text box
repeats until form is finished, grabs ticket
Task 2:
hit floor 2 look around
hit floor 3 look around
hit overview
hit floor 1
go to search type in ‘penguin’
go back to map
hit floor 2 and find it
Task 3:
floor 1
click triangular symbol
click round symbol
tap outside to close all bubbles
click triangular symbol, see info about session
“It was hard to not confuse triangles and circles, they look alike”
Task 4:
click on circles and triangles to read bubbles
“I expect the bubbles to close automatically when I click a different location”
click on section
“I would like if it at least said the name of the section”
User 1 - Changes made to the prototype after this test:
...
| Wiki Markup |
|---|
{html}<a href="javascript:showhide('design3');" id="design2show">Show this user test</a>{html} |
| Wiki Markup |
|---|
{html}<div id="design3" class="hidable">{html} |
User 2 - Observations:
Task 1:
Click tickets
Starts filling out information
(The user thinks expiration date is for the tickets)
(The user realizes it’s for the credit card when he reads ‘security code’)
Picks Boston first, then changes to California (his home town)
Click Buy
Task 2:
Search for ‘penguin’
Clicks on ‘look on map’
“I know I have to head over to that triangle now”
Task 3:
Search for ‘penguin staff session”
“I can go it’s 4pm”
“I don’t know if the number of current attendees means there is no space left”
“I’ll now head over”
Task 4:
(Confused, don’t know if to search)
Go to floor
Click on one of the symbols
“It should keep the titles for each one and more info should be on the legend”
“Legend is hard to find”
“Bubbles should be larger”
“Hover over should show titles”
Jeremy Comments:
Regarding ticket screen, “there is no info on the top”, “cc info and ticket information
should be separated”
User 2 - Usability issues & Changes made to the prototype after this test:
...
| Wiki Markup |
|---|
{html}<a href="javascript:showhide('design4');" id="design2show">Show this user test</a>{html} |
| Wiki Markup |
|---|
{html}<div id="design4" class="hidable">{html} |
User 3 - Observations:
Task 1:
“It’s touchscreen?”
Click tickets
Click ‘Today?’
Enter info
Click Buy
“Does it give me a QR code or something?”
Task 2:
“I’m not sure if this map is for the inside of the building, or how to get here in Boston”
Click Map
Click ‘lookup on map’
“touch the penguin?”
“is this supposed to be floor 2?”
“there is no gps...”
“I’m distracted by these icons jumping slightly”
Task 3:
(A home button is clearly needed for all screens)
Press floor 1
(Map now shows “events” instead of “sessions”)
“I thought the legend would list all things”
Task 4:
Click floor 2
“I would walk go to map from home”
User 3 - Usability issues & Changes made to the prototype after this test:
...
| Wiki Markup |
|---|
{html}<a href="javascript:showhide('design5');" id="design2show">Show this user test</a>{html} |
| Wiki Markup |
|---|
{html}<div id="design5" class="hidable">{html} |
User 4 - Observations:
Task 1:
Click tickets
Click ‘Today?’
Fills in form
Click ‘Buy’
“What is the price?!”
“Are there guest types?”
“I don’t know my confirmation number...”
Task 2:
Click search
‘Penguin’
Click ‘lookup on map’
“Does it mean I’m here?”
“Where am I?”
“Are there directions?”
Task 3:
“I want to go Home”
“There is no Home button”
Type “floor 1 events” in search
Click on ‘Map’
Click on floor 1
“expected to see a list of events on the left”
Task 4: (Find info regarding red fish)
Click on floor 2
Click on floor overiew
Click on section
(list of animal pictures show up)
“Is it a long list? It will be hard to find...”
User 4 - Usability issues:
...