UX Design — Fundamentals of UX (part 4)
User Testing
We shared the example prototype with the rest of the team and we decided to do dry run with one of the testers. With there concent, we recoded her taking on the app with a brief introduction statement:
Image you have 3 children (Billy Hanly, James Makoi & Silvia Patron) the first being in primary school and the last two are secondary school. You are very busy and would like to book transport for you children so they can be picked up and dropped of at the school safe and soundly.
We have created an app and would like for you to test the functionality and clarity of using the app.
Test #1
From this test, we saw clearly some issues, main one was unfamiliarity with the tool e.g when the user thought they needed to type instead of just click.
One of the other confusions was when we where selecting the school, the default behaviour was to click on the next tab before clicking next.
We made a small change to the prototype to reflect this change.
Test #2
On Test two, the user was more familiar with the system and was able to navigate it much better.
The user upon completing the second test reported that the process made sence and was quite quick, they did point out on the confirmation screen that they could not remember what address they entered.
Test #3
The second test was performed by another test candiate the results where quite suprising, we received this feedback from them
Feedback provided after the test:
1. Initial screen — Expected register instead of get started.
2. Back button was too far away — wanted to go back to see if she could change any of the children’s details, also wanted to check the address was correct here but it was missing
3. Selecting the school — tabs confused here — they nearly got in the way — the changing title on the tabs were confusing. She wasn’t sure why only three schools were shown.
4. Payment screen — cost confused here.
5. Likes dob rather than age on the Childrens details
I was also very interested in how she thought she could select her location by dragging the map around.
This was really good feedback that we could address but we wanted to do another test to see are these finding personal or will our other tester find the same issues.
Test #4
Test 4 found similar issues with selecting children and school. The tab system for selecting change we did based on feedback from test 2 might of been a premature change, and could of effected the next set of tests.
This tester however did not have any other issues with location, registration or payments.
Future Changes:
I just want to say that the feedback we got is fantastic. Given more time we could iron out some of these small issues we faced with the user and test again.
We also used a software called XD for this design, where users can critique the design and see this in the software to make changes. Its sort of like a todo list for when redoing the design.
Check out the full list of comments and changes.
Conclusion
The final prototype is good but not there yet, we need more time to iron out the UI and how people interest with it. We only looked at a small portion of the app and have not covered all cases. It would be nice to look deeper and test more.
