Every good course starts with someone who really knows the work. In our business we call them Meyvns: the electricians, engineers, clinicians, technicians and leaders whose expertise gives training its credibility.
But expertise on its own doesn’t make a course. Some of the most knowledgeable people we’ve worked with have also been the hardest to turn into great learning, not because they lack anything, but because they know too much to see the subject the way a beginner does.
That gap is where learning design does its most important work.
Why experts leave things out
Experts don’t skip steps on purpose. Over years of practice, much of what they know becomes automatic. They no longer think about the decisions they make, so they don’t mention them when they explain the task.
Researchers who study expertise have measured this. Work on cognitive task analysis by Yates, Feldon and Clark (2011) reports that experts omit about 70% of the decisions they make when they describe how to perform a complex task.
Think about what that means for a course. If we simply write down what an expert tells us, learners may get the visible steps but miss most of the judgement that makes the difference between doing the task and doing it well.
Start with the job, not the content
The quickest way to lose the learner is to start with a list of topics. Experts naturally think in terms of everything they know. Learners need to know what they’ll be doing, and what they need to know to do it.
So before we talk about content, we ask:
- What does a competent person actually do in this role?
- What does good performance look like, and what does poor performance look like?
- Where do new people usually go wrong?
- What can go wrong on the job, and how do experienced people recognise it early?
The answers shape everything that follows, including the assessment, which we often draft before the content. If we know what learners must demonstrate, it becomes much easier to decide what belongs in the course and what doesn’t.
Draw out the hidden decisions
Asking an expert to explain how they do something tends to produce the textbook version. Asking them about the last time they did it produces the real one. A few techniques help.
Walk through a real example. Tell me about the last time you did this. What did you notice first? What did you do next, and why?
Ask about the exceptions. When does the standard approach not work? What would make you stop and check?
Contrast novice and expert. If a first-year apprentice and a 20-year veteran did this side by side, where would you see the difference?
Watch, then ask. Where we can, we observe the task being done and ask about the moments where the expert paused, checked or changed course. Those moments are usually where the hidden decisions live.
Separate need to know from nice to know
Experts care deeply about their field, which is exactly why we want them involved. It also means everything feels important. Left unchecked, a 20-minute module becomes a two-hour lecture.
We use a simple test for each piece of content. Does the learner need this to perform the task, make a decision or stay safe? If not, it may belong in a reference guide or further reading rather than the core learning.
This isn’t about dumbing things down. It’s about respecting the learner’s attention and cognitive load, so the essential ideas have room to land.
Respect the expert’s time
Most subject matter experts have a day job, and course development is extra work on top of it. The fastest way to lose their goodwill is to waste their time. We try to:
- Prepare before every session. Arrive with drafts, specific questions and examples, not a blank page.
- Ask for reactions, not essays. It’s far easier for an expert to correct a draft than to write from scratch.
- Batch the reviews. A few focused reviews at agreed points work better than a constant trickle of requests.
- Close the loop. Show experts how their input changed the course. People stay engaged when they can see their impact.
Keep the learner in the room
Throughout the process, someone needs to speak for the learner. That’s the learning designer’s job. We bring in learner profiles, test explanations with people new to the field, and ask the question experts rarely ask themselves: would this make sense to someone on their first day?
When the expert and the learning designer each play their part, the result is training that’s accurate, current and genuinely usable. That partnership is the reason Meyvn Collective exists. It’s also how we built the Critical Environment Technician course for the Microsoft Datacentre Academy.
Practical takeaways
- Expect experts to leave out much of their decision-making, and design your process to uncover it
- Define the job and the assessment before the content
- Ask about real examples, exceptions and the difference between novice and expert performance
- Test every piece of content against what the learner needs to do
- Protect your experts’ time with prepared, focused sessions