The Questions to Ask Subject Matter Experts Before They Leave

The most important questions to ask subject matter experts before they leave are not "what do you do each day?" They are questions about judgment: which exceptions they handle, how they define key terms, what they check before approving something, and why things are done the way they are.

Procedures are often written down somewhere. Judgment usually is not.

This guide gives you a ready-to-use question set organized by the type of knowledge each question captures, techniques for getting past vague answers, and a method for turning interview notes into documentation your team and your systems can actually use.

Why Does Knowledge Walk Out the Door When Experts Leave?

Knowledge leaves with experts because much of it was never recorded anywhere except in their heads.

Panopto's Workplace Knowledge and Productivity Report, a YouGov survey of 1,001 U.S. employees, found that 42 percent of institutional knowledge is unique to the individual who holds it.

The same research found employees lose 5.3 hours a week waiting for information from colleagues or recreating knowledge that already exists.

This undocumented know-how is often called tribal knowledge: practical expertise shared informally within a team but not captured in formal documentation.

It includes:

• Workarounds
• Unwritten rules
• Customer history
• The reasoning behind decisions

Tribal knowledge is also a major cause of knowledge silos that lead departments to interpret the same policy differently.

The practical implication is simple:

When an expert gives notice, you are not losing a set of tasks. You are losing the answers to questions nobody thought to ask.

What Kinds of Knowledge Should You Capture?

You should capture five kinds of knowledge, and each needs different questions.

Most offboarding checklists only cover the first.

Knowledge Type	What It Is	Usually Documented?	Risk if Lost
Procedures	The steps of a task	Often	Low to medium
Definitions	What key terms really mean in practice	Rarely	High
Rules and exceptions	What must, must not, or may happen, and when not	Rarely	Very high
Decision logic	How choices are made when conditions vary	Almost never	Very high
Context and relationships	Why things are this way, who to call, history	Never	Medium to high

Plan your interview time around the bottom four rows.

That is where the irreplaceable knowledge sits.

The Questions to Ask Subject Matter Experts, by Knowledge Type

The best questions to ask subject matter experts are specific, scenario-based, and tied to one kind of knowledge at a time.

Use the sets below as an interview guide, not a script.

Questions About Procedures

Procedure questions confirm the steps and expose where the written version is wrong or incomplete.

• Walk me through the last time you did this task, step by step.
• Where does the documented procedure differ from what you actually do?
• Which steps do you skip or reorder, and when?
• What inputs do you need before you can start, and where do they come from?
• What does "done" look like? How do you know the output is correct?

Questions About Definitions and Vocabulary

Definition questions reveal how the expert interprets the terms that rules depend on.

• When you say "[customer / active / approved / urgent]," what exactly qualifies?
• Is there anything that looks like a [term] but isn't one?
• Do other departments use this word differently than you do?
• Which terms do new people most often misunderstand?

Questions About Rules and Exceptions

Rule questions capture what must or must not happen, and the cases where the normal rule does not apply.

• What is never allowed here, even if someone senior asks?
• Is there any situation where an approved request can still be rejected?
• Which customers, products, or regions get special treatment, and why?
• What exceptions do you handle that aren't written down?
• When two rules conflict, which one wins?

Questions About Decision Logic

Decision questions reveal the criteria the expert weighs, which is the knowledge hardest to replace.

• What do you check before you approve, reject, or escalate?
• Which factors matter most? Which can you ignore?
• Tell me about a borderline case. What tipped your decision?
• What would make you change your usual answer?
• What do you look for that a newer person would miss?

Questions About Context, History, and Relationships

Context questions preserve the "why" so successors don't undo past decisions by accident.

• Why is this done this way? What happened before it was?
• What has gone wrong before, and what did you change afterward?
• Who outside the team do you rely on, and for what?
• Which systems or spreadsheets contain logic only you understand?
• What is the one thing you worry will break after you leave?

How Do You Get Useful Answers Instead of Vague Ones?

You get useful answers by asking about specific past cases and then probing until the answer becomes a condition you could write down.

Experts compress years of judgment into phrases like:

"It depends."

or:

"You just know."

That compression is the knowledge you need to unpack.

Use This Probe Ladder When an Answer Is Vague

1. Ask for an instance.
   "Can you think of the last time that happened?"

2. Ask for the condition.
   "What specifically about that case made you decide that way?"

3. Ask for the boundary.
   "If that factor were different, would your answer change?"

4. Ask for the exception.
   "Is there ever a case where that wouldn't apply?"

5. Read it back.
   "So the rule is... Is that right?"

Step five matters most.

Reading a rule back in plain language lets the expert correct you on the spot, which is far cheaper than discovering the error after they are gone.

How Do You Turn SME Answers Into Documentation?

You turn SME answers into usable documentation by converting each judgment into:

• A defined term
• An explicit rule
• A decision table

Do not rely on a narrative summary alone.

Narrative notes record what someone said. Structured rules record what the business does.

Worked Example

Interview note: "Usually we approve credit extensions for existing clients, unless they've been late a lot recently. Big clients get more slack."

Questions That Resolve It

• What counts as an "existing client"?
  Answer: at least one paid invoice in the last 12 months.

• What is "late a lot recently"?
  Answer: two or more invoices more than 15 days late in 6 months.

• What makes a client "big"?
  Answer: over a set annual revenue threshold.

• What does "more slack" mean?
  Answer: three late invoices allowed instead of two.

Resulting Rules

• A client is an existing client if the client has paid at least one invoice in the last 12 months.
• A credit extension must not be approved for an existing client who has had two or more invoices paid more than 15 days late in the last 6 months, unless the client is a key account.
• A credit extension must not be approved for a key account that has had three or more invoices paid more than 15 days late in the last 6 months.

Every vague word in the original note became either a definition or a condition.

That is the difference between documentation a successor can apply and documentation they must reinterpret.

Note: This example is illustrative; thresholds will differ by organization.

How Should You Prioritize When Time Is Short?

When time is short, prioritize knowledge that is:

• High-impact
• Frequently used
• Held by only one person

Notice periods are often brief, so you cannot capture everything.

Priority	Criteria	Action
1	Only this person knows it, and errors are costly	Interview first, document as rules
2	Used often, partly documented	Validate and fill gaps
3	Rare, but high risk such as audits, year-end, incidents	Capture scenarios and contacts
4	Well documented and widely known	Confirm only

What Should a Knowledge Transfer Plan Include?

A knowledge transfer plan should include:

• An inventory of what the expert knows
• Prioritized interview sessions
• A documentation format
• A successor who practices the work
• A validation step

Sample 30-Day Knowledge Transfer Plan

Week	Focus	Output
1	Inventory responsibilities, systems, decisions, contacts; rank by priority	Knowledge map
2	Interview on definitions, rules, exceptions for priority 1 items	Draft vocabulary and rules
3	Interview on decision logic and context; successor shadows	Decision tables, context notes
4	Successor performs work; expert reviews and corrects	Validated documentation

Knowledge Transfer Checklist

Use this checklist to confirm the transfer is complete before the expert's last day:

• Responsibilities, recurring tasks, and calendar-based duties listed
• Key terms defined in writing and confirmed by the expert
• Undocumented exceptions captured as rules
• Major decisions captured with criteria or decision tables
• Spreadsheets, scripts, and system logic explained and located
• Key contacts and relationships recorded
• Successor has performed the work at least once with review
• Documentation stored in a shared, owned location
• Open issues and in-flight work handed over

What Are the Most Common Mistakes in SME Knowledge Transfer?

The most common mistake is treating knowledge transfer as an exit interview instead of a structured elicitation process.

Other common mistakes include:

• Starting too late. A single meeting in the final week captures little.
• Recording without structuring. Hours of video are hard to search and rarely rewatched.
• Asking only "what" questions. Procedures transfer; reasoning does not.
• Accepting "it depends." It always depends on something. Find out what.
• Skipping validation. If the expert never reviews the written rules, errors survive.
• No owner afterward. Documentation that no one maintains goes stale quickly.

Why This Matters More When You Plan to Use AI

Captured SME knowledge matters more with AI because AI tools can only apply knowledge that is written down clearly and consistently.

An AI assistant connected to your documents cannot recall an exception your expert handled from memory.

If definitions are vague or rules are missing, the AI will fill the gaps with guesses.

Structured knowledge means:

• Defined terms
• Explicit rules
• Documented decision logic

This structure serves both successors and AI systems.

Capturing it before an expert leaves is one of the most direct ways to make business knowledge AI-ready.

How BRS Helps Teams Capture Expert Knowledge

Business Rule Solutions (BRS) reports more than 30 years of experience in asking the right questions to elicit specialized business knowledge, working with business rules and operational decisions, and building structured business vocabulary.

The RonBot Learning Experience brings that method into everyday work.

According to BRS, RonBot helps teams:

• Craft questions for SMEs
• Discover hidden assumptions
• Address exceptions and conflicts
• Retain institutional knowledge
• Support onboarding
• Work directly from your own policies, procedures, and transcripts

It is paired with the BRS Professional Training Suite, which includes a module on rules and policies covering how to capture rules and use pattern questions to elicit them, plus modules on vocabulary and decision tables.

You can read the BRS perspective on business knowledge and AI or learn more about Business Rule Solutions.

Key Takeaways

• The questions to ask subject matter experts should target judgment: definitions, rules, exceptions, decision criteria, and context.
• Scenario-based questions and a probe ladder turn "it depends" into writable conditions.
• Convert answers into defined terms, explicit rules, and decision tables, not narrative notes.
• Prioritize knowledge that only one person holds and that is costly to get wrong.
• Start early, validate with the expert, and assign an owner afterward.

If an expert on your team is leaving soon, start with the priority 1 items and the rules-and-exceptions questions this week.

To build this capability across your team, explore RonBot training plans.

---

Frequently Asked Questions

What Questions Should You Ask a Subject Matter Expert?

Ask about how they define key terms, what rules and exceptions they apply, what criteria drive their decisions, and why processes work the way they do.

Scenario-based questions work best.

What Is Tribal Knowledge?

Tribal knowledge is practical, undocumented expertise held by individuals or teams, such as:

• Workarounds
• Unwritten rules
• Decision reasoning

How Long Does SME Knowledge Transfer Take?

It depends on the role's complexity.

A structured plan over several weeks, with interviews, documentation, shadowing, and validation, captures far more than a single exit meeting.

What Is the Difference Between an Exit Interview and a Knowledge Transfer Interview?

An exit interview asks why someone is leaving and how to improve the workplace.

A knowledge transfer interview captures the knowledge needed to keep doing their work.

How Do You Document Tribal Knowledge?

Convert it into:

• Defined terms
• Explicit rules
• Decision tables

Then have the expert validate it and store it in a shared, owned location.

Who Should Run the SME Interview?

Someone skilled at elicitation, often a business analyst, ideally with the successor present so they hear the reasoning firsthand.