<aside> 👋
This, and all of the blogs, give an overview of the process and steps taken for each part. I’ve included images taken from the Figma File where the majority of the work lives to illustrate the process.
If you would still like to see further details on each part, please view the Figma File in full.
It can be found at the end of this page, or on this master page.
</aside>
With V3 concluded, I wanted to take the opportunity to conduct another round of user testing. This would help me identify the strengths and weaknesses of my product and implement changes.
I started by planning the tasks and hypothesises for testing with. Similar to last time, I focussed on the key flows, making sure to ask users questions in a in direct manner as to now overly guide them.
<aside>
Users will find the onboarding process natural and intuitive. The ordering of steps will make sense and the habits section will be understandable.
You’ve recently learnt about a new public transport app called “Metronet”. Now that you’ve downloaded it, you want to create an account to use the app.
</aside>
<aside>
The primary functions of metronet will be intuitive and easily understood by new users.
Take some time to take in the home screen for metronet.
</aside>
<aside>
Users will understand the difference between “Go Somewhere Now” and “Plan for Later”. Users will be provided with sufficient information when choosing a route. Selecting and configuring tickets for complex routes with multiple passengers will be intuitive.
You are planning an upcoming trip to Sligo for you and another and need to book train tickets for it.
How would you do so?
</aside>
<aside>
Users will be able to quickly find a route for in the moment transport. Users will naturally find ways to filter and set preferences for routes. Users will find the route tracking and in the moment guidance useful.
You’re about to travel to university and want to get there with public transport, however you don’t want to use trains.
How would you us metronet to find and follow a route.
</aside>
<aside>
Users will be able to find journey details through either path. Users will understand the separation of “tickets and passes” and “upcoming journeys” as distinct types of information.
You’ve recently booked tickets for an upcoming trip to Dublin and want to check the journey details.
How would you do this?
</aside>
<aside>
Users will be able to find network details easily and understand the USP of the product.
You’ve recently had a bad experience with one of your local transport network and want to remove it from your networks.
How would you do this?
</aside>
I also prepared a test script, based of a template I had received. The template version was very precise with the exact language of the script, whereas I prefer to just have bullet points so I talk more naturally, so I edited the script into this fashion.
<aside>
</aside>
<aside>
Test Script – Edited for Testing
</aside>
I linked together a simple prototype similar to the last round of testing, using break screens to indicate the start and end of tasks.