MozillaWiki

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

Page Discussion

Labs/Ubiquity/Usability/Usability Testing/Fall 08 1.2 Tests (view source)

Revision as of 04:32, 23 June 2009

547 bytes added ,  23 June 2009
m
→‎Continual Improvement
mNo edit summary
 
(16 intermediate revisions by the same user not shown)
Line 17: Line 17:
|- Style="background-color:#efefef;"
|- Style="background-color:#efefef;"
| <center>'''Tag'''</center>
| <center>'''Tag'''</center>
| <center>'''[[Labs/Ubiquity/Usability/Usability_Testing/UI_Triangulation#Rankings |Freq.]]'''</center>
| <center>'''Freq.'''</center>
| <center>'''[[Labs/Ubiquity/Usability/Usability_Testing/UI_Triangulation#Rankings |Sev.]]'''</center>
| <center>'''[[Labs/Ubiquity/Usability/Usability_Testing/UI_Triangulation#Rankings |Sev.]]'''</center>
| <center>'''Videos'''</center>
| <center>'''Videos'''</center>
Line 74: Line 74:
| 6, 7, 11
| 6, 7, 11
| Learnability
| Learnability
| Wiki, hotkey, mashup,
| Wiki, hotkey, mashup, etc.  See [https://wiki.mozilla.org/Labs/Ubiquity/Usability/Usability_Testing/Fall_08_1.2_Tests#Demonstrating_Value_.28marketing.29 Demonstrating Value]
|
| [https://ubiquity.mozilla.com/trac/ticket/547 547]
|
|
|-
|-
| Confused by wiki
| Confused by mozilla wiki
| 1
| 2
| 2
| 2
| 6, 8
| 6, 8
| Learnability
| Learnability
|
| We should move the help to something other than this Wiki.
|
| [https://ubiquity.mozilla.com/trac/ticket/402 402]
|
|
|-
|-
Line 92: Line 92:
| 9, 5
| 9, 5
| Learnability
| Learnability
|
| The "Help system" [http://www.indolering.com/indolering.com/Ubiquity_Blog/Entries/2008/12/9_Alternative_UI_Recommendations*.html includes] Wikipedia and Google.
|
|
|
|
|-
|-
| URL instead of email command
| URL instead of email command
| 2
| 3
| 2
| 2
| 11,4,9
| 11,4,9
Line 131: Line 131:
| Learnability
| Learnability
| External validity of this data is poor because all users were using the same wifi connection (ie not a random sample)
| External validity of this data is poor because all users were using the same wifi connection (ie not a random sample)
|
| [https://ubiquity.mozilla.com/trac/ticket/547 547]
|
|
|-
|-
Line 140: Line 140:
|
|
| Video is buzzword laden
| Video is buzzword laden
|
| [https://ubiquity.mozilla.com/trac/ticket/547 547]
|
|
|-
|-
Line 149: Line 149:
|
|
| Sound
| Sound
|
| [https://ubiquity.mozilla.com/trac/ticket/547 547]
|
|
|}  
|}  
Line 168: Line 168:
|- Style="background-color:#efefef;"
|- Style="background-color:#efefef;"
! <center>Tag</center>
! <center>Tag</center>
! <center>[[Labs/Ubiquity/Usability/Usability_Testing/UI_Triangulation#Rankings |Freq]]</center>
! <center>Freq</center>
! <center>Videos</center>
! <center>Videos</center>
! <center>Notes</center>
! <center>Notes</center>
Line 174: Line 174:
|-
|-
| Email-
| Email-
| 4
| 5
| 9, 11
| 9, 10, 11
| Two seperate issues
| Multiple issues, one being that users don't understand the need for modifiers ("'''to''' janedoe@gmail.com" or "email '''this'''").  Another being that users try typing in the URL of their service provider (mail.yahoo.com)- when that failed they assumed it didn't work with their email service provider.  Finally, the email command is just very buggy.
|
| [https://ubiquity.mozilla.com/trac/ticket/572 572] [https://ubiquity.mozilla.com/trac/ticket/574 574]
|-
|-
| Email+
| Email+
Line 185: Line 185:
|
|
|-
|-
| Maps-
| Map-
| 3
| 3
| 8, 9, 10
| 8, 9, 10
|
| Somewhat invalid as the errors are due to discovery problems with Ub itself. All participants cruised to Google Maps instead of using the command, provide [http://www.azarask.in/blog/post/can-ubiquity-be-used-only-with-the-mouse/ contextual reminders/clue] on Google Maps itself?
|
|
|-
|-
| Maps+
| Map+
| 4
| 4
| 7, 8, 10, 11
| 7, 8, 10, 11
Line 210: Line 210:
|-
|-
| Weather-
| Weather-
| 1
| 0
| 10
|  
|
|
|
|
Line 224: Line 224:
| 1
| 1
| 5
| 5
| Sudo did not show up in Define.com. Fallback dictionaries (urban, wiktionary, Google's define:, etc)
| Sudo did not show up in Define.com. Fallback dictionaries (urban, wiktionary, Google's define:, etc) would be a smart idea.
| 404
| [https://ubiquity.mozilla.com/trac/ticket/404 404]
|-
|-
| Define+
| Define+
Line 236: Line 236:
| 2
| 2
| 10
| 10
|
| This caused [http://www.indolering.com/indolering.com/Ubiquity_Blog/Entries/2008/11/12_Ubiquity_Translator_Command.html more confusion] than is reflected here.  Executing it was not the problem, users didn't expect it to change the text on the page.
|
| [https://ubiquity.mozilla.com/trac/ticket/54 54]
|-
|-
| Translate+
| Translate+
Line 248: Line 248:
| 1
| 1
| 10
| 10
|
| Couldn't guess the command correctly.
|
|
|-
|-
Line 254: Line 254:
| 6
| 6
| 5, 6, 7, 8
| 5, 6, 7, 8
|
| Requiring the user to click on the map is "counter intuitive."
|
| [https://ubiquity.mozilla.com/trac/ticket/542 542]
|-
|-
| Map-insert+
| Map-insert+
Line 386: Line 386:
It's hard to gauge how long people stayed tuned in to the screencast.  They would often experiment and then come back.  It would be good to get some analysis with a little JS to track how long our current user-base stay on the page/tab after clicking play.  Stay tuned for some [www.indolering.com blog posts] on thoughts concerning video.
It's hard to gauge how long people stayed tuned in to the screencast.  They would often experiment and then come back.  It would be good to get some analysis with a little JS to track how long our current user-base stay on the page/tab after clicking play.  Stay tuned for some [www.indolering.com blog posts] on thoughts concerning video.


=== Packaging Ubiquity for the Mainstream ===
Please provide the lessons you learned about packaging Ubiquity for the mainstream.
It is difficult to parse out what caused many problems, the formatting of the auto-suggest, the awkward help system, or the lack of visual reference for Ubiquity.
One thing that is interesting is that once participants started using Ubiquity they became fairly competent quickly.
The core interface for Ubiquity might not need help as much as changing the development cycle to include heavy-duty analysis of what users do and what they expect.
URL bar integration is a given, and Aza's implementation is very close to what I was envisioning, making findability a much smaller issue.  The study did provide some insight and push towards tweaking the auto suggest functions, the help system, and zeroed in on specifically bad ''commands''.
So I think the biggest lesson for me is how essential of careful communication is for new UI's.  We have to make sure we communicate in such a way as to not scare users off, not give false impressions, and convince users that Ubiquity is worth learning before they interact with Ubiquity.


-Zach


=== Demonstrating Value (marketing) ===
=== Demonstrating Value (marketing) ===
Line 415: Line 402:


=== Continual Improvement ===
=== Continual Improvement ===
TPS continual development cycle/ turning everything into a scientific experiment, [http://video.google.com/videoplay?docid=-6459171443654125383 implementation in software], measuring success of changes.
TPS continual development cycle turns everything into a scientific experiment, coming up with theories, hypotheses, testing, and analysis to make exacting decisions based upon those changes.
Participants have high expectations of Ubiquity to get things just
Participants have high expectations of Ubiquity to get things just
right. If a problem prevents a user from using a command they are unlikely to try again. While we do our best to anticipate those expectations and problems we can't
right. If a problem prevents a user from using a command they are unlikely to try again. While we do our best to anticipate those expectations and problems we can't
Indolering
501

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/129668...151203"