Labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests/Tester 08a: Difference between revisions

m
(New page: === Tester 008 === "My idea is that the interface should be so intuitive that one doesn't even have to try, it should just do what you think it should do." === Highlights === # Mistaking...)
 
 
(11 intermediate revisions by one other user not shown)
Line 1: Line 1:
=== Tester 008 ===
== Tester 008 ==
"My idea is that the interface should be so intuitive that one doesn't even have to try, it should just do what you think it should do."
''Embed [http://www.viddler.com/explore/indolering/videos/11/ video] here.''


=== Highlights ===
== Highlights ==


# Mistaking the awesome bar for Ub 04:20 -Specifically the Google "feeling lucky" function 05:00!
# Mistaking the awesome bar for Ub 04:20 -Specifically the Google "feeling lucky" function 05:00!
# Random guessing of commands 29:30
# Random guessing of commands 29:30


=== Preliminary Recommendations ===
== Preliminary Recommendations ==
====Ubiquity Core====
This tester highlights a deficit of statistical UI testing, remote testing of click through on a page cannot show when the user clicks on something thinking it will do something it doesn't.  We can't very well log all of the users keystrokes.  Is there a way to monitor this behavior?
 
===Ubiquity Core===
# Merge Ub with the awesome bar
# Merge Ub with the awesome bar
# Use data gathering to capture failed commands to increase intelligence of the thesaurus
# Use data gathering to capture failed commands to increase intelligence of the thesaurus
# Consider inserting iframes, working with providers to support commands directly.
# Consider inserting iframes (as opposed to JPEG screen captures), working with providers to support commands directly.
# Make a fallback of google
# Make Google a fallback
# Make help non-linear
# Make help non-linear


====Translate Command====
===Translate Command===
Raskin's 1st law of Interface Design "A computer shall not harm your work or, through inaction, allow your work to come to harm " 22:15  -I believe a single user has guessed to reload the page, after three previous failed attempts.
Raskin's 1st law of Interface Design "A computer shall not harm your work or, through inaction, allow your work to come to harm " 22:15  -I believe a single user has guessed to reload the page, after three previous failed attempts.


=== Timeline ===
==Metrics==
 
{| cellspacing="0" border="1"
|-
| <u>Research Questions <br /></u>
| <u>Performance Benchmarks<br /></u>
|-
| How do users try and access Ubiquity
#Number of things they tried before launching Ub.
#Time before launching Ub
#Did the instructor have to directly show them how?
|
#3
#20 minutes
#No
|-
| How do they learn the command syntax?
|
|-
| Do users value Ubiquity?
*Feedback
*Followup studies
|-
| How would we identify problematic commands via statistical analysis?
*look at failed commands & commonalities
**Lack of completion
**High error rates
*User feedback of poor commands, correlate with data
| *Tester put in commands elsewhere that they did not belong, can we monitor that?
|}
 
== Timeline ==
* "Take the Ubiquity Tutorial, that sounds boring" 00:50
* "Take the Ubiquity Tutorial, that sounds boring" 00:50
* Reads everything but skips over hot-key.
* Reads everything but skips over hot-key.
Line 30: Line 63:
* Tries video 13:30
* Tries video 13:30
* F*ng loves the demo 14:00
* F*ng loves the demo 14:00
* Massive amount of random guessing of commands, most of which is not apparent as he just types randomly on the keyboard 29:30</div>
* Randomly guesses commands 29:30
canmove, Confirmed users, Bureaucrats and Sysops emeriti
960

edits