Steve Krug's Usability Script. Hi, . My name is Steve Krug, and I'm going to be walking you through this session. You can't do anything wrong here. The 1-page usability test plan. The Usability Test Plan is a critical document to help you manage and organise a usability test. But it can sometimes appear too documentation-heavy in agile environments. In fact, this is probably the one place today where you don't have to worry about making mistakes. I may not be able to answer them right away, since we're interested in how people do when they don't have someone sitting next to them, but I will try to answer any questions you still have when we're done. With your permission, we're going to videotape the computer screen and what you have to say.
The video will be used only to help us figure out how to improve the site, and it won't be seen by anyone except the people working on the project. It also helps me, because I don't have to take as many notes. There are also some people watching the video in another room. It simply says that we have your permission to tape you, but that it will only be seen by the people working on the project. It also says that you won't talk to anybody about what we're showing you today, since it hasn't been made public yet. Task Scenarios for Usability Testing. Topics. All Article Topics. All Topics. (hide). Author. All Authors. Recent Articles. Popular Articles. Turn User Goals into Task Scenarios for Usability Testing. January 1. 2, 2. 01. Summary: Guidelines for usability test tasks: engage participants by writing task scenarios that are realistic, encourage an action, and don. This is the essence of usability testing. Usability Test Plan Template Use this template when creating your test plan. The Method section is where you present the “script” for your usability test. This section will be divided into two parts: A) Overview of the. Usability Test: Usability Testing Script (DOC, 81 KB, 6 pages. May 2014) System Usability Scale / Post-Test Questions (DOC, 500k, 1 page, Dec. 2014) Usability Test Plan Template (from usability.gov) Usability. When the right participants attempt realistic activities, you gain qualitative insights into what is causing users to have trouble. This helps you determine how to improve the design. Additionally, you can measure the percentage of tasks that users complete correctly as a way to communicate a site. These assignments are frequently referred to as tasks. Ask yourself: What are the most important things that every user must be able to accomplish on the site? For example, nngroup. Find articles on a specific topic. Sign up for Usability Week seminars. Learn about our consulting services. Engage Users with Task Scenarios. Once you. A task scenario is the action that you ask the participant to take on the tested interface. For example, a task scenario could be: You're planning a vacation to New York City, March 3 . Go to the American Airlines site and jet. Blue Airlines site and see who has the best deals. Task scenarios need to provide context so users engage with the interface and pretend to perform business or personal tasks as if they were at home or in the office. Poorly written task often focus too much on forcing users to interact with a specific feature, rather than seeing if and how the user chooses to use the interface. A scenario puts the task into context, and, thus, hopefully motivates the participant. The following 3 task- writing tips will improve the outcome of your usability studies.(1) Make the Task Realistic. User goal: Browse product offerings and purchase an item. Poor task: Purchase a pair of orange Nike running shoes. Better task: Buy a pair of shoes for under $4. Asking a participant to do something that he wouldn. Poorly written tasks make it harder for participants to suspend disbelief about actually owning the task. In the example the participant should have the freedom to compare products based on his own criteria. Coming up with realistic tasks will depend on the participants that you recruit and on the features that you test. For example, if you test a hotel website, you need to make sure that the participants would be the ones in their family responsible for travel research and reservations. Alternatively, you can decide to let the participants define their own tasks. For example, you could recruit users who are in the process of buying a car and let them continue their research during the session, instead of giving them a task scenario. Go to www. fandango. And unfortunately, people. Additionally, having them talk through what they would do doesn. Go to the website, sign in, and tell me where you would click to get your transcript. Better task: Look up the results of your midterm exams. Step descriptions often contain hidden clues as to how to use the interface. For example, if you tell someone to click on Benefits in the main menu, you won. These tasks bias users. In that case, you may want to use the established term. Avoiding clues does not mean being vague. For example, compare the following 2 tasks: Poor task: Make an appointment with your dentist. Better task: Make an appointment for next Tuesday at 1. Dr. Petersen. You might think that this second task violates the guideline for tasks to be realistic if the user's dentist isn't really Dr. However, this is one of those cases where users are very good at suspending disbelief and proceeding to make the appointment just as they would with a differently- named dentist. You might need to have the user pretend to be seeing Dr. Petersen if you're testing a paper prototype or other early prototype design that only includes a few dentists. If the task scenario is too vague, the participant will likely ask you for the more information or will want to confirm that she is on the right path. Provide the participant with all the information that she needs to complete a task, without telling her where to click. Summary. During a usability test, mimic the real world as much as possible. Recruit representative users and ensure that each task scenario: 1) is realistic and typical for how people actually use the system, when they are on their own time, doing their own activities; 2) encourages users to interact with the interface; and 3) doesn.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |