Empowering
Hybrid Commuters

Empowering Hybrid Commuters

Empowering
Hybrid Commuters

When I joined the project, the team faced a critical challenge: users had to set fixed weekly commute days, which created barriers for those with hybrid or fluctuating work schedules. This inflexibility led to dissatisfaction, inefficiency, and higher operational costs. The web app was still in development, and the team was in the process of implementing the Commute Subscription model. My role was to build upon this by introducing a Flexible Scheduling subscription model. This model would allow users to schedule different days each week with just a day's notice, adapting to hybrid work schedules and reducing operational costs.

When I joined the project, the team faced a critical challenge: users had to set fixed weekly commute days, which created barriers for those with hybrid or fluctuating work schedules. This inflexibility led to dissatisfaction, inefficiency, and higher operational costs. The web app was still in development, and the team was in the process of implementing the Commute Subscription model. My role was to build upon this by introducing a Flexible Scheduling subscription model. This model would allow users to schedule different days each week with just a day's notice, adapting to hybrid work schedules and reducing operational costs.

When I joined the project, the team faced a critical challenge: users had to set fixed weekly commute days, which created barriers for those with hybrid or fluctuating work schedules. This inflexibility led to dissatisfaction, inefficiency, and higher operational costs. The web app was still in development, and the team was in the process of implementing the Commute Subscription model. My role was to build upon this by introducing a Flexible Scheduling subscription model. This model would allow users to schedule different days each week with just a day's notice, adapting to hybrid work schedules and reducing operational costs.

When I joined the project, the team faced a critical challenge: users had to set fixed weekly commute days, which created barriers for those with hybrid or fluctuating work schedules. This inflexibility led to dissatisfaction, inefficiency, and higher operational costs. The web app was still in development, and the team was in the process of implementing the Commute Subscription model. My role was to build upon this by introducing a Flexible Scheduling subscription model. This model would allow users to schedule different days each week with just a day's notice, adapting to hybrid work schedules and reducing operational costs.

60k+

Commuters

Available On

Web | IOS | Android

Empowering
Hybrid Commuters

Empowering
Hybrid Commuters

Objective

Enable users to schedule different days each week, improving their commuting experience and aligning with their ever-changing work patterns.

Initial Subscription Model

The original model required users to set fixed weekly commute days, with changes taking up to two weeks. This rigidity created significant challenges for users with fluctuating or hybrid work schedules, making it difficult to adapt to their dynamic needs.

Flex Subscription Model

FLEX Subscription Model

The Flex model allows users to schedule commute days on-demand, even within an hour of departure. This flexibility adapts to dynamic work schedules and reduces operational costs by minimizing missed or unnecessary rides.

My Process

Observe

Reflect

Create

The design process I followed is iterative and continuous, much like the infinity symbol it represents. Inspired by design thinking, this approach blends research, reflection, and creation in a seamless cycle. Each phase informs the next, ensuring design decisions evolve based on insights and feedback.

In the Observe phase, we gather user insights, which are then synthesized in the Reflect phase to identify patterns and generate solutions. In the Create phase, concepts are developed into prototypes and tested, with insights from testing continuously feeding back into the cycle for ongoing refinement and adaptation.

Observe

Leveraging AI to Synthesize User Insights

Users

Due to budget and time constraints, as well as limited access to real users, conducting new user research was not feasible. Instead, I used a private GPT to synthesize prior research from lean UX workshops, market surveys, and real user interviews to identify the needs of users who schedule their commutes on different days each week, along with a list of app features to support them.

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

George

Hybrid Commuter

Responsibilities

• Balance rides with hybrid schedule

• Ensure timely office arrival

Motivations

• Efficient and stress-free commute

• Flexible scheduling options

• Save on commuting costs

Pain Points

• Unpredictable rider attendance

• Communication breakdowns

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

• Easy-to-use mobile app

Emily

Vanpool Driver

Responsibilities

• Ensure safe and timely ride-sharing

• Handle ride logistics and scheduling

Motivations

• Build a community among riders

• Keep operations efficient

• Ensure rider satisfaction

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

• Easy-to-use mobile app

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

George

Hybrid Commuter

Responsibilities

• Balance rides with hybrid schedule

• Ensure timely office arrival

Motivations

• Efficient and stress-free commute

• Flexible scheduling options

• Save on commuting costs

Pain Points

• Unpredictable rider attendance

• Communication breakdowns

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

• Easy-to-use mobile app

Emily

Vanpool Driver

Responsibilities

• Ensure safe and timely ride-sharing

• Handle ride logistics and scheduling

Motivations

• Build a community among riders

• Keep operations efficient

• Ensure rider satisfaction

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

• Easy-to-use mobile app

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

George

Hybrid Commuter

Responsibilities

• Balance rides with hybrid schedule

• Ensure timely office arrival

Motivations

• Efficient and stress-free commute

• Flexible scheduling options

• Save on commuting costs

Pain Points

• Unpredictable rider attendance

• Communication breakdowns

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

• Easy-to-use mobile app

Emily

Vanpool Driver

Responsibilities

• Ensure safe and timely ride-sharing

• Handle ride logistics and scheduling

Motivations

• Build a community among riders

• Keep operations efficient

• Ensure rider satisfaction

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

Desires

• Simple, flexible scheduling system

• Affordable pay-per-ride model

• Easy-to-use mobile app

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

PROTO-PERSONAS (GPT)

SUPPORTING FEATURES (GPT)

MVP FEATURES

Creating a Product Model Canvas to Map Touch-points and Impacts

I represented the front-end user experience in creating the Product Model Canvas, collaborating with back-end and product experts. This detailed the commuter’s journey, impacted screens, and back-end functions, providing a roadmap for efficient integration and future use.

Booking Rides

Waitlist

User can multi-select dates to commute, up to 3 months advance

High Impact

Flex customers will now need to select specific ride days in order to book

Updates Schedule and can view new ride days

High Impact

Flex Customers must wait 24 hours to see newly assigned driving days

High Impact

Waitlist management and oversight will be a new responsibility for Operations team

High Impact

After securing waitlist seat, Flex customers will need to confirm their booking

Chooses to join waitlist and confirms booking

Receives notification that a seat is available on the requested ride

Confirms their seat and is added to the ride

Books ride with available seat

or

(Consolidated sample of an impacted area)

Reflect

Reflect

Exploring key patterns for viewing and booking rides

Exploring key patterns for viewing and booking rides

Exploring key patterns for viewing and booking rides

To determine the best user experience for viewing and booking rides, two patterns were explored. The first, an iOS calendar view, displays static daily details at the bottom of the app. The second, featuring scrolling months, opens a bottom sheet with detailed information for each day. After team feedback, the second option was selected for its improved usability and flexibility.

To determine the best user experience for viewing and booking rides, two patterns were explored. The first, an iOS calendar view, displays static daily details at the bottom of the app. The second, featuring scrolling months, opens a bottom sheet with detailed information for each day. After team feedback, the second option was selected for its improved usability and flexibility.

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with details on bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with details on bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with details on bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with details on bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with details on bottom sheet

VIEWING RIDES

BOOKING RIDES

1. IOS Calendar pattern

VS.

2. Scrolling months with details on bottom sheet

Constructing Mid-fidelity Wireframes to Define All Details

Constructing Mid-fidelity Wireframes to Define All Details

To determine the best user experience for viewing and booking rides, two patterns were explored. The first, an iOS calendar view, displays static daily details at the bottom of the app. The second, featuring scrolling months, opens a bottom sheet with detailed information for each day. After team feedback, the second option was selected for its improved usability and flexibility.

To determine the best user experience for viewing and booking rides, two patterns were explored. The first, an iOS calendar view, displays static daily details at the bottom of the app. The second, featuring scrolling months, opens a bottom sheet with detailed information for each day. After team feedback, the second option was selected for its improved usability and flexibility.

Create

Viewing Rides

Users can easily view their rides for the next three months, see who they’ll be riding with, and set a driving preference in case a driver is needed

Booking Rides

After tapping 'Add Rides,' users can select their ride dates. Within 24 hours, the back-end system factors in the user's preferred driving days and assigns driving dates accordingly.

Settings

Users can set their preferred driving days and choose notification preferences to be alerted about any unscheduled rides for the following week.

Additional Flex Integrations

Sign Up

Average Seat Occupancy

Avg. Seat Occupancy

Average Seat Occupancy

Cancel Subscription

Cancel Subscription

Other Product Enhancements

Original

Lack of WCAG AA Compliance
The original design did not meet accessibility standards, making it difficult for users with disabilities to navigate and interact with the app effectively.


Slow Load Time
A high number of API calls caused delays in loading, leading to a frustrating user experience as users waited for content to appear.


Cluttered Layout
The screen was overcrowded, with important information scattered across different sections, making it harder for users to quickly find what they needed.


Limited Map Functionality
The route map was small, making it difficult to get a clear view of the commute and interact with it effectively.


Inefficient Navigation
The design required multiple taps to view ride details and stops, leading to unnecessary complexity and time spent navigating.

Revised

WCAG AA Compliance
The new design fully meets accessibility standards, with improved contrast, keyboard navigation, and screen reader support, making it easier for all users to interact with the app.


Faster Load Time

We reduced the number of API calls, optimizing performance and significantly improving load times for a more seamless experience.


Streamlined Layout
The layout is now more intuitive, with clearly organized sections that allow users to quickly access the most important information without unnecessary scrolling.


Larger, Interactive Route Map
The route map is now larger and more responsive, offering a clearer view of the commute and improving the overall user interaction.


All-in-One Stop List
The list of stops is now displayed on the same screen as the route map, giving users a clearer overview of their journey and eliminating the need for extra taps.


Commuter Numbers at Stops
Riders can now see the number of commuters waiting at each stop, allowing them to anticipate how many others will be in the vehicle and choose their seats accordingly.