Overview
Charter schools in many communities do not provide bus transportation. As a result, parents coordinate daily carpools for drop-off and pickup. While drop-off schedules are usually consistent, pickup responsibilities vary due to after-school clubs and activities, creating daily coordination challenges.
This case study documents how I identified the problem, conducted user discovery, defined an MVP, shipped a lightweight solution, and iterated based on real user feedback.
The Problem
Parents rely on group texts and informal spreadsheets to coordinate carpools. This leads to:
- Confusion around daily responsibilities
- Last-minute schedule changes handled manually
- Uneven distribution of pickup and drop-off duties
- Stress for parents and risk of missed pickups
The biggest breakdown occurs during pickup, where schedules vary and change frequently.
Goals & Success Criteria
Primary goal
Reduce daily coordination effort while ensuring clear accountability for drop-off and pickup responsibilities.
Success criteria
- Parents can see daily responsibilities without texting
- Schedule changes are handled without group coordination
- Responsibilities rotate fairly across families
Discovery & User Research
I interviewed 5 parents who regularly participate in carpools for charter school students.
Key questions
- What’s hardest about coordinating drop-offs and pickups?
- How do you manage changes today?
- What happens when someone can’t make it?
- What would an ideal solution look like?
Key insights
- Parents want a single source of truth
- Last-minute changes are the biggest pain point
- Fairness matters more than optimization
- Simplicity is critical for daily use
“The morning is usually fine. Pickup is where everything breaks.”
“We spend more time coordinating than actually driving.”
Solution Summary
A lightweight carpool coordination app that:
- Creates a shared, private group for parents
- Captures child schedules
- Automatically assigns and rotates responsibilities
- Sends proactive notifications
- Handles last-minute changes without chaos
The solution prioritizes clarity, reliability, and low effort over feature richness.
Core User Workflow
Create Group → Add Kids & Schedules → View Daily Assignments → Receive Notifications → Handle Changes
This workflow guided all MVP decisions.
Key Screens & Flows
1. Create or Join a Carpool Group
Purpose: Reduce setup friction and support trust-based groups.
What users can do: Create a group (school + grade) and invite parents via link.
📸 Visual: Group creation / invite screen
2. Add Child & Schedule
Purpose: Capture essential scheduling information without over-engineering.
What users enter: Child name, drop-off time, pickup time (fixed or variable).
Design choice: Allowed “varies” instead of complex rules.
📸 Visual: Add child schedule screen
3. Daily Assignment View (Primary Screen)
Purpose: Provide clear ownership with zero interpretation.
What users see: Today’s drop-off and pickup responsibility, assigned children per parent, and an upcoming rotation preview.
📸 Visual: Daily assignment dashboard
4. Notifications
Purpose: Proactively communicate responsibility changes.
Examples: “You’re responsible for pickup today at 4:30 PM”, “Pickup reassigned due to availability change”.
Design choice: Notifications instead of in-app chat to avoid duplicating existing tools.
📸 Visual: Notification examples
5. “I Can’t Make It” Flow
Purpose: Handle failure states gracefully.
Flow: Parent marks themselves unavailable, responsibility is reassigned, and the new parent receives a notification.
📸 Visual: Unavailable / reassignment flow
MVP Scope & Tradeoffs
Included in MVP
- Group creation
- Child schedules
- Daily assignments
- Responsibility rotation
- Notifications
- Manual opt-out and reassignment
Explicitly excluded
- In-app chat
- Pickup codes
- Club-specific logic
- Calendar integrations
Rationale: Reliability and clarity were more valuable than flexibility for daily use.
Feedback & Iteration
What worked
- Reduced reliance on group texts
- Clear accountability for pickups
- Fairness increased trust within the group
What surfaced
- Requests for chat (intentionally deferred)
- Edge cases with club schedules
Iteration decisions
- Improved assignment visibility
- Added manual overrides
- Maintained simple scheduling logic
Outcome
The MVP validated the core problem and solution:
- Less daily coordination effort
- Clearer responsibility ownership
- Reduced stress during pickups
Key Learnings & Reflection
- Designing for failure states is critical in coordination tools
- Simplicity drives adoption for daily-use products
- Explicit non-goals strengthen product focus
- Real user feedback beats assumed needs
This project strengthened my skills in problem discovery, MVP definition, tradeoff articulation, designing under real-world constraints, and iterating based on live feedback.