Grab · Product sense · Mid · 45 to 60 minutes

How should Grab serve grocery shopping?

Grab is a Southeast Asian superapp that offers ride hailing, food delivery, payments, and other on demand services. Answer this product management case and get it graded line by line against a weighted rubric.

Product sense
Prioritization
User insight
Metrics
Platform thinking

The situation

It is early 2020 and you are the PM responsible for a small pilot that lets people order groceries and daily essentials through Grab. The team started testing the concept in Malaysia and Singapore before COVID-19, but demand for home delivery is now rising much faster as social distancing restrictions spread across the region. Leadership sees a chance to help consumers quickly, but they do not want to overbuild before they understand the real use case. Right now the pilot rides on the existing GrabFood experience. Early feedback shows friction. Some shoppers struggle to find specific items, because the flow is oriented around browsing merchants rather than shopping for products. Some drivers are caught off guard by larger retail orders, because these orders look similar to food jobs. Merchants are also adapting to a different prep and fulfillment pattern than restaurants. Your regional product lead asks you for a recommendation on the next product direction for the next two quarters. Assume you have basic funnel data, support tickets, and feedback from merchants and drivers, but only a short history of usage.

What to produce

Write a 1 to 2 page product recommendation memo.

Your answer must

Identify the primary user needs and jobs to be done for this service, and explain how they differ from food delivery.
Diagnose the 2 to 3 most important product problems in the current pilot for consumers, merchants, and drivers.
Present 2 to 3 strategic options for the next two quarters, compare their trade offs, and recommend one.
Define the MVP scope and sequencing for the next release or releases, including what you would build now versus defer.
Specify success metrics and guardrail metrics that would tell Grab whether the direction is working.

Constraints

You should reuse existing Grab platform capabilities where possible, because speed matters and engineering capacity is shared with other businesses.
You cannot assume a brand new logistics network, a separate app, or a long implementation timeline before users need the service.
The solution should be able to expand across multiple Southeast Asian markets with different shopping habits and delivery expectations.

Format

Use sections such as users and needs, key problems, options, recommendation, MVP scope, metrics, and risks.

How Grab actually played it

The product team behind GrabMart explains how a pandemic-era need for groceries and essentials led to a new service built quickly on top of the GrabFood platform. After weekly growth of around 50 percent, the team redesigned the experience around how people actually shop for a mart. It is a good example of reusing a platform to test a new category, then investing once demand is proven.

Launch a new vertical on existing rails first, redesign after demand shows up.
Rapid growth is the signal to rebuild the experience for the real use case.
Cross-functional teams formed around a single customer need ship faster.

Built from The GrabMart Journey by Grab Engineering.