השוואת שיטות

	הליכה משותפת פלורליסטית	הליכת חשיבה קוגניטיבית
תחום	אינטראקציה אדם-מחשב	אינטראקציה אדם-מחשב
משפחה	Hypothesis test	Hypothesis test
שנת המקור	1992	1990
הוגה השיטה	Randolph G. Bias	Clayton Lewis, Peter Polson, Cathleen Wharton, John Rieman
סוג	User-centered walkthrough with mixed stakeholders	Evaluative walkthrough examining how users learn to use an interface
מקור מכונן	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	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).
כינויים	Pluralistic Usability Walkthrough, PW	Cognitive Walkthrough, CW Analysis
קשורות	4	4
תקציר	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.	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.