How to process SME feedback faster

If you have ever finished a 90-minute SME call with three pages of unstructured notes and absolutely no idea where to start, you are not alone. The SME-feedback-to-revision-plan step is the most consistently underestimated part of an instructional designer's day. The call itself is half the time. Translating it into actionable work is the other half — and it is the half nobody schedules.

This post lays out a workflow we have refined across hundreds of training engagements. None of it is theoretical. All of it survives contact with real SMEs.

Capture before you interpret

The single biggest mistake IDs make is trying to filter while listening. The SME mentions a tone problem on slide four; we paraphrase. The SME flags a compliance gap on slide nine; we summarize. By the time we sit down to write the revision list we are working from our notes, not from what the SME actually said.

Capture verbatim. If you are recording the call, transcribe it afterwards. If you are not, write down direct quotes — in the SME's words — even when it slows you down. The signal is in the language the SME chose. "I would not say it that way" is different from "this is wrong."

Structure feedback into three buckets

Once you have a verbatim capture, sort each item into exactly one of three buckets:

1. Action — something specific to change in the content. "The SOP version on slide 7 is from last year; replace with the 2024 update."
2. Open question — something you cannot resolve without more information. "Is the new compliance language final, or are we still waiting on legal review?"
3. Context — useful background that does not directly translate into a change. "This module is also being shown to the field team."

Most IDs lump everything together and end up with a 40-item revision list that includes things they cannot start working on. Separating open questions from actions cuts your real revision list by 30-40 percent and prevents the "blocked" frustration of starting work that depends on a clarification you have not asked for yet.

Cite back to the source

For every action item, write the SME quote that produced it. Two reasons. First, when the SME asks "did you address my feedback on the third storyboard", you have the receipt. Second, when you draft the rewrite, the source quote tells you what success looks like — you are not interpreting your own paraphrase.

This is also how Rough Cut's SARA module works. Every checklist item links back to the source span, so the trail is always intact.

Draft the reply email immediately

Write a reply to the SME the same day. It does three things at once:

• Confirms receipt so the SME knows you heard them.
• Forces you to internalize the feedback by writing it back in your own words.
• Surfaces the open questions explicitly so the SME knows you are blocked on them.

The email does not need to be polished. It needs to be sent. A two-paragraph "here is what I heard, here are the open questions, I will have a v2 storyboard by Friday" message moves the project forward and protects you from the slow-burn problem of an SME who thinks their feedback fell into a void.

Set a rhythm

The same workflow applies whether you are dealing with one SME session or twenty. The cadence is the difference. For a single course with a single SME, daily is fine. For a multi-SME enterprise rollout with parallel review cycles on different modules, try a Monday-Wednesday-Friday rhythm: synthesize Monday, draft revisions Wednesday, ship updates Friday. The structure prevents the all-at-once crash that turns a manageable review cycle into a weekend.

When you outgrow this

The single-SME workflow above breaks down somewhere around three or four parallel reviewers on the same project. At that point you need conflict detection, deduplication, and someone (or something) keeping the revision plan coherent across reviewers. That is what the StorySync module does — but the underlying workflow is the same. Capture, structure, cite, reply, set a rhythm.

The tooling does not change the principles. It just keeps you out of the spreadsheet long enough to do the work.