1.

Testing your Design

Testing a design in the UX design process is crucial for ensuring that the product
meets the needs and expectations of users. Here are the key steps involved in the
UX design testing process:
Choose the Right Method:
Usability Testing: Observing users as they interact with your design to identify
any issues.
A/B Testing: Comparing two versions of a design to see which performs better.
A simple test for good design does exist.
A screen that passes this test will have surmounted the first obstacle to
effectiveness. The test is this: Can all screen elements (field captions, data, title,
headings, text and information, types of controls, navigation elements, and so on)
be identified without reading the words that identify.
A component of a screen be identified through cues independent of its content?
If this is so, a person’s attention can quickly be drawn to the part of the screen
that is relevant at that moment. People look at a screen or page for a particular
reason, perhaps to locate a piece of information such as a customer name, to
identify the name of the screen, or to find an instructional or error message.
The signal at that moment is that element of interest on the screen. The noise is
everything else on the screen. Cues independent of context that differentiate the
components of the screen
will reduce visual search times and minimize confusion.

[Link] Testing
Usability testing is the practice of testing how easy a design is to use with a group
of representative users. It usually involves observing users as they attempt to
complete tasks and can be done for different types of designs.
It is often conducted repeatedly, from early development until a product’s release.
To be clear, usability testing is, at its core, a means to evaluate, not create. It is
not an alternative to interaction design, and it will never be the source of that great
idea that makes a compelling [Link], it is a method to assess the
effectiveness of ideas you’ve already had and to smooth over the rough edges.
Usability testing is also not the same as user research. For some practitioners,
“tests” can
include research activities such as interviews, task analyses, and even creative
“participatory
design” exercises. This conflates a variety of needs and steps in the design process
into a single activity.

[Link] of Usability Testing

here are some common types of usability testing explained simply:
Remote Usability Testing: Participants use a product or website from their own
location while researchers observe and gather feedback remotely. It’s
convenient and allows testing with diverse users without geographical
constraints.
Moderated Usability Testing: A researcher guides participants through tasks,
observes their interactions, and collects feedback in real-time. It’s helpful for
understanding user behavior and thoughts as they navigate through the product.
Unmoderated Usability Testing: Participants complete tasks independently,
without direct guidance from a researcher. They usually record their screen and
verbalize their thoughts while interacting with the product. It’s efficient for
gathering feedback from a large number of users quickly.
Comparative Usability Testing: This involves testing multiple versions of a
product or interface to determine which performs better in terms of usability. It
helps in making informed design decisions by identifying strengths and
weaknesses of each version.
Think-Aloud Testing: Participants verbalize their thoughts and actions as they
interact with the product. This provides insights into their decision-making
process and helps identify usability issues that might not be obvious otherwise.
A/B Testing: Also known as split testing, it involves presenting users with two
(or more) versions of a product or interface and measuring which one performs
better based on predefined metrics such as conversion rate or user engagement.
Guerrilla Usability Testing: Conducted informally in public spaces or online
communities, often with minimal planning and resources. It’s useful for
gathering quick feedback from a diverse range of users in a natural setting.

4. Usability Testing Process

1. Create your prototype
2. Test planning
3. Recruiting people
4. Test execution
5. Analysis and documenting the test result
6. Reporting

5. Preparing and planning for the Usability Tests

[Link] the test objectives

First of all, it is important to know why you want to perform a usability test. What
is the goal?
To define the goal, you need to evaluate the current state of your UX design
project:
 • If you do not yet have a UI, you may want to perform the test with
competing products. This way, you want to evaluate what features and
other design issues work with similar products;
• If you already have a UI, it may be time for you to test your product to gain
insights. Then you will have a direction on what development
improvements are needed;
• Or, you may already have a released product and want to re-evaluate some
features and understand what needs to be updated or not.
Next, you need to understand what exactly you need to be tested:
What information do you consider important to collect;
What problems do you want to address?
With this information, you can understand exactly what will be tested and have a
few hypotheses, so you can build your scenarios, tasks, and scripts more
efficiently.

2. Choose which type of usability test you will use(Qualitative and

Quantitative)
There are different types of usability testing, each with its own characteristics,
objectives, pros, and cons.

Qualitative or Quantitative
The first choice that must be made is between qualitative and quantitative tests:

• Qualitative: intended to find information about how users use and behave
with your product. The qualitative type of testing is well suited to find
problems during the User Journey;
• Quantitative: to collect quantitative information about the user
experience. Time and success rate are some examples of
observable metrics.
Remote or In person
Another choice regarding the type of usability test is the geographical location of
the [Link] tests can happen in person or [Link]-person testing
requires the moderator and the user to be physically in the same place. On the
other hand, remote testing is done with the mediator and the user in different
locations.
Although it may seem like little difference, face-to-face tests tend to collect much
more information than remote tests. This happens because the observation of the
mediator is extremely important. They can analyze the user's body expression and
behavior, which is a bit more challenging to capture in a remote session.
Moderated or unmoderated
A moderated usability test is administered by one person, a researcher or a UX
Designer, who can answer and ask questions to the user. In addition, they
introduce the test to the articipant and give explanations of how it will work.
On the other hand, an unmoderated test is one that does not have a person to
supervise and follow the user. Generally, in this type of test, the user will perform
the tasks without asking or being asked any questions during the session.
It is important to say that a moderated test brings more insights and
information to the research. Because the researcher-participant interaction
allows deeper exploration of the user's questions and doubts, on the other hand,
it costs more than an unmoderated session.

The types of usability testing can be combined. You can opt for a qualitative,
face-to-face, moderated test; or a remote, non-moderated qualitative test.

3. Consider what tools you’ll need

Do you require any additional Usability testing tool or software to get the job
done? This doesn’t necessarily mean tools directly related to usability testing—it
can also include note-taking software, video conferencing tools, project
management platforms etc.
It’s essential to be prepared for the testing process, and part of that is ensuring
you’ve got all the tools you need Here’s a look at some of the software this could
include:
• Zoom: for video conferencing
• Airtable: for project management
• Maze: for remote usability testing and continuous research
• Notion: for taking notes
• Uxcel: for educating the rest of the team on what you’re doing

[Link] Participants
At a first glance, we may believe that the more participants in the test, the
better. But the truth is not quite like that.
The basic behaviors of your users tend to be similar. So a larger number of
participants will only bring repetition of results and no more relevant data than
if it was done with fewer people.
Therefore, the efficient number to apply the usability test is 5 people! More than
that and you will only waste time and money. But remember that the choice and
the definition of your user profile or persona is the key to a successful result.

5. Set Up the Test Environment

Choose appropriate tools and software for conducting the test, such as screen
recording software or remote testing platforms. Ensure all necessary hardware
and software are ready, including devices that reflect what users typically use.

6. Pilot Test
Run a Pilot: Conduct a pilot test with a small number of participants to identify
any issues with the test plan, tasks, or equipment.

[Link] Data
Collect all the essential test result data for futher test.

8. Analyze the Results

Collected data result to be analyzed by either expert or researcher.

9. Report
A usability report lays out the findings from your usability testing and what you
can learn from them. This report can then be shared with relevant teams to update
them on findings for current and future projects. After all, insights are useful
across the organization—not just in product development.
Your usability report should include a variety of details from the usability testing
process—not just the results. Include details that provide context and accurately
communicate the time, effort, and energy that goes into successful usability
testing. This report isn’t just about sharing results, it’s also about ensuring
everyone understands the importance and impact of user research.