A usability test is not an interview

Morten Hertzum

7 Citations (Scopus)

Abstract

Usability tests are conducted to gauge users’ experience with a system, preferably before it is released for real use, and thereby find any problems that prevent users from completing their tasks, slow them down, or otherwise degrade their user experience. Such tests are important to successful systems development, yet test procedures vary and the quality of test results is sometimes contested. While there is no single accepted procedure for usability specialists to follow when conducting usability tests, these tests normally involve users who think out loud while using a system and an evaluator who observes the users’ behavior and listens in on their thoughts. This common core of usability tests is illustrated in Figure 1. The possible variations include, for example, whether the users work individually or in pairs, whether the evaluator is in the room with the user or in an adjoining room, whether use of the system consists of solving preset tasks or exploring the system more freely, and whether the interaction between the evaluator and user is kept to an absolute minimum or involves frequent prompts for reflections and experiences.
Original languageEnglish
Journalinteractions
Volume23
Issue number2
Pages (from-to)82-84
Number of pages3
ISSN1072-5520
DOIs
Publication statusPublished - 2016

Fingerprint

Dive into the research topics of 'A usability test is not an interview'. Together they form a unique fingerprint.

Cite this