📍 New York City
Artboard Copy 3.png

BoltBus

 
boltbus.png
 
 

I started the process by following my curiosity. “How does Bolt bus make money?” I set to find out with the resources at my disposal

Research

 
4 copy.png
 

Dissecting of the Current State of the Site

 
 

with the intention of studying the mechanics of the site, separating it’s visual design from its features and functionality

 
 

with these notes in mind… i translate them into actions, ways to apply these observations and findings into applicable product notes

 
1_pa9RClzZ0XmdO8EQOV-1fg.png
 

i then go through, bullet point by bullet, asking and answering as many “why” questions as possible. my intent, as a designer, is to realize and resolve user needs preemptively.

from the process, i distill that step 1 can be classified as the “user input” stage. the following screenshots are is the thought and note taking process that helped me arrive at this conclusion:

Part 1: The UX of User Input

 
 

putting some of these notes into interactions…

 
 
storyboard ➡️

storyboard ➡️

1_X07eiMHTF9C47dy0goBC1w.gif
 

in the wireframing / exploration process, a new questions to consider reveal themselves:
1. how to accommodate for special needs passengers?
2. distinguishing yet consistent inputs between a round and one way trip

 
UI explorations that lead to the following interaction ➡️

UI explorations that lead to the following interaction ➡️

 

i nestled the special needs requirement under the passenger select to consolidate features and declutter the main page. 

the lighter the visuals ~> lighter the cognitive load

in this journey, the user’s intention is to select the # of seats they anticipate.
the # of special needs seats is a subset of the # of passengers. since this use case does not apply to the majority of the audience, it makes sense for it to reveal itself rather than having the user process another decision.

 
P2 1.png
P2 2.png
P2 3.png