Your objectives are approved and you’ve inserted them in your lesson. Awesome! You continue developing your content, building your interactions, and eventually … your course is finished! Testing begins and you’re feeling pretty good about things. Then you notice that your email box is filling up with comments from testers and a feeling of dread starts to set in. What has gone wrong?
Same story as above only this time your course is finished. It passed all of the internal evaluations and students have begun taking the course. The phone is ringing off the hook, your team is being blasted with emails, and your boss is becoming visibly upset. What’s going on?
In both situations people are complaining they can’t complete the interactions because the exercises deal with content that wasn’t addressed in the lessons. How can this have happened? Your objectives were approved and the content should’ve addressed the objectives. Your exercises were designed to measure the objectives. Why is this happening?
Sound familiar? If not, consider yourself lucky. So what is the source? Typically it’s one or more of the following issues:
Your objectives were written and finalized early on in the process. Somewhere along the way content changed and no one evaluated the objectives again to determine if they were still applicable. This tends to happen more often when someone else, perhaps a subject-matter expert (SME), writes the content and you and your team are developing the course based on the material you’re provided.
Remember, you’re objectives define what you want the student to be able to achieve at the end of the learning segment. They tie directly to your content. You need to ensure the content you’re including actually supports those objectives. If they don’t tie together, you must do one of two things: revise the content or revise the objective. Keep in mind that changing one or more objectives may affect a higher level objective so use caution. Because of this, it is recommended that you revise the content. Do yourself a favor … take the time to review the content and ensure it addresses what it’s supposed to address. Taking a little extra time upfront will save you a ton of time in the end.
Another situation might involve exercises that are too difficult because there wasn’t enough supporting information, discovery, or both provided in the lesson. Maybe the exercise is dealing with something that hasn’t even been covered in the material. Your development team and SMEs are quite possibly too close to the material and may not be able to recognize there is an issue with an interaction(s).
If more than one person is having difficulty, then you need to take a look at the content that you’re covering in an exercise and decide if you need to beef up your content, redesign the interaction, or even add a method for users to review the related content if they’re struggling. First and foremost, make sure what you’re testing students on was literally addressed in the content. You should also review the exercise to determine if the instructions are clear. Ensure your interaction works as it was designed. So many little things can cause big-time problems for users which will eventually cause even bigger issues for you.
So what’s the real message you should take away from this blog? Pay attention. Pay attention to your objectives all the way through a project. Pay attention to testers and students who voice complaints and concerns. Pay attention to the details. Not only will it make your life easier, it will help you ensure students are actually learning what you need them to learn from your course.