Client
Insights: Usability Testing 101
Role
Product Designer
Year
2022
It’s an exciting time for UX designers as diverse areas of knowledge are starting to consider user experience as an everyday practice of comprehending particular aspects of products and services. This inisight is about explaining Usability Testing to engineers who may be facing Usability Testing for the first time after this brief introduction to the tool.
What is Usability testing?
UX Researchers use this methodology to find problems but also opportunities by asking 5 real users to perform some key tasks of our interest followed by some questions.
Where do I start?
Here is a personal approach to what to do first and the following steps:
The basics
1. Set goals
It is important to have a clear understanding of our goals.
What do I want to test? Why?
2. Define roles
In case you are part of a team, it is helpful to approach the sessions organized and defining the roles is one of the possibilities to make our work easier.Facilitator: the person who is going to guide the user.Assistant: the person who is going to record, take notes and help when needed.
3. Choose users
How do I select the right users? We have 2 possible situations, and we are going to select users in different ways accordingly to which one we are at.
Real users
When users are already using the product or a similar one.
This situation is easier when it comes to obtaining and knowing users.Potential users
When the product we want to test is a new product in the context is going to be placed.
This situation is complex. Try to define your user to obtain better results. A perfect tool to define them is Personas.
4. Design tasks
The tasks that we are going to present to our users should be:
Real
Think about how your users naturally use the product or service and create tasks they would likely perform in an everyday real experience.Consecutive
Think about how your users naturally use the product or service and create tasks in a certain order they would likely perform in an everyday real experience.Simple
Produce tasks with simple vocabulary that your users can comprehend and relate to. Using complex or technical vocabulary can influence the results.
5. Prepare Script
When we work with people, many things can go wrong. We must prepare ourselves and our work to anticipate as much as we can. One of the ways to do that is by creating our script and steps in a way that is clear to us.
The goals of the script are:
Introduce yourself, explain the idea behind the test, and make sure the participant is comfortable and gives consent to follow the next steps.
Ask questions that take you closer to the participant and get to know the basics of the experience and the user's general characteristics.
Perform tasks.Make closure questions about the test to get more information about the experience and anything else that the user is willing to share.
Demonstrate appreciation and give a present for the time spent in helping the test.
6. Note-taking
Every researcher has a technique to take notes while the participant performs the tasks. However, there are some key elements to bear in mind:
The efficiency → the technique should be practical to analyze the results and compare tests.
The speed → the technique should allow rapid note-taking.
In usability tests, things happen quickly and we should be too.
One example is Rainbow Spreadsheet:
Here we identify patterns.
This technique helps us track rapidly as the test goes by. It does not require much time to record insights, only colouring the problematic steps and we can add as many details as we want.
7. Prepare set-up
It is of great importance that the facilitator can view:
the participant
the interface
the participant is operating on
the tasks
the script
anything to take notes on
The participant should always have access to:
the facilitator
the tasks (written)
the interface
The perfect set-up could need multiple devices but the advantages are evident when we work comfortable and have access to everything that’s happening. Also, resolving problems that might come up should be easier when we have all this knowledge of what is going on with the users while they perform the tasks.
📌 Try to perform a zero test, when you practice and check everything goes smoothly and just how you want it to be.
What to measure?
Quantitative vs Qualitative data
Usability testing is great for collecting qualitative information. Here we can acknowledge user concerns, experiences, anecdotes, the way they manage problems, and anything they are willing to share with us.On the other hand, we can also collect quantitative information, some of the common factors are time and success. But we should be careful: if we are looking for quantitative insights this is not the right tool for it, 5 users are not enough users to make assumptions about the behavior of a whole market segment.
Results
We have to identify patterns.
One way of presenting them is in two main categories: pains and gains.
It is also useful to add the users' comments that we might consider relevant.
In conclusion
Plan and practice
Prepare for every situation by planning and practicing what you already have planned. When we work with people, almost anything can happen that breaks our perfect plan. Take these as opportunities to excel in your ability to adapt to different approaches and experiences.
Be flexible
Although is true that the basis of Usability testing is repeating the same process for each user, we have to be flexible and receptive enough to attend to the necessities of every individual’s experience in the process.
Be receptive and sympathetic
The most important aspect of working with people is being receptive and sympathetic. Remember they have a problem, a necessity, or even simply helping you. Be present and thoughtful, these are the things that cannot be planned or practised but are the ones that truly make a difference in the quality of your work.