Methoden vergelijken

	Het "hardop denken"-protocol	Cognitive Walkthrough
Vakgebied	Mens-computerinteractie	Mens-computerinteractie
Familie	Hypothesis test	Hypothesis test
Jaar van ontstaan	1980	1990
Grondlegger	K. Anders Ericsson and Herbert A. Simon, adapted to HCI by Clayton Lewis	Clayton Lewis, Peter Polson, Cathleen Wharton, John Rieman
Type	Protocol for capturing user cognition and decision-making during task execution	Evaluative walkthrough examining how users learn to use an interface
Oorspronkelijke bron	Ericsson, K. A., & Simon, H. A. (1980). Verbal reports as data. Psychological Review, 87(3), 215–251.	Lewis, C., Polson, P. G., Wharton, C., & Rieman, J. (1990). Testing a walkthrough methodology for specifying and evaluating user interface designs. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 387–392).
Aliassen	Talk-Aloud Protocol, Concurrent Thinking Aloud, TA	Cognitive Walkthrough, CW Analysis
Verwant	4	4
Samenvatting	The Think-Aloud Protocol is a usability testing method in which participants verbalize their thoughts while completing tasks on a system. As users navigate an interface, they continuously narrate their observations, interpretations, and reasoning, allowing researchers to understand their mental models, decision-making, and frustration points. Originating from cognitive psychology research by Ericsson and Simon (1980), this method was adapted for HCI by Clayton Lewis and has become one of the most widely used techniques for identifying usability problems and understanding user behavior.	Cognitive Walkthrough is an inspection method for evaluating interface designs by simulating and analyzing how users will learn to use a system through exploration and trial. Developed by Clayton Lewis, Peter Polson, Cathleen Wharton, and John Rieman in 1990, this method is grounded in cognitive psychology and focuses specifically on learnability—whether first-time or occasional users can discover how to perform tasks without formal training. Evaluators role-play user actions, answer a set of critical questions about feedback and discovery at each step, and document usability problems.