Skip to content

Tacit Knowledge Elicitation

Draw out expert know-how that is used in practice but not yet articulated.

The Diagnostic Story

Symptom: Experts perform reliably but cannot explain how. When asked to describe their reasoning, they give compressed summaries or post-hoc rationalizations that novices follow only to get tripped up by the exceptions the summary omitted. Training relies on long shadowing without clear targets, and different experts disagree without being able to say why. Proposed protocols capture the visible steps while losing the craft — and performance drops when the protocol is followed by someone who was not there to absorb the rest.

Pivot: Observe the practice in context rather than asking for a self-report, probing the cues that trigger decisions, the comparisons experts make, and how they handle exceptions. Contrast expert and novice reasoning to surface what the expert does differently and implicitly. Externalize the knowledge provisionally, then validate it against cases and performance before treating it as transferable.

Resolution: Key-person dependency decreases and training targets become concrete enough that novices can aim at something specific. Documentation and decision support reflect what practitioners actually do rather than what looks good in a process diagram. What cannot be fully articulated is marked honestly rather than papered over.

Reach for this when you hear…

[aviation training] “The captain said the approach felt wrong but could not explain it — we need to sit with her and work through the cue by cue until we can name what she is sensing.”

[surgical skills transfer] “The resident can reproduce every step in the textbook but still misses the tissue tension that tells you when to stop — that is the thing we have to find a way to teach.”

[software reliability engineering] “Our senior SRE knows within two minutes of looking at a dashboard whether the system is about to fall over, and when she leaves we have nothing — we need to extract that pattern before she goes.”

Mechanisms / Implementations

  • Apprenticeship Observation: Places a learner inside real practice alongside an expert, so know-how surfaces through participation, running commentary, and correction rather than through interview.
  • Case Library Capture: Builds a searchable collection of real cases — each with its cues, the judgment made, the outcome, and its boundaries — so expertise transfers through contrast between examples rather than through a single rule.
  • Cognitive Interview: Walks an expert back through one specific remembered episode in fine-grained detail, reinstating the original context to recover the cues, reasoning, and rule-breaks they can no longer summarize.
  • Cognitive Task Analysis: Systematically decomposes a whole judgment-heavy task into the goals, cues, strategies, and decision points that drive it, producing a structured knowledge model that another practitioner could reproduce.
  • Critical Incident Technique: Collects and dissects the rare high-information episodes — successes, failures, and near misses — where routine behavior broke, because those are the moments that reveal the judgment ordinary descriptions leave out.
  • Decision Trace Review: Reconstructs an actual decision sequence from the records and artifacts it left behind, then walks the practitioner through the timeline to recover what they knew, and chose, at each step.
  • Expert Debrief: A short, recurring after-the-case review in which practitioners talk through what they noticed, considered, and were unsure of — turning tacit judgment into a standing team habit rather than a one-off study.
  • Judgment Aid: A compact, practice-facing card or prompt that puts the few decisive cues, watchpoints, and exceptions in front of a practitioner at the moment of the judgment — supporting attention without replacing skill.
  • Shadowing Session: An observer watches an expert do real work in its natural setting — silently and without participating — to capture the timing, tool use, and embodied cues that no interview would surface.
  • Simulation Replay: Reconstructs a realistic case and plays it forward under controlled conditions, so what different practitioners notice and decide as it unfolds can be compared, and elicited knowledge tested against fresh eyes.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Also references 9 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Critical Incident Elicitation · subtype · recognized

Elicit tacit judgment from memorable successes, failures, near misses, and edge cases.

Expert-Novice Contrast Elicitation · subtype · recognized

Elicit tacit knowledge by comparing what experts and novices notice, represent, and decide in the same case.

Shadowing-Based Elicitation · mechanism family variant · recognized

Elicit tacit knowledge by observing practitioners in real work and probing what was noticed or decided.

Cue-Based Judgment Capture · affective or cognitive variant · recognized

Elicit the cues and thresholds that trigger expert interpretation, action, escalation, or restraint.

Tacit Knowledge Transfer Debrief · communication variant · candidate

Use a structured debrief between expert and learner to surface cues, rationales, mistakes, and next-practice targets.