3 Usability Techniques


Published on

  • Be the first to comment

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

No notes for slide
  • Timings for CPL (rough)10 minutes - Intros and so on70 minutes - usability overview plus persona / story walk-through 40 minutes - hallway evaluations10 minutes – break60 minutes - usability testing20 minutes - wrap up - putting this into your work context
  • #1 focuses on the importance of looking at your work from the perspective of a user. The basic technique is a quick user story (persona based on what you know at this point).
  • Make this as a bile
  • #2 is about how to get people to try something out, instead of offering opinions. The basic technique in this segment is writing realistic tasks and observing behavior.How we will do it:screenshots and post-it notesCan have each table rotate to the next table for 5 minutes, etc. to jot down comments on post-it notesWon’t have time to get everyone through all the tables, but should get good idea
  • #3 puts the first two into real usability test, and teaches how to moderate and observe, along with some thoughts about who makes a good usability test participant.
  • What should we use for the demo usability test?We could use the Use Tax notice from the Hallway exercise because they will all have seen it and they'll have a copy.
  • We are testing with a VA brochure -- the before; as with the other documents we have an after to share at the end of the exercise.We should give the moderators and observers the brochure to look at for a few minutes to decide how to do the test and to decide whether to do a paraphrase test or a go through it and ask questions test.
  • Steve runs instant usability tests in his workshops – he asks for volunteers to name a web site, and runs a test with someone in the audience using the site. They always find at least a few problems.
  • This is where Nicole talks about First Friday and Whitney talks about NCI
  • This starts our conclusion.Remember that we've looked at 3 techniques from this toolkit.
  • We've shown review techniques but don't wait for the end of a project to focus on usability and accessibility.Use these review techniques on your CURRENT version at the start of a project.Use all the other techniques, too.
  • And a reminder of who sponsored this workshop today
  • 3 Usability Techniques

    1. 1. Three ways to help users understand your informationA usability workshop for World Usability Day<br />Whitney Quesenbery<br />Ginny RedishKate Walser<br />November 10, 2010<br />
    2. 2. Topics for this workshop<br />Introduction to usability and usability techniques<br />Three techniques for today<br />Persona / story walk-through<br />Hallway review<br />Informal usability test<br />
    3. 3. Introduction to usability and usability techniques<br />Poster from Usability Professionals’ Association showing an overview of a user-centered design approach<br />
    4. 4. Plain language and usabilitygo hand in hand<br />Plain language means that people can<br />Find what they need<br />Understand what they find<br />Use the information to meet their goals<br />Usability means that people can meet their goals<br />Effectively (completely, accurately)<br />Efficiently (in an appropriate amount of time)<br />With satisfaction<br />
    5. 5. Usability is about people<br />All kinds of people<br />doing all kinds of things<br />online and offline<br />Photo credits iStockphoto, russeljsmith, Trace Center<br />
    6. 6. Different types ofpeople…doing differenttasks… have differentusability needs<br />For this person, efficiency and effectiveness are the most important dimensions.<br />For this person, easy to learn and error tolerant are the most important dimensions.<br />
    7. 7. Usability focuses on users’ behavior<br />Understanding users' needs<br />Designing to meet those needs<br />Making sure you have met those needs<br /> − in the time and effort that users are willing to spend<br />Attitudes and satisfaction are important.<br />But most important is what people dowith your document or web site.<br />
    8. 8. Usability is a toolkit of techniques<br />Do a final usability testto compare to benchmark <br />Analyze and measurefor maintenance <br />Prototype (or write drafts) iteratively<br />Create a style guide and templates<br />Inventory your content<br />Develop your content strategy<br />Do card sorting<br />Do persona / story walk-throughs<br />Set measurableusability goals<br />Do hallway reviews<br />Write relevant stories<br />Do rapid, informal iterative usability testing<br />Create personas<br />Conduct benchmark usability tests<br />Watch, listen to, and talk with users as they work(contextual interviews)<br />Use each technique − when you need it and at the right scale.<br />Analyze search logs and server logs <br />Articulate your business goals<br />
    9. 9. Persona / storywalk-through<br />When you have no timeand no access to users<br />Persona of a commuter, created in a workshop at the Society for Technical Communication<br />
    10. 10. What is a persona / story walk-through?<br />A usability technique that <br />takes no special equipment or set up<br />gets your whole team involved in the processAnd can even be a bit of fun!<br />You can do this (and any of our techniques) with<br />a document (paper, web-based)<br />an entire web site or a partial web site<br />a specific web topic or even one web page<br />We'll call this your "content.”<br />
    11. 11. Step 1: Don’t look at it yet<br />Sounds contradictory?You have only one chance to look at somethingfor the first time and to think about it like a new user.If you look at it before you try to use it, you’ll see it differently.If you are reviewing your own material, set it aside for a fewhours before you do the persona / story walk-through.<br />
    12. 12. Step 2. Write down your goals for your content<br />Your site visitors' goals (and their reality)<br />Your organization'sgoals for this specific document or content<br />Success − for youand your users<br />Answer people's questions about your topic<br />Have people complete a transaction correctly without calling<br />Get more people to fill out a form correctly without calling<br />
    13. 13. Step 3: Create a mini-persona<br />Who is using your content?<br />Who is a typical person for this content?<br />What adjectives or phrases describe this person?(busy? anxious? curious? nervous? knows relevant technical vocabulary? or not?done this lots of times or never before?) <br />Give that person a name, an age,a few personal characteristics<br />Think about how well you know this person, and how much they are − or are not − like you.<br />Mariella Garcia<br />
    14. 14. Step 4: Tell that persona's story related to your content<br />Why has that person come to your content?<br />What is your persona's goal? <br />What is your persona trying to do? looking for?<br />What does your persona expect to find? to happen?<br />
    15. 15. Step 5: Walk through your persona's story as the persona<br />"Channel" your persona.<br />Start where your persona would in the story.<br />When / how would your persona get the document?(Open the envelope.)<br />Where would your persona start in the web story?(Know the URL? Go to Google?)<br />Go through the content (document, web site, web topic, web page) as if you were the persona carrying out the persona's story.<br />Take notes of what works well and what does not.<br />
    16. 16. Try it! <br />We'll work on this example:<br />Home page of the Tricare web site.<br />Tricare is the medical insurance company for military personnel, retirees, and their families.<br />It offers several plans with health, dental, pharmaceutical coverage.<br />The site must serve current and new customers.<br />That should be enough for you to set up a persona / story<br />walk-through.<br />
    17. 17. Try it! <br />Work with a neighbor<br />Don't look at it yet.<br />Write down Tricare's goal(s) for the web site.<br />Create a mini-persona of one typical user of the Tricare web site.<br />Write the start of the persona's story. Why is your persona coming to the Tricare site?What does your persona expect to happen? <br />Now be your persona doing the persona's storyand make notes about how well the Tricare home page works or does not work for your persona and your persona's story.<br />
    18. 18. Considering what you learned<br />Positives: Did any part of what you were reviewing work well?<br />Concerns<br />Relationship problems<br />Are the organization's goals and the persona's goals in alignment?<br />How well does the site satisfy either set of goals?<br />Conversation problems<br />Are the headings, text, and images meaningful to your persona?<br />Did your persona understand the words? find where to click? <br />Appearance problems<br />Does it look tidy and attractive?<br />Is space used well?<br />
    19. 19. Making use of what you learned<br />Reporting<br />Include at least one positive comment.(You want to keep what is working well.)<br />Have examples of problems from the persona’s perspective.<br />Think about how critical the problems are.<br />Think about what keeps the persona from being successful.<br />Fixing<br />Yes, fix the easy-to-fix problems.<br />But fixing the one or two most critical problems is much more important.<br />
    20. 20. A bit more about being user-centered<br />What we’ve just done is a persona / story walk-through<br />The user's story – the persona and goal – guides the review.<br />Your knowledge of usability and good design helps you understand the problems the persona encounters.<br />Guidelines or a checklist can help you keep important points in mind.<br />Ginny did a large review with this technique for AARP.<br />
    21. 21. What are the benefits and risks of this technique?<br />Benefits<br />Easy to do.<br />Doesn't need users, space, equipment.<br />Risks<br />You may know less about these users than you think.<br />Methods that rely only on guidelines are known to be rather poor at predicting actual problems.<br />You (or your colleagues and managers) may resist doing usability testing because the review seems good enough.<br />You become over-confident.<br />
    22. 22. Doing a little bit more<br />Get a second opinion. <br />More people means more insights and less chance of getting fixated on a minor issue.<br />Decide whether you want more or less expertisein the persona and the reviewers.<br />Add a wider coverage of people and tasks.<br />Include more personas, especially those that contrast.<br />Include more stories for each persona.<br />Make the report more comprehensive − if that will actually accomplish what you need.<br />More detailed descriptions of problems.<br />Include screenshots to point to specific problems.<br />
    23. 23. Hallway reviews<br />Getting input from morepeople in your organization<br />Post-it notes with comments about a home page (portal) for students who are new to the Open University<br />
    24. 24. What is a hallway review?<br />A usability and design technique to capture feedback from<br />Target users<br />Team members<br />People in the organization<br />Customers<br />Post screenshots or examples of the information in<br />Meeting rooms<br />Hallways<br />Online (using tools like Notable − screen shot and link on a later slide)<br />
    25. 25. Step 1: Decide what to review<br />Which do you want to review?<br />Information – use a printout of the wording<br />Information plus design – use a screenshot or wireframe<br />What do you want hallway reviewers to critique?<br />Clarity – can someone read and understand it easily?<br />Tone – does it set the right tone?<br />Context – is there enough to help with understanding?<br />“Enablers” – do the surrounding elements (design, headings, label, etc.) help reinforce the message?<br />
    26. 26. Step 2: Think of questions AND bounds<br />Help frame the feedback<br /> Post personas and sample scenarios / tasks with questions to gauge ability to complete scenario (e.g., What’s the penalty for paying late? Where did you find the answer?)<br />Post thought-provoking questions (samples on next slide)<br />What will hallway reviewers know that your personas won’t?<br />Think of the game “Taboo”<br />Background information<br />Internal, insider words, phrases<br />
    27. 27. Sample questions<br />Could you answer [question 1]? If so, where did you find the information?<br />How clear is the information?<br />What else would the reader need to know to understand thisinformation?<br />Are there any design elements that promote understanding?<br />What would you suggest rewording?<br />Are there any words your friends, family, or colleagues wouldhave trouble understanding?<br />
    28. 28. Step 3: Find the right place<br />High-traffic areas when you need…<br />Volume<br />Diverse population<br />Lower-traffic areas, but with RIGHT people<br />Subject matter experts<br />Help desk<br />Trainers<br />
    29. 29. Step 4: Gather materials and post<br />Get approval / clearance if needed<br />Sample materials<br />Large easel sticky notes<br />Print-outs of site pages or pamphlets<br />Post-it notes (arrow post-it notes too!)<br />Tape<br />Pens, markers<br />Answer drop-box (if you want to review answers to questions)<br />
    30. 30. Or set up an online area to collect<br />Notable – http://www.notableapp.com<br />flickr – http://www.flickr.com<br />To give people “Add a note” option, go to You > Your Account > Privacy & Permissions<br />
    31. 31. Step 5: Check in and observe<br />See reactions as people encounter the review<br />Check response rate<br />Post new copies of screenshots if response rate is good<br />Adjust the “framing” if needed<br />Provide more clarification on task<br />Follow up on questions, results as appropriate<br />
    32. 32. Try it! <br />We'll work on this example:<br />Information that the Washington State Department of Revenuewrote for every business owner in the state.<br />Organization's goals: <br />If business owner owes this tax, pay it.<br />If business owner does not owe this tax, go on record to say that.<br />Persona:<br />Owner of a small business with 10 or fewer employees.<br />Is very busy; needs to spend most of time focused on the business.<br />Doesn't want to get in trouble with Revenue, but doesn't know tax law or tax language.<br />Gets a lot of mail from a lot of sources.<br />
    33. 33. Considering what you learned<br />Positives: Did your reviewers make any positive comments?<br />Concerns: What did you learn from reviewers' comments about -<br />Relationship problems<br />Are the organization's goals and the persona's goals in alignment?<br />How well does the site satisfy either set of goals?<br />Conversation problems<br />Are the headings, text, and images meaningful to your persona?<br />Did your persona understand the words? find where to click? <br />Appearance problems<br />Does it look tidy and attractive?<br />Is space used well?<br />
    34. 34. What are the benefits and risks of this technique?<br />Benefits<br />Quick and easy<br />Cheap<br />Fewer time constraints than scheduled sessions<br />Can reach more reviewers and cover more ground<br />Risks<br />More often, gather feedback from insiders – less often, target users<br />Similar challenges to focus groups – one reviewer’s commentsmay influence another <br />Little chance to learn more about the comments<br />
    35. 35. Can we lessen the risks?<br />Separate the markings from the commentsAsk reviewers to<br />Initial / mark the area they want to critique<br />Jot down the comments / ideas and drop in a box andreference the mark (e.g., KW1)<br />Spread out the hallway reviews<br />Requires more effort aggregating feedback<br />Distributes the number of comments that could bias otherreviewers across multiple copies<br />Use copies of the same screenshots and give each its own“focus” (e.g., clarity, tone, etc.)<br />
    36. 36. Usability testing<br />Informal testing with people who use your information<br />Informal usability testing of voting materials at the Farmer's Market in Olympia, Washington<br />
    37. 37. What is a usability test?<br />Observe real people using something in a realisticor semi-realistic environment<br />Not just asking them about it<br />See how easily real people find what they need to accomplish a task <br />Confirm or challenge assumptions<br />Improve materials<br />Don’t argue about design or language. Test with real users.<br />Learn where and how to prevent mistakes or help peoplerecover from mistakes.<br />Find where the information is not "plain" enough for peopleto revise it.<br />
    38. 38. How easily can we learn from users?<br />Gathering feedback from people can be as simple aswatching someone use something to find information.<br />Let them explore the material as they would really do. <br />Don’t explain or demo.<br />Watch what they do.<br />Note where they do and do not read.<br />Listen to their comments.<br />Take their problems seriously.<br />
    39. 39. How easily can we learn from users?<br />Usability testingdoes not have to be formallengthy, or expensive. <br />You don’t need<br />a formal laboratory<br />100s of participants<br />special equipment<br />special recording systems<br />Poster from Washington State<br />
    40. 40. Why not do this in a group?<br />In focus groups, you get <br />preferences<br />opinions<br />group consensus<br />In a usability test, you get<br />individual behavior and performance<br />what happened, as well as why<br />
    41. 41. What do you need for a usability test?<br />What<br />The material you want to test<br />Where <br />A quiet room (Maybe. We know of very successful usability testing in an open marketplace, a hangar at an air show, the chemotherapy center at the NIHClinical Center.)<br />Who<br />Moderator <br />Observer/note-taker<br />Users: 3 − 6 people, one at a time<br />
    42. 42. The moderator runs the session<br />Impartial, unbiased, observing<br />No teaching!<br />Listen and watch<br />Open-ended questions: Why?How? What were you doing? <br />Moderator roles: <br />Flight attendant: Ensuring safety and comfort<br />Scientist: Planning, maintaining objectivity, managing data<br />
    43. 43. Briefing the user<br />Thanks for trying out this […]. Your doing this will help improve this material. <br />Note: If you never use the words "test" or "evaluate" with the user,you will not have to say "We are not testing you."<br />You can stop anytime.<br />Your involvement will be confidential.<br />If you get stuck or confused, say so.<br />Please let me know what you are thinking as you use this …<br />
    44. 44. Techniques to maximize information<br />If the user says, “hmmm” or “oops” or “I wonder…”<br />Say, “What questions do you have right now?”<br />If you are doing "think aloud" and the user is silent for 10 or 20 seconds (count!) <br />Say, “What are you thinking?” <br />If users stop because they think they're done or they are stuck (and you think there’s a problem) <br />Summarize what you saw the user do.<br />Ask "What would you do now?"<br />
    45. 45. Think aloud during − or after the task<br />Consider asking people to “think aloud” as they work<br />What they’re doing<br />Why they’re doing it<br />If it's a usability test that you can't do with think aloud,go back over the material<br />Ask the participant to walk you through what they did and why.<br />Use the material as a guide for the discussion.<br />Ask if anything was confusing or frustrating.<br />
    46. 46. Different ways of having people try outdifferent materials<br />Web site where you are observing people both find andunderstand information<br /> Ask participants for their own scenarios. (Have you used this site? What for? Please show me how you did that with this site. or Would you be likely to use this site? What for? Please show me how you would do that with this site.)<br /> Give participants scenarios you have written. (Write scenarios that will have people use parts of the site you are worried about.)<br /> Use both of these with their own scenario first.<br />
    47. 47. Different ways of having people try outdifferent materials<br />Single document (letter, notice, one web page)<br />Paraphrase: Have participants <br /> read a section themselves (depending on the document that could be a sentence, a paragraph, a heading and the text under the heading)<br /> tell you in their own words what it means (note what they get right, what they get wrong, and what they leave out)<br />Read, comment, and answer questions:<br /> Have participants go through the document as they would if you were not there, while commenting to you with their reactions as they go through the document.<br /> Then ask them questions about facts from the document. (You can write the questions like scenarios.)<br />
    48. 48. Observers and note-takers<br />Watch quietly.<br />Do not distract the person participating in the usability test. <br />Do not react to anything that happens during the test.<br />No laughing, gasps, shaking your head, whispering.<br />Do not ask questions or try to discuss the test with the participant.<br />
    49. 49. Observers and note-takers<br />Take good notes.<br /> Write down what you see and hear.<br /> Be specific. Not "he's confused." But "he said he doesn't know what APR means."<br /> Don't translate. Put down the user's words.<br /> Don't infer the user's reasons for doing something. (The moderator may ask as it is happening. If not, at the end, you may be able to ask the moderator to take the user back to the event and ask what was happening then.)<br /> Don't solve problems while taking notes. That's for later. It will take all your concentration to note what is happening.<br />
    50. 50. Observers and note-takers<br />Watch (and listen) for whether the user<br />has any trouble understanding or following instructions?<br />asks questions or appears confused?<br />has to correct mistakes or re-read information?<br />has any comments?<br />
    51. 51. Watch and listen to a demostration<br />We'll demonstrate a short usability test.<br />You are all observers / note-takers.<br />
    52. 52. Try it<br />Break into small groups (3-4 people)<br />Choose 1 person to be the participant<br />Choose 1 person to be the moderator<br />Others observe and take notes<br />Participants all come up to the front to get a briefing while the moderators and observers become familiar with the document we are going to have you try out.<br />
    53. 53. Considering what you learned<br />Positives: Did any part of what you were testing work well?<br />Concerns<br />Relationship problems<br />Are the organization's goals and the persona's goals in alignment?<br />How well does the site satisfy either set of goals?<br />Conversation problems<br />Are the headings, text, and images meaningful to your persona?<br />Did your persona understand the words? find where to click? <br />Appearance problems<br />Does it look tidy and attractive?<br />Is space used well?<br />
    54. 54. Base your findings on what the users did and said<br />Did they read or use the information accurately?<br />Were there any <br />signs of hesitation or confusion?<br />misreadings or misunderstandings?<br />requests for assistance?<br />adaptive behavior?(taking out reading glasses, moving closer to the document, holding the paper up to the light − could all be signs of problems with the information design)<br />surprises?<br />other expressions of emotion (anger, disgust, delight, satisfaction)− what specific aspects of the materials were those about?<br />
    55. 55. Report on what you observed in the test<br />How you report depends very much on your situationand the usability maturity of the organization.<br />Reports can range from<br />a brief memo of what was agreed on in a debriefing meeting (Everyone involved observed sessions, attended the meeting, and will fix the problems.)<br />a short report with very brief identifying information, and then bulleted lists or tables of findings and recommendations(Usability testing is well understood and people just need the results to act on.)<br />a detailed report with an explanation of usability testing, details of what you did, quantitative and qualitative results, video clips and screen shots, recommendations<br />
    56. 56. Can we really find problems runningusability tests with so few people?<br />Yes!<br />This is not “science” but a way to find problems…and fix them before the material is released.<br />Experience tells us that usability testing uncovers problems more clearly than any other method.<br />Seeing the problem is the first step to solving it.<br />
    57. 57. Rocket Surgery technique<br />Steve Krug's "do it yourself" method<br />test on a regular schedule, a morning a month<br />test to get answers to a limited number of issues<br />3 participants (one hour each)<br />observers note 3 insights from each of the 3 sessions<br />debrief and decide immediately after the sessions<br />to participate in decisions based on the test,you must observe at least on session<br />no report! just a brief memo of what the team will change inthe next month<br />tweak to fix; just do what is needed to eliminate the problems<br />
    58. 58. Usability is a toolkit of techniques<br />Do a final usability testto compare to benchmark <br />Analyze and measurefor maintenance <br />Prototype (or write drafts) iteratively<br />Create a style guide and templates<br />Inventory your content<br />Develop your content strategy<br />Do card sorting<br />Do persona / story walk-throughs<br />Set measurableusability goals<br />Do hallway reviews<br />Write relevant stories<br />Do rapid, informal iterative usability testing<br />Create personas<br />Conduct benchmark usability tests<br />Watch, listen to, and talk with users as they work(contextual interviews)<br />Use each technique − when you need it and at the right scale.<br />Analyze search logs and server logs <br />Articulate your business goals<br />
    59. 59. Usability andaccessibility must be designed in<br />They can’t be piled on top after the rest of the design is done!<br />
    60. 60. Plain language matters. <br />The Center advocates for clear communication and plain language everywhere − in government, business, non-profits, and universities.<br />
    61. 61. We support those who use plain language, train those who should use plain language, and urge people to demand plain language in all the documents they receive, read, and use.<br />
    62. 62. The Center’s projects include:<br /><ul><li>ClearMark awards, celebrating the best in clear communication and plain language
    63. 63. WonderMark awards, telling the world what’s not plain.
    64. 64. Demand to Understand, encouraging everyone to demand clear communications before they sign an agreement.
    65. 65. Educational programs about plain language− like this one.</li></li></ul><li>Plain Language and usability resources<br />What is plain language?http://centerforplainlanguage.org/about-plain-language/<br />How-to for plain language: guidelines and tools http://www.plainlanguage.gov/howto/index.cfm<br />How-to for usability: basics, templates, and guidelines http://www.usability.gov<br />Toolkit for starting plain language in your organizationhttp://centerforplainlanguage.org/toolkit/<br />Usability training at Web Manager Universityhttp://www.usa.gov/webcontent/wmu/<br />Usability Professionals’ Associationhttp://www.usabilityprofessionals.org<br />
    66. 66. Books on usability and plain language<br />Handbook of Usability Testing (2nd Edition) by Jeffrey Rubin and Dana Chisnell<br />Letting Go of the Words by Ginny Redish<br />Rocket Surgery Made Easy (The Do-It-Yourself Guide to Finding and Fixing Usability Problems)by Steve Krug<br />Storytelling for User Experience by Whitney Quesenbery and Kevin Brooks<br />
    67. 67. Janice (Ginny) RedishRedish & Associateswww.redish.net<br />ginny@redish.net<br />Whitney QuesenberyWQusabilitywww.wqusability.comwhitneyq@wqusability.com<br />Kate WalserCX Insightswww.cxinsights.comkate@cxinsights.com<br />