Your SME Is Not Your Enemy

Every instructional designer has heard the complaints, and most of us have made them. The SME is too busy to respond. The SME wants forty slides of content for a ten-minute lesson. The SME rewrites the storyboard at the final review. The SME signs off on a draft and changes their mind the week before launch.

Those frustrations are real. But after enough projects, a pattern emerges: the SMEs who cause the most friction are usually the ones who were never told what their role on the project was.

What You’re Actually Asking Them to Do

Consider the position the SME is in. They have spent years, often decades, building expertise in their field. Someone asked them to contribute to a training project, usually on top of a full-time job, usually with a vague description of what “contributing” means. They have probably never been told what an instructional designer does, why we ask so many questions, or why we can’t include everything they know.

Without a defined role, the SME will fill the gap with the only role they are sure of: the person who knows the most, and who therefore decides. That is not hostility, and it is not arrogance. It is a reasonable response to a situation nobody explained.

Establish the Lanes

The simplest way I know to describe the division of labor is this: you are the technical SME, and I am the training SME.

The SME owns accuracy. They own the real-world context, the exceptions and edge cases, and the things only experience teaches. If a step in the process is wrong, they are the one who knows.

The instructional designer owns structure. We own the learning objectives, the sequencing, the interaction design, the accessibility, and the decisions about how to present the content so a learner can actually use it. The SME decides whether the content is correct, and the designer decides how to teach it.

Problems start when the lanes blur. An SME who dictates the interaction type or insists on a specific slide layout is stepping into the designer’s lane. A designer who overrides a technical detail because it doesn’t fit the storyboard is stepping into the SME’s. Naming the lanes at the start gives both people permission to stay in their own.

Set Expectations Before the First Interview

The most useful conversation in any SME relationship happens before any content is discussed. It takes about ten minutes, and it covers the following:

Time. How many hours will this realistically require, and over what period? An SME who agreed to “a few meetings” and discovers it is forty hours will disengage, and they will be right to.

Availability. What is a reasonable response time on both sides? If you need an answer within two days, say so, and agree on what happens when the answer doesn’t arrive.

Review cycles. How many rounds of review will there be, and what is each round for? One consolidated review per phase works far better than rolling comments that arrive whenever someone has a spare minute.

The kind of feedback. Ask reviewers to separate “this is incorrect” from “I would have done this differently.” The first is the SME’s lane, and the second is a preference that the designer weighs against the learning objectives.

Sign-off. Who has final approval, and who resolves disagreements when two SMEs contradict each other? That should be the project sponsor, not whoever argues longest.

Changes after approval. Make it clear, kindly and in advance, that changes after sign-off affect the schedule and sometimes the budget.

None of this is adversarial. It is the same clarity we would want in any project, applied to the relationship that most determines whether the project succeeds.

The SME Is Your Best Source of Evidence

Once the relationship is defined, the SME becomes the most valuable resource on the project. They know where new employees actually fail. They know which step in the process generates the most errors and why. They know what they wish every new hire understood on day one. That is the information a needs analysis is looking for, and nobody else in the organization has it in the same form.

The questions that surface it are specific, and they show respect for the expertise. Where do people get this wrong? What do experienced people do automatically that new people don’t know to do? What would you tell someone in their first week that isn’t written down anywhere?

It also helps to respect their time. Send questions in advance, and bring a draft instead of a blank page. Most SMEs will happily correct a draft, and few enjoy starting from nothing.

Where I Land

If the relationship with an SME has turned adversarial, the first place I look is not at them. It is at what I did, or failed to do, to define the relationship at the start.

Our job is to make an expert’s knowledge usable by people who don’t have it yet. We cannot do that without the expert, and we will not get their best work if they spend the project guessing what we want from them. Tell them what you need, tell them what they can count on from you, and treat them as the ally they are.

Next
Next

I Learned to Navigate With a Thomas Guide. My Learners Will Only Ever Know the GPS.