How to conduct a usability test?

When?

usability  testing is conducted during the design and development phase of a project, after the initial prototypes have been developed. 

Getting Started

Usability testing aka UT is making the actual people try the designs to check if they are able to use it or not. Basically, it’s a process of evaluating how easy it is for users to interact with a product, website, or software application.

UTs are important milestones in the iterative design process.  Design is iterated till UT results show acceptable quality. This method brings in user’s feedback into the product design process and makes the design ‘user centric’ in true sense.

How to?

1. Define the objectives: Identify the purpose of the usability testing, and what aspects of the product you want to test.

2. Select the participants: Choose a representative group of users who are likely to use the product. They should match your target audience in terms of demographics, knowledge, and experience.

3. Create prototype: Create a suitable prototype to be shared with the participants for user testing.

4. Prepare test scenarios: Develop scenarios that simulate real-world situations and tasks that the users are likely to perform with your product.

5. Create a testing environment: Set up a testing room that is quiet and free of distractions. Provide the necessary equipment such as a computer, a webcam, and a microphone.

6. Conduct the test: Have the users perform the test scenarios while you observe and take notes. Encourage them to think aloud as they interact with the product.

7. Analyze the results: Collect data on the users' behavior, comments, and feedback. Analyze the data and identify the areas of the product that need improvement.

8. Report the findings: Prepare a report summarizing the usability issues that were identified during testing. Prioritize the issues based on their impact and severity and make recommendations for improvement.

9. Iterate and improve: Use the feedback to improve the product and continue to iterate until you have addressed all the usability issues.

Required Participants

Participants play different roles in UTs

1. User: Person who tests the design

2. Moderator: Person who prepares, sets up, and ensures that the test goes as planned. This usually is the researcher or designer.

3. Observer(s): People who watch the test in progress. They can also act as note-takers. The designer, product manager, and other stakeholders in the project 

Types of prototypes used

Prototypes used for testing depend on the type of project, for example

• For designing from scratch, testing could be done with low-fidelity, mid-fidelity and high fidelity prototypes

• For adding new flows/ features to an existing product, mid-fidelity prototypes are useful

• For refinement or redesign, high fidelity prototypes make more sense

Types of Usability tests 

1. Guerilla Test: This is a popular, relatively fast, and informal way to test ideas. 

1. This type of test is used for validating concepts. Paper prototypes or basic wireframes are used for this method.

2. This could be done as roughly as chatting with a user with paper prototypes.

2. Lab Test: UTs conducted in a lab setup where users do the tasks and observers watch them. 

1. This is best used for testing enterprise or business applications where users are trained to use the products.

2. This is a very systematic format that includes recording the tests.

3. Report is generated later after a number of tests are conducted. 

3. On-site Test: UTs conducted in the user's natural environment:

1. This can be testing any consumer facing products, mobile apps, etc. where it is important to observe people using the product in their native environment.

2. This test needs to be planned and arranged in advance.

3. Multiple testing sessions can be conducted at different locations for a single round of testing.

4. Findings are compiled after all onsite tests are completed.

4. Remote Test: This test is conducted when the user and moderator are not at the same place. 

1. This is used when it is not possible to visit the users in person to conduct the tests. This is a cost effective method though it has its limitations. 

2. Users need to be tech enabled in order to participate in the test remotely. 

3. People tend to be conscious and present their best self since someone is observing them on video. They might not be going through the product naturally as they would.

4. Multiple observers can remotely watch the test and reconcile overall findings.

5. Unmoderated Test: This test is run by an application without the need for any moderation. Designer gets the usage report from the application.

1. This is best used when quantitative data is required and a clickthrough prototype is in place.

2. Managing and arranging this type of test is simple.

3. This could be done with a tool like TryMyUI or UserLytics 

4. Report generation is automatic.

Do’s & Don'ts

 

Do’s

Don’ts

Be clear on what needs to be tested. Plan in advance. Get the right participants Have a few extra participants if some drop off at the last minute. Do a dry run before actual tests. Give clear instructions before the test. Make users feel comfortable before starting the test. Plan some incentives for participants. Plan the test such that it gets completed in set time. Complete the synthesis soon after completing the tests.

Don’t plan too much in a single test. Don’t keep software or any other setup for the last minute. Don’t prompt or over instruct the users. Don’t overwhelm the users. Don’t use the exact same words from UI to describe the tasks. Don’t interrupt users during the test. Don’t forget to make notes. Don’t forget to record the session.

 

 

Templates 

• Usability Testing Kit from UXPin (https://www.notion.so/Usability-testing-script-53ccea29283644d9aa4f31833935bac3)

• Usability Testing Report Template from Xtensio (https://app.xtensio.com/design/39pqy155)

• Usability testing plan from Qatalog (https://docs.google.com/document/d/1M1oUk97dYvdM8EF6Fr-J_8FBjj7Qs1KBTNkFfpFKsqI/edit)

• Usability Testing Script from Slava Shestopalov (https://www.notion.so/Usability-testing-script-53ccea29283644d9aa4f31833935bac3)

Suggested Tools 

For Preparation & Planning

• Cubyts

• GoogleDocs

• Pen & Paper 

For Conducting Tests

• UserZoom

• UserTesting

• Usability Hub

• Dscout

• LookBack

• Optimal Workshop

• Loop11

• UXArmy

For Synthesis & Report Making

• GoogleDocs

• Office365

• Mural

• Miro

• Figma

References 

• Usability Testing 101 from NNGroup (https://www.nngroup.com/articles/usability-testing-101/)
• Usability testing: your 101 introduction from HotJar (https://www.hotjar.com/usability-testing/)
• 12 templates and checklists to get you started with usability testing (https://www.hotjar.com/usability-testing/template-checklist/)
• How to run moderated usability testing from HotJar (https://www.hotjar.com/usability-testing/process-examples/)
• Turn customer conversations into actionable insights from Lookback (https://www.lookback.com/)
• Usability Testing from IxDF (https://www.interaction-design.org/literature/topics/usability-testing)
• User testing: How many users do you need? From Maze (https://maze.co/blog/user-testing-how-many-users/)

Other Related Best Practices

• User Research Basics

• Prototyping Basics

• How to do a Design Audit

• How to conduct a Critique Workshop