A think-aloud (or thinking aloud) protocol is a method used to gather data in usability testing in product design and development, in psychology and a range of social sciences (e.g., reading, writing, translation research, decision making, and process tracing).
Description
editThink-aloud protocols involve participants thinking aloud as they are performing a set of specified tasks. Participants are asked to say whatever comes into their mind as they complete the task. This might include what they are looking at, thinking, doing, and feeling. This gives observers insight into the participant's cognitive processes (rather than only their final product), to make thought processes as explicit as possible during task performance. In a formal research protocol, all verbalizations are transcribed and then analyzed. In a usability testing context, observers are asked to take notes of what participants say and do, without attempting to interpret their actions and words, and especially noting places where they encounter difficulty. Test sessions may be completed on participants own devices or in a more controlled setting.[1] Sessions are often audio- and video-recorded so that developers can go back and refer to what participants did and how they reacted.[2]
History
editThe think-aloud method was introduced in the usability field by Clayton Lewis[3] while he was at IBM, and is explained in Task-Centered User Interface Design: A Practical Introduction by Lewis and John Rieman.[4] The method was developed based on the techniques of protocol analysis by K. Ericsson and H. Simon.[5][6][7] However, there are some significant differences between the way Ericsson and Simon propose that protocols be conducted and how they are actually conducted by usability practitioners, as noted by Ted Boren and Judith Ramey. [8] These differences arise from the specific needs and context of usability testing; practitioners should be aware of these differences and adjust their method to meet their needs while still collecting valid data. For example, they may need to prompt for additional information more often than Ericsson and Simon would allow, but should take care not to influence what participants say and do.
Process
editA typical procedure of think-aloud protocols would include:
- Design the study and write the guide: Determine the number and type of participant for the study. Generally 5 participants would be sufficient.[9] The next step is to write a guide that ask the participants to complete the tasks intended with clear step-by-step instructions. In the script, there should be reminders to participants to say their thoughts out when performing tasks.
- Recruit participants: The team should set up a screener for eligibility of participants. After contacting the person of interest and setting up meeting details such as time and location, the team could also provide additional information to help participant better prepare for the activity.
- Conduct think-aloud protocol: After stating the purpose and asking for consent, the team should proceed by giving instructions to the participant. Ask open-ended questions and follow-up questions. The team should avoid asking leading questions or giving clues.
- Analyze the findings and summarize insights: The team should use notes taken during the sessions to generate insights and to find common patterns. Based on the findings, the design team could then decide directions to take action on.
As Kuusela and Paul[10] state, the think-aloud protocol can be distinguished into two different types of experimental procedures. The first is the concurrent think-aloud protocol, collected during the task. The second is the retrospective think-aloud protocol, gathered after the task as the participant walks back through the steps they took previously, often prompted by a video recording of themselves. There are benefits and drawbacks to each approach, but in general a concurrent protocol may be more complete, while a retrospective protocol has less chance to interfere with task performance. Nonetheless, some concurrent protocols have not produced such interference effects,[11] suggesting that it may be possible to optimize both completeness and authenticity of verbal reports.
Benefits
editThe think-aloud method allows researchers to discover what users genuinely think of your design.[12]
Related method
editA related but slightly different data-gathering method is the talk-aloud protocol. This involves participants only describing their actions but not other thoughts. This method is thought to be more objective in that participants merely report how they go about completing a task rather than interpreting or justifying their actions (see the standard works[which?] by Ericsson & Simon).[citation needed]
See also
edit
References
edit- ^ Mclaughlin, Matthew; Duff, Jed; McKenzie, Tom; Campbell, Elizabeth; Sutherland, Rachel; Wiggers, John; Wolfenden, Luke (2021-07-26). "Evaluating Digital Program Support for the Physical Activity 4 Everyone (PA4E1) School Program: Mixed Methods Study". JMIR Pediatrics and Parenting. 4 (3): e26690. doi:10.2196/26690. ISSN 2561-6722. PMC 8367175. PMID 34309565.
- ^ Mclaughlin, Matthew; Duff, Jed; McKenzie, Tom; Campbell, Elizabeth; Sutherland, Rachel; Wiggers, John; Wolfenden, Luke (2021-07-26). "Evaluating Digital Program Support for the Physical Activity 4 Everyone (PA4E1) School Program: Mixed Methods Study". JMIR Pediatrics and Parenting. 4 (3): e26690. doi:10.2196/26690. ISSN 2561-6722. PMC 8367175. PMID 34309565.
- ^ Lewis, C. H. (1982). Using the "Thinking Aloud" Method In Cognitive Interface Design (Technical report). IBM. RC-9265.
- ^ http://grouplab.cpsc.ucalgary.ca/saul/hci_topics/tcsd-book/chap-1_v-1.html Task-Centered User Interface Design: A Practical Introduction, by Clayton Lewis and John Rieman.
- ^ Ericsson, K., & Simon, H. (May 1980). "Verbal reports as data". Psychological Review. 87 (3): 215–251. doi:10.1037/0033-295X.87.3.215.
{{cite journal}}: CS1 maint: multiple names: authors list (link) - ^ Ericsson, K., & Simon, H. (1987). "Verbal reports on thinking". In C. Faerch; G. Kasper (eds.). Introspection in Second Language Research. Clevedon, Avon: Multilingual Matters. pp. 24–54.
{{cite book}}: CS1 maint: multiple names: authors list (link) - ^ Ericsson, K., & Simon, H. (1993). Protocol Analysis: Verbal Reports as Data (2nd ed.). Boston: MIT Press. ISBN 0-262-05029-3.
{{cite book}}: CS1 maint: multiple names: authors list (link) - ^ https://www.researchgate.net/publication/3230127_Thinking_aloud_Reconciling_theory_and_practice Thinking Aloud: Reconciling Theory and Practice, by Ted Boren and Judith Ramey.
- ^ Nielson, Jakob. "Why You Only Need to Test with 5 Users". Nielsen Norman Group.
- ^ Kuusela, H., & Paul, P. (2000). "A comparison of concurrent and retrospective verbal protocol analysis". American Journal of Psychology. 113 (3). University of Illinois Press: 387–404. doi:10.2307/1423365. JSTOR 1423365. PMID 10997234.
{{cite journal}}: CS1 maint: multiple names: authors list (link) - ^ Byrd, Nick; Joseph, Brianna; Gongora, Gabriela; Sirota, Miroslav (2023). "Tell Us What You Really Think: A Think Aloud Protocol Analysis of the Verbal Cognitive Reflection Test". Journal of Intelligence. 11 (4): 76. doi:10.3390/jintelligence11040076. PMC 10146599. PMID 37103261.
- ^ Experience, World Leaders in Research-Based User. "Thinking Aloud: The #1 Usability Tool". Nielsen Norman Group. Retrieved 2021-12-13.
{{cite web}}:|first=has generic name (help)
External links
edit- Thinking Aloud: The #1 Usability Tool - an introduction to the think aloud method
- Using moderated usability testing - UK government resource on using think aloud