If you’ve ever worked with a SME on scenario-based learning, you know it can sometimes be challenging. SMEs who are accustomed to working on traditional elearning may be uncomfortable or unsure how to help you write scenarios. I have used these 3 tricks to help SMEs get “unstuck” while working together.
Ask for Their Stories
SMEs almost always have a collection of good stories about their topic. The trick is figuring out how to get those stories out of their heads and into a format you can use in a course.
Try these questions to gather for stories and consequences:
- Can you give me an example of how someone used this technique successfully? What were they able to accomplish by doing it right?
- What are the common mistakes people make? What happens when they make that error?
You may have to keep probing for more details with follow up questions like, “Tell me more about…” or “What happened next?”
The questions above give both positive and negative examples, plus the consequences for actions. The success story can become the outline for the correct path in your branching scenario. The mistakes help you identify the decision points in your scenario and the consequences following those choices.
Start Writing Even If It’s Wrong
Sometimes it’s hard to get anything from a SME. We’ve all worked with SMEs who were too busy to get on the phone or sit down for a meeting, or who replied to all of our questions with one- or two-word answers. I worked with one SME whose thought processes are so linear that she literally couldn’t read a flow chart unless someone physically sat next to her and pointed at each box while explaining it.
For whatever reason, if you’re having trouble drawing information out from a SME, start writing something yourself. Do your research–review existing training materials, online articles, books, blogs, etc. Make your best guess and start writing a scenario as best you can. The trick is, it doesn’t matter if it’s wrong. At this stage, you’re just trying to get something other than a blank page. Ask the SME to review it and point out all your errors. Even a recalcitrant SME will have a hard time not correcting your mistakes–and now you suddenly have more realistic mistakes or consequences.
SMEs frequently have a hard time envisioning how a storyboard will translate into a final product. Creating a prototype early helps them see how everything will work and how learners will progress through the scenario.
No matter how hard you work on the storyboard, even with multiple rounds of revision and a final approval, expect at least some small changes once the scenario is built and functioning. Build a few iterations into your project plan. An early prototype helps catch major problems before you build the entire scenario. If your SME is stuck, a prototype of part of the scenario might help them see how to fill in the gaps for the rest of the scenario.
Do you have a great trick for working with SMEs on branching scenarios? Tell me about it in the comments!
Read all my posts about Storytelling and Scenario-Based Learning.