Forum Discussion
Hello from Moses — technical trainer exploring better SME review workflows
Hi everyone,
I’m Moses Zhu, a technical trainer and digital transformation consultant.
My background includes enterprise software development, AI and digital transformation consulting, and project-based training. I recently led a three-month Java and Spring training program for new employees, where learners produced requirements, process diagrams, database designs, code, testing materials, and final presentations.
One challenge I keep seeing is that training projects generate a lot of feedback, revisions, evidence, and approval decisions, but these are often spread across documents, spreadsheets, email, and chat.
I’ve joined this community to learn how instructional designers manage:
- SME feedback
- scope changes
- storyboard revisions
- version approval
- final sign-off
I’m especially interested in practical workflows rather than adding more process or documentation.
What part of SME review usually causes the most rework in your projects?
Looking forward to learning from everyone.
Moses
2 Replies
Hi MosesZhu welcome to ELH!
I'm sure your issue has a lot of friendly faces to it. Speaking as someone who also collects, changes, and iterates based on feedback quite frequently, I think one of my core pieces of advice is to utilize things like central repositories that can be utilized by tools like Claude to read and give impact statements. Tracking in a single place that you can then reference within your future iterations to me has made the process a lot more manageable.
Looking forward to seeing you more throughout ELH and in our Community, welcome again :)
Welcome to the best eLearning and instructional design community on the planet! 🙌🏾
Your process/workflow callouts apply to all of us, whether you're a corporate ID, eLearning developer, or freelancer. How functional and streamlined those workflows are (IMHO) depends on the maturity level of the learning function and, in particular, the ID team within any given enterprise. If processes do not yet exist, it takes time to foster workflow/process adherence among stakeholders.
+1 upvote on Rachael_Silvano's perspective.
