Last week I write about factors affecting the adoption of non-mandatory e-learning, and made a comment that whether or not your e-learning will be mandatory (i.e. compulsory for staff to complete) will affect your instructional design approach. Today I'll address this comment.
First of all, let me explain this post is only addressing differences in the instructional design of mandatory and non-mandatory e-learning courseware. It will not address other types of e-learning.
Okay, let's create some context by looking at some typical examples of mandatory and non-mandatory e-learning.
Examples include HR policy and safety procedures. The intention of mandatory e-learning is to push information out to staff. Completion is tracked, and consequences ensue if staff don't complete the e-learning.
Examples include operational skills such as project management, and software skills such as Excel. The intention of non-mandatory e-learning is to provide staff development; an opportunity for staff to pull the information they need.
Below is a list of common differences in the instructional design of mandatory and non-mandatory e-learning:
Returning to last week's post, if you are about to develop e-learning courseware to inform staff of operational procedures or processes, be sure to keep the menu headings simple and explicit, and keep the navigation free to enable learners to explore.