Having a second set of eyes on your e-learning content can go a long way toward helping to ensure you’re putting out quality content. However, the review process can quickly become complicate...
Published 6 years ago
Version 1.0
Blog Post
Hi Nicole, I posted similarly in LI but here goes:
1) SMEs - if 2 or more, designate a lead to consolidate comments and resolve conflicting comments prior to sending me one file. Also no 'secret' SMEs - identify all reviewers/approvers up front vs. thinking we're done and they say "ok we just need to send to Jill now for her approval"... "Jill????"
2) Final Content - be sure it's final and all stakeholders have signed off BEFORE you start building SL content so D1 or D2 isn't wasted just getting SME edits on what wasn't really final content.
3) Project schedule milestones/due dates - Stay on top of them. We're not using 360/Review yet nor a proj mgt app so old school Outlook email it is. My subject is something like "Action Requested - xxxxxxx Draft 1 ready for review" and included is next two milestone notes like "Draft 1 comments due EOD Fri 4.12" and "Due Soon Draft 2 release Wed. 4.17". Lastly, add a follow up reminder to the sent message to fire the morning of due date + 1. Sticking with this example, comments not in my inbox Monday morning 4.15? I'm sending a friendly follow up "Draft 1 comments past due" email.
4) One I forgot in LI... Translations... we use a translation vendor but policy requires internal native speakers review/edit the translation to ensure it's appropriate for our company environment. We now have the internal reviewers review/edit the Word translation file BEFORE we import into SL so we need only 1 foreign SL draft round they want to see once everything's been adjusted.
1) SMEs - if 2 or more, designate a lead to consolidate comments and resolve conflicting comments prior to sending me one file. Also no 'secret' SMEs - identify all reviewers/approvers up front vs. thinking we're done and they say "ok we just need to send to Jill now for her approval"... "Jill????"
2) Final Content - be sure it's final and all stakeholders have signed off BEFORE you start building SL content so D1 or D2 isn't wasted just getting SME edits on what wasn't really final content.
3) Project schedule milestones/due dates - Stay on top of them. We're not using 360/Review yet nor a proj mgt app so old school Outlook email it is. My subject is something like "Action Requested - xxxxxxx Draft 1 ready for review" and included is next two milestone notes like "Draft 1 comments due EOD Fri 4.12" and "Due Soon Draft 2 release Wed. 4.17". Lastly, add a follow up reminder to the sent message to fire the morning of due date + 1. Sticking with this example, comments not in my inbox Monday morning 4.15? I'm sending a friendly follow up "Draft 1 comments past due" email.
4) One I forgot in LI... Translations... we use a translation vendor but policy requires internal native speakers review/edit the translation to ensure it's appropriate for our company environment. We now have the internal reviewers review/edit the Word translation file BEFORE we import into SL so we need only 1 foreign SL draft round they want to see once everything's been adjusted.
- Thank you so much for leaving your helpful tips, Chris! Good advice!