1. Damian Gordon

2.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five step process

3.  The paper used in this presentation describes a practical methodology to perform usability testing  Specifically, how usability testing can be applied to improve a user’s experience with navigating, finding information, and interacting with a Web site

4. Know your goal:  To identify the problem areas of your software [Web site] by testing to solve those problems, (and always keep your tests and analysis simple!)

5.  Usability Is a measure of how easy it is to use something: ◦ How easy will the use of the software be for a typical user to understand, learn, and operate ◦ e.g., “user-friendliness”

6.  “...the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.”

7.  Usability testing is an effort to ascertain the degree to which software has met the usability needs of its intended user base  Usability is difficult to evaluate and measure

8.  Usability Testing is an attempt to quantify software user-friendliness according to: 1. Skill needed to learn the software 2. Time required to become efficient in using the software 3. The measured increase in user productivity 4. A subjective assessment of a user’s attitude toward using the software

9.  The idea is to place users in front of some version of the software under test and watch how these users try to use it  Can be expensive depending on what tasks you have users try and on what you are watching for  Not cost-effective if done too late in dev cycle  Can uncover usability problems that design guidelines and inspections may have missed

10.  Formal testing might entail building a usability testing lab, equipping it with an array of computers, audio-video equipment, then staffing it with psychologists, technicians, and human-computer interaction specialists

11.  Informal approach: No fancy lab or expensive equipment  A simple test plan and task list are prepared, notepad and pencil  Participants are observed by an impartial moderator  The advantage is that informal testing looks at what people actually do when they are doing real work in an ordinary setting

13. Develop a test plan: ◦ For simple testing, prepare a list of questions ◦ For more detailed testing, have a script prepared  Test Plan is important because you can create a framework for your testing process  It allows you to communicate your goals with the client & align expectations

14. Create a Task List:  Create lists of tasks or questions that a typical user should be able to complete in an hour  Tasks should not be too simple nor too difficult to accomplish  e.g., 1. Find a concert show you want to see 2. Purchase tickets on line 3. Find directions to the venue

15.  Informal usability tests only require a pencil, paper, computer and browser  Sometimes might use a video camera and record each session  Sometimes watched by development team  Often usability tests can be conducted within the user’s own environment  Keep a printed version of the site for note taking, and then watch and learn...

16.  A challenging aspect in usability testing is finding suitable participants  Important to gather on ongoing user base  Test outside the team—testing with people who are not associated with your company or your Web site

17. Prior to conducting sessions with participants:  Test out your test plan beforehand with co- workers or friends that have an acceptable degree of Web user experience  The first usability test should be fun, informative, and low-stress

18.  Introduce yourself, explain the process to the user  User will be asked to perform a set of pre- defined tasks (but do not tell them how many or how long each will take)  Make the user feel comfortable  Speak only to give a new task and take notes during the process

19.  Once the usability test session is over, prepare a short summary of the session and the results  Outline specific problem areas and any unexpected results  Include any personal observations

20.  Collect basic data: ◦ Could the user complete the task? ◦ Did they need help? ◦ Track how much time it took them ◦ Note any stumbling blocks (problems/obstacles) ◦ Overall observations, commentary ◦ Debrief the user, allow user to speak their mind ◦ Prepare a post-test survey

21. Post-Test Survey:  Prepare a survey online or in paper form for the user to fill out after they have completed the testing process  Questions should include what the user thought the Web site was like: graphics, logic, content, navigation, and their overall satisfaction  Gather data about overall effectiveness of the site in relation to the goals of each task

22.  Compile and summarize data  Transfer handwritten notes to computer  Write your reports while they are fresh in your mind,  Create a summary after testing is complete, into a table that shows the results of each test, include problem areas, comments and user feedback from the survey

23.  Identify difficulties and problem areas  Identify why there was difficulty or the source of any problems (specific factors such as navigation, text, graphics, etc.)  Identify any specific task-oriented issues

24.  Compile and recommend ◦ Gather all your compiled information and translate into recommendations ◦ Concentrate on high-level functionality first ◦ Then focus on recommendations for improved user experience (what works and what does not work well for users!) ◦ Determine the implementation plan  Write up a formal report