Paul, that is the system we use. We have to manually average the rating for each question to truly see how a course is rated. It is time consuming and a waste of time when comparing to course evaluations which provides great reporting tools.
I love this idea. The star rating is just ok in my head. It's subjective. My 3 star could look different from someone else's 3 star but having multiple choice would allow us to understand what they liked and didn't like about that course so we can make the appropriate changes.
We would really like to see this implemented as well. Our team is considering using google forms for course evaluations because of the lack of options with the built-in evaluations.. This would be a huge waste of the great in app reporting tool and the Absorb Analyze dashboard for course evaluations.
The solution of adding an assessment or survey without the ability to make it optional not only means that we need to add an assessment to every course (an unnecessary lesson and more work for admins), but also that users are forced to fill out a survey/assessment to complete the course. If the google form link is placed in the resources section, the user may never find it.
We really do like the course evaluation form and all of the functionality and reporting that comes with it, but our design team would really like to see more options as it would really help to add value to the responses we collect. Simple multiple choice and multi select options would be wonderful.
This is a good idea, but with 2022 quite full we likely won't get to this unless demand escalates. In the meantime some clients achieve this by including a mandatory Assessment as the final learning object in their Course (or Curriculum if the desire is to evaluate an ILC in this manner), which unlocks all question types as options. The responses don't get summarized in the same way, but have the advantage of all appearing on the same report for direct comparison. Does that help meet your objectives Rhea? Please feel free to provide more context here!
Paul, that is the system we use. We have to manually average the rating for each question to truly see how a course is rated. It is time consuming and a waste of time when comparing to course evaluations which provides great reporting tools.
I love this idea. The star rating is just ok in my head. It's subjective. My 3 star could look different from someone else's 3 star but having multiple choice would allow us to understand what they liked and didn't like about that course so we can make the appropriate changes.
We would really like to see this implemented as well. Our team is considering using google forms for course evaluations because of the lack of options with the built-in evaluations.. This would be a huge waste of the great in app reporting tool and the Absorb Analyze dashboard for course evaluations.
The solution of adding an assessment or survey without the ability to make it optional not only means that we need to add an assessment to every course (an unnecessary lesson and more work for admins), but also that users are forced to fill out a survey/assessment to complete the course. If the google form link is placed in the resources section, the user may never find it.
We really do like the course evaluation form and all of the functionality and reporting that comes with it, but our design team would really like to see more options as it would really help to add value to the responses we collect. Simple multiple choice and multi select options would be wonderful.
This is a good idea, but with 2022 quite full we likely won't get to this unless demand escalates. In the meantime some clients achieve this by including a mandatory Assessment as the final learning object in their Course (or Curriculum if the desire is to evaluate an ILC in this manner), which unlocks all question types as options. The responses don't get summarized in the same way, but have the advantage of all appearing on the same report for direct comparison. Does that help meet your objectives Rhea? Please feel free to provide more context here!