We started today’s class, giving a refresher and explanation of exactly what usability means, what is considered in usability, and what affects it. In short to me, usability can be seen as ‘Does it work’, ‘How well does it work’, and the lecturer topped it off with ‘Does it do what users need?’
To me, I feel like the best way usability was described in today’s class, is that products should be designed in a way that doesn’t require the user to struggle or ask for help. It should be considered as an easy flow from one point to another without having to struggle.
Another area that was covered within today’s class, was covering the importance and the how of user testing, who to test, how many and what way I should go about. I found it pretty helpful to see what exactly i should layout when getting a person to test one of my own designs/ products. For example, I would be able to just toss them straight into a product and monitor what they do first, as well as following this up by providing them with a task, without any help. Such as getting them to make a bank transfer, within a banking app.
It was also pretty good to hear what would be suggested as to how I should record a usability test, which would consist of a Screen recorder, and audio. I don’t need to show the face of the user, meaning I can keep them anonymous for their own comfort. Applications like quicktime, would be perfect for screen recording.
Participant
The person using the digital product
Facilitator
The manager, providing context to the participant on what to do as well as taking notes on what issues may appear to the participant
Observer
Not always required but good to have, extra input when recording notes