Schedules & Maps

UX DESIGN / UI DESIGN

Goal: Help new and existing users to intuitively identify the corresponding routes and mode options based on where they want to go, and what time they want to ride on CapMetro's service. Help the user to quickly filtered through all the various route schedules available on CapMetro services.

Building a better experience for users to find schedules

The Brief – reimagined the current Schedules and Maps web tool

Deliverables — Design an interactive high-fidelity prototype and develop a functioning tool with the following features:

  • Multi service modal tool with a particular emphasis on travel schedule planning
  • Promote a shift to mobile device/phone usage
  • Better promote fares information and purchase options

My role
Sole UX/UI Designer

In colaboration with:
UX Copywriter: internal team member
Recruitment and user session moderation:
External vendor talent

Duration
12 weeks

Tools
Figma, Teams, Photoshop, Illustrator, Camtasia, Paper & Pencil

Final Deliverable – See Live Solution

UX Design Process

With a focus on new insights gained from qualitative usability reaseach/testing - I went about reimagining the UI for this project: Planning (Analyzing and Evaluating)


Empathize

After defining a scope based on the scenarios drawn from new and existing users, the next step in the process was creating user stories and a persona to better empathize with the user’s needs and goals.

As a new user, I want to:

  • learn about different schedules, so that I can figure out what is best for me.
  • be shown where the different stops are located, so that I know I'm choosing the right routes when planning a trip.

As a frequent user, I want to:

  • be able to see transit schedules, so that I can establish travel plans that match my daily routines.
  • be able to easily access travel schedules for different mode types.
  • be able to veiw travel schedules on different devices.

Who we are designing for:

Below are an example of a few customer archetypes that were used to create empathy with our real-world users

Define

I started the first step in my process by defining and answering the 5Ws

1. What?

An intuitive experience that make route scheduling easy and quick.

2. Who?

Users who are new or returning to ride the service, want to easily discover schedule options to fit their routine.

3. When?

Users can use the web tool whenever they like. They will use the tool while they are searching for routes and planning and understanding a trip schedule.

4. Where?

As the tool aims to get users into a routine, it can be used whenever and wherever users like.

5. Why?

Riders want to reach their destination on time and to not miss their bus or train.

Leveraging Insights

Reviewing an older set of evaluations and looking at competitors:

I absorbed past work done by one of our research vendors during a site redesign project from a few years back. I reviewed the personas and user research studies reports. It was important to get a better sense of possible gaps we could fill as we moved forward with the project rather than completely reinventing the wheel.

How do we stack up? Next I did a comparison with others in the industry for inspiration and also to identify gaps.

Competitive Evaluation –How is this addressed on other transportation websites or applications?
What are good examples and (if possible) what are bad examples?

  • RTD: Denver, CO (rtd-denver.com) – Hovering over ‘Schedules’ presents a drop down menu for further selection: Bus, Light rail, etc. Expose PDF download option.
  • Transport for London: London, England – tfl.gov.uk – Bus Route Map selection

Distinguishing modes of transportation for Schedule data (Denver).

Users are allowed the option to download a PDF map of their selected route.

Users are given the option to select a map by area (London).

More Questions – learning more about the user

  • What were users happy with?
  • What frustrated the users the most?
  • What did users just want to change?

I felt is was important for me to figure out the essential features the tool would need to make it useful to the user based on the needs uncovered. I created a crude user flow diagram and made quick sketches to map out these features and see what kind of changes would be necessary as I started to think about and move into the design phase of the project.

Mapping Some Essential features

  • Intuitive route Selector
  • Good mobile experience
  • Ability to access a route in less than 3 clicks
  • Ability to quickly access fare purchase options

Solution Before Modifications:

“Generally, just from past experience I hate going into the Schedules and Maps thing because suddenly you're in a world of: ok, like wait, which one am I on?
– AnthonyHipster Rider
“I guess it would be helpful if [Schedules & Maps] was more interactive.
– Blaire CProspective Rider

Heuristics Evaluation – what heuristics have been violated?

  • Visibility of system status
  • Efficiency of use

Problem/Implications:

  • Users may not initially realize the default map shown is Route 1- Metric/South Congress.

Recommendations:

  • Maps need to be more interactive.
  • Introduce the page in a way that represents the routes available
  • De-emphasize the reliance of full schedules

Most participants expressed that the schedules were difficult to read. Further, the use of tabs to seperate modes types was too much to keep track of.

Solution After Modifications:

By stepping back and looking at the project and thinking about the users needs based on their feedback that their interaction with the tool was very confusing due to an unorganized presentation of content on the page.

To simplify things, I did the following:

  • I quickly begin to reimagine the tool - I first started by working with my UX writers to distill copy in ways so as to describe elements in their proper context using the least amount of text.
  • To better contextualize the user interaction, I thought of ways to simplify the layout through the use of component an then deply them in ways that would make sense in terms of the user-flow.

I updated this initial screen for the Schedules and Maps tool focused on insights and analysis gained from earlier user research sessions.

Solution Before Modifications:

“OK this is drop down, I kind of see what they want, but it's just so many options... thinking I want the five? hmmm I don't I don't know what to do."

– Pam, Student Rider

Heuristics Evaluation – what heuristics have been violated?

  • Aesthetic and minimalist design

Problem/Implications:

  • Drop-down menu under ‘Select a Route’ introduces too many options to the user.
  • In addition, users unfamiliar with the routes will not be able to differentiate between options.

Recommendations:

  • Introduce the page in a way that represents the routes available, and organize routes so that users are less overwhelmed by options

Most participants expressed that the text size was too small, and the schedules were difficult to read. Further, using a map to orient themselves to the city and the route was desirable to many.

Solution After Modifications:

It is also good to note that the previous solution embodied multiple pages which required the user to have to navigate a very un intuitive user-flow.

To streamline things, I did the following:

  • Users expressed the need for an easy to understand and intuitive navigation experience.
  • The outcome was a one page solution for the tool. Now users are able to access each mode-variant of the tool, and were able to access any route using a drop-down menu or typing in an input field, all without ever having to refresh the page.

Result, an intuative and rcognizable dropdown with an autocomplete fuctionality with universal route and mode accessibility

Ideate

Brainstorming Ideas

Moving along after the analyzation and eveluation process – next, I started sketching ideas as low-fidelity wireframes with pencil and paper. I moved on to Figma for my mid-fidelity wireframes, where I used a 12-column grid to create the initial layouts for mobile, tablet, and desktop devices. Because we are a public entity, I often find value in referencing (USWDS) design priciples in my design practice.

Design & Prototyping

Because of a short runway and condensed golive, I moved straight to Figma to create high-fidelity and interactive prototypes just in time for a quick round of usability testing.

Most of CapMetro users access the site via mobile and more than 19% of the U.S. population has specific accessibility needs, compatibility and accessibility elements were critical to the design and accounted for in every step of the process, including the code.

Testing

Rapid Usability Testing

Due to market demands and senior leadership mandates, this project had a rapid release requirement with an immovable launch date associated with it.

Through rapid usability testing, I was able to:

  • Gather quick feedback during wireframing or low-fidelity design phase
  • Identify user pain points and priorities early on
  • Undergo some iterations on designs before development
  • Focused on making user experience as frictionless and intuitive as possible (more testing needed)

Next Steps

It is my goal and desire to do some more extensive testing based on the current design with users in the market place in order to further validate the design based on findings from our last round of user testing. It certainly would be important to find out to what extent the established flow of information and visual design resonate with current users. I would also like to see where there are gaps and opportunities for improvement. Continuous iterations are an integral part of my design process.

August 2022, Update: Currently the tool is undergoing a re-development for itergration into a Sitefinity CMS solution. After that is complete, I will revisit usability testing and evaluation. I am confident that the next round of testing will yield even more insights and clue us in on additional ways to optimize the tool even more, thus making it even better for our customers.