Forum Discussion
Remediation for Assessment
I would like to connect them with the outside resources that exist in our LMS/help site that match up with what they missed. Ideally, after they complete the assessment, they would go to a screen where it would show the competencies they missed and then link them to the specific pieces of content to review then come back and retake the assessment. The content they would need to review would not be part of this course but be in other forms of content, so it wouldn't be sending them back to the section but other resources. So, very similar to the pulmonary/cardiology example but for other content to review.
As long as the links aren't dynamically generated, connecting people to that content should be easy. We use Workday for instance, and it's very easy to directly link learners to other content elsewhere in Workday's LMS.
I think the easiest way is going to be the cardio/pulmo method, one slide per competency so you can funnel people to the content they specifically need. An advantage of that is reduced seat time since no one can choose to pursue content they don't need to review, which is a potential downside to the second method below.
The second is to put all of the competencies on one slide like Judy offered. Showing only the content people should review though might be more complex due to how the buttons and text boxes are actually shown on the slide, especially as the number of competencies grows. It's trivial to hide an outbound button by default and only show it if the learner scores below a threshold, but if they pass, that hidden button's going to leave a blank space on the screen like she said. If you design a slide for eight competencies but only show three, the learner may attribute the empty space to bad design rather than an indication of their successes.
That can look weird depending on the configuration, so if you see benefit to having all of the recommended ones on one slide, I personally would put them all on one slide and then visually design it to recommend the ones they should/must take:
My example still allows people to review the passed competencies (in case they feel they got lucky or may want to explore it anyways) but buttons have Disabled and Hidden states that you can use on passed competencies to just outright prevent click-through.
I agree with you and think having them all in one slide would be the best option since they may miss more than one competency. Thank you for visually showing me this option. What elements did you use in this to show the percentages in each competency with the review button? Do you have any storyline files you can share?
I did retain the .story file, yes! It was just pure visuals when I made it, but I've gone ahead and added some triggers to demonstrate how the images and buttons might change states. I didn't create any logic for the third competency since I think the first two show the breadth. Let me know if you have any questions about it.
At a high level, the design schema assumes each question slide has feedback layers. The feedback layer that shows when the learner gets the question right are perfect for a trigger that increases a number variable by 1, so if each feedback layer increments whichever variable corresponds to the competency of that slide, the effect is to count how many of that competency's questions are answered correctly.
In the attached example, I gave the variables comp1Total and comp2Total default values to work with for when the slide is previewed, but in practice those would start at zero and increment as the learner correctly answers questions in the quiz.
An easier version of this slide would be to avoid percentages entirely, but I like them more than showing questions correct as fractions (e.g., 3/5) so I added native triggers that derive a percentage from comp1Total:
5 in this case would be the number of questions, which returns a decimal less than one, so it's then multiplied by 100 to turn it into a percent. The result is shown on the screen using a reference to the variable: %competency1Score% followed by an extra %.
Since triggers can accumulate quickly, I used a JavaScript trigger to show how the second competency's score can be calculated. I'm not sure if you've ever used the getVar() and setVar() functions to access Storyline's variables, but hopefully that trigger shows JavaScript doesn't need to be convoluted. In theory, the scores for every competency can be calculated with a single JavaScript trigger, greatly simplifying your project.
One last design note: I setup the buttons to leverage the built-in Disabled state. That state prevents someone from clicking on it. Since it's only shown when we don't want the learner to open the link, I removed the border from the button so that it stops looking like a button. In preview, the learner just sees the words "Well done!" and the illusion is that the button has been replaced by text. In reality of course, the button's still there. It's just styled to not look like a button.
I can't thank you enough! This is beyond helpful