Blog/Quality Assurance

How to Perform Usability Testing in 7 Simple Steps

How to Perform Usability Testing in 7 Simple Steps

Usability testing often feels like a complex, resource-consuming process that requires specialized expertise and large investments. However, this misunderstanding prevents organizations from benefiting from one of the most valuable testing methods in product development.

According to Jakob Nielsen, a usability pioneer, the best results come from testing no more than 5 users. The first few participants reveal the most noticeable issues, making usability testing accessible to organizations with limited resources. IBM researcher Dr. Claire-Marie Karat stated, “A rule of thumb is for every one dollar invested in user experience research, you save $10 in development and $100 in post-release maintenance”.

This article breaks down usability testing into 7 simple steps, making it palatable for teams of all sizes and levels of experience. Whether you are a product manager looking to validate a new feature, a designer wanting to test the application interface, or just a student planning research for studies, these steps will guide you through the usability testing process efficiently and effectively.

Step 1: Define testing goals

Before starting the usability testing process, you need to define clear objectives. These 8 key elements can help you:

  1. Scope: What aspects of the product are you evaluating? What are you testing?
  2. Purpose: Why are you conducting this test? What questions are you trying to answer? 
  3. Schedule and location: Determine the testing timeline, where you will conduct the tests, the frequency of testing, and any potential costs.
  4. Sessions: Decide on the number of trials.
  5. Equipment: Write down all technology, materials, and resources required.
  6. Participants: Define your target users, recruitment methods, compensation, and participant roles.
  7. Scenarios: Create realistic user personas, their motivations, and goals.
  8. Metrics: Establish concrete measurements for each scenario to evaluate performance and satisfaction.

Defining these elements may seem difficult at first, but they form the foundation of an effective usability test. Without clear goals, you will risk collecting data that doesn't address actual product concerns.

Meeting with stakeholders can help with getting answers and defining these key elements. You will collect information about their product knowledge and identify which features need more testing.

The acronym "SMART" stands for Specific, Measurable, Achievable, Relevant, and Time-bound objectives.

Step 2: Choose the appropriate testing method

Before diving into usability testing, you must select the right testing method based on your circumstances. Look at your available resources, target audience, and defined goals to determine the most appropriate method. There are four overall usability testing methods:

  • Qualitative vs. quantitative
  • Moderated vs. unmoderated
  • Remote vs. in-person
  • Explorative vs. comparative
Testing type Key characteristics When to use
Qualitative Focuses on why and how users behave
Collects insights and feedback about behavior
Involves a smaller number of trials
Results in subjective observations
When you need a deeper understanding of user behavior
During early design phases
When identifying usability issues
When you want to understand the reasons behind user actions
Quantitative Focuses on what, where, and how many
Collects numerical data (time on task, success rates)
Involves a larger number of trials
Results in statistical measurements
When you need metrics to measure performance
For benchmarking against competitors
When proving the ROI (Return on Investment) of design changes
For tracking improvements over time
When you need data for stakeholders
Moderated Researcher guides participant through tasks
Allows for questions and clarification
Needs more resources
Provides detailed feedback
For complex products
When testing early prototypes
When you need to understand the user's thought process
When flexibility is needed during the session
For sensitive topics
Unmoderated Participants complete tasks independently
No direct researcher invasion
More economical and scalable
Usually performed through testing platforms
When testing with large user groups
When the budget is limited
When geographic variety is important
For simple, straightforward tasks
When you need results fast
Remote Conducted over the internet
Participants use their own devices
Greater geographic reach
Lower logistical overhead
During pandemic restrictions
When participants are geographically dispersed or geographic variety is important
To test in users' natural environments
When the budget is limited
In-person Conducted in a physical location
Direct observation of users
Better control over the testing environment
Easier to capture non-verbal cues
When physical interactions matter
For hardware or physical product testing
When you need controlled testing conditions
For complex products
Explorative Open-ended investigation
Discovers how users naturally interact
Less structured tasks
Focuses on discovery
In the early design process
When developing user requirements
To understand current user behavior
When exploring new concepts, ideas
Comparative Tests multiple design alternatives
More structured tasks
Comparison of performance
When deciding between design options
When optimizing a specific feature
To validate design decisions
Before final implementation

Step 3: Recruit the right participants

Finding the right participants is important for collecting meaningful insights from a usability test. As mentioned earlier, you typically need only 5-8 participants for qualitative testing.

Graph illustration for usability issues found per number of test users

Begin by developing user personas that capture not just demographics, but also behavioral patterns, goals, and technical skills of the target audience. These user personas should provide detailed criteria to ensure that selected participants represent the actual user base. Think about factors like experience with similar products, domain knowledge, accessibility needs, and device preferences.

Tips for effective participant recruitment

  1. Start recruitment early, ideally beginning 2-3 weeks before the actual testing.
  2. Recruit 20-30% more participants than needed, in case someone declines.
  3. Use clear selection criteria by defining must-have and nice-to-have characteristics.
  4. Don’t forget about testers' accessibility needs.
  5. Personalize communication and send individual invitations and reminders.
  6. Clearly explain time frameworks, compensation, and testing purposes.
  7. Track recruitment sources, tools, and success rates for future optimization.
Participants taking part in a usability testing event.

Step 4: Create the testing plan

Creating a good usability testing plan transforms set objectives into actions. This preparation phase requires reviewing test scenarios, providing guidance for the moderator, and conducting logistical activities. The testing plan is like a blueprint, which ensures consistency across testing sessions.

Step 5: Conduct the test sessions

Following these 5 phases will ensure that the test sessions run smoothly and collect valuable insights:

  1. Pre-session setup: Performed 15-30 minutes before the session, to ensure that the environment is ready for usability testing. During this phase, you will test all equipment, prepare required materials, review information about participants, and set up recording systems if needed.
  2. Welcome and introduction: This phase helps establish rapport and comfort between the moderator and participants. You can explain the process, set expectations for the session, and make participants feel comfortable. This phase is brief and typically takes only 5-10 minutes.
  3. Main testing: Participants execute the prepared scenarios and tasks, and the moderator documents their behaviours.
  4. Result summarizing:  This phase may take about 10 minutes. During this time, you can ask pre-prepared questions and gather your participants’ pointers for improvements of the product being tested. 
  5. Session conclusion: During this phase, the moderator expresses their appreciation, explains next steps, and answers participants' questions. This phase is brief and should take no longer than 10 minutes.

The main testing phase is the longest and most important one, and it will help you understand how people will use a product in real life. To collect more information and findings, you, as a moderator, need to ask questions that help people explain what they are thinking during the testing, but without telling them what to say. 

If someone seems stuck, do not jump in very fast -  just give them time to figure things out by themselves. Don’t forget about the participant's body language. One of the most important things is to make them feel comfortable, so they can show you how they use the product. Stay relaxed and calm, but interested in the process.

Step 6: Analyze your findings

After the testing session, you will have a lot of raw data that needs sorting and analysis to capture insights. Look for patterns you can see across different participants - if many of the participants have the same problem, it could be a sign of big issues. 

Compare what testers did with what you thought they would do. Sort findings by severity level and focus on the problems that stopped users from completing tasks or scenarios. 

Pro tip: Remember there’s a difference between real usability problems and personal preferences.

This table will help you sort findings by severity level:

Severity Level Description Example
Critical Prevents task completion and requires an immediate fix Users can’t find the checkout button
Major Complicates user flow and requires a high-priority fix Users need multiple attempts to complete registration
Medium Noticeable issue that needs improvement Users need time to select navigation options
Minor Confuses users and may be fixed in future releases Before proceeding, users read the instructions multiple times to correctly understand

Step 7: Present results and implement changes

The final step is presenting your findings and ensuring they lead to concrete improvements. Without proper presentation and change implementation, even the most insightful usability testing provides little value to your product and users.

To create an effective usability testing report, you should:

  1. Begin with a summary, where you will provide a high-level overview of key findings and recommendations.
  2. Briefly explain how testing was conducted, and present the methodology used.
  3. Highlight critical issues first by organizing findings by severity.
  4. Use visual evidence, like screenshots, videos, and other attachments, to illustrate problems.
  5. You should not just identify problems, but also provide or suggest recommendations and solutions.
  6. Include positive findings in the presentation to prevent unnecessary changes.

The bottom line

Usability testing does not have to be complicated or expensive. By following these 7 simple steps, you can conduct effective usability testing for your product. The insights gained from usability testing can improve your product's user experience, leading to higher user satisfaction and better outcomes. As Steve Krug, author of "Don't Make Me Think," famously said, "The best way to learn how to make anything more usable is to watch people actually try to use it".

Regular testing throughout the development process is better than waiting until your product is almost complete to discover usability issues that could have been found earlier with less effort and cost. Even informal testing is better than no testing at all.

Ready to launch a product your users will love and recommend? Reach out today to learn more about our usability testing services and how we can help you outperform your competitors.

QA engineer having a video call with 5-start rating graphic displayed above

Deliver a product made to impress

Build a product that stands out by implementing best software QA practices.

Get started today