This is a very fair criticism, and I think you are right that I was mixing up two different things.
The public testimonials are mainly there for prospective participants. They are not meant to be a rigorous measure of learning outcomes. For some people, it is useful to see that somebody they know, or an institute they trust, attended one of our courses. But that does not tell us in a systematic way whether participants actually improved their skills.
For improving the courses, anonymous and structured feedback is much more important. I really like the idea of separating this more clearly: a short pre-course survey to understand prior experience and expectations, a post-course survey to measure perceived changes in confidence and skills, and maybe even a follow-up after some months to see what participants actually used in their work.
I also agree that recommendation scores could be useful, although I would probably see them as one indicator among several, rather than the whole picture.
So yes, I think your point is very helpful: public feedback can be useful for transparency, but it should not be confused with a proper evaluation of learning outcomes. I will have a closer look at how Software Carpentry does this.
Thanks a lot for taking the time to write such a detailed answer.
Not my particular area, but do you really need to make all the reviews visible individually? You could solve your problem by aggregating feedback and determining the signal from the noise of real consistent themes and offer summaries you've synthesised of what you're hearing?
That is a really good point, thanks.
The reason we currently show individual feedback is mainly that we do not want to selectively interpret it ourselves. People can see the original wording and decide what they find relevant.
There is also a practical reason: a few times, people told us they noticed a review from someone they know personally or from an institute they trust, and that was what first made them look more closely at our courses.
But I agree that an aggregated summary of recurring themes could be much more useful, especially for people who do not want to read many individual reviews. For example: what participants consistently found helpful, where they struggled, and what we changed based on their feedback.
Maybe the best approach is both: keep the original feedback visible for transparency, but also add a short summary of the main patterns. That would probably make it easier to understand the overall picture.
Thanks, this gives us something useful to think about.