1 / 17

Usability Testing

Usability Testing. Jakub Franc User Researcher Software eXperience Design Group Sun Microsystems. Presentation Outline. What is Usability testing? What is it good for? How to do it?. Introductory Information (1/2). Data collection method Direct identification of usability problems

efuru
Download Presentation

Usability Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Usability Testing • Jakub Franc • User Researcher • Software eXperience Design Group • Sun Microsystems

  2. Presentation Outline What is Usability testing? What is it good for? How to do it?

  3. Introductory Information (1/2) Data collection method Direct identification of usability problems Provides information about real usage of the product Chance to see real user performing tasks in her/his own way

  4. Introductory Information (2/2) Various levels of elaboration Various purposes Evaluating single version of product Comparing two versions of product (even against competitor's products) Significantly reduces development and service cost

  5. What does it look like?

  6. When to test? Whenever! In the beginning of PLC – prototypes Before release (alpha/beta versions) Disaster check After release Input for planning following versions

  7. Advantages and Disadvantages Advantages Provides information about real usage of the product Effective Relatively cheap Disadvantages UI should be testable It does not provide solutions to problems Requires a lot of input from development team

  8. Qualitative vs. Quantitative Approach Qualitative 6 – 8 participants Less time consuming, reveals 90% of problems Common in commercial environment Quantitative 20+ participants Statistical evaluation - metrics Government contracts, universities

  9. How Many Participants?

  10. How to Run Such a Study?

  11. What Do We Need for Testing? Participants Observers Product Optional: lab, recording equipment Thorough preparation Patience

  12. Participants Target audience Screener Recruiter Schedule Incentive

  13. Instructions Explain the purpose of testing Inform participants about recording of the study “Think aloud” We test the product, not the participant Describe test process

  14. Tasks Model real usage of product Based on real motivation (task focused) Expressed in words of user Do not describe in-between steps Incorrect: Go to left menu and find soap in 14 CZK to 16 CZK price range. Correct: Buy lavender soap in this eshop.

  15. Report Delivers findings Helps to incorporate findings into production process Structure Goals Setting (tasks, participants) Results (recommendations) Conclusions Screenshots

  16. Literature Mike Kuniawsky: Observing The User Experience Jacob Nielsen: Usability Engineering

  17. Thank you for your attention • Jakub Franc Jakub.Franc@sun.com

More Related