All Work

Guideo

Problem

During my 5 weeks at Brainstation, our class was given the assignment to create a transit app. It was left up to us to find a transit problem, and solve it with the skills and digital tools learned in class. For this project we used the human centered design approach which included identifying problems in current user experiences by user interviews and testing our solutions by having users navigate rough sketches (using the Marvel app) and low fidelity wireframes (using Moqups).

The homepage of the wireframe. After testing, I found out it was best to stick to an interface like Google Maps, due to relatability.
This wireframe showcases the swapping from catching a bus to just walking, as the bus has been delayed.

Research

The first step in the process was identifying the problem! I interviewed four people using the following set of questions:

  1. Describe the last time you walked somewhere.
  2. What apps do you use to navigate?
  3. What makes you choose walking over public transit?
  4. What would you like to change about the process of navigating somewhere?
  5. What information do you wish was readily available?

After conducting the interviews, I identified some common issues:

  1. Transfers were a hassle due to delays and misinformation.
  2. Navigation apps only provided fixed routes. Users couldn’t customize routes, like walking partway instead of using a streetcar.
  3. Detailed information, such as "Presto only" routes or pricing, wasn't easy to find.
  4. Uber was expensive, and Uber Pool didn’t prioritize timely arrivals.

Interestingly, none of my interviewees minded walking 20 minutes if it meant avoiding another streetcar or bus.

Information Architecture & Personas


I designed an information architecture focused on making commute routes fully adaptable.
Persona #1 - based around a young professional commuting to Toronto from a suburban area.
Persona #2 - based on a middle aged person travelling within their own area.

User Flows & Sketches

Waze and Google Maps were the main user interface inspiration. All of the users I interviewed were very familiar with them, and I wanted to use conventional, industry standard guidelines. Every second counts when trying to get somewhere, so recognition is key.

Original sketch for user flow 1.

Original First User Flow & Sketch - Use bussing to get to work

During sketch mock-up testing, I discovered that my initial hypothesis—that users would prefer choosing how to travel over where to go, was confusing. Test users expected a map and destination selection, and the approach lacked purpose, as people typically decide how to travel only after knowing the destination.


Some other interesting observations were that the "Go" button was confused with the Go Transit and users instinctively looked at the top of the screen to enter information. I created two new user flows that reflected map and location first user flows, and during testing these seemed better received.

Version 2 First User Flow Sketch - Walk due to delays

This new first flow is about a user is trying to find their way to work, and a delay comes up. They are be prompted to reroute and they follow the route. The revamped sketch included a full screen map, with a textbox at the top to type in the location.

New sketch for user flow 1. The difference is the map focused UI on the first screen.
This first user flow is based around changing routes mid navigation.

Second User Flow - Navigate to David's Tea

The second one is a user who wants to walk halfway instead of using public transit all the way. It's a spiritual successor to the original first sketch, in that it helps the user plan their route better.

Sketch of user flow 2 - similar to the original first flow, however it's map based.
User flow 2 - walking instead of a transfer.

Wireframe

The full wireframe has 2 interactive user flows.

First User Flow - Walk due to delays

If you click on the Work button, you will follow the User Navigates to Work flow. This one demos how the app handles delays and re-routes.
Second User Flow - Navigate to David's Tea

The User Navigates to David's Tea task flow can be started by clicking in the second textbox at the top, next to the location marker. This flow showcases how to modify routes.

Presentation


Project Deliverables

All of the following deliverables can be found in the presentation above.

  • 4 User Interviews
  • Information Architecture
  • 2 Personas
  • 2 User Flows & Sets of Sketches
  • Wireframe

The differentiating factors of Guideo were three things:

  1. A faster way to identify alternative routes, and modify specific parts of a route with walking.
  2. Pricing information is readily available, and it notifies if a route is presto only.
  3. It will notify and provide alternative walking routes when there is a delay.

Results

I came away from the course with a greater understand of how to produce a better user experience. I learned how to throw away my ego when being critiqued. How to stay silent and provide not provide answers during user testing. When and how to prod for knowledge the interviewee thought was common sense.

Industry professionals Gerard Dolan and David Aboutboul taught our class invaluable life and career lessons. I hope to carry a design thinking approach to everything that I do henceforth.