Bandingkan metode
Tinjau metode pilihan Anda berdampingan; baris yang berbeda akan disorot.
| Retrospective Think-Aloud× | Pluralistic Walkthrough× | |
|---|---|---|
| Bidang | Interaksi Manusia-Komputer | Interaksi Manusia-Komputer |
| Keluarga | Hypothesis test | Hypothesis test |
| Tahun asal≠ | 1980 | 1992 |
| Pencetus≠ | K. Anders Ericsson, Herbert Simon, adapted by Gary Olson and colleagues | Randolph G. Bias |
| Tipe≠ | Post-task verbalization method for reflecting on decision-making | User-centered walkthrough with mixed stakeholders |
| Sumber perintis≠ | Ericsson, K. A., & Simon, H. A. (1980). Verbal reports as data. Psychological Review, 87(3), 215–251. DOI ↗ | Bias, R. G. (1994). The pluralistic walkthrough: Coordinating technology and pedagogy in software development. In J. Nielsen & R. L. Mack (Eds.), Usability Inspection Methods (pp. 63–76). John Wiley & Sons. ISBN: 0-471-01877-5 |
| Alias≠ | Delayed Verbalization, Post-task Thinking Aloud, RTA | Pluralistic Usability Walkthrough, PW |
| Terkait | 4 | 4 |
| Ringkasan≠ | Retrospective Think-Aloud is a variant of the Think-Aloud Protocol in which participants complete a task without verbalization, then immediately review a video or replay of their task performance and narrate their thoughts, reasoning, and reactions. This method captures post-hoc reflection on decision-making and user experience without disrupting task execution. Particularly valuable for exploring user awareness, emotional reactions, and retrospective sense-making, Retrospective Think-Aloud provides the explanatory richness of concurrent thinking aloud without the disruption. | The Pluralistic Walkthrough is a usability inspection method that brings together users, developers, and usability specialists to walk through an interface and voice their reactions and concerns. Developed by Randolph Bias in 1992, this method combines elements of cognitive walkthroughs with user involvement, creating a collaborative evaluation setting that captures diverse perspectives. By including actual users in the evaluation session, the method bridges the gap between expert judgment and real-world user experience, uncovering unexpected insights and building stakeholder consensus around design improvements. |
| ScholarGateSet data ↗ |
|
|