Blinkit · Product sense · Entry · 45 to 60 minutes
Should Blinkit handle hospital orders differently?
Blinkit is an Indian quick commerce app that delivers groceries and household essentials in about 10 to 25 minutes. Answer this product management case and get it graded line by line against a weighted rubric.
- Product sense
- User empathy
- Prioritization
- Experimentation
- Metric design
The situation
You are a PM on Blinkit's consumer ordering experience team. The team has noticed that some orders are being placed to hospitals, where users may be patients, caregivers, or family members trying to get food or essential items quickly during a stressful moment. Today, Blinkit treats these orders like any other order. Leadership has asked you to review whether Blinkit should do something different for this context. Why now: quick commerce is crowded, Blinkit already competes strongly on speed, and the company wants to build stronger loyalty and differentiation through the product itself, not only through marketing. The tension is that any special treatment could help users in a vulnerable situation, but it could also slow down other customers, raise fairness questions, create privacy discomfort if Blinkit appears too aware of location, or add operational complexity to stores and delivery partners. You need to recommend whether Blinkit should act, what user problem is worth solving, and how to test the idea without harming the core fast delivery experience.
What to produce
Write a 1 to 2 page product brief.
Your answer must
- Define the target user and the specific problem Blinkit should or should not solve for hospital-context orders.
- Present at least two product options, including a do nothing option, and recommend one with clear reasoning.
- Explain the key tradeoffs, especially impact on other users, fairness, privacy, and misuse risk.
- Propose success metrics and guardrail metrics for both user experience and operations.
- Outline a simple experiment or rollout plan that could validate the idea before broad launch.
Constraints
- Do not assume major changes to rider workflows or store operations.
- Rely mainly on data Blinkit already has in the ordering flow, such as delivery location and order context.
- Your plan must protect Blinkit's core promise of fast delivery for the broader user base.
Format
Use short sections with headings: problem, options, recommendation, metrics, experiment, risks.
How Blinkit actually played it
Uses one small moment, Blinkit prioritising an order placed from a hospital with a kind message, to discuss empathy in product design. Ties it to differentiation, loyalty and awareness.
- Context-aware touches can build loyalty at low cost
- Use data you already have to show care
- Small details can be the story users share
Built from Blinkit Did Something That India Is Loving (And It Is Not Fast Delivery) by Sid Arora (JAPM).
Related case studies
- Fix damaged item support on BlinkitBlinkit · Product sense · Entry
- Spotify, Improve Repeat Podcast ListeningSpotify · Product sense · Mid
- Airbnb monthly stays experienceAirbnb · Product sense · Senior
- Google Maps EV Road Trip PlanningGoogle Maps · Product sense · Mid
- Help new graduates land a first job on LinkedInLinkedIn · Product sense · Entry
- Duolingo for a learner with a trip in four weeksDuolingo · Product sense · Entry