Usability research asks, with evidence, whether people can use a design to do what they came to do, quickly, correctly and without frustration. It does not guess: it watches real users attempt real tasks and measures what happens. A few well-run sessions find most of the serious problems.
Key concepts
- Task-based testing: give a person a realistic goal, not instructions, and watch.
- Think-aloud: participants speak their thoughts while working, which reveals confusion.
- Metrics: task success, time on task, errors and satisfaction scores.
- Qualitative and quantitative: observation explains why; numbers show how much and how often.
- Sample and bias: pick participants who resemble the real users, and avoid leading questions.
Vocabulary
- Moderated and unmoderated: a facilitator is present in the first; people test alone in the second.
- A/B test: two versions shown to different users to compare a measured outcome.
- Heuristic: a general rule of thumb for judging an interface.
- SUS: the System Usability Scale, a short standard questionnaire.
What to study, in order
- Learn the common usability heuristics and review an interface against them.
- Write three realistic tasks for a product, with a clear success condition for each.
- Run a session with five people, saying little, and record where they hesitate.
- Count successes, times and errors, rank the problems by severity, and write a short report.
- Fix the top problems and test again, and read about the statistics for A/B tests before trusting one.