HUSKY NightRoute

Class Project

UX / UI Designer

PROBLEM SPACE

“Night time safety” is always one of the main problems students care about.

NIGHT TIME

SAFETY CONCERNS

1,247,321 violent crimes nationwide，At least 60 % happens at night. (securitymagazine.com)

Due to reasons such as class schedule and group meetings, UW students have to stay late at school, which leaves them facing a dangerous trip back home.  

UW NIGHTRIDE 

operated by the university, provides free shuttle survices for students at night time. 

SAFETY ESCORT SERVICES

Pick up students at one of eight campus stops

Drops passengers at their doors

Operate weekdays 8pm - 2am

UPass members only

Interviews

My team arranged a semi-structured contextual interview with 3 regular night ride passengers to both understand their prospective and observe how do they interact with the services. 

Uncertain

"I can’t really hear him, so I actually got off one or two blocks away from where he supposes to drop me off."

Unreliable

 "... it sometimes stops at the stops and sometimes doesn’t, but I don’t know why. I have to ask the bus driver if they can take me."

Insecure

"I never saw the bus driver check their Husky ID or something"

Chain of Causality

Design Challenge

How might we help UW students to have a reliable, rest assured commute experience from campus at night?

Outcomes

We want students to . . .

01

feel in control of their commute.

02

be informed of what is going on.

03

build trust toward school services.

Principles

Give students control

Students should always feel like they are in an environment they want to be in, and have the power to change that if they’re not comfortable.

Updates and Informs

Students should always know where they are and where they are headed.

Maintain privacy

Gather just enough personal information from users and keep those secured. 

IDEATION & ITERATION

Wireframes

Verify passengers' UW affiliation

View campus stops

+

live schedule updates

Input address 

+

review route information

User Testing

Key

Findings     

Unfamilar with NightRide Service

First time riders are confused on how the service functions and wht it need their address.

Complicated Sign In Process   

Students are confused what's UPass membership. After confirming with the service office, we realized it is basically everyone's uw NetID.

Privacy                                                 

Users feel unsafe to show the estimate area of their stops, even when we reinforced that the dots on map won't reveal their location.

Communication with bus driver   

Users still want the ability to communicate with driver, especially changing address.

Confirm onboarding         

Users feel that people aren't on the shuttle can also add stops, which might lead to confusion. Thus, we planned to add a driver confirmation screen in our next delievery cycle.

UI DESIGN

FONTS

COLOR

Heading 

Montserrat Bold

Body text

Monserrat Regular

Button

Monserrat Median

FEATURE WALK THROUGH

Onboarding Pages

first time login

NightRide service is different from conventional bus services, so it might be confusing for first time users to use the service, so we provided ditailed instructions for first time users. Acknowledge that many users do skip onboarding screens, we still planned the rest user flows to be intuitive and it should not create trouble is any user skipped this information. 

Select Bus Stop

/

On Boarding

waiting for bus 

Users can select any stop they want. We also list the stops in order of distance in case users aren‘t familiar with the campus. 

We want to offer an effortless way for students to "talk to" NightRide drivers.

Effortless Communication

onboarding & finishing trip

We want to offer an effortless way for students to "talk to" NightRide drivers. By allowing students to input address from mobile devices and conforming destination, we aim to eliminate the unreliable and uncertain issues of the current system.

Hi-Fidelity Monk up

Testing Screens