Empowering Seattle residents to bridge transit gaps in public transportation

Background

As part of a 10-week project for INFO 360, I was tasked with designing a product to advance one of the 17 United Nations Sustainable Development Goals. My team chose UN Sustainable Development Goal 11: Sustainable Cities and Communities.

As the Lead Designer, I drove the full product lifecycle from research to delivery. I conducted user interviews and developed personas, led rapid ideation sessions, executed usability testing across multiple rounds, established our design system, and created high-fidelity prototypes that shaped the final product vision.

The Problem

Transit deserts in Seattle limit transportation options, disproportionately affecting lower socioeconomic and Black households. This lack of access restricts opportunities for jobs, education, and healthcare, as seen in higher unemployment rates and reduced student attendance and performance. Improving transit access can reduce air pollution and emissions, benefiting both the environment and underserved communities. Source

My Solution

GoFarther.org is a website that crowdsources bus stop suggestions from riders to help cities identify and fill gaps in public transit access. The app collects location-tagged submissions to highlight proposals for feasible new stops that connect underserved transit areas.

Requesting to create a stop

Seattle residents can easily propose new bus stops. Users input their desired location, usage frequency, and travel times, helping transit authorities make informed decisions.

Requesting to extend bus route

Seattle residents can propose bus route extensions, where users pinpoint desired new extensions, inputting their location, usage frequency, and travel times, enhancing the network's reach and convenience.

Requesting to modify bus stop

Seattle residents can request improvements to existing bus stops. Users can easily report safety concerns, cleanliness issues, or suggest schedule changes, with an option for more detailed feedback.

View community requests

For engaged residents, the community map displays where other users have proposed new stops or route extensions. Viewers can explore these suggestions and gauge local transit needs.

research and problem exploration

Secondary research

My team initially explored the problem space by doing desk research by analyzing existing sources about transit deserts. We found that the main cause of transit deserts is poor transit planning and lack of municipality knowledge of that poor planning. While downtown Seattle and northern neighborhoods are well-served by light rail and buses, southern neighborhoods suffer from inadequate transit.

Expert interviews

We interviewed Christine Bae, an Associate Professor in the Urban Planning Department at the University of Washington, to understand best practices in transit planning and strategies for improving access.

Christina recommends providing some transit access to suburban areas: a connecting line from the suburbs to a nearby light rail station. This allows suburban residents an option to access the larger transportation infrastructure when needed, while most day-to-day travel is still done by personal car.  

finding 1

Extending Existing Routes is More Successful

Adding stops to routes is less costly and complex for transit agencies to expand a current route. Creating new bus routes requires more planning around new paths, schedules, etc.

finding 2

Light Rail With Connecting Bus Routes

Connecting areas to light rails with bus routes is convenient for longer-distance riders, as light rail offers quicker transit into the urban core. Riders can transfer to buses for specific neighborhoods, reducing long bus rides from outlying areas

finding 3

Lower Demand For Public Transit in Suburban Areas

Public transit demand is lower in suburban areas, where higher-income households prefer using personal vehicles, making these areas transit deserts despite available services.

User interviews

Along with our domain expert, I interviewed 3 individuals who have expressed frustrations with public transit in their area.

01

Long Commute Times

Users' walking distances to the nearest bus stop range from 5 to 40 minutes, with one user relying entirely on the bus despite the lengthy walk.

02

Driving Preference

Users chose to drive instead of taking the bus due to the inconvenience of long walks, but they still dislike the traffic associated with driving.

03

Limited Bus Service

Users expressed frustration with the infrequent bus schedule, which operates only at specific times during the day and not on weekends

04

Closer Bus Stop Desires

Users wished for bus stops to be located closer to their homes, as current distances are inconvenient.

05

Light Rail Access

Users preferred using the Light Rail but found it inaccessible due to the distance from their home and the bus stop that connects to it being too far away.

06

Cleanliness & Accuracy

All users emphasized the need for cleaner bus stops and more accurate bus arrival times to improve their commuting experience.

Crafting personas from research insights

From our interviews, I decided to expand our idea to include areas with higher incomes and not only underserved areas, as a connecting line from the suburbs to the light rail station allows suburban residents an option to access the larger transportation infrastructure when needed.

After analyzing our research data, our team identified two distinct groups of users within Seattle's public transit system: suburban commuters and urban transit-dependent residents. These groups were crystallized into personas that serve as data-driven representations of our target audience.

Problem Statement

Following the completion of the research phase, I formulated several problem statements that aligned closely with my findings. The most relevant problem statement was then selected to guide the remainder of this project:

How might we empower Seattle residents to directly influence public transit planning in their area to increase transportation access, equity, and sustainability?

ideation

Honing in on the features

Now that I had a good understanding of who we are building for and their needs, I was able to start thinking of solutions. I identified that the solution needed to extend an existing bus route, modify an existing bus route, and create a new bus stop.

Based on these key experiences, I determined our applications' 2 main request features: Creation of a bus stop and modification of a bus stop.

Low-fidelity sketches

Using my ideation and key experiences, I sketched our low-fidelity user flows, depicting our initial vision user flow for GoFarther.org.

Prototyping and testing

Mid-fidelity prototyping

After the paper sketches, my team moved it into Figma where it was easier to move things around. The working name for our application at the time was BusSign, but down the line, it evolved into GoFarther.org

Landing Page - Request Stop
Request Stop: Fill out questionnarie pop-up
Existing Stop:
Existing Stop: Select a bus stop to modify
Existing Stop: Fill out questionnaire pop-up

Usability Testing

My team conducted A/B testing with 7 new student participants who regularly use public transit. Half received an introduction to GoFarther.org and its goals (Group A), while the other half got no context (Group B). All users completed key website tasks, followed by reflective discussions. This approach helped us assess how context affected user interactions and perceptions, informing our design decisions.

All users were asked to complete a series of tasks related to the key features of the website, and then we debriefed with each participant to ensure they didn't feel like they failed if they couldn't complete certain tasks by guiding them through any incomplete tasks.

  • Task 1: Notify Seattle legislators where you want a new bus stop to be added to improve public transit access.
  • Task 2: See where other people have requested stops.
  • Task 3: Notify Seattle legislators that an existing bus stop requires modifications.
  • Task 4: Notify Seattle legislators than you want to extend a bus route.

Usability takeaways: onboarding, labeling, and visual design

From those usability tests, we found that we needed an introduction to our app, more clear UI, and better information hierarchy.

01

Set Proper Context Through Onboarding

Participants who received no introduction needed better guidance and explanatory content. Without any upfront instructions, users struggled to grasp the app's purpose and understand how to accomplish key tasks like requesting new stops or providing feedback.

02

Implement Clear Labeling and Descriptive UI

Participants were confused by ambiguous icons, buttons, and unexplained functionality across the app's interface. Several participants developed misconceptions about certain features based on their own interpretations of unlabeled UI elements.

03

Optimize Information Architecture

We needed to apply better information hierarchy and visual design principles to guide users toward primary actions and interactive elements. Participants consistently missed or forgot about critical buttons like "Request New Stop" when placed in the bottom corner.

iteration

Setting proper context through onboarding

I incorporated pop-up instructions that directed the user depending on if they want to request a stop or modify an existing route, allowing the user to better navigate the website based on their objectives.

Implementing clear labeling and descriptive UI

I added more clear labeling to our buttons so users had some type of context. I additionally made the state of the button more apparent.

Optimizing information architecture and visual design

I enlarged the 'Request a New Stop' and 'Modify an Existing Route' buttons and moved them to the top of the screen. This prominent placement emphasizes our application's core functions, helping users immediately recognize these as the website's primary features.

Design System

Color and typography

I chose a color palette with primarily blue tones to establish a sense of reliability and credibility since our service requires trust and confidence from users. I used a sans-serif typeface to allow for ease of readability and to make GoFarther.org feel modern and user-friendly.

Design Library

As Lead Product Designer for GoFarther.org, I established a comprehensive design system, creating reusable components and documentation to ensure a consistent and intuitive user experience across the platform.

Final High-Fidelity prototype

Now that we were able to iterate our design and adhere to our design system, let's take a look at the final Figma prototype showcasing the polished interface for GoFarther.org.

Reflection

While I had some design experience at the University of Washington, my knowledge was entirely self-taught through YouTube tutorials and Medium case studies. This 10-week course significantly expanded my understanding of user-centric design.

I learned a great deal from activities like domain expert interviews, user research, and collaboration, which helped me refine my qualitative and quantitative research skills while strengthening my storytelling. In hindsight, I wish I had conducted more usability studies to see if our task completion rate went up. I also wish I interviewed more individuals in transit deserts to deepen our insights.

Despite these challenges, hearing from people affected by limited transit access was incredibly motivating. This project reinforced my belief in design’s ability to address equity issues and advocate for underserved communities—a mission I’m proud to have advanced through GoFarther.org.