What is Usability Testing?

Table of content

Usability testing is a research method where representative participants attempt realistic tasks while a team observes whether the product supports those tasks effectively and where friction occurs.

TL;DR

Usability testing observes people attempting realistic tasks.
The goal is to see where the design supports or blocks user intent.
Tests can be moderated or unmoderated, remote or in person.
Task success, time, errors, hesitation, and qualitative comments can all be useful.
Testing should create actionable design changes, not only a report.

What happens in a usability test?

A participant receives a realistic scenario such as: “You noticed a suspicious charge. Show how you would temporarily freeze your card.”

The researcher watches what the participant does, where they hesitate, what they expect, and whether they recover from mistakes.

The interface is being tested, not the participant.

Moderated vs. unmoderated testing

Moderated testing includes a facilitator who can probe behavior and ask follow-up questions.

Unmoderated testing lets participants complete predefined tasks independently and can scale to larger samples.

What can teams measure?

task completion
time on task
errors and retries
first-click success
path taken
assistance needed
confidence or ease ratings

Usability testing vs. user interviews

User interviews explore experiences primarily through conversation. Usability tests emphasize observed behavior while a person uses an artifact.

How do you run a usability test?

Define the question the test should answer.
Select the right artifact and fidelity.
Recruit representative participants.
Write realistic task scenarios.
Observe without giving away the path.
Capture failures, hesitation, and comments.
Group patterns across participants.
Prioritize findings by severity and frequency.
Change the design and test again where needed.

Common mistakes

Giving instructions instead of tasks

“Click Settings and then Freeze” tests obedience, not usability.

Defending the design

Confusion is evidence, not a debate.

Testing too late

Earlier testing makes change cheaper.

Ignoring failed and alternate states

Real tasks often break outside the ideal path.

The bottom line

Usability testing asks: can real users accomplish this task with the design we created, and where does the experience get in their way?

Relevant Figr resource

Read How to Conduct Usability Testing for the full workflow.