#18626
Cognitive walkthrough is a review technique where expert evaluators construct task scenarios from a specification or early prototype and then role play the part of a user working with that interface--'walking through' the interface. They act as if the interface was actually built and they (in the role of a typical user) was working through the tasks. Each step the user would take is scrutinized: impasses where the interface blocks the 'user' from completing the task indicate that the interface is missing something. Convoluted, circuitous paths through function sequences indicate that the interface needs a new function that simplifies the task and collapses the function sequence.
#18617
Contextual inquiry is basically a structured field interviewing method, based on a few core principles that differentiate this method from plain, journalistic interviewing. Contextual inquiry is more a discovery process than an evaluative process; more like learning than testing. Contextual inquiry is based on three core principles: that understanding the context in which a product is used (the work being performed) is essential for elegant design, that the user is a partner in the design process, and that the usability design process, including assessment methods like contextual inquiry and usability testing, must have a focus. For example, suppose you need to assess the usability of a wrench for automotive repair. Using contextual inquiry, you'd visit mechanics at auto repair shops and see how they work. You'd take in not only physical arrangements such as the location of the tool chests, or cramped conditions inside engine compartments, but also environmental concerns, such as the level of cleanliness of their hands, or the noise level in the shop, or the tight schedules imposed by their bosses. All of these would help define a context for their work--and thus a context for the usage of your product, the wrench. You'd also listen to their gripes about your product; how it slips out of their hands if they've been working on greasy stuff, how it gnaws the corners off stubborn bolts. You'd ask them what would make their jobs easier; what design changes would help them. They're a partner in the design process. Of course, you'd conduct all this research centering on the one thing you're analyzing: the wrench. This focus is important--it sets the goals for the visit ('We need to know how they store their wrenches'). Once you're done with your site visit, you can assess from your notes whether you found out what you needed to know.
Hom, James. VWH.net. Articles>Usability>Methods>Contextual Inquiry
#18618
Ethnographic Study / Field Observation
Observing users in the field is often the best way to determine their usability requirements. Traditional usability testing, while providing a laboratory environment that makes data collection and recording easy, also removes the user and the product from the context of the workplace. Sometimes, it's best to see exactly how things are done in the real world.
Hom, James. VWH.net. Articles>Usability>Methods>Contextual Inquiry
#18627
Formal Usability Inspection takes the software inspection methodology and adapts it to usability evaluation. Software inspections, more commonly known as code inspections, started at IBM as a way to formalize the discovery and recording of software problems ('defects' in quality jargon, 'bugs' in the vernacular). The technique also provided quantitative measurements that could be tracked using statistical process control methods. Code inspections were also adapted to check and track documentation defects, and usability defects were a logical next step. Formal usability inspections include aspects of other inspection methods too. Heuristics are used to help non-usability professionals find usability defects. Inspectors walkthrough tasks with the user's goals and purpose in mind, similar to cognitive walkthroughs, although the emphasis is less on cognitive theory and more on encountering defects.
#18625
Heuristic evaluation is a variation of usability inspection where usability specialists judge whether each element of a user interface follows established usability principles. This method is the part of the so-called 'discount usability engineering' method.
#18619
Interviews and focus groups let you query users about their experiences and preferences with your product. Both are formal, structured events where you directly interact with users, asking them to voice their opinions and experiences regarding your product.
#18622
Journaled sessions bridges usability inquiry, where you ask people about their experiences with a product, and usability testing, where you observe people experiencing the product's user interface. Journaled sessions are often used as a remote inquiry method for software user interface evaluation. A disk is distributed to a number of test subjects containing a prototype of the software product, as well as additional code to capture (or journalize) the subjects' actions when using the prototype. Users perform several tasks with the prototype, much as in formal usability tests, and their actions are captured with the journalizing software. Upon completion of the series of tasks, the users return the disks to you for you to evaluate. Because the journaling portion of the evaluation is largely automated, this approach to remote, hands-off inquiry is certainly more 'usable' then self-reporting logging, where users are requested to write down their observations and comments and send them back to you.
#18628
Pluralistic walkthroughs are meetings where users, developers, and usability professionals step through a task scenario, discussing and evaluating each element of interaction. Group walkthroughs have the advantage of providing a diverse range of skills and perspectives to bear on usability problems. As with any inspection, the more people looking for problems, the higher the probablility of finding problems. Also, the interaction between the team during the walkthrough helps to resolve usability issues faster.
#18621
Questionnaires are written lists of questions that you distribute to your users. Questionnaires differ from surveys in that they are written lists, not ad hoc interviews, and as such require more effort on the part of your users to fill out the questionaire and return it to you.
#18624
Snapshots is a method where the user takes screen snapshots at different times during the execution of a task or series of tasks.
#18623
Self-reporting logs are paper-and-pencil journals in which users are requested to log their actions and observations while interacting with a product. Like journaled sessions, this technique allows you to perform user evaluation at a distance. Unlike journaled sessions though, this technique requires much more work on the part of your subject user. You'd use journaled sessions when you need detailed information from the remote tests; for example, the actual mouse movements or sequence of dialog boxes and menu items accessed by the user. Obviously, requesting the user to record all of their actions in a log, down to each individual click, is out of the question. (Although if you're lucky enough to get someone who's anal enough to do that, well, just think, is that guy representative of your user population? Good luck...) Self-reporting logs, therefore, are best used when you don't have the time or resources to provide the interactive package required for journaled sessions, or when the level of detail provided by journaled sessions isn't needed. For example, you might want just general perceptions and observations from a broad section of users.
#18620
Surveys are ad hoc interviews with users, where a set list of questions is asked and the users' responses recorded. Surveys differ from questionaires in that they are interactive interviews, although not structured like contextual inquiries nor formally scheduled and organized like focus groups.
#13966
Welcome to the Usability Methods Toolbox! I've attempted to compile information about almost all of the methods and techniques (well, ok, a lot of them) used in usability evaluation. I hope you find helpful information here, or at least a pointer to additional information that will help you find what you need. I'll be continually updating the site with new sources and info, so please send me feedback!
