Blinkit · Product sense · Entry · 45 to 60 minutes

Fix damaged item support on Blinkit

Blinkit is a quick commerce app that delivers groceries and everyday items from nearby dark stores in minutes. Answer this product management case and get it graded line by line against a weighted rubric.

product sense
prioritization
metrics
user empathy
tradeoff judgment

The situation

You are a PM on Blinkit's consumer product team, focused on the experience after an order is delivered. The team believes speed is Blinkit's biggest advantage, but recent user research shows that when something goes wrong, especially damaged or missing items, trust drops fast. Customers can raise an issue in the Help section, often by uploading a photo, but resolution can feel slow and uncertain compared with the promise of instant delivery. Support says these cases create repeat contacts and frustration. Growth says this may be hurting repeat usage and word of mouth. Operations warns that making refunds too easy could increase abuse and eat into thin margins. Leadership wants a clear recommendation for the first product change to improve this part of the journey without slowing down fulfillment or adding a large manual support burden. Your job is to define the problem, pick a target user need, and propose the best first improvement to the damaged item resolution flow.

What to produce

Write a 1 page product brief, 600 to 800 words.

Your answer must

Define the user problem clearly, including when in the journey it happens and why it matters for Blinkit's habit loop.
Choose one primary user segment or use case to optimize for, and explain why you are narrowing scope that way.
Propose one main product change to the damaged item support flow, with a simple user flow and the key tradeoffs.
Specify a success metric framework, including one north star for this problem and at least three supporting metrics that capture speed, trust, and business risk.
Explain how you would validate the idea, including one experiment or rollout plan and one key abuse or edge case to watch.

Constraints

Do not change Blinkit's core promise of very fast delivery or rely on slower replacement logistics as the primary fix.
Assume no large increase in human support headcount in the near term.
Your proposal should work within existing app surfaces such as order details, help, chat, and notifications.
You may not solve this by offering full refunds for every complaint without any controls.

Format

Use short section headers such as problem, target user, proposal, metrics, risks, and validation.

How Blinkit actually played it

Looks at Blinkit's 10-minute delivery model with dark stores, the user journey, strengths and improvement ideas.

Speed is a product feature backed by operations
Map the journey to spot friction
Pair every critique with a suggestion

Built from Blinkit Product Teardown: Deconstructing the Quick-Commerce Machine by Prod Lab.