So a recent twitter lrnchat was about working with SMEs (Subject Matter Experts), and here are some of the responses to the first question “Q1) What are the challenges working with subject matter experts?”:
- JaneBozarth: Q1: Helping them focus on critical/must know, not everything-there-is-to-know
- philharriman_ek: Q1 SMEs can be so deep into their subject that it can take real effort to find the learner context.
- Quinnovator: Q1: SME’s don’t know how they do what they do (cognitively compiled), so have to work to get the right focus
- tmiket: Challenge to get SMEs to think like a novice. They’ve forgotten how much they’ve learned along the way
- PearlFlipper: Q1 One of the challenge is they want to include EVERYTHING?!
At the risk of indulging in SME-bashing (not my intention – I’m exactly the same way in my areas of expertise), I would agree that it’s really difficult to be an expert and forget all those hard-won knowledge details of your field that comprise your expertise (it’s all about closets, really).
The Instructional Design View:
Here’s how this goes sometimes: You are a well-intentioned instructional designer, concerned about making sure the learner’s cognitive load is managed, and that your novice learners have a lean, focused, first exposure to difficult content that doesn’t overwhelm them, and allows them to start tentatively constructing their understanding of the material. You want to keep it as simple as possible, but no simpler. Your motto: Less is More.
The Subject Matter Expert View:
Your SME has a herculean task akin to giving someone directions from downtown Manhattan to Bloomington IN, and is worried that unless she spells out every right turn, every likely detour, and every place the route is confusing, then the poor learner could get lost and it would be the SME’s fault. Additionally, she’s driven the route hundreds of times, and knows the best places to get gas, where you definitely DON’T want to eat, and what the best times are to avoid traffic in each city.
This is hard-won knowledge, too. She suffered through a lot to accumulate all those details – wrong turns, traffic jams, extra miles, food poisoning – and she really wants to save those learners from having to learn it the hard way. Her motto: My Pain is Your Gain.
So who’s right?
You, as the instructional designer, are starting to panic — you know that you have limited time and resources to create this training, and the more content you put in, the less you are able to do with it. If it’s e-Learning, it will turn into the Dreaded Page-Turner, because you just don’t have time to create the 17 different problem-based scenarios to account for all of the different exceptions she’s describing. It turns into a battle, where you keep trying to cut things, and she keeps saying “but they need to know this!”
So who’s right? Well, you both are, depending on your perspective.
But here’s the good news — I have a tool for you. It’s one of my favorites in my instructional design toolbox, although I don’t get to use it as often as I like.
First, let me tell you a story.
Too Much Information:
A few years ago, I was working on a massive training project for new hires. Basically, these poor newbies had to learn EVERYTHING, and in a hurry. To give you a sense of what their job entailed, they needed to know chemical compositions, electrical troubleshooting, customer service, vehicle safety, basic business and territory management, mechanical repair, plumbing, machine installation, programming several kinds of large commercial machines, parts and inventory management, and first, foremost, and above all, sales procedures and skills. We were creating a really interactive course for them, and trying very hard to keep text density low.
And, I had the greatest SMEs — these guys had decades in the field, and had more stories than you could imagine — if they didn’t know the answer, they’d make one up and still be right.
But the magnitude of the material and the sheer scope of their knowledge meant that we were quickly getting into the push/pull kind of situation I described above. Even though they knew better, they’d wind up firehosing content because they just knew so darn much.
I was job-shadowing them one day (always, always, always do this if you can), and, I was listening to them tell stories over lunch. As I was listening to them, it occurred to me…
“…these guys sound just like the Car Talk guys.”
If you don’t know what Car Talk is, then head on over to the NPR site, and give them a listen. It’s a radio show with Click and Clack, a/k/a the Tappet Brothers, and they take listener calls, talk about cars, and laugh pretty continuously at their own jokes. But all sorts of people (who don’t care about cars at all) listen pretty regularly.
We created our own version of Car Talk for the course. Basically, it was a page, with a graphic of the two of them, and a dialogue conversation between the two. We were dealing with pretty stiff bandwidth constraints, so audio wasn’t an option, but if I was doing it now, I’d just plunk a cheap digital recorder down in front of them and grab it as it comes.
It was a pretty simple format that we could re-use over and over:
(my mock up of the template style, not the actual version)
So, um, what’s the big deal about that?
So, now, you are probably thinking that “whoa – you’ve totally oversold what basically amounts to an okay-ish e-Learning page template.”
But this relatively minor design element paid off hugely, in a number of different ways:
- It took exceptions out of the main course flow: The biggest benefit was that doing this took all that “yes, it is a one-off exception/more detail/but they have to know it” information out of the main course flow. Instead, we tucked “Want to know more about? ” links into the corner of the interface, that the user could choose to pursue then (if they were interested), or access later.
- It was the magic word: Whenever the content threatened to overwhelm the course material, we could just say “Oh, we’ll make that a TechTalk.” It eliminated the vast majority of the content wrangling that I described above. In fact, the client said “Oh, that can be a TechTalk” more than we did.
- It was a way of managing scope: TechTalks were the SME’s responsbility to write (which may or may not work in your world), and very low cost for us to implement.
- It made heroes of the SMEs: We had our artist do caricatures of the SMEs and used them as the experts (photos would work just as well). But this was a really great opportunity to provide some recognition of their contribution to the whole course.
But here’s the real trick
All of that was pretty good, but here’s the real trick if you do this:
Take it out of the e-Learning altogether.
Use one of those nifty other ways to communicate it later, one tip at a time:
Because it doesn’t matter how good a job we do managing the cognitive load of our new learners, they still aren’t going to want to know this stuff until they’ve been on the job a few months (or in this case, years), and they’ve had opportunities to bump into the relevant situations (and this buys also buys you all sorts of advantages, like time-distributed learning, multiple exposures to the material, and a knowledge management base).
You want the learner reaction to be “Oooh, that’s how that works” instead of the “what, huh, what?”
* Thanks to xkcd.com for the generous usage policy