Impossible Task? Deriving a 1 through 5 rating from 3 numbers
May 21, 2015
Here's my issue... I have a three column table with 6 performance statements in each column. The rater must choose from each column those performance statements that apply. After making the choices they need to decide on an overall performance rating of 1 (Needs Development) through 5 (Exceeds Expectations).
For Example: Rater has chosen 2 from Needs Development, 3 from Meets Expectations, and 1 from Exceeds Expectations. So the column values are 2, 3, and 1, which would probably receive an overall rating of 3. A 3, 3, 0 would receive an overall 2, etc.
I have been trying to figure to the easiest way to implement this and I am coming up blank. Averaging and Median don't work.
Has anyone done this in Storyline 2? Any suggestions about how to implement it?
15 Replies
Hi Matthew. This is easy to do in Storyline. Just attach your calculations to a button. I have attached an example you can use.
I noticed after some testing that the variables do not reset when you enter new values into the numeric entry boxes. To fix this, just add another button called "Reset" or whatever, and attach four triggers to that button to reset the four variables when clicked. This allows a user to sit and play on the slide virtually forever without messing up the calculations.
Thanks for the quick response, however averaging doesn't work right in this situation. For example, if the rater chose none in column 1, 3 in column 2, and 3 in column 3, the average would of 0+3+3=6 6/3=2, but in actuality on the rating scale of 1 to 5, the choices would merit a 4, since a 2 is a balance between Needs Development and Meets Expectations, and a 4 is a balance between Meets Expectations and Exceeds Expectations.
Right. This means the equation is different than in the example I gave you. What you can do is adjust the final equation when clicking the button.
So for example, what I did was divide the total of the three numeric entries by 3 to get the final answer. What you need to do is adjust that equation to fit your needs. So this could be for example, divide by 3 and add 1, or something similar.
Here's a sample page that calculates how many behaviors are selected in each column. I have removed any decision making actions until I can figure out the coding. This is in Storyline 2.
I love the look and feel of this slide. This is a complex activity, and I do not understand how you want the final results calculated. You said that in one instance, a 2 average would actually be a 4. Until I understand that concept, it would be difficult for me to help you with that, but I think if you adjust the final calculations using the methodology I showed you, i.e. attaching the calculations to a button rather than a rolling total, that it should "fix" the issue I see on that slide.
My comment is that the 6 evaluates to a 2, in the form, all choices are in the Meets or Exceeds column, therefor the rating at the bottom would be somewhere between a 3 and a 5. For the 0, 3, 3 scenario, averaging the columns results in a 2 which is too low an overall rating. I am considering a different method to weight the choices. I'll post the results here if it's successful.
Hey Matthew -
Here's a simple, unfinished example. I use "function objects" that are hidden by default, shown, then hidden again to prime for another execution whenever I count stuff up on the stage. Take a look at the attached.
In my example, I added buttons to sets to prevent selecting multiple characteristics in the same thread. I think the last row represents what you've got going on but I'm not sure. The top 4 rows are pretty parallel. The last few seem to unravel a bit.
It adds up each column. Items in the first column are worth 1. Second worth 2. Third worth three. Using this setup, you can add up the values and use a simple threshold on the average. So dividing the sum by 5 (total columns in my example) the final score would be 1 if all of the buttons in the first column are selected. If all of the buttons in the right column are selected it will be 3. You could then map that value to a conditional range and assign a whole number value to the evaluation item score. By ordering your triggers, you can build a quasi "if, then" setup.
Assuming 5 rows (my example, yours has 6), each 0.6 along the scale will be equal to a whole evaluation value.
The triggers for that would be something like this:
Executing these triggers in order, it'll set the eval score progressively lower until it reaches the lowest average score. You can do something similar with your 6 row output. Circling back around, this allows you to have a single object to execute calculation triggers and have this update whenever an item is selected or changed.
That... Is... Awesome! I knew Storyline could do it, but that Matthew's challenge was more complex than simple averaging. Articulate should do a challenge week on this type of thing. Seriously!
This thread made my head hurt...but glad that you got the help you needed here Matthew! :-)
It's not done yet! I need to tweak the algorithms to get consistent results. More on this later.
Here's the Beta version of the page. I still need to add a performance narrative for the learner to work from and an instructions tab so the learner knows what to do. Basic instructions are to select an appropriate level for each behavior listed. The levels are Needs Development, Meets Expectations, and Exceeds Expectations.
I used Steve Flowers suggestion of using a hidden function object and set up numeric ranges to round the rating correctly. I weighted the responses in each column, added all the columns, then divided by 7. This took a little experimentation to get all the right weights and divisor, but it worked out in the end.
Thank you everybody for the comments and suggestions!
Thanks for sharing Matthew :) Great to see the community work together and pay it forward.
This is my first large e-learning project using Storyline. After countless months of evangelizing for Storyline, we finally received the software. We now have one of the big industry standards tools in our toolbox. Previously we were provided another (unnamed) development tool. While it is a very capable program, it does have some critical limitations dealing with anything Action Script 3 related, as well as not being widely used.
I am very happy with the speed and quality of support these forums and blogs provide. I have also been busy submitting feature requests for future versions.
Thanks Matthew! Way to jump in and contribute.
This discussion is closed. You can start a new discussion or contact Articulate Support.