The Art of the SME Interview: Extracting "Need-to-Know" from "Nice-to-Know"
Subject matter experts possess an ocean of knowledge. Here is how to use behavioral probing, pattern detection, and consequence testing to isolate what actually moves the needle.
Executive Summary
Subject Matter Experts (SMEs) are, by definition, individuals who know vastly more than any single training program should ever cover. Left unguided, an SME interview quickly triggers an avalanche of technical nuance accurate and valuable in the expert’s daily work, but overwhelming and counterproductive for a novice learner.
The core skill of content gathering is not transcribing everything the expert shares, but systematically filtering "need-to-know" actions from "nice-to-know" background information. By employing behavioral questioning, active pattern detection, the "So What?" consequence test, and transparent upfront framing, instructional designers transform SMEs from defensive gatekeepers of detail into active partners in prioritization.
Key Takeaways (TL;DR)
1. Prioritize behavioral over knowledge questions: Ask about past failures and preventative actions instead of asking for broad conceptual overviews.
2. Track emotional and verbal patterns: Treat repeated stories, moments of frustration, and unprompted anecdotes as high-priority training targets.
3. Apply the "So What?" consequence test: If skipping a piece of information causes zero operational disruption, relegate it to a job aid or cut it entirely.
4. Set expectations early: Frame the interview upfront around performance outcomes to prevent SMEs from feeling like their expertise is being dismissed.
5. Separate core learning from reference docs: Use courses for high-friction decision-making and performance support tools for static reference data.
The Intake Dynamic: Information Dump vs. Performance Extraction
Unstructured SME interviews treat all information equally, leading to cognitive overload. Performance-driven interviews isolate high-consequence behaviors before drafting begins.
Trait | 1. Traditional Knowledge Intake | 2. Behavioral Performance Extraction |
Primary Question | "What do employees need to know about this?" | "What happens on the job when someone gets this wrong?" |
Target Deliverable | Comprehensive theoretical overview | Targeted decision-making practice & job aids |
Handling Background | Added directly into slide content | Moved to a searchable reference library |
SME Relationship | Passive content source | Active collaborator in risk prioritization |
Filter Metric | Subject completeness | Operational consequence & error reduction |
The 4-Part Framework for Extracting "Need-to-Know"
1. Shift to Behavioral Probing
Open-ended knowledge prompts (e.g., "Explain the steps in this process") invite lengthy lectures. Replace them with behavioral probes rooted in failure modes and real-world execution:
Traditional Prompt: "What are the core features of this machine?"
Behavioral Probe: "Walk me through the last time an operator broke this machine—what was the root cause, and what exact action would have prevented it?"
Outcome: Surfacing real-world friction immediately reveals the high-stakes decisions that warrant dedicated practice time.
2. Track Behavioral Patterns & Emotional Signals
Listen actively for subconscious prioritization cues that the SME may not explicitly state:
Frequency: When an SME mentions the same edge case or customer complaint two or three times unprompted, flag it as a critical learning objective.
Vocal Shift: Pay attention to shifts in vocal inflection, sighs, or expressions of frustration ("People always forget to toggle this setting"). Those moments highlight persistent operational pain points.
3. Deploy the "So What?" Consequence Filter
When an expert shares a complex technical detail, run it through the "So What?" filter to determine where it lives in your learning ecosystem:
4. Frame the Prioritization Upfront
SMEs often resist trimming content because they interpret cutting information as minimizing their domain's importance. Diffuse this tension in the first five minutes:
Kickoff Framing Script: "Our goal today isn't to capture everything you know—that would take weeks. Our goal is to identify the critical actions someone must take on day one to succeed. We will deliberately move background theory into quick reference guides so the course stays 100% focused on real-world practice."
The Visual Architecture: Content Triage Pipeline
Practitioner Playbook: Executing Lean SME Interviews
Send a "Pre-Flight" Agenda: Inform the SME that the session will focus exclusively on top performance challenges, common pitfalls, and real-life scenarios—not a slide-by-slide policy review.
Use the 80/20 Rule on Call Notes: Tag transcript notes in real time using two labels: [Action/Decision] and [Reference/Wiki].
Validate the Cut List: Close the interview by reviewing the triage list with the expert: "We agreed that Steps 1–3 are critical for interactive practice, while Steps 4–8 will be formatted into a 1-page digital reference sheet. Does that accurately reflect your priorities?"
Final Thoughts & Discussion
An effective SME interview is not a passive recording session; it is an active extraction process. When you guide the conversation around operational consequence rather than sheer volume, you protect the learner's attention, streamline development, and earn the lasting respect of your subject matter experts.
Over to you: What is your go-to question for steering an SME away from theoretical background and back toward practical job performance?
Comments