Hi E-Learning Heroes community! I'd appreciate your thoughts/input/experiences when you've had to deal (or what you'd do) with training content that needs updating on a regular basis. Think of, for instance, an e-Learning course on an enterprise application that has (or would have) constant iterations in its UI or key functionality. Mostly looking for general ideas/guidelines as to what you've done or would do. Hope it made sense, and if not, happy to clarify.
Do most updates impact what's in the eLearning? How?
Are you using an eLearning course for the initial training/certification for users to gain access to the associated software?
How do you normally communicate updates to users who have already completed the initial training? (For example, do they have to retake an entire eLearning course?)
What resources are available for updating eLearning courses and/or other related materials?
I've sometimes used a disclaimer in courses when the look of the UI might change a bit, but the functionality remains the same. For example: "The screens you see when using the software may look somewhat different than the example screens in this course. This may be due to an incremental update that does not impact how this software functions."
I'm also a big proponent of performance-support materials. If the company wants users to complete a course for compliance or other reasons, then include enough basic info to provide an overview. But put details in job aids that can be more readily accessed (and more easily updated).
@Judy you're a rock star, thanks! To your questions:
- How often do the updates happen? // Not happening yet as we're developing the content but wanted some pro input in advance. - Do most updates impact what's in the eLearning? How? // For sure many of the updates will have to do with one of the tools that final users work with a lot. The look and feel of the UI will change, and it's likely to keep changing iteratively in the future. I could put off creating the sections pertaining to that tool but we're pressed to start developing the course. - Are you using an eLearning course for the initial training/certification for users to gain access to the associated software? // Not in this case. - How do you normally communicate updates to users who have already completed the initial training? (For example, do they have to retake an entire eLearning course?) // This is geared to new hires, so they wouldn't have to take it again, but open to hear ideas on best practices in communicating updates. - What resources are available for updating eLearning courses and/or other related materials? // Storyline tools
FYI re: "resources." That question is actually about the people available to do the updates. The company needs to plan for (i.e., budget for) the time needed to update training materials every time the software changes. This could include not only the Storyline developer, but also people to do reviews/approvals. Plus the LMS admins needed to upload the revised course.
In other words, don't forget to consider the effort/cost needed to maintain a course.
Great question! I like Judy's idea of including a disclaimer that talks about how the UI may have changed. In addition to including a disclaimer, you could also add a slide in the beginning that presents the new UI.
5 Replies
A lot depends on the answers these questions:
I've sometimes used a disclaimer in courses when the look of the UI might change a bit, but the functionality remains the same. For example: "The screens you see when using the software may look somewhat different than the example screens in this course. This may be due to an incremental update that does not impact how this software functions."
I'm also a big proponent of performance-support materials. If the company wants users to complete a course for compliance or other reasons, then include enough basic info to provide an overview. But put details in job aids that can be more readily accessed (and more easily updated).
There should also be a clear communication strategy to inform users about updates.
@Judy you're a rock star, thanks! To your questions:
- How often do the updates happen? // Not happening yet as we're developing the content but wanted some pro input in advance.
- Do most updates impact what's in the eLearning? How? // For sure many of the updates will have to do with one of the tools that final users work with a lot. The look and feel of the UI will change, and it's likely to keep changing iteratively in the future. I could put off creating the sections pertaining to that tool but we're pressed to start developing the course.
- Are you using an eLearning course for the initial training/certification for users to gain access to the associated software? // Not in this case.
- How do you normally communicate updates to users who have already completed the initial training? (For example, do they have to retake an entire eLearning course?) // This is geared to new hires, so they wouldn't have to take it again, but open to hear ideas on best practices in communicating updates.
- What resources are available for updating eLearning courses and/or other related materials? // Storyline tools
Hi, Omar,
I'm glad my input is helpful.
FYI re: "resources." That question is actually about the people available to do the updates. The company needs to plan for (i.e., budget for) the time needed to update training materials every time the software changes. This could include not only the Storyline developer, but also people to do reviews/approvals. Plus the LMS admins needed to upload the revised course.
In other words, don't forget to consider the effort/cost needed to maintain a course.
Good luck!
Thanks, Judy! I really appreciate it.
Hi Omar,
Great question! I like Judy's idea of including a disclaimer that talks about how the UI may have changed. In addition to including a disclaimer, you could also add a slide in the beginning that presents the new UI.
This discussion is closed. You can start a new discussion or contact Articulate Support.