1 / 15

Usability testing

Usability testing. Frank Ritter & Olivier Georgeon April 22 nd 2009 Revised 27nov17. Why use user-testing?. Demonstrate a weakness or strength of a design feature during the design process; Evaluate the adequacy of an overall design, or of particular design features;

roachj
Télécharger la présentation

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 Frank Ritter & Olivier Georgeon April 22nd 2009 Revised 27nov17

  2. Why use user-testing? • Demonstrate a weakness or strength of a design feature during the design process; • Evaluate the adequacy of an overall design, or of particular design features; • Where guidelines and principles do not always apply; • Where guidelines and principles (and even task analysis) are not always persuasive (true, but sad, really); • Where designers require feedback; and • Because all people (including designers) make mistakes (i.e., user-testing can be used as a type of proof-reading). • You have done | (logs learning vision TA) | of them

  3. Prerequisites for a usability study • Have tasks/ task scenarios • Have example users • Note: not many prerequisites

  4. Formative and summative evaluation • Formative, to help design, to IN form • Places to improve • Project presentations, marks on labs • Summative, to sum up • Is this interface up to standard? • Time to do a task, time to learn a task • Error rates • What is an error? Corrections you can find, blowback (other long term effects) • is harder to do, harder to work to standard • E.g., Project grade

  5. Verbal Protocols • Talk aloud while doing a task • Ericsson and Simon (1983; 1984; 1990) provide a theory of when and why you can and cannot do this • What information is in working memory • NOT NOT “why and how someone thinks that they do a task” • Concurrent or retrospective (if task too fast)

  6. Visual Protocols • Video of users • May be unnatural • Takes time to analyse • Used in retrospective protocols • Getting tools to analyse such things • Dribble files, RUI, as cheap substitutes

  7. Eye Movements • Rarely used • Expensive • Used in Yellow Pages, web studies sometimes, cockpits • Expensive so very high risk or very high payoff

  8. Patterns of use • Put object in work environment: used in WTC robot work • Can find disconnects between requests (we need style sheets) and use (Word users don’t use styles until quite expert); the search and rescue robot does not look usable

  9. Surveys • Can measure attitudes • But have to be quite careful, maybe your item is the least disliked of a disliked category(e.g., LaPiere study) • Always allow unfilled in questions and open questions (else, they can’t quit what they want, and you lose chance for other opinions) • Again, a disconnect between behaviour and belief

  10. Workload • NASA TLX measure, how hard are you working? • Some eye movements being used • Heart rate and other heart measures • Dual tasking, looking for degraded behaviour in a second task

  11. Paper and pencil mockups • Show evaluators mockups of the interface “Story boarding” • Show to real users, other designers • If done with computer or tools, Wizard of Oz • Early, inexpensive, qualitative, broad brush

  12. Prototyping • Making something fast • Looking at it, with any of the previous and later methods • Can blend with WoO • Real systems can also be used

  13. Cooperative evaluation • So-called User-centered design • Work with the users, include them on the design team

  14. Ethics • Treat subjects/participants, fairly, kindly, like you would like to be treated • Anonymous data is the first step • Don’t waste their time • Efficient • useful • IRB approval

  15. Risks The point of all these studies is to explicitly or implicitly reduce system risks

More Related