Regional Transportation District

Optimizing a Transit Website to Help Riders Navigate Schedules and Ticketing

Objective
Metro Denver's transit system needed a new website to help riders get to where they need to go – faster.
Background

The Regional Transit District is Metro Denver's public transit system; offering bus, regional shuttles, lightrail, and commuter rail services to the Front Range.

RTD came to us with two goals: get off their old CMS, and make it easier to access schedules. Their existing CMS contract was expiring, and after 8 years on it, it was difficult to update.

The primary audience included both frequent and occasional transit users, so we couldn't rely on users learning through repeated use.

60% of RTD website visitors accessed the website from a mobile device – likely while en route to using an RTD service.

Problem

The existing RTD website had performance issues, was not optimized for mobile, and was difficult for staff to update–preventing critical notifications from being delivered to riders.

Their existing site buried key information for riders within unclear parent categories—schedules and ticket information under multiple layers of navigation, maps and station details were mixed in with details about project funding and construction updates.

Solution

We simplified the site's information architecture to ensure prominent access to scheduling and ticketing information. 

We created a clear distinction between trip planning actions and information seeking actions, and the new information architecture reflected that in structure.

Using site analytics, competitive analysis, and user interviews, we identified the most visited paged associated with using the transit system and grouped them together.

The new website resulted in increased views per user (+40%), lower bounce rates (-15%), and increased site speed (+30%). A shiny, new CMS using Sanity, Cloudinary, and Vercel helped to improve operational efficiency for RTD staff.

Multi-modal discovery
The discovery process helped us understand issues with the existing experience and understand our competitors. We observed that the best transit websites had prominent, easy access to trip planning, and schedules would often be available in the context of specific stations.
How might we optimize RTD's information architecture and content structure to best serve frequent and occasional riders?
Process
Current State
Step 1

Mapping of legacy site structure: the multiple levels and layers of navigation buried key information for riders. The items marked with the green dot denote links to RTD's NextRide app, creating additional friction and pathing for users to navigate.

Analytics
Step 2

Path of returning users

Grouping by User Need
Step 3

Creating primary content zones for Riders and Informational users

CMS Setup
Step 4

Template pages within the CMS allowed for flexibility while maintaining a consistent design system.

Process
Current State
Analytics
Grouping by User Need
CMS Setup
01
Step 1

Mapping of legacy site structure: the multiple levels and layers of navigation buried key information for riders. The items marked with the green dot denote links to RTD's NextRide app, creating additional friction and pathing for users to navigate.

02
Step 2

Path of returning users

03
Step 3

Creating primary content zones for Riders and Informational users

04
Step 4

Template pages within the CMS allowed for flexibility while maintaining a consistent design system.

Process
Current State
Analytics
Grouping by User Need
CMS Setup
01
Step 1

Mapping of legacy site structure: the multiple levels and layers of navigation buried key information for riders. The items marked with the green dot denote links to RTD's NextRide app, creating additional friction and pathing for users to navigate.

02
Step 2

Path of returning users

03
Step 3

Creating primary content zones for Riders and Informational users

04
Step 4

Template pages within the CMS allowed for flexibility while maintaining a consistent design system.

Process
  • Research and Discovery
  • Defining Migration and Content Strategy
  • Product Design
  • Wireframing
  • Visual Design
  • Development Hand-off
Service Alerts' Future State
Service alerts were one of RTD's biggest operational pain points. The process for updating service alerts made it impossible to provide timely, relevant alerts to RTD's ridership. Their new infrastructure would improve publishing no problem–but I wanted to give RTD a better experience for Service Alerts that would complement the site's new publishing capabilities.