Give Joy the expert's role and the course topic, and get an interview guide built to surface the judgment and instinct a subject-matter expert carries in their head but rarely writes down.
Draft an SME interview guide to extract what a [senior claims adjuster] knows for a [fraud-detection course].
An illustrative example. Your output will reflect your own sources, data, and prompts.
This is built around the course objectives and the claims SOPs in your Knowledge Center, and it leans on the six question sets that tend to pull tacit expertise out of an adjuster. Each set targets a different kind of knowledge, so you're not just collecting the documented process back.
The goal of this conversation is the judgment an experienced adjuster applies before the process ever kicks in, the feel for a claim that doesn't add up. Open easy, then move from documented steps toward the calls they make on instinct. Record it if they'll let you; the exact phrasing they use is often the teachable part.
Warm-up & context
Decision points
Edge cases & exceptions
War stories
Common novice mistakes
Red flags & heuristics
Use the probe column below when an answer sounds complete but stays general. Most of the teachable detail is one "can you give me an example?" past the first response.
| Topic | What to probe for |
|---|---|
| First read of a claim | The specific fields they check and the order, not "I review the file" |
| Gut feeling | What the feeling is actually reading, translated into observable signals |
| Escalation threshold | The concrete trigger, not the policy wording, and who they call |
| Edge cases | A real example where the standard rule gave the wrong answer |
| Novice mistakes | The tell that separates a first-year read from a seasoned one |
| Red-flag weighting | Which signals they trust, which they discount, and why |
Two tips for the room. When you hear "it depends," that's the door, not the wall: follow with "depends on what?" and "give me a case where it went the other way." And when they describe a decision as obvious, ask what a smart new hire would have done instead. The gap between those two answers is the course.
Want me to tailor this for a 30-minute slot, or turn the war stories and edge cases into scenario seeds you can build practice activities from?
Subject-matter experts are fluent in their own judgment, which is exactly why they can't narrate it. Ask a general question and you get the documented process back. The knowledge worth teaching lives in the decisions they make without thinking, the exceptions they've learned the hard way, and the mistakes they watch novices repeat. Getting to it takes deliberate questions, and most of us are writing them on the drive over.
Name the expert's role and the course you're building, and point Joy at any course objectives, SOPs, or prior interview notes in your Knowledge Center. Rough is fine.
Say what you want the interview to pull out, whether that's decision-making, edge cases, or the mistakes learners keep making. Joy shapes the question sets around it.
You get an interview guide organized by question set, with a topic-by-topic probe table and tips for getting past "it depends." Every group targets a different kind of expert knowledge.
Tweak any question, ask Joy to tailor the guide for the time you have, then copy it into your notes doc or interview tool and run the conversation.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Question sets target the judgment, exceptions, and instinct that experts carry but rarely document, not the process that's already in the manual.
Joy reads the course objectives and existing SOPs in your Knowledge Center so the questions map to what learners actually need to be able to do.
A topic-to-probe table tells you what to dig for on each subject, so a promising answer doesn't stop at the surface.
Ask for a shorter version for a 30-minute slot, or a deeper one for a half-day session, and Joy trims or expands the sets to fit.
Trim the guide to the highest-value questions for a 30-minute conversation when the expert can't spare more.
Turn the war stories and edge cases the expert shares into rough scenario starters you can build practice activities from.
Adapt the guide to interview two or three experts together, with questions that draw out where their judgment differs.
Generate a second-round guide that goes deeper on the one or two areas where the first interview revealed the richest material.
Experts default to describing the documented process because that's the version they can narrate. The guide moves from easy warm-up questions toward decision points, edge cases, and war stories, which are the prompts that surface judgment rather than procedure. The probe table tells you what to dig for when an answer stays general, and the built-in tips help you get past "it depends" to a concrete example.
No. Joy drafts the interview guide as text in the chat. You review it, tailor it, copy it into your notes doc or interview tool, and run the conversation yourself. The value is walking in with the right questions in the right order, not automating the interview.
Yes. The six question sets, from decision points to novice mistakes to red flags, apply to almost any expertise. Give Joy the expert's role and the course topic, and it fills the groups with questions specific to that domain.
Ask Joy to tailor the guide for the time you have. It trims to the highest-value questions for a short slot, or expands the sets for a longer session, so you're not trying to cover a 60-minute plan in half the time.
Joy can turn the war stories and edge cases the expert shares into rough scenario seeds, which are starting points you can build practice activities and case studies from. It drafts the text; you shape it into the course in your authoring tools.
Join the waitlist and be first to try this workflow when JoySuite launches.