Your SlideShare is downloading. ×
dmc.umn.edu
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

dmc.umn.edu

1,274
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,274
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Also “Preference” and “Performance” as breakdowns
  • Microsoft Word Photographs
  • We want to give you a simple approach that anyone can use without having a lab or a lot of equipment. Intended to be a stripped down version that people can practice on their own.
  • Fix image so project and evaluator are taken out
  • Transcript

    • 1. Intro to Usability: How to Get Started Lee-Ann Kastman Breuch David Rosen
    • 2. Intro to Usability: How to Get Started Copyright 2007 by the Regents of the University of Minnesota. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission. To disseminate otherwise or to republish requires written permission. David Rosen Usability Consultant Office of Information Technology November 8, 2007 Lee-Ann Kastman Breuch Associate Professor Department of Writing Studies
    • 3. Usability Services
      • Our objective is:
      • To enable project teams to see a user interface design from the user’s perspective
      • To involve users in the design process
      • To give teams the ability to understand the user’s experience and apply it toward improving the product design
    • 4. Background About Usability Services
      • Internal Service Team in the Office of Information Technology
      • Projects for enterprise-level web applications and web sites
      • Projects for web design teams in individual colleges and departments
      • External Sales Projects (primarily for the State of Minnesota and industrial affiliates of our lab partners)
    • 5. Usability in Writing Studies
      • WRIT 4501: Usability and Human Factors in Technical Communication
        • Principles/concepts of human factors/usability testing
        • Developing objectives, criteria, and measures
        • Conducting tests in lab, field, and virtual environments
        • Using software programs to analyze qualitative/quantitative data
        • Offered Spring semester every year
    • 6. Usability Lab
      • Open House in our lab between 3:30 – 5:00 p.m. today
      • Great for having an entire team observe the usability process
    • 7. Session objectives
      • Basics about usability
        • How is it defined and measured?
        • Why is it important?
      • How to see a design from the user’s perspective
        • Who are your users?
        • Activity: Inspecting a design from the user’s point of view
      • How to observe the users’ experience of a design
        • A simple approach to usability testing
        • Activity: Demonstration of a usability test
    • 8. Basics about Usability
      • www.usability.gov
    • 9. What is Usability?
      • Usability Services’ working definition:
      • Ability of users to accomplish their own objectives without outside help
      • Usability.gov:
      • How well users can learn and use a product to achieve their goals, and how satisfied they are with the process
      • Joseph Dumas and Ginny Redish:
      • How quickly and easily people who use a product can accomplish their tasks
    • 10. What Does Usability Measure?
      • It measures the quality of a user’s experience in terms of:
        • Effectiveness and efficiency
        • Ease in learning and remembering
        • Error handling
          • Error-free process
          • Understandable error messages
          • Recoverability
        • Subjective satisfaction
          • Is the look and feel compatible with the purpose?
          • Do users regard the design as pleasant/satisfying?
    • 11. Why Should We Be Interested?
      • Millions of web sites offer similar functions/goods/services, but may be difficult to use
      • Ultimately these sites won’t attract or keep users
      • Usability increases users’ abilities to find information and their satisfaction with web sites
      • Saves $ by reducing help desk calls and fewer re-designs
    • 12. The Importance of a Usable Web Site
      • User Interface Engineering, Inc.:
        • People cannot find the information they seek on web sites 60% of the time
        • People will take 7 seconds before giving up on a site
      • Jakob Nielsen:
        • Studies of user behavior on the Web find a low tolerance for difficult designs or slow sites.
        • Users don’t want to learn how to use a home page
        • People have to be able to grasp the functioning of the site immediately after scanning the home page
    • 13. What is User Centered Design?
    • 14. UCD as a Methodology
      • UCD, also called usability engineering, is a structured approach that involves users throughout the web development life cycle
        • Identifying objectives
        • Defining requirements
        • Developing alternative design prototypes
        • Analyzing user interface issues
        • Development and testing
        • Resolving accessibility issues
        • Implementation
    • 15. The ROI of Usability
      • Find usability problems early when they are easier and less expensive to fix
      • Usability.gov
      • 63% of all software projects overrun their budget or estimate
      • 80% of maintenance cost is due to unmet or unforeseen user requirements
      • Cost of fixing a problem is 10x more in development than in design
      • Cost of fixing a problem is 100x more in production than in design
      • Usable systems save money by reducing development time and the amount of required maintenance
    • 16. Ways to Integrate Usability
      • Focus groups
        • Learn about users ideas/preferences
      • Individual/Contextual Interviews
        • Learn details of specific user’s processes and ideas
      • Personas
        • Identify and describe a typical user and design for them
      • Use Cases
        • - Describe how users will use each feature
    • 17. Ways to Integrate Usability
      • Writing for the Web
        • Optimize content based on the way users read online
      • Terminology Reviews
        • Learn whether planned terminology is understandable/appropriate
      • Card Sorts
        • Learn how users expect content to be categorized
      • Inspection Techniques
        • Heuristic inspections based on guidelines
        • Persona-based inspections
    • 18. Ways to Integrate Usability
      • Usability Testing
        • Paper prototypes (early on)
        • Design mock-ups (electronic)
        • Testing a working prototype (possibly multiple rounds)
        • Benchmark testing (implemented product)
    • 19. Ways to Integrate Usability
      • Accessibility Evaluation
        • Automated compliance checking (first step)
        • Hands-on heuristic review
        • Testing with participants
      • Online Surveys
        • Learn what users think about an implemented product
    • 20. Seeing a Design from the User’s Perspective
    • 21. Recognizing Your Users
      • Who are your users and how will they use the web site?
        • Identify main user groups
        • Describe the key characteristics of each group
          • Age
          • Education
          • Demographics
          • Job title and major responsibilities
          • Goals and tasks with respect to your web site
          • Environment/Context for use
          • Expected attitude toward your web site
    • 22. Using Personas
      • A persona is a fictional person who represents a major user group for your site
      • Personas give design teams a way to look at a web site from a particular user group’s perspective
      • A fictional name and picture may help to make the persona seem more “real”
    • 23. Using Personas: Activity He is a Minnesota resident moving to North Dakota to take a position as a bank manager in Minot. He needs to get a North Dakota Driver’s License. “ I’m going to be really busy with my new job. I hope I don’t have to take my driver’s tests all over again just because I’m moving.”
    • 24. Using Personas: Activity
      • Name:
      • Age:
      • Position:
      • Family:
      • Education:
      • Computer Use:
      • Hobbies:
    • 25. Using Personas: Activity
      • Look at the North Dakota Department of Transportation page on Licensing and Registration
      • Where would the bank manager find information about getting a driver’s license in North Dakota?
      • Identify potential usability issues with this page
      • Share your issues
    • 26. Using Personas: Activity
      • The information is located under the link, “What Every Driver Needs to Know”
      • Then it’s under the link, “Driver’s License Requirements”
    • 27. Inspection vs. Usability Testing
      • Advantages of Inspections
        • Quick
        • Inexpensive
        • Good process to use before usability testing
        • Helps put you in the user’s state of mind
    • 28. Inspection vs. Usability Testing
      • Drawbacks to Inspections
        • Inspections are about users “by proxy”
        • Inspection results are not based on observations of user behavior; usability testing directly observes users
        • Usability.gov:
        • Approximately 20% of usability issues will be missed, and there may be numerous false identifications, up to 50%
    • 29. Suggestions for using Inspections
      • Bring together a small group of stakeholders
      • Identify user categories
      • Bring pictures
      • Create personas
      • Walk through the site from the perspective of each persona
    • 30. Usability Testing: A Simple Task-Based Approach
      • Preparing for a usability test
      • Conducting a usability test
      • Collecting and analyzing results
    • 31. Preparing for a Usability Test
      • Identify usability goals
        • What counts as success?
        • e.g.: That the intended users are able to easily and quickly find the information they are seeking on a web site
      • Identify who the users are
        • Identify major user categories
        • You may choose to develop personas
    • 32. Preparing for a Usability Test
      • Develop participant recruiting criteria
        • Decide how many total participants to test
        • Identify how to represent the target audience in the recruiting categories
        • Identify sources for recruiting lists
      • Recruit participants
        • Make sure that recruiting communications do not give away exactly what will be tested
    • 33. Preparing for a Usability Test
      • Identify typical tasks
        • These should be things for which users would normally use the web site
        • For each task, develop a plausible scenario for completing the task
        • Give motivation, but not specific instructions
        • Avoid matchup of words between web site and scenario text
    • 34. Preparing for a Usability Test
      • Sample Scenario
      • “ You are an undergraduate student at the University of Minnesota. You have lost your University Identification Card. Find out how to replace it and if there is any cost to do so.
    • 35. Preparing for a Usability Test
      • Develop debriefing questions
        • Open-ended questions to get information that won’t be obtained through observation
        • These should be about the overall experience of using the site
    • 36. Conducting a Usability Test
      • Participant Consent
        • Each participant should read and sign a participant consent form
          • Consent to be observed, recorded, and quoted
      • “Think Aloud” protocol during task completion
        • Example of our briefing
    • 37. Conducting a Usability Test
      • Observers take notes on usability issues encountered by the participant
      • In a lab, the team watches from a separate room
        • Team members see problems first-hand
        • No disagreement about the existence of issues
        • Business experts can identify issues that technical staff would miss and vice versa
    • 38. Conducting a Usability Test
      • May want to record audio and/or video
      • Could record the screen as an .avi file
      • Limit total number of observers in the same room as the participant to 3 or fewer
    • 39. Activity: Usability Demo
      • A volunteer from the audience, please
      • A demonstration of how the completion of a scenario would work in a usability session
      • The rest of the audience will act as “observers” and take notes on what they see
    • 40. Activity: Usability Demo
      • Scenario
      • You are moving permanently to Aurora, Illinois (in the Chicago area). You currently hold a valid Minnesota driver’s license. Use the web site to find out where to go and what to bring to obtain an Illinois driver’s license. You want to find out whether you will be required to take a road test.
      • Web site:
      • http:// www.cyberdriveillinois.com /departments/ drivers/ drivers_license/home.html
    • 41. Activity: Usability Demo
      • Debriefing Questions
        • How would you characterize your experience of using the web site?
        • What seemed to be easy about the site?
        • What seemed difficult or confusing?
        • Was there anything that you expected that you didn’t find?
        • What did you think of the appearance of the site?
    • 42. Activity: Usability Demo
      • What usability issues
      • did you see?
    • 43. Conducting a Usability Test
      • Debriefing the participant
        • Your debriefing questions should be open-ended
      • One more technique before they leave
        • Present a Desirability Matrix, and ask the participant to choose the 5 words that most accurately describe the site
        • You can then ask why the participant chose those words
    • 44. Desirability Matrix
    • 45. Collecting and Analyzing Results
      • Debriefing the observers (the team)
        • Document usability issues that the observers saw in the session
        • Usability Results Spreadsheet
        • Do this immediately after the session, so events are remembered more accurately
    • 46.  
    • 47. Collecting and Analyzing Results
      • Presentation of Results
        • Every evaluation should provide something to refer back to later
          • Usability Results Spreadsheet, organized by severity
          • Possibly a usability evaluation report summarizing goals, methodology, and results
          • Attach any recordings
    • 48. Wrap Up: Some Basic Principles
      • The usability process is intended to gain information about the user’s experience , not the project team’s
      • Project teams benefit by observing the user’s process directly
      • Usability testing gives you information about what users actually experience
      • You don’t need a lab to conduct usability tests
    • 49. Usability Lab Open House
      • You’re invited to visit our usability lab in
      • B-26 Walter Library
      • 3:30 – 5:00 p.m. today
    • 50. Questions? Lee-Ann Kastman Breuch: [email_address] David Rosen: [email_address]

    ×