Responsive Web App
December, 2019
Conducted User Research Interviews and Analysis
Co-crafted User Experience Design and Information Architecture
Contributed assets to Hi-Fidelity Prototype
Aaron Bishop
Missy Chen
Gautham Sajith
Reduce overhead for carpooling student athletes
Figma
We designed Kidspool, a web app for organizing youth athlete carpools, to free up more time for parents by improving the existing carpool structure — making it more flexible, accessible, and fair.
Users may tap a card to either offer a ride or request a ride.
Need met: Parents act as both drivers and ride-requesters, and our UI needs to serve both those needs.
Need met: We encourage equal contribution to carpooling through an in-app currency.
Giving rides earns tokens, and requesting rides costs tokens. Tokens help parents avoid awkward conversations by providing automatic indirect feedback to under-contributing parents.
Tapping on an active event-details page shows the driver’s route status and a live tracking dot for the ride. There are also affordances to contact the driver.
Need met: Children’s safety is a primary concern with this platform, and the live tracking and driver contact give parents peace of mind.
Need met: Parent drivers don’t need to leave the application to navigate to their pickups. They can respond to incoming requests from within the app.
Parents will be given a link by their coach to join their team’s Kidspool community. Parents create an account, fill in their contact information, and most importantly, fill in their driving availability (bottom-right in the image).
Presenting this in the onboarding also establishes a precedent that parents are all expected to drive in addition to requesting rides.
Since safety is a primary concern for parents, we take advantage of the bigger screen size to give parents a more comprehensive map. Yet the design is still consistent with the user interactions and elements of the mobile application to ensure learnability.
From six interviews we conducted, we developed personas for parents, coaches, and club & league administrators.
We generated several key insights from this analysis:
Some of the lowest points in parents' emotional journeys involve the time commitment of getting their kids to practices and games.
Conversely, coaches are most frustrated with time spent on planning and logistics, communication with parents, and player absence.
We crafted storyboards for potential solutions and speed-dated them with colleagues.
Insight: Parents and coaches need to spend less time getting kids to practice.
Carpooling already reduced parents' drive times and fostered community. Yet, from our research, we knew that even with carpools, parents still struggled with the time commitment of their children's sports.
We identified opportunities in three areas:
With a mobile-first approach, we worked together to converge on what screens were key:
Next, we diverged, each of us creating low-fidelity prototypes:
We selected screens that best conveyed parents' mental model about carpooling.
We focused on an event-based model. Each upcoming practice, game, or other team event will be an “event card” on the home screen.
We received feedback that the UI and colors felt hectic and overloaded. We also received feedback that the event name (“Soccer practice”) felt more emphasized than it needed to be, and that the actual useful information (i.e. event statuses) felt secondary. Next, we focused on reducing the amount of data presented and emphasizing event statuses.
This image shows our development across our hi-fi prototypes:
We learned a great deal about youth sports and its positive impact on the Pittsburgh community. Based on the positive feedback our design received, we believe that it has real potential to improve carpooling and, by extension, youth sports in real world settings.