Log
- Introduction given before recording started. Usability Tester and I had collaborated before, so they already knew the parameters of the test and that I would encourage them to speak their thoughts aloud
- Briefing read to Usability Tester prior to test starting
- 1:49 – Assumption explained that user has already input their details into the “Email Address” and “Password” fields
- 2:02 – Thought: Usability Tester seemed confused about the “Submit” button, perhaps this should read “Log in” to explain what the button would do
- 2:02 – Title of page reads “Login”… Perhaps this should be changed to “Log in”
- 2:18 – Limitation of the prototype explained again for the Usability Tester – Keynote does not understand swipe gestures, so the user can only tap
- 2:35 – Usability tester understood onboarding process – “that all seems fine”
- 2:49 – Usability Tester has started a test despite the briefing which asked them to check rules on cabling. Why? Is this because the revision element is not clear and is hidden behind a menu that is not visible on screen? Is this a limitation of the hamburger menu style? (Note: I could not include a hamburger menu icon itself in this prototype, so have just put the word “Menu” for now)
- 3:03 – Trailing cable information is learned from the testing process. This is good, but not how I imagined the user to learn this information
- 3:25 – Briefing repeated for the Usability Tester
- 3:50 – At this point, having realised a design error resulting in the Usability Tester completing a test rather than revising information, I prompt the Usability Tester to look elsewhere for the information (and hopefully remind them to keep the phone “dark”). I found this process quite difficult, as it was hard to ascertain whether my instructions were causing confusion, or whether the app’s design was, all the while I was trying not to push the Usability Tester into producing any particular outcome
- 4:18 – Usability Tester asks whether there is a Dark Mode within the app. This is an interesting point… Should I respond to functionality questions like this, or should the Usability Tester just be told to look for themselves?
- 4:32 – Dark mode found successfully
- 4:50 – Usability Tester is still trying to gain information from tests, rather than looking it up in the TV Studio Rules area. This is definitely a design flaw. This functionality must be made more obvious and not buried within a menu. Thought: Would “TV Studio Rules” even be the correct name for this??
- 5:46 – Asked for thoughts, Usability Tester highlights that the app’s main screen, the “Start a Test” screen gave her the assumption that that was the way to find information. It was only when they entered the menu that they “realised” how to find the information
Summary
- Usability Tester’s response to the onboarding screens are exactly as desired
- I need to practice carrying out Usability Tests more. I was suffering from brain fog a lot at the time of the test, hence the “Ums” (and other utterances) and gaps in my speech. Despite this, I need to be more prepared for when the Usability Tester asks me questions – rather than giving them the answers, I need to try to direct them into finding the answers within the app itself
- Hamburger menu structure may be stifling the user’s ability to navigate the app, and this should be researched more. Tab Bar may be the solution
- Some potential name changes in copy may also aid navigation (see below)
Actions
- Change “Login” page name to “Log In”
- Change “Submit” button on “Login” page to “Log in” to describe the action of the button
- Thought: The page name “Start a Test” is almost telling the user what to do when they enter the app, when really it is optional. The tests are visible for convenience, but there are other activities in the app that the user may need. Perhaps the page’s name should be changed to “Available Tests”?
- Experiment with adding a “Tab Bar” for navigation, allowing users to notice and access revision information and settings more easily, rather than being hidden offscreen in a menu
- Reconsider the page name “TV Studio Rules” to describe the pages purpose instead… Perhaps “Revise” or “Revision”