...Check Your Knowledge

From Wikiversity

Back to Topic: Instructional Design > User Testing of E-Learning Courses > Analyzing the Results

[edit] Knowledge Check 1

Read the user testing data and then indicate whether it is quantitative or qualitative by selecting the appropriate radio button. When you are finished making your selection, click the "Submit" button.

1. 2. 3. 4. 5. 6.

[edit] Knowledge Check 2

Read the user testing data and then indicate whether its severity by selecting the appropriate radio button. When you are finished making your selection, click the "Submit" button.

1.

2. Is this an error? Shouldn't you select the “US HUMERUS” to navigate to the Additional Details page instead of the "Procedures" header?

Answer = Major

Feedback = Because this tester is an actual user of the system in the field, he has caught an error in the content. You never want to convey wrong information to the learner, so this is something that should definately be fixed during final revisions to the course.

3. I personally feel that this lesson needs to be divided in two. Provider Access and then the separate one call Beneficiary Resources. You could actually tailor beneficiary resources directly to patients. This could be put on Kiosks at MTF, send out CD’s with the lesson.

Answer = Minor

Feedback = Remember that by the time a course gets to the user testing phase, it is at the end of the development cycle. In most cases, returning to the storyboard phase to rechunk a lesson's content will be out of scope. In addition, the suggestion to provide the information on Kiosks/CDs is also out of scope in this case. This type of action would have needed to be indicated during front-end analysis during requirements gathering. These are both great suggestions and should be documented for future revisions to the e-learning course.

4. This does an excellent job of explaining the different roles. I wasn’t clear on my role until now. Didn’t know we could modify the webpage for the MTF - good info. This may be the best WBT I have ever used. It shows you what you need to know with out a lot of unnecessary information.

Answer = N/A; comment only

Feedback = Comments like this one require no action on your part. However, they should remain a part of your formal user testing documentation. They also provide you and your team-members a great pat on the back for a well-designed course.

5. 6. 7. 8. 9. 10.

[edit] Knowledge Check 3

...this is the kcheck that will use the user testing results that the learner generated by doing the kcheck in the previous lesson (need Christine's information to create)...