Questions › Root Cause Analysis › Top-MNC
Conversion is flat but engagement is up in food delivery group ordering. What is going on?
- Root Cause Analysis
- Top-MNC
- Medium
- 10 min
Problem Statement Description
Swiggy’s group ordering experience is used by office lunch coordinators who create a shared cart or ordering session, invite colleagues, collect individual meal choices, and place one combined order for delivery to the workplace. Recently, the product team has observed that engagement within group ordering has increased, but conversion has remained flat. For example, users may be opening group order flows more often, inviting more participants, browsing menus longer, or adding more items, yet the number of completed group orders is not increasing proportionally.
Your task is to investigate what could be going on. Treat this as a root-cause analysis problem, not a redesign question. You should clarify what “engagement” and “conversion” mean in this context, identify where the funnel may be changing, and reason through whether the pattern reflects a real user behavior shift, a measurement issue, operational friction, segment mix change, or marketplace constraint.
The analysis should be grounded in the realities of Indian food delivery and workplace lunch ordering: time-sensitive ordering windows, multiple participants with different preferences, restaurant availability, minimum order values, delivery batching, payment coordination, cancellations, and repeat usage by coordinators who need reliability and low effort.
The experience should consider:
- How to frame the anomaly: time period, baseline, magnitude, seasonality, and whether the issue is sudden or gradual
- Clear definitions of engagement and conversion, including numerator, denominator, and funnel stage
- Segmentation by office lunch coordinators, group size, city, restaurant type, time of day, new versus repeat groups, and corporate versus informal ordering
- Instrumentation checks for event tracking, attribution, duplicate sessions, abandoned carts, invite events, payment events, and order completion
- Hypotheses across user behavior, restaurant supply, pricing, delivery reliability, payment friction, group coordination delays, and promotion or loyalty changes
- Evidence needed to validate or reject each hypothesis, including funnel cuts, cohort trends, qualitative feedback, operational metrics, and marketplace health indicators
- Immediate mitigations versus longer-term fixes, while accounting for cost, operational load, privacy, accessibility, and trust
- Prevention mechanisms such as dashboards, alerting, data quality checks, and leading indicators for repeat group orders
The goal is to explain how you would systematically diagnose why higher engagement is not translating into higher completed group orders, identify the most likely drivers, and recommend what evidence and next actions the product and operations teams should prioritize.
What this question tests
- Root Cause Analysis
- Data Interpretation
- Prioritization
- Risk Handling
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Root Cause Analysis questions
- Diagnose a sudden drop in self-serve success for partner integration marketplaceTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in payment reliability for warehouse task plannerTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in admin confidence for customer feedback hubTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in recommendation relevance for offline order captureTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in workflow automation for compliance review queueTop-MNC · Root Cause Analysis · Medium
- Diagnose a sudden drop in revenue recovery for multi-device handoff flowTop-MNC · Root Cause Analysis · Medium
All Root Cause Analysis questions · Product manager interview questions by skill area