Subject matter expert (SME) interviews often begin with a reasonable request: “Walk me through the process.” The expert explains the official steps, the interviewer takes notes, and everyone leaves believing the important knowledge has been captured. Then a new employee follows the document and reaches a situation the expert never mentioned because, to the expert, the answer was obvious. Experts often forget to explain the cues, assumptions, and decision points that they use when the standard process no longer applies.
Unfortunately, that missing information causes confusion, inconsistent decisions, longer onboarding, and repeated help calls. The most useful knowledge is often not presented in the standard process.
Effective subject matter expert interviews are designed to uncover that missing information. They move beyond “what do you do?” to ask what is the exception, what is a common failure, what signals trouble ahead, and what does an experienced person notice before anyone else does. The goal is to uncover the differing paths in the process that not everyone will recognize.
Why Experts Leave Out the Most Important Details
Experienced employees rarely withhold information on purpose. They have repeated the work so many times that many decisions no longer actually feel like decisions. The most commonly identified trouble areas become the “other” path, the one that experts follow without realizing that the path even changed. In these situations, experts continue the interview without pausing to name the clue or explain the reasoning behind their actions.
This automatic expertise is called tacit knowledge: practical understanding built through experience but not yet written down. It includes shortcuts, warning signs, exceptions, relationships, and the history behind a rule. A procedure may say to request approval. The expert knows which requests need an early conversation, which reviewer needs added context, and which missing detail will send the request back. Unintentionally, this tacit knowledge is often left out of interviews.
General questions produce general answers. In contrast, deeper probing questions produce detailed, useful answers. A useful interview creates prompts that help the expert reconstruct a real event, compare normal and abnormal cases, and explain how a choice was made. That interview difference determines whether the final document includes all of the details needed to understand and complete the task at hand.
Do Not Wait for a Departure Notice
Organizations often begin expert knowledge transfer when a medical situation, retirement, promotion, or resignation creates urgency. This urgent moment is the worst time to discover the process has never been mapped, the backup has not been trained, and the expert has only a few weeks left on the job. Capturing knowledge as an emergency task increases the pressure of documenting quickly rather than effectively and makes it an exit task rather than part of your regular business routine.
Build subject matter expert interviews into moments when knowledge is already visible. In other words, capture lessons after a difficult incident, a major customer exception, a system implementation or upgrade, an audit, or a process redesign when that knowledge is fresh. Interview an expert when a backup is assigned, not only when the expert announces a departure. These triggers turn knowledge capture into regular maintenance and not an urgent task.
Prepare Before You Ask for the Expert’s Time
The last thing you want to do is have a first meeting with the subject matter expert that feels like a waste of time for either of you. A strong knowledge capture interview starts before the meeting.
Gather knowledge from both existing training materials and users, if available:
- Review the existing SOPs, job aids, training slides, support tickets, and so on.
- Talk briefly with people who depend on the process. Their questions show where the written version and the working version differ.
Set a narrow objective. For example, “Document purchasing” is too broad for one meeting. “Capture how the user reviews, corrects, and approves purchase requests above the standard threshold” gives the expert a clear boundary and makes it easier for them to identify authentic examples that should be included in the documentation.
Before the interview, answer as many of these questions as possible to help you focus the interview discussion. Then use the interview to fill in the gaps for any missing content.
- Who uses the output? A new hire may need more context than an experienced backup.
- What must the person be able to do? Define the decision or task, not merely the topic.
- Where does the process break down? Identify known errors, delays, and repeat questions.
- What background information is available and what does it tell me? Review existing SOPs, completed examples, screenshots, and support tickets.
When sending the interview invite to the SME, include the purpose of the meeting so that everyone involved understands the content to be discussed and explained. For example, state if you want to generate a list of job responsibilities for a specific role, document how to complete a specific task, or determine what updates need to be made in existing documentation.

Ask Subject Matter Expert Interview Questions That Reveal Decision Paths
The best subject matter expert interview questions ask the expert to explain, compare, and recall. Start with the standard process path to establish the foundation, but then branch out to cover the different paths where decisions can alter next steps.
- Comparison: “What separates an easy case from a difficult one?”
- Exception: “When would you not follow the standard step?”
- Signal: “What tells you something is wrong before the system generates an error?”
- Consequence: “What happens later if this detail is missed now?”
- Recovery: “Tell me about the last time this failed. How did you determine the cause?”
- Escalation: “What can a new employee decide, and what must be referred to someone else?”
- History: “Why does this rule exist, and what problem was it meant to prevent?”
Listen to the Explanation, AND Observe the Work
People describe work differently from the way they perform it. Whenever possible, ask the expert to demonstrate a real or representative task while explaining what they notice. Watch the order of actions, the information consulted, and the points where the expert pauses. A pause often marks a decision that will disappear from a simple step list.
Use appropriate safeguards for confidential, regulated, or customer information. A sanitized example can still show how the expert thinks. Ask the expert to explain why each screen, field, report, or reference matters. Then compare the demonstration with the existing documentation. Differences may reveal a missing instruction, an outdated requirement, or a workaround that should never have become standard practice.
Keep the Conversation Focused Without Rushing It
Good facilitation balances structure with curiosity. Use a subject matter expert interview guide, but do not treat it as a script that must be completed in order. If an answer reveals a costly exception or a critical control, follow it. Hold less important questions for a second session rather than cutting off the detail that makes the first session valuable.
Repeat important points in plain language and ask the expert to confirm your understanding. Define acronyms and local terms as they appear. If two experts describe the same process differently, do not average their answers into a tidy but inaccurate version. Identify whether the difference comes from role, location, customer type, risk level, or an unresolved policy question.
When the expert gives an example, stay with it. Ask what information was available, which options were considered, and why one option was chosen. Then ask whether the same reasoning applies every time. These follow-up questions separate a repeatable rule from a one-time story.
End by summarizing what was captured, what still needs evidence, and who can answer the remaining questions. Ask the expert to name the one mistake a replacement is most likely to make. That final question often surfaces the warning, assumption, or decision rule that the rest of the subject matter expert interview missed.
Common Subject Matter Expert Interview Mistakes and Better Alternatives
Common interview mistakes can limit the value of the knowledge you capture, even when the expert is knowledgeable and willing to share information.
Mistake: Beginning the subject matter expert interview without planning.
Alternative: When interviews begin without a clear purpose, they rarely produce meaningful results. If possible, gather background information from a project manager or existing content to develop an interview outline before the first interview. If that is not an option, use the initial interview to define key topics and identify possible knowledge gaps.
Mistake: Recording without guiding.
Alternative: Having an expert provide knowledge without guidance rarely produces usable content. The interviewer should direct the conversation by asking follow-up questions, clarifying terminology, and identifying exceptions and decision points. Rather than simply recording what the SME says, dig deeper to uncover the reasoning, context, and assumptions behind the work.
Mistake: Assuming that the subject matter expert is the ONLY expert.
Alternative: Most often, a subject matter expert is assigned to a project because of knowledge of the subject. However, do not assume that the SME is the only expert. During the subject matter expert interview, you may discover that others are better equipped to provide specific details because of their experience with a task or system. Ask for an introduction to additional experts when their knowledge is relevant to the project.
The Bottom Line: Interview for Decisions, Not Just Steps
Subject matter expert interviews succeed when they uncover the reasoning behind expert decisions. The standard process provides a starting point. The real value comes from the details—the signals, exceptions, consequences, and recovery decisions that allow another person to act with confidence.
In summary:
- Prepare before the subject matter expert interview.
- Ask about exceptions, not just standard steps.
- Explore real examples and past problems.
- Observe how the expert/user performs the work.
- Identify decision points and alternate paths.
- Capture the reasoning behind expert actions.
Capture how experts decide, not only what they do.
Clear, tested knowledge capture gives employees practical guidance they can use when completing a task or learning about a process. Contact Writing Connections to learn how our experienced team can help interview your experts and produce quality SOPs, job aids, training materials, and knowledge base content. You can find us on LinkedIn at linkedin.com/company/writing-connections-llc, where we share our community activities and thoughts about technical writing.