Flipkart · Execution · Mid · 60 to 90 minutes

Flipkart sale event readiness for core shopping

Flipkart is an Indian ecommerce marketplace where customers buy products across categories like electronics, fashion, grocery, and home goods through its app and website. Answer this product management case and get it graded line by line against a weighted rubric.

Prioritisation
Metric design
Execution planning
Risk management
Cross-functional alignment

The situation

You are the PM for Flipkart's core shopping journey on Android app and mobile web, covering home discovery, product detail, cart, checkout entry, and order confirmation. The Director of Product and the engineering lead have asked you for a sale readiness plan for Big Billion Days. Assume the following numbers for this case: in the first 6 hours of last year's event, sessions hit 5 times a normal peak, app crash rate rose from 0.4% to 2.1%, product page load time went from 2.8 seconds to 6.4 seconds, checkout success dropped from 91% to 83%, and customer contacts about orders placed but not visible in My Orders doubled. This year, commercial teams want more promotional modules, richer media, and tighter countdown mechanics because sale traffic and ad commitments are higher. Engineering is warning that the current stack has little room for extra complexity, and there are only 8 weeks left before code freeze. Your job is to decide what product changes, protections, and launch gates are needed so Flipkart can handle the spike without hurting customer trust or revenue.

What to produce

A 1 to 2 page product readiness plan.

Your answer must

Define the 3 to 5 user journeys that must be protected during the sale, and explain why they matter most for customers and the business.
List the core metrics you would use for readiness and event health, with a baseline, target, and guardrail for each.
Provide a prioritised plan with must do, should do, and will not do before the event, including clear tradeoffs between new sale experiences and reliability work.
Lay out an execution timeline from now to event day, including testing, launch gates, decision owners, and rollback criteria.
Identify the main cross functional dependencies and top risks, and explain how you would handle them before and during the event.

Constraints

There are 8 weeks until the sale, and a code freeze starts 7 days before the event.
You can use only the existing Core Shopping, Platform, and Analytics teams, no new headcount.
You may change Android app and mobile web experiences, but you cannot redesign the payments stack or warehouse systems before this event.
Budget is fixed for the quarter, so proposals should rely mostly on reprioritisation rather than major new vendor spend.

Format

Structure the answer as goals, metrics, priorities, plan, and risks. Be explicit about what you would not ship before the sale.