What to Do When Your SME Gives Conflicting Feedback on the Same Course Video

Here is a situation every instructional designer and course producer has been in at least once. You send a training video out for SME review. Two experts watch it. One says the process in section three needs more detail. The other says section three is already too technical and needs to be simplified. Both are domain experts. Both have real authority. Both are telling you to do something different to the same two minutes of video.

SME conflicting feedback on the same course video is not a rare edge case. It is a structural problem that appears whenever more than one expert has input into content that touches their area of expertise. The conflict is not the problem. The conflict is a signal that the content is sitting in genuinely contested territory, and the production team needs a decision, not more rounds of revision.

Here is how to handle it.

First: Distinguish Conflicting Feedback From Complementary Feedback

Not all disagreements between SMEs are actual conflicts. Sometimes what looks like conflicting feedback is two reviewers giving different types of notes.

• SME A says "add more context about why this step matters."
• SME B says "cut the explanation of the background process."

Are these in conflict? Maybe not. SME A might be talking about motivation for the step, and SME B might be talking about the historical background. If you address both specifically, you might be adding a sentence about motivation while removing a paragraph about history, and both reviewers would be satisfied.

Before you escalate a conflict, read both pieces of feedback carefully in context. Watch the video at the timestamp where each comment lands. Ask yourself whether these notes are actually about the same thing or just adjacent things.

If they are genuinely in conflict, one reviewer wants more of something and the other wants less of the same thing at the same moment. That is a real conflict and requires a decision.

• Read both conflicting notes in full before treating them as a conflict
• Watch the video at both timestamps to see if they refer to the same moment
• Determine if both notes address the same content or just the same time range
• If genuinely conflicting, flag it for a decision before editing begins
• Document which note was followed and why, for the record ## Who Makes the Decision This is the question most production teams avoid, and avoiding it is what causes conflicting feedback to drag out across multiple revision rounds. You cannot make the decision. As the instructional designer or course producer, you are not the domain authority. Choosing one SME's feedback over another's without authorization creates a liability if the content turns out to be wrong. You need to escalate to the person who has authority over both SMEs. In a corporate context, this is usually the L&D manager, the program owner, or the business stakeholder who commissioned the course. In a vendor relationship, it is the client's named content owner. The escalation does not need to be a meeting. An email that says: "We have received conflicting feedback from [SME A] and [SME B] on section three of lesson two. [SME A] recommends [x] at 2:43. [SME B] recommends [y] at the same point. These approaches are mutually exclusive. Please advise on which direction to take so we can proceed with the revision." That is a direct, professional escalation that puts the decision where it belongs and keeps the production timeline moving.

CALLOUT Escalate, do not arbitrate || When two SMEs give genuinely conflicting feedback, escalate to the content owner before editing. Choosing one without authorization creates risk.

Document the Conflict and the Resolution

When you escalate a conflict and get a decision, document both.

• Which SMEs gave which feedback
• At which timestamp in which version
• What the conflict was
• Who made the final decision
• What direction was chosen
• When that decision was made

This documentation matters for two reasons. First, when the SME whose feedback was not followed reviews the next version and asks why their note was not addressed, you have a clear record showing that a decision was made above their level. Second, if the content is ever challenged, you can show a clear chain of decision-making.

In PlayPause, the comment thread for a given video version serves as part of this record. The conflicting comments are both visible at the exact timestamps where they were left. You can add a reply to each one explaining what decision was made and why. That thread becomes the documentation without any extra effort.

Preventing the Conflict Before It Happens

Some conflicts are inevitable, but many are preventable. The most common cause of conflicting SME feedback is not genuine disagreement about facts. It is unclear scope: both SMEs think they have authority over the same content.

If SME A is the process expert and SME B is the compliance expert, and the content happens to be about a process that has compliance implications, both reviewers legitimately own some of it. Without a clear delineation, they will both give notes as if they own all of it.

Before sending a video for review, map the content to reviewers explicitly. "SME A: please review the process steps in sections one through three for accuracy. SME B: please review the regulatory language in section four for compliance." If a section genuinely requires both reviewers, make that explicit and name who has final authority if their feedback conflicts.

For how to manage SME feedback rounds without losing track of video revisions, scope mapping at the start of each review round is the single most effective preventive measure.

When the Conflict Is About Opinion, Not Fact

Not all SME conflicts are factual. Sometimes two experts genuinely disagree about the best way to explain something, the best example to use, or the appropriate level of detail for the target audience. Both are factually correct. They just have different pedagogical preferences.

In these cases, the decision belongs to the instructional designer, in consultation with what is known about the target learner. The ID has the professional standing to say "I understand both perspectives, and given the learner profile, we are going with approach X because it better matches the target audience's prior knowledge."

This is different from arbitrating a factual dispute. On factual disputes, the content owner decides. On pedagogical questions, the ID decides, and that decision should be documented with a brief rationale.

@@QUOTE Factual disputes go up the chain. Pedagogical disputes are yours to make.

Running the Revision After the Decision

Once you have a clear decision, proceed with the revision immediately. Do not wait for the SME whose feedback was not followed to pre-approve the direction. They had their input opportunity. The decision has been made above both reviewers.

When you send the revised version for final SME review, include a summary of what was changed and why. For a model of how to write that kind of handoff clearly, the instructional designers feedback from three stakeholders on one lesson video guide covers the communication side in detail. Be direct: "We received conflicting feedback on section three from [SME A] and [SME B]. Following consultation with [decision-maker], we proceeded with the approach recommended by [SME A]. Section three now [brief description of what changed]."

This transparency reduces the chance of the overruled SME re-raising the same issue in the next round, and it demonstrates professional process discipline.

For speed up SME review cycles when building corporate training videos, handling conflicts decisively is one of the most important cycle-time improvements you can make. A conflict that sits unresolved for a week waiting for both SMEs to schedule a call can be resolved in a day with a clear escalation email.

For collecting timestamped feedback from subject matter experts, having both conflicting notes visible in context at their exact timestamps makes the escalation email faster to write and easier for the decision-maker to act on.

Handle SME conflicts with a clear process instead of hoping reviewers will reconcile their own feedback. PlayPause gives you the comment record, the version history, and the approval trail to manage every review round cleanly. Start free at /pricing.