What we did
We explored how we could ask users how useful a resource is. We also asked users in testing whether this would influence them when assessing how useful a resource is for their school.
We explored how we could ask users to rate resources through the following designs:
What we found
In testing, user's weren't too interested in coming back to the service after using individual resources, to review them. They were also not interested in how other people rated each resource when deciding whether a resource is useful for them. This is because every school is different and has varied needs in tackling workload, so a resource may be helpful for particular schools.
We need to keep the codebase of our service as simple as possible, so that adding future resources to the service is easy and simple for non-developers. However, we discovered that implementing this kind of functionality is too complicated and was less feasible than we originally expected.
What we decided
As a result of our exploration and user testing, we believe there is no strong need to ask users how helpful each individual resource is to them, due to every school setting being different and it being technically complicated to build.
Asking users to give feedback on the service and share any ideas of what has worked in their school through feedback forms, is enough to help us improve our service and potentially add more helpful material in the future.