kanchangaur.com / LA Metro Safety and Security Hub
LOS ANGELES

LA Metro / metro.net / public safety

Safety and Security Hub_

Turning metro.net’s static safety page into one hub for reporting incidents and seeing Metro’s safety work.

My role
Product designer
Timeline
2.5 months
Platform
metro.net, desktop and mobile
Status
Live on metro.net
Pages shipped
5
The shipped Safety & Support landing on desktop and mobile, with three ways to report right under the hero image.
01

My role and who I worked with

As the product designer, I led the redesign end to end:

  • Stakeholder kickoffs and the project brief, with the project manager
  • Rider research: a survey on metro.net, interviews and a review of other transit agencies
  • Information architecture and a mobile-first UX and UI for the hub
  • Standardized data visualization templates and a Crime Dashboard audit
  • Prototypes for usability testing, and developer handoff through implementation
  • Kanchan GaurMEProduct Designer
  • Project ManagerProject brief, milestones and timeline
  • Lead DeveloperBuild and implementation
  • Metro teamDay-to-day partners at LA Metro
  • Executives and CEOGoals and priorities
  • PR and content teamSafety narrative and messaging
  • Art DepartmentImagery for the hub
  • Data LeadSafety data and the Crime Dashboard

Client/Los Angeles County Metropolitan Transportation Authority (LA Metro)

02

Summary

LA Metro wanted riders to see what it is doing about safety, trust the numbers, and know how to report a problem.

Metro’s safety section on metro.net was one static, text-heavy page. Over 2.5 months I redesigned it into a Safety & Security Hub with five pages:

  • Safety & Support landing
  • Rider Guide
  • By the Numbers
  • Safety Team
  • Report an Issue

The hub is live at metro.net/safety-support.

03

The problem and the goal

What wasn’t working

  • Invisible safety work. Metro had more ambassadors, officers and security teams on the system, plus cameras across stations and vehicles, but riders rarely saw this work. That gap fed concern and misinformation.
  • A static page. One long page of text blocks, hard to navigate and with no numbers.
  • No way to keep up. The page couldn’t show safety measures that change month to month.
  • Reporting at the bottom. The way to report an issue was the last thing on the page.
The old safety page: text blocks for support teams, safe spaces and social challenges, with reporting at the very bottom.

Four audiences, four questions

Riders reacting to an incident

“I saw something unsafe.”

  • Report it right away through the Transit Watch app
Media and PR

“I need crime stats for media coverage.”

  • Safety reports and data they can download
Board members and officials

“I want to know which safety initiatives are active.”

  • Easy monthly updates on safety initiatives
Transit advocates

“I want to know how Metro is addressing homelessness.”

  • Outreach programs, initiative stats and support services

The goal

Design an engaging, rider-centered Safety & Security Hub that conveys Metro’s safety initiatives, builds transparency and moves riders to act, within a tight timeline.

  • Give riders the safety information they need, with clear next steps
  • Build transparency with data-backed storytelling
  • Drive engagement with interactive data visualizations and actionable content
04

My process

  1. 01DiscoverStakeholder kickoffs and the project brief
  2. 02UnderstandRider survey, interviews and a review of other agencies
  3. 03DefineKey insights and audience needs
  4. 04IdeateSolution mapping and feature prioritization
  5. 05DesignWireframes, prototypes and a mobile-first UI
  6. 06Hand offDeveloper handoff and support through implementation

Aligning with Metro’s vision

I led the stakeholder meetings to agree on goals and objectives for the hub.

  • A structured kickoff questionnaire surfaced priorities, challenges and expectations from executives, PR, law enforcement representatives and the data lead
  • With the project manager, I turned the answers into a project brief covering strategic goals, key milestones, timeline and deliverables
  • The brief became the shared reference that kept the cross-functional team aligned

Understanding rider needs

  • Designed and ran a survey on metro.net about riders’ safety concerns and expectations
  • Interviewed riders, Metro staff and transit advocates about how they perceive crime and security
  • Reviewed how other transit agencies communicate safety, to find best practices
Remote interview sessions with riders, Metro staff and transit advocates.

Key user insights

Riders told us they value four things. Each one became a job for the hub:

Trust

Show Metro’s safety work with current updates and clear accountability.

Information

Turn safety statistics into simple visuals with short explanations.

Easy reporting

Make the Transit Watch app easy to find, explain it, and link straight to reporting.

Safety guidance

Give short, scenario-based tips for first-time riders and common situations.

Finding the story in Metro’s own reports

  • Reviewed Metro’s Board reports, monthly safety emails, weekly dispatches and employee safety updates
  • Pulled out the safety information that matters most to riders
  • Found the structure for the homepage in Metro’s three safety pillars

Information architecture

  • Ran brainstorming sessions for solution mapping and feature prioritization
  • Structured the homepage into clear content blocks
  • Outlined the pages around it in four areas: Metro’s Performance, Our People, Our Initiatives and Programs, and Data and Transparency
  • Shipped five pages: Safety & Support, Rider Guide, By the Numbers, Safety Team and Report an Issue
Information architecture: four areas and the pages planned under each.
05

How I solved it

I built the hub around a story of action, accountability and progress, so Metro’s safety work and the numbers back each other up.

Reporting comes first

  • Three ways to report right under the hero: the Transit Watch app, 911 and a text line (213.788.2777)
  • Clear calls to action that explain the Transit Watch app and link straight to it
  • A Report an Issue button in the hub’s navigation

Three pillars, each backed by numbers

  • Eyes on the system: more visible Metro Ambassadors, law enforcement and security teams, plus cameras across stations, stops, trains and buses
  • Used for transit, and only transit: TAP-to-Exit to encourage fare payment, and sound-based deterrents to reduce loitering
  • Partnerships for societal issues: crisis response teams, and outreach that connects people experiencing homelessness to housing and services
  • Each pillar leads with a plain-language headline and a stat block, such as cameras, customers helped, fare checks and people placed in housing
The three pillars on mobile, each headline backed by its own numbers.

Numbers with context

  • Chose the key crime metrics: most reported crimes, total arrests, and trends by location and time
  • Balanced them with Metro’s response: law enforcement, Metro Ambassadors and security installations
  • Designed standardized chart templates with Systemwide, Bus and Rail views, comparisons with last month and last year, time ranges, and a context note under each chart
  • Built the templates as modules that Metro’s teams can update on their own
  • Audited Metro’s Crime Dashboard so safety data looks consistent across platforms
By the Numbers on desktop and mobile: one chart template, with a context note under every chart.
One template, four datasets: fare enforcement, arrests, crimes and ridership.

Wireframes and prototypes

  • Low-fidelity wireframes to set content hierarchy and flow
  • Interactive prototypes to test usability with stakeholders and selected users
  • A mobile-first approach for accessibility and responsive layouts
  • Reused components from the Customer Experience Hub I designed for Metro, for speed and brand consistency

Content and visual design

  • Partnered with PR and the content team on a clear safety narrative
  • Worked with Metro’s Art Department on imagery
  • Designed to WCAG 2.1 AA accessibility standards
  • Worked closely with developers through implementation
The Safety Team page, and the eyes-on-the-system numbers on mobile.
06

Outcome

2.5 mo

From research to developer handoff

5

Pages in the live hub, from the landing page to Report an Issue

4

Charts on By the Numbers, all built from one template

  • Easier access: intuitive, streamlined access to safety resources and reporting
  • More trust: data-backed storytelling made Metro’s safety efforts more transparent
  • Clearer numbers: simplified statistics improved comprehension
  • Faster delivery: component reuse sped up design to development, within a tight deadline
  • A go-to reference: Metro leadership, media and stakeholders use the hub for safety updates
  • Still live: in October 2026 the hub keeps the same structure and shows August 2026 figures
07

Learnings

Talk to riders directly

Direct conversations with riders made the hub more intuitive and more meaningful to use.

Align early and often

A structured kickoff and frequent check-ins kept a large, cross-functional group moving without friction.

Numbers need a story

Safety stats built trust once they were part of one narrative, with context for every number.

Reuse what already works

Components from the Customer Experience Hub kept the brand consistent and helped deliver in 2.5 months.

· los angeles, california ⌘K to jump anywhere