Turn an expert interview into a transferable learning curriculum
Conversations with domain experts are full of tacit knowledge that evaporates if you don't structure it immediately. This prompt transforms raw interview notes into a curriculum someone else — or future you — can actually learn from.
I just interviewed or had a deep conversation with an expert in {{EXPERT_DOMAIN}} and I want to turn what I learned into structured knowledge that is teachable and durable.
Here are my raw notes from the conversation:
{{INTERVIEW_NOTES}}
Audience who will use this curriculum: {{TARGET_AUDIENCE}}
1. Extract the core mental models or frameworks the expert used — the ways they organized their thinking that felt different from how a non-expert would approach the same problems. List each one and explain it in plain language.
2. Identify the tacit knowledge in the notes — things the expert said that only make sense if you've had experience in the field. These are the highest-value things to make explicit. Rewrite each one so a smart outsider could understand and apply it.
3. Find the expert's "rules of thumb" — heuristics they use to make fast decisions. For each one, state: the rule, the situation it applies in, and the situation where it would give bad advice.
4. Build a 5-module curriculum outline that would teach {{TARGET_AUDIENCE}} what the expert shared, in a logical sequence. Each module should include: a learning objective, the key content, and one practical exercise.
5. Flag any areas in the notes where the expert's advice might be specific to their context and not generalize — where a learner following it blindly could go wrong.
Note: If {{INTERVIEW_NOTES}} are sparse or mostly high-level, the curriculum will be thin. Where the notes have gaps, flag them explicitly rather than filling them with generic content. {{EXPERT_DOMAIN}}{{INTERVIEW_NOTES}}{{TARGET_AUDIENCE}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{EXPERT_DOMAIN}}{{INTERVIEW_NOTES}}{{TARGET_AUDIENCE}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.