From subject-expert interview to production-ready course blueprint

Asking an expert to “send the content” often produces a folder of slides and documents with no clear learning sequence. Asking the expert to write the course creates a different problem: it consumes scarce time and shifts design work onto someone who may not have the tools or interest to do it.

A structured interview or workshop provides a better bridge. The production team prepares the questions, captures the reasoning and returns a concrete blueprint for review.

Prepare before the conversation

Collect representative source material and identify the intended audience, context, delivery constraints and project purpose. Review the material enough to avoid spending expert time on facts that are already clear.

Prepare an initial map of topics and uncertainties. The interview should focus on judgement, variation and priorities rather than asking the expert to narrate every slide.

Begin with performance

Ask what the learner must be able to do after the experience, where they currently struggle and what consequences follow from poor performance. Invite examples of strong and weak performance.

Questions might include:

• What does an experienced person notice first?
• Which decision creates the greatest difficulty or risk?
• What plausible option do learners choose for the wrong reason?
• Which part of your reasoning is rarely written down?
• What would convince you that the learner can apply this independently?

Capture boundaries and sources

Record what is evidence, what is local practice, what varies by context and what remains debated. Identify the authoritative references and the date or version that matters. These distinctions protect accuracy and help future updates.

For professional or regulated content, identify who has final approval and whether legal, clinical, policy or compliance review is required.

Find the teachable examples

Examples make expert reasoning visible. Ask for a typical case, a difficult case, a common error and a near miss. Explore how the expert distinguishes them and what feedback they would give.

These examples can become worked explanations, branching scenarios, assessment distractors, oral prompts, visual annotations and feedback criteria.

Choose the interaction after the reasoning is clear

Do not ask the expert whether they want a video, 3D model or simulation before the learning action is defined. Instead ask what the learner must see or do. The production team can then recommend the medium and explain the trade-offs.

Return a blueprint, not a transcript

The raw interview is a source. The review artefact should be a concise blueprint that includes:

• Audience, context and prerequisites.
• Outcomes and evidence of performance.
• Module sequence and key explanations.
• Representative examples and decisions.
• Interactive activities and feedback.
• Media requirements and accessibility alternatives.
• Assessment and progress signals.
• Source references, boundaries and reviewers.

A good blueprint lets the expert approve the educational product without asking them to build it.

Use staged review

Review the structure before scripts and media are complete. Review the prototype before producing the entire course. Review final content in the platform and on representative devices. This protects expert time and prevents late structural changes.

Maintain a decision record

Record what was approved, what remains provisional and why a design choice was made. This helps new reviewers, future updates and governance. It also prevents the same foundational decision from being reopened in every meeting.

Respect the expert’s unique contribution

The expert should spend time on accuracy, judgement, examples and boundaries. The managed team should own facilitation, structure, scripts, media coordination, implementation and quality assurance. That division makes the relationship efficient and produces a stronger learning product.