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

From MozillaWiki
Jump to navigation Jump to search
(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...)
 
(Added Metrics box)
Line 17: Line 17:
====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.
====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?
|-
| 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
|}


=== Timeline ===
=== Timeline ===

Revision as of 19:34, 12 December 2008

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

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

Preliminary Recommendations

Ubiquity Core

  1. Merge Ub with the awesome bar
  2. Use data gathering to capture failed commands to increase intelligence of the thesaurus
  3. Consider inserting iframes, working with providers to support commands directly.
  4. Make a fallback of google
  5. Make help non-linear

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.

Metrics

Research Questions
Performance Benchmarks
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?
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

Timeline

  • "Take the Ubiquity Tutorial, that sounds boring" 00:50
  • Reads everything but skips over hot-key.
  • Decides to try tutorial 2:15, immediately hates visual presentation.
  • Immediately skips past the hot key explanation
  • Tries typing in command and hitting enter without trying hotkey. 04:00
  • Mistakes the Awesome bar for Ub 4:20
  • Mistakes Google's "feeling lucky" function for Ub 05:00
  • 12:08 "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."
  • Gives up on Tutorial after almost 10 minutes 13:00
  • Tries video 13:30
  • 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
Retrieved from "https://wiki.allizom.org/index.php?title=Labs/Ubiquity/Usability/Usability_Testing/Fall_08_1.2_Tests/Tester_08a&oldid=120504"