Request
A user enters the coordination flow through the mobile product.
02 · Mobile · Ride coordination · Registered charity
Designing a ride system nontechnical teams can operate.
I led zero-to-one product and engineering work for a ride-coordination platform. Discovery with low-technology-literacy users shaped a dispatch experience that reduced administrative work and supported live ride operations.
500+active users in British Columbia
20 hrsadministrative work saved weekly
iOS + Androidlive release ownership
The human constraint
A system is not operationally successful if staff need engineering to run it.
The product needed to coordinate rides while remaining usable for people with different levels of technical confidence. Administrative work was consuming roughly 20 hours each week, so usability was an operational capacity problem, not a cosmetic concern.
I conducted discovery with low-technology-literacy users, translated findings into the dispatch workflow, built custom operations dashboards, integrated the ride-provider API, and managed releases across both major mobile platforms.
Live organization
The product operates inside a real charity serving youth and families.
get2thr.org is live
Safe transportation for youth and families.
The public organization site provides the service context behind the operational platform: pre-scheduled, safety-vetted transportation that helps young people reach approved activities.
Visit Get2Thr!Service journey
The experience had to keep the user, operations team, and live ride state aligned.
Manage
Nontechnical operations staff handle bookings from a purpose-built dashboard.
Book
The URide integration enables vehicle booking inside the application.
Track
Live status information keeps the ride state visible without a separate workflow.
What I prioritized
Reduce coordination cost without removing human oversight.
EvidenceProduct responseWhy it mattered
Low technology literacySimplified dispatch workflowUsability under real operational pressure
20 admin hours each weekCustom operations dashboardMore capacity without engineering support
Live ride coordinationURide booking and status integrationOne connected operating experience
Execution
Product ownership continued after the feature was built.
The work crossed product design, external API integration, operations tooling, and mobile release management. I handled deployment to the App Store and Google Play, keeping responsibility connected from discovery through live release.
Public case study note
The public organization and service context are linked above. User identities, internal operations screens, and confidential ride data are intentionally omitted.
What this changed in my product practice
“For operational products, accessibility is capacity: every confusing step becomes more administrative work somewhere else in the system.”
My next measurement layer would separate time saved by workflow stage, then pair it with support requests and task completion so the team could see exactly where product improvements created operational leverage.