A ride for you.
Peace of mind
for them.

The first release let members book their own rides from their own accounts. A family admin could pay through a shared payment method, follow the ride and receive updates. A group chat connected the admin, the rider and the driver.

This changed the design problem. It wasn't just a booking flow anymore. It was a relationship: who can see the journey, who pays for it, and what each person understands before they agree.

Make the first invitation easy.
Leave room for the rest.

We started with a multiple-contact invitation flow. After alignment with design leadership, we narrowed the MVP to getting the first member invited and the family created. When the CX team raised concerns, Razil and I worked through the fuller multi-invite option too. Comparing both helped the team align on the simpler release.

The important detail was underneath the screens: both approaches used compatible Duxton components. A list item could become a checkbox row later. A smaller first release would not force engineering to rebuild the foundation.

The shareable-link idea came from Alex Hungate during WPC. It addressed two needs together: inviting multiple people and helping users who were uncomfortable giving access to their contacts. That distinction matters to the story: my design contribution was in evaluating the paths and making the system adaptable; the idea grew through the team.

The MVP assumed a family member could make their own booking. BoBo addressed the next situation: someone else needs to do it for them. A parent. An older relative. A loved one who needs a hand.

The central design challenge was keeping the actual passenger connected. Booking, payment and coordination might begin on the helper's phone. Access to the ride and its safety features also needed to reach the person in the car.

Safety follows the passenger.

The admin gets the tools to arrange and follow the journey. The family member gets the booking in their own app, a direct connection to the driver and access to safety features. The driver needs to understand who the booking is for.

That last perspective is why this case study starts inside the car. A family product is also a driver product. The job card, contact choices and group conversation need to make a three-person situation understandable at a glance.

The third chapter was about independence. Teens want to get to school, meet friends and make everyday plans. Parents want to know that the right car arrived and that help is within reach.

Teens brought age-specific needs into the Family Account foundation: parent-led setup, ride visibility, additional safeguards and a more explicit moment of trust at pickup.

Before the journey,
a small exchange of trust.

The driver provides a Ride PIN. The teen enters it on their own phone to verify the match. The direction is intentional: the passenger is actively confirming the vehicle they are about to ride in.

The working deck compares both PIN directions. For the initial release, the recommended teen-enters-PIN approach reused existing GrabNow-related capability, accepting additional passenger friction to reach families sooner.

It sits within a broader set of safeguards. Grab's launch materials describe prioritised assignment to top-rated drivers, AudioProtect enabled by default for teen rides, and automatic ride updates for the family admin. Availability and age rules vary by market.

The parents and teens
didn't always agree.

In January 2025, six parents and six teens took part in paired remote interviews in Singapore. The teens already used Grab independently at least weekly. This was a focused qualitative study, not a measure of every family's needs.

When asked about a version without the Ride PIN, four of the six parents would still consider the service. Most of the teen participants wanted to keep the PIN. The person being reassured and the person taking the risk did not necessarily value the same safeguard.

The report recommended retaining the PIN. It also showed that reducing friction isn't always the same as removing information: teens welcomed more explanation when it was paced one idea at a time.

Across these releases, a single-rider model became a system of connected roles. First, a family could share payment and follow a ride. Then a helper could book while the passenger stayed connected. Finally, teens could take a more independent journey with safeguards around them.

The measurable public record is the release history and regional expansion. Internal adoption and experiment results are preserved in the private research catalogue; this case study does not turn them into unsupported public claims.