©Rose Norman, University of Alabama in Huntsville


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

©Rose Norman, University of Alabama in Huntsville

  1. 1. Audience Analysis as “Usability Testing” <ul><li>Key Terms </li></ul><ul><li>Usability Testing: Functions, Criteria, Methods </li></ul><ul><li>Theories and Methods </li></ul><ul><li>New Approaches (Mirel in Dubinsky) </li></ul>
  2. 2. New Terms <ul><li>Usability </li></ul><ul><li>Usability Specialist </li></ul><ul><li>Usability Testing </li></ul><ul><li>All come from the computer industry, where designing for ease of use has been a priority since the 1980s, when Apple showed the industry it could be done. </li></ul>
  3. 3. New Terms: Usability <ul><li>Usability – “ any system designed for people to use should be easy to learn (and remember), useful, . . . Contain functions people really need in their work, and be easy and pleasant to use.” </li></ul><ul><li>(J.R. Gould and C. Lewis, “Design for Usability,” 1985; qtd. by Mirel 221, my emphasis). </li></ul><ul><li>Key features: “ease of use, ease of learning, pleasantness, usefulness . . . ; all combined, they provide users with a positive work experience ” (Mirel 221, my emphasis) </li></ul>
  4. 4. New Terms: Usability Specialist <ul><li>People who conduct user research and task analysis for software design, especially user interface design. (Mirel 233) </li></ul><ul><li>From a Ticketmaster Job Ad: </li></ul><ul><li>The Web Usability Specialist works closely with the Product Management team to facilitate and moderate usability tests to find ways to increase user frequency of use and retention for ticketmaster.com and its client applications. </li></ul><ul><li>Degree in Human Factors, Marketing Research or Marketing </li></ul>
  5. 5. New Terms: Usability Specialist <ul><li>From a Macromedia Job Ad: </li></ul><ul><li>The Web Usability Specialist works closely with the Product Management team to facilitate and moderate usability tests to find ways to increase user frequency of use and retention for ticketmaster.com and its client applications . </li></ul><ul><li>Degree in Human Factors or related field. </li></ul>
  6. 6. Job Titles of “Usability Professionals” <ul><li>Usability Specialist </li></ul><ul><li>Usability Engineer </li></ul><ul><li>User Experience Designer </li></ul><ul><li>Information Architect </li></ul><ul><li>Interface or Interaction Designer </li></ul><ul><li>Human Factors Specialist </li></ul><ul><li>From Usability Professionals Association (UPA) Website http://www.upassoc.org/usability_resources/about_usability/about_usability_professionals.html </li></ul>
  7. 7. Job Titles of Closely Related Fields <ul><li>Web Designer </li></ul><ul><li>Technical Writer </li></ul><ul><li>Business or Requirements Analyst </li></ul><ul><li>Technical or Software Analyst </li></ul><ul><li>Market Researcher </li></ul><ul><li>Instructional Designer </li></ul><ul><li>Industrial Designer </li></ul><ul><li>From Usability Professionals Association (UPA) Website http://www.upassoc.org/usability_resources/about_usability/about_usability_professionals.html </li></ul>
  8. 8. New Terms: Usability Testing <ul><li>A term from the computer industry describing a stage in the process of developing software applications. The goal is to make them “user-friendly.” </li></ul><ul><li>Usability Specialist Ginny Redish defines it this way: observing representative users “ . . . in a controlled setting with researchers as observers” ( Redish and Schell 67 ) </li></ul><ul><li>Technical communicators have come to apply it to using the same methods to test the documentation that goes with software (or other products). Any form of instructions can profit from usability testing. </li></ul>
  9. 9. Usability Testing: Functions <ul><li>Verify – is the manual accurate? </li></ul><ul><li>Validate – can people use it as intended? </li></ul><ul><li>Diagnose – provide a feedback loop </li></ul><ul><li>Imitates computer software “V&V”: </li></ul><ul><li>verification: read for technical accuracy </li></ul><ul><li>validation: watch it in use or simulation </li></ul>
  10. 10. Usability Testing: Criteria <ul><li>To be valid, a usability test must meet these two criteria (Redish and Schell 67): </li></ul><ul><li>“ test subjects must be people who might actually use the product” </li></ul><ul><li>“ the work in the test must be similar to the work that users would actually do with the product” </li></ul>
  11. 11. Usability Testing: Methods <ul><li>User-Edits (subject-oriented) </li></ul><ul><ul><li>Read aloud and do </li></ul></ul><ul><ul><li>Good for short instructions or parts of a manual </li></ul></ul><ul><li>Protocol-Aided Edits (task-oriented) </li></ul><ul><ul><li>Give user a task and a manual & watch them do it </li></ul></ul><ul><ul><li>Provides insight into user “heuristics” (how users discover answers) </li></ul></ul><ul><li>Beta Testing (software testing term) </li></ul><ul><ul><li>Send to typical user and wait for complaints </li></ul></ul><ul><ul><li>Not methodical or monitored; can’t tell what hasn’t been tested. </li></ul></ul>
  12. 12. Usability Testing: Methods <ul><li>Lab Testing (AIR style) </li></ul><ul><ul><li>Attempts to answer the shortcoming of the other three methods </li></ul></ul><ul><ul><li>Claimed to </li></ul></ul><ul><ul><ul><li>be more informative than user edits </li></ul></ul></ul><ul><ul><ul><li>gather more data than protocol-aided revision </li></ul></ul></ul><ul><ul><ul><li>be more methodical than beta testing </li></ul></ul></ul>
  13. 13. Theories vs. Methods <ul><li>Methods: Applicable Theories </li></ul><ul><li>User edits Reading levels ? Mutual knowledge? </li></ul><ul><li>Protocol analysis Cognitive psychology </li></ul><ul><li>Beta testing Perhaps computer scientists have some? </li></ul><ul><li>AIR lab testing Triangulating research </li></ul><ul><li>Memory testing Cognitive psychology </li></ul>
  14. 14. Summary, Redish & Schell <ul><li>Usability testing draws on theory about t ask-oriented documents vs. content-oriented documents </li></ul><ul><li>Redish and Schell’s methods of usability testing are all text-based . None of their methods would work without a text. </li></ul><ul><li>Subsequent research shows that a document can be task-oriented and still not address the user’s tasks. </li></ul>
  15. 15. <ul><li>Ease of use and usefulness may not be the same thing. </li></ul><ul><li>Context is key to usefulness—as context varies, what was easy to use may be hard </li></ul>
  16. 16. New Approaches (Mirel) <ul><li>Mirel focuses on usability for software for performing complex tasks. </li></ul><ul><li>She uses a case study about bar code medication software to demonstrate the importance of designing for “work-in-context.” It is easy to use as long as everything goes perfectly. Then it becomes frustrating, making the nurse’s job harder instead of easier. </li></ul>
  17. 17. New Approaches (cont.) <ul><li>Mirel proposes a different approach to usability that focuses on usefulness as defined by how well a product works in the context for which it was intended. </li></ul><ul><li>Her approach requires a conceptual change in the design process from procedural frameworks to structural frameworks </li></ul>
  18. 18. New Approaches (cont.) <ul><li>Procedural frameworks - task-oriented; step-by-step; suitable for “linear, rule-driven, or formulaic tasks” (Mirel 234). This approach dominates software development </li></ul><ul><li>She describes this approach as a “decomposition method” that breaks everything down into isolated tasks, with the idea that the sum of them adds up to a whole. </li></ul><ul><li>This approach misrepresents what goes on in complex tasks. Complex tasks require human interaction and decision-making, so the software needs to be flexible enough to “lean on” users. </li></ul>
  19. 19. New Approaches (cont.) <ul><li>Mirel argues for a new model: </li></ul><ul><li>Structural frameworks - organize performance based on “pragmatic patterns of work in context . . . describing functional relationships and regularities of behaviors” (229) to assist users in problem-solving. Her analogy is genres. </li></ul><ul><li>Context is key to her new model, which is spatial, rather than linear. </li></ul>
  20. 20. New Approaches (cont.) <ul><li>Mirel’s argument for designing for context resembles Johnson’s “Audience Involved.” </li></ul><ul><li>For complex tasks, users need to be able to interact with and dynamically influence the software. But software developers don’t like relinquishing control. Their model is procedural (steps always lead to the same end), rather than structural, which may lead to a “multiplicity of interpretation” (323) </li></ul>
  21. 21. New Approaches (cont.) <ul><li>Mirel argues that all conventional methods of software development place usability testing after companies make fundamental decisions about market and feasibility, and often after deciding on scope and architecture. </li></ul><ul><li>What customer input they get is from market researchers, business strategists, and account managers (cf. Johnson’s story of the engineers and marketing people who wrote the documentation for the voicemail system) </li></ul>
  22. 22. New Approaches (cont.) <ul><li>All software companies “freeze” the product at some stage. </li></ul><ul><li>Usability specialists rarely have a say in when to freeze or what features to freeze. </li></ul><ul><li>The interface freeze often comes “before usefulness is assured or fully designed for” (233). They wind up testing only for “ease of use.” </li></ul>
  23. 23. Summary <ul><li>Usability may refer to “ease of use” or “usefulness” or “ease in learning” </li></ul><ul><li>The term originated with software and has been extended to software documentation </li></ul><ul><li>Usability specialists use a variety of methods to test software products for one or more of these features </li></ul><ul><li>“ Ease of use” does not ensure “ usefulness .” </li></ul><ul><li>Changing to a structural model for software development, emphasizing tasks holistically (work-in-context), rather than as isolated tasks would be more suitable for complex tasks. </li></ul>
  24. 24. Works Cited <ul><li>Mirel, Barbara. “Advancing a Vision of Usability.” Reshaping Technical Communication . Mahwah, NJ: Lawrence Erlbaum, 2002. Rpt. Dubinsky 218-39. </li></ul><ul><li>Redish, Janice C., and David A. Schell. “Writing and Testing Instructions for Usability.” Technical Writing: Theory and Practice. Ed. Bertie E. Fearing and W. Keats Sparrow. New York: Modern Language Association, 1989. 63-71. </li></ul><ul><li>Spilka, Rachel. “Orality and Literacy in the Workplace: Process- and Text-Based Strategies for Multiple-Audience Adaptation.” Journal of Business and Technical Communication. 4 (1990): 44-67. Rpt. In Peeples, 71-83. </li></ul>