The second Usability Test raised many issues and suggestions for feature changes; admittedly, these made me feel quite overwhelmed. I appreciate that feedback is invaluable and leads to improving iterations of prototypes, however this feedback needs to be prioritised or categorised in some way in order for me to process it.
I’ve reflected upon my first module on the MA programme, when I discovered the Design Hierarchy of Need. I could categorise the feedback I received from each Usability Test into the five categories: functionality, reliability, usability, proficiency, and creativity. Then, I will prioritise resolving issues based upon which category they call into, starting at functionality, moving towards creativity. This article in Smashing Magazine was helpful, providing defining criteria for each category: More Info: https://www.smashingmagazine.com/2010/04/designing-for-a-hierarchy-of-needs/
Above, you can see that feedback concerning “[the] ability for users to reset their login details/password” is high priority, falling into the functionality category. Many suggestions have also fallen into the usability category, which I may be able to focus on in my next iteration of a paper prototype. However, I am acutely aware that I must move on to producing a medium-fidelity prototype very soon in order to keep to my time planning.