In this 9 day sprint I worked along side 3 other UX designers and focused the interface design on iOS. We implemented a daily scrum – strictly time-boxed to 15 minutes. We stood up every morning to recap what we did the day before, what we were doing that day, and what impediments were in our way and how we might overcome them.
To help organise our tasks and responsibilities we used Trello, which is a collaborative work management tool. It shows you what’s being worked on, who’s working on what and where something is in process.
- Better support multi-modal travel with particular emphasis on travel planning and avoiding delays
- Promote a shift to walking and cycling whilst integrating data and features from Melbourne Bike Share
- Better promote ticketing information and purchase
- Competitor/ business analysis findings
- User research findings as personas, customer journey maps and supporting narrative
- Commentary and supporting documentation of ideation and iterative design process with evidence of Sketches & proof of ideation process, design iterations, user flows, site-map
- Project presentation for a business audience
- Interactive digital prototype
We first started off researching what methods of transport people used and the different ways people navigate cities. We curated a 10 question google survey which was predominantly context specific to find out more about the user. This was then followed by a PTV App specific survey that helped us establish what the main pain points were and what needed to be implemented.
We received 130 responses to our surveys and collated some extremely insightful data from this. Below is some of our key findings.
- Safer routes would motivate users to cycle more
- Users would opt for a healthier route (walking or cycling) if they knew the weather forecast
- The app was extremely content heavy and seemed chaotic to use
- You couldn’t search for landmarks which was a huge-pain point
- The disruptions page didn’t give alternative routes when your journey was affected
We split our competitor analysis into two parts; Indirect competitors, which included Google Maps, Citymapper & TripGo and some direct competitors; NYC Subway, Opal Travel & BvG
- Do offer routes for walking & cycling
- Allows the user to plan journeys
- Offers a real time map feature
- Language is personable (eg. ‘Where do you want to go?’)
- Don’t offer routes for walking & cycling
- Allows the user to plan journeys
- Offer map features of varying functionality
- Language is direct (eg. ‘Select destination’)
Design Studio Method
After we digested our research, we began our Design Studio which is a Lean UX method. This helped us come up with ideas to solve our problem statement:
“How might we make it easier for people to travel”
Here’s how we practiced Design Studio in our project:
- Problem Definition – we created a persona and scenario in which they had to perform a task within the PTV app
- Diverge – we split up and rapidly generated as many design solutions as possible in the time allocated, allowing 3 minutes to present our ideas to the rest of our team & give feedback
- Iterate – after receiving feedback we split once more to iterate on our designs and come back to present our new wireframes/ UI designs
- Converge – after discussing all of our ideas, we collectively decided on choosing one idea and implement that to our ideation
By providing an app which informs people of healthier alternative routes, offers information about safety, weather issues and disruptions, we will make it easier for users to plan a journey and encourage more active travel choices.
Iterations & Paper Prototypes
After our Design Studio we began to sketch up our paper prototypes and started our first round of user testing, implementing changes after each round. Here’s some of the key findings from our prototypes:
- The weather function was in the way and not relevant within the IA in that section
- Users just wanted to see the fastest route
- Users wanted to be able to see the travel options available
When iterating from our original designs, we implemented the Agile framework of responding to change over following a plan. This worked well, as we tested fast and often and came to our high-fidelity clickable prototype which once tested was a huge success.
Check out the clickable prototype here!
We received some constructive feedback from our prototype and if we were to iterate the app further, these are the area’s we would like to focus on:
- Health integration, achievements, disruptions and reminders
- More on disruptions
- Push Notifications