HopSkipDrive is a car service for children, between the ages of seven and seventeen. Founded by three working professional parents, with the vision of helping mothers with their children’s busy schedules. With national expansion in progress, HSD mobile app will soon accommodate a flexible carpooling feature.
Create a carpooling feature within the existing product flow (iOS mobile app.)
Enabling multiple pickup/drop off locations from a single ride booking
Incorporate bill splitting for parent users
All parents to opt in/out/make changes to a carpool ride booking
More communication when multiple children are on route
An easy way to view and split bills
View ride history
Process: Plan, Discover Define, Design, Test
Methods: User Research, C&C Analysis, Task Analysis , Persona, Wire Flows, Prototype
Tools: Photoshop, InDesign, InVision, Excel, Asana, Slack, Pen and Paper, POP (Paper On Prototype)
In conclusion, we managed to remain within the existing product process minimizing development costs and disruption to what parents are accustom to. Parents in a car pooling group can create a carpool ride, add parents who agree to taking part. Anyone can set pick up and drop off points and they can also re-shuffle the ride schedule if something crops up. Finally they can view how the bill is split up amongst them.
PERSONA & SCENARIO
AGREE ON A COMMON LANGUAGE
First we settled on a common language so the UX team and client were on the same page.
- Alpha Parent = Parent who sets up the carpool ride
- Alpha Child = her child and siblings who'd be picked up at a default home location
- Sub Parent = A parent whom is invited to join a group of carpooling parents
- Sub Child = The subs child and siblings whom will gain permission to join the ride
- Pick Up = A default collection point all parents must fill in
- Drop Off = A default final destination all parents must fill in
- Notes = Details description about destination parking, security details, access
- Create ride = Filled out PU/DO destinations
- Book ride = Final step of booking a paid ride
A COMMON GOAL
Settling on a scenario helped us focus. A multiple pick up––with a single destination. Much like a common morning carpooling ride with neighborhood kids whom all go to the same school.
BREAKING APART THE PROCESS
By mapping out the existing steps we could see what was viewed by the multiple parties and where we needed to add deeper Sub Parent actions.
We started to add in the additional big picture needs and then regrouped them into phases that matched the existing process, so as not to deviate from the established product flow and remain within technical constraints.
Task Flow Analysis
We were then able to break the steps down into individual user tasks and link them together. As we got closer to a User Flow, we started to see patterns emerging from the fog. This took several days of iterations (along with way too much coffee, blood, sweat and tears.)
One of the main requests was more flexibility in adjusting rides. We looked at two options embracing the iOS platform. A hold and drag for ride summaries. Or a finger drag on the on screen map. Changing any of the waypoints would adjust time and cost of ride.
WIRE FRAMES V.1
Building out rough wire flows allowed us to agree on the critical actions and steps needed before going into high quality screens.
Wire FrameS V.2
After quickly going back to the drawing pad, resolving the issues headed back into Photoshop.
Utilising the tool kit from the HSD design team, we build out the new screens while adhering to design guidelines.
Despite the complexity of actions needed for a multiple ride for children, we've managed to pair it down into several short phases.
Back to work