...
If we were to do this project again, we would like to conduct earlier computer prototype user testing, especially with the uploading interface. During GR6 user testing we discovered that there are were minor deficiencies in the current interface that only music directors could spot. Our This is partly because fellow classmates were are not well acquainted familiar with the WMBR workflow, and failed to identify some areas of improvement (such as the FCC obscene word marking featureneeds of WMBR music directors (such as marking tracks as containing obscene words with the FCC flag). Furthermore, we should could have , as a team, prioritized our tasks better and made more conscious decisions regarding the design. This would have allowed us to address the most important issues first (uploading, editing), and focus our efforts on components that are central to the purpose of done better task prioritization, focusing on key components of the system earlier (uploading files and editing details) as they are central to the KaJaM! application.
Finally, we discovered that user testing can be very challenging because users often feel pressured pressure to "do the right thing", rather than identifying identify usability issues. There were several instances where the user would become withdrawn, uncommunicative, and frustrated that he or she could not complete the scenario tasksusers became less communicative as they became frustrated with completing a scenario task. It was an important cue for us to be patient and re-assuring them that the problems lie in our design, and not their competence. We learned to accept criticism objectively and recognize that "the user is always right".
...