As an e-learning designer, it’s good practice to periodically review your e-learning courses and make sure they’re up to date and functioning as expected. Depending on how many courses you cr...
Published 6 years ago
Version 1.0
Blog Post
Nice work, Allison!
It's great to have a checklist like this, but it's even better not to need it. Every item on this checklist could be part of a design spec. Why create problems that we then have to fix later when we could prevent them completely?
Here's what this list could look like on the front-end of the problem:
Are there any references to events? Note this as the BEST BY DATE for the content that is visible to the learners upfront, and on a shared content maintenance calendar.
Are there any references to products that change from time to time? Note this as the BEST BY DATE for the content that is visible to the learners upfront, and on a shared content maintenance calendar.
Is there any photos/text referencing specific people in the company? Add this to the course notes textfile that accompanies each course and set the LMS to notify you when these users drop from the feed.
Information about internal processes that tend to change? Note this as the BEST BY DATE for the content that is visible to the learners upfront, and on a shared content maintenance calendar.
Information about laws and regulations? Use a permlink to link/embed to the specific documents.
Do not include contact information (email addresses and phone numbers) for specific people.
Do not upload logos/branding in your course, link to it instead.
Do any of the screenshots feature older versions of tools or images of people wearing outdated uniforms or logo apparel?
Note all technology used in course and validate annually and at major infrastructure revisions.
Use a broken link checker to automate broken link notifications.
Note all external references on your course notes textfile.
Do a thorough QA process separate from the SME content review.
There you go, two articles for the price of one :)
It's great to have a checklist like this, but it's even better not to need it. Every item on this checklist could be part of a design spec. Why create problems that we then have to fix later when we could prevent them completely?
Here's what this list could look like on the front-end of the problem:
Are there any references to events? Note this as the BEST BY DATE for the content that is visible to the learners upfront, and on a shared content maintenance calendar.
Are there any references to products that change from time to time? Note this as the BEST BY DATE for the content that is visible to the learners upfront, and on a shared content maintenance calendar.
Is there any photos/text referencing specific people in the company? Add this to the course notes textfile that accompanies each course and set the LMS to notify you when these users drop from the feed.
Information about internal processes that tend to change? Note this as the BEST BY DATE for the content that is visible to the learners upfront, and on a shared content maintenance calendar.
Information about laws and regulations? Use a permlink to link/embed to the specific documents.
Do not include contact information (email addresses and phone numbers) for specific people.
Do not upload logos/branding in your course, link to it instead.
Do any of the screenshots feature older versions of tools or images of people wearing outdated uniforms or logo apparel?
Note all technology used in course and validate annually and at major infrastructure revisions.
Use a broken link checker to automate broken link notifications.
Note all external references on your course notes textfile.
Do a thorough QA process separate from the SME content review.
There you go, two articles for the price of one :)
Hi Sam,
Thanks for the additional information.
What "broken link checker" would you suggest?
Thanks for the additional information.
What "broken link checker" would you suggest?