KM-301d · Module 2

Think-Aloud Protocols & Critical Incident Technique

4 min read

Think-aloud protocol and critical incident technique are two complementary tools in the extraction toolkit. Think-aloud captures expertise in the moment of execution — what is the expert thinking as they work? Critical incident technique captures expertise through retrospective reflection on high-stakes events — what happened, what they did, and why it worked or failed. Together, they cover the two primary windows into expert cognition: the present and the past.

  1. Think-Aloud Protocol: Setup Ask the expert to perform a real or simulated task while narrating their thinking aloud. "Tell me what you are noticing. Tell me what you are deciding. Tell me what you are ignoring and why." Record audio and video. The analyst does not interrupt except to prompt verbalization when the expert goes silent for more than thirty seconds.
  2. Think-Aloud Protocol: Analysis After the session, review the recording and code the narration: classify each verbalization as observation, inference, decision, action, or evaluation. The frequency and depth of each category reveals the cognitive structure of the task. Decisions that are verbalized at length are genuinely deliberate. Decisions that are verbalized in one word are automatic. Both are important.
  3. Critical Incident Technique: Setup Ask the expert to recall a specific incident — a deal that almost fell apart but did not, a diagnosis that turned out to be the wrong one, a decision that they would make differently now. The incident must be specific: a real event, a real outcome, a real time and place. Generic examples reveal the curriculum, not the expertise.
  4. Critical Incident Technique: Probing For each incident, probe: "What were the early signals?" "What was the first decision you made?" "What did you not know at that point that you wish you had?" "At what moment did you know you had it right?" "What would a less experienced person have done differently at this specific point?" The incident is the anchor. The probing surfaces the knowledge.

Do This

  • Use think-aloud for procedural and perceptual tasks where real-time cognition can be observed
  • Use critical incident for judgment and decision tasks where past high-stakes events are the richest data source
  • Anchor critical incident probing to real artifacts — emails, notes, decisions — to reduce hindsight distortion
  • Run both techniques with the same expert across multiple sessions — the intersection of present and past cognition is the fullest picture

Avoid This

  • Use think-aloud for highly automatic tasks where verbalization disrupts performance — experts cannot simultaneously do and narrate without interference
  • Accept generic examples in critical incident sessions — "a typical difficult customer" is not an incident
  • Treat the first incident an expert offers as the most important — the second and third incidents after sustained probing are often more revealing