When it comes to developing eLearning courses, there are many things that can go wrong. Okay, so that isn’t the most positive start to this blog post! But the fact is that a single eLearning developer will not pick up every error in the first version of an eLearning course. Just as an author works with an editor, and a journalist needs a proofreader, it is only natural that eLearning developers need feedback from other people to identify errors and problems. Fresh eyes are needed because the developer is often too close to the material. But effective course reviews cannot be done in an ad hoc manner. To collect quality feedback, you need a structured review process. This involves determining who will review a course (both internally and externally) and what the timeframes for review will be. In this post I will look at some important aspects of the quality control process.
Clarifying the Review Process
I
f you are developing a course for a new client, it is important to communicate with them about the review process. This should be done at the start of a project. If you wait until near the end of the development process, you could run into problems such as project timeline blowout and additional costs. A typical problem is the late entrance of unexpected stakeholders who request additional content be added to the course. To avoid such problems, you must provide a clear understanding of how the review will work before the project commences. Consider the following questions:
In some cases you might be developing a course with the help of several Subject Matter Experts (SMEs). For example if there are 5 SMEs, are you prepared to go through 5 different review documents? What happens if different team members have different views on necessary changes? A good solution is to ask the team to nominate a spokesperson for the group. The SMEs could have a team meeting amongst themselves and then the team leader can produce a single review document on behalf of the team. This would save you time and also keep costs down (a good incentive for the client).
Checking for Accuracy
The first version of your course is likely to have inaccuracies but there is no need to panic. If you have a thorough checklist of questions at hand, it will help you and others to identify errors. In fact, I have found that many SMEs actually like spotting errors (as long as there are not too many!).
Here are some questions to consider:
Checking for Consistency
Consistency is needed to make your course look professional and cohesive. It helps to give the learners a sense of stability when working through the content. Some questions to consider when checking for consistency include:
Using templates will assist with consistency. But more on that in another blog post.
Checking for Functionality
When a course has been published and loaded to a Learning Management System, it is ready to be checked for functionality. Keep in mind that features such as links to websites may work in the pre-publishing phase, but then not work on the LMS and vice versa. Before the course goes live, make sure you have tested all the technical components of the course from the environment where the course will be deployed. Allow time for problem-solving because it can take longer than you think, especially if there is a problem you have not encountered before. I have found the eLearning Heroes community an excellent resource for finding solutions to technical problems.
Here are just a few things to watch out for:
Final Word
This is just a sample of things to check. It is best to develop your own review checklist, even if it’s as simple as a table in a Word document. Here is a simple template to download. I recommend developing a new checklist for each client. By tailoring the checklist to the clients’ needs, you are more likely to meet their specific requirements.
|
About Administrator: B Online Learning offers Certified Articulate training workshops around Australia and custom on site Articulate training. Browse our website for more informaiton on all our training and solutions that enable clients and students to build better eLearning. |
Comments
Posted On
Jan 11, 2013Posted By
Mereki WhiteHi there,
Thanks for this article, very timely for me at the moment as I am approaching pilot stage for a big project. We’ve used a similar template, but with some more pointed questions at the end to seek feedback on context and positioning, value of the tools provided in the course etc etc.
I am going to conduct my first ever ‘in person’ pilot – i.e. get a bunch of users in a room and actually watch them interact with the material. I’m hoping it yields the little ‘nitty gritty’ type of feedback people tend to gloss over or forget if they are just filling out a form to email back. At the moment I have no tool for collecting the details of what I observe or am told during that session – and am at a bit of a loss as to whether one is necessary, and if so what it should include. I’d love to hear from any other developers on this, but will also trawl the elearning heroes forums for similar threads.
Cheers.