Evaluation Method

Usability Testing

A UX evaluation method for observing how people use a product, service, prototype, or content flow to complete realistic tasks.

Concept facts

Usability testing is an evaluation method in which representative users attempt realistic tasks while a team observes what helps, blocks, confuses, or supports use.

Also known as
Usability test, user testing, moderated testing, unmoderated testing.
Used in
Product evaluation, prototype testing, service journey review, form evaluation, and content-flow review.
Interpret with
Task success, errors, time on task, user satisfaction, accessibility barriers, participant fit, and task realism.

Plain-language explanation

Usability testing helps teams learn what happens when people try to use a product or service for a real purpose. It is not limited to self-reported opinions because the evidence comes from observed behavior during tasks.

Tests may be moderated or unmoderated, remote or in person, early-stage or close to launch. The method should match the decision the team needs to make.

Why it matters

Usability testing can reveal barriers that internal teams miss, including unclear labels, confusing flows, missing feedback, inaccessible controls, or instructions that make sense to experts but not to users.

Use contexts

  • Testing public-service forms and portals.
  • Reviewing fintech, telco, healthtech, and edtech flows.
  • Evaluating prototypes before build.
  • Comparing existing and redesigned journeys.

Application guidance

Recruit participants who reflect the intended audience, create realistic tasks, define success criteria, and record what users do, where they hesitate, what errors occur, and what support they need.

Practical example

A development-sector organization is preparing to deploy a field data-collection tool for community workers collecting household and agricultural aid information in low-connectivity areas.

Usability testing asks field staff to complete realistic tasks: register a household, save data offline, recover after a sync failure, and verify whether a record has been submitted. The sessions reveal that users can enter data but cannot confidently distinguish between locally saved records and successfully synced records, creating risk of duplicate or missing program data.

Interpretive boundaries

  • Usability testing does not replace analytics, surveys, QA, accessibility review, or business validation.
  • Small tests can reveal important issues, but they should not be used to make unsupported population claims.
  • Participant tasks must be realistic enough to produce useful evidence.
  • Observed behavior should be interpreted with context, not used to blame users.

Applied at Userhub

Usability testing is relevant when Userhub evaluates whether people can understand and complete important service, product, or platform journeys.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

  • ISO. (2018). Ergonomics of human-system interaction – Part 11: Usability: Definitions and concepts (ISO Standard No. 9241-11:2018). International Organization for Standardization.
  • Rubin, J., & Chisnell, D. (2008). Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests (2nd ed.). Wiley Publishing.
  • Dumas, J. S., & Redish, J. C. (1999). A Practical Guide to Usability Testing (Revised ed.). Intellect Books.
  • Frøkjær, E., Hertzum, M., & Hornbæk, K. (2000). Measuring usability: Are effectiveness, efficiency, and satisfaction really correlated? Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, 345-352. https://doi.org/10.1145/332040.332455

Cite this entry

APA

Userhub. (2026). Usability Testing. UX Reference. https://userhub.com.bd/reference/usability-testing/