...
- Error Text - Minor - As noted by the TA, error text was far from the fields that had the error. This was not mentioned in the user testing because the screen that we used for user testing happened to be larger than the one used for GR5 demoing. Thus, it was clear to users when the text appeared that it had appeared.
- User did not know if they had a QR code scanner - Roadblock - We could ask poster makers to insert instructions on how to download a QR scanner. We could ask poster makers to also provide a text URL for them to enter.
- Color took a while to change - Minor - We could indicate that the page was processing while the new QR code was loading.
- Didn't hit set size - Minor - The user typed in a size, but did not hit "Set size". We could automatically set the size when the box loses focus.
- The user did not download the QR code. - Major - The user did not see the message to download the code. This may have been because we did not fully explain that the purpose was to create a code, download it, and make a poster. In future tests we could ask users to make an event poster.
- The user did not want to give their email - Minor - We could add a message saying their email will only be used once.
- Network slow - Out of Scope - The user was confused when the internet network was slow; little you can do about this.
- User surprised could see other RSVPs - Out of Scope - Security was not a requirement for this project.
Reflection
- The main thing that we learned over the course of the semester is that we are not our user. That is, even if we think something is simple, obvious, or clear, this does not mean that the user will feel the same way. We have a lot of preconceived notions about what things should do because we actually created them, the users of our system will not be in that position and are thus much more likely to be confused.
...