Swiggy Stories Feature Analysis

Candidate: That's an interesting product question. Let me break this down systematically. First, I'd want to understand what success looks like for this feature. Are we primarily trying to increase user engagement, boost order frequency, improve restaurant visibility, or drive revenue growth?

Candidate: I'd approach this with a combination of pre-launch research and a structured A/B test. For pre-launch, I'd analyze user behavior data to identify engagement patterns - like how users currently discover new restaurants, time spent browsing vs. ordering, and whether visual content correlates with order decisions.

Candidate: Excellent point. I'd start with user research - surveys and interviews to understand current pain points. Questions like: "How do you currently decide what to order?" and "What additional information would help you choose restaurants?" I'd also analyze existing engagement with restaurant photos and descriptions to see if visual content already correlates with conversions.

Candidate: With mixed signals, I'd design a targeted A/B test. I'd segment users based on their ordering behavior - frequent orderers vs. browsers, new users vs. loyal customers. The hypothesis would be that the Stories feature benefits users who spend more time discovering food rather than those who have established ordering patterns.

Candidate: I'd establish both leading and lagging indicators.

• Leading indicators: Story views per session, time spent viewing stories, click-through rate from stories to restaurant pages, story completion rates.
• Lagging indicators: Order frequency, average order value (AOV), user retention, and restaurant discovery rate (orders from previously unordered restaurants).

For isolation, I'd run the test for at least 4 weeks to account for weekly patterns, ensure balanced exposure to promotions and seasonal effects between control and treatment groups, and use statistical techniques like difference-in-differences if there are concerns about external factors that can't be perfectly controlled by randomization.

Candidate: That's a critical risk I'd monitor closely. I'd track the conversion funnel: Stories views → Restaurant page visits → Add to cart → Completed orders. If I see increased top-funnel engagement but decreased conversion rates, I'd investigate whether:

1. Users are getting decision paralysis from too many options.
2. The Stories content is entertaining but not purchase-driving.
3. The feature is inadvertently slowing down the core ordering process.

I'd also segment the analysis by user intent if possible – are users explicitly looking for discovery different from those with a known meal in mind?

Candidate: For restaurants, I'd track both engagement and business metrics.

• Engagement: Story creation rate by restaurants, views per story posted by restaurants, follower growth for restaurant profiles (if applicable).
• Business metrics: Increase in orders for restaurants actively using Stories (especially from new customers attributed to Story views), and overall restaurant satisfaction surveys.

I'd also measure retention rates of restaurants actively using Stories vs. those who don't, to see if it improves partner loyalty.

Candidate: Great question. I'd segment restaurants by categories: quick service vs. premium dining, cuisine types, visual appeal of food, and perhaps their existing marketing sophistication. I suspect restaurants with highly photogenic food or unique preparation processes might benefit more. If the data shows uneven benefits, I might recommend a phased rollout – starting with restaurant categories that show the strongest positive impact, then gradually expanding while improving the feature based on learnings to better suit other segments.

Candidate: I'd build a comprehensive ROI model considering both costs and benefits.

• Costs: Development time (engineering, design, QA), ongoing maintenance, content moderation (manual and automated tool costs), customer support related to the feature, infrastructure scaling.
• Benefits: Incremental revenue from increased order frequency & AOV (attributed from A/B test), potential reduction in customer acquisition costs if organic engagement and discovery improve, and possibly new revenue streams like promoted stories in the long term.

I'd also try to qualitatively assess long-term strategic value – does this feature help Swiggy compete with other platforms or create a stronger moat around restaurant relationships? The ROI calculation would compare the monetized benefits against the costs over a defined period.

Candidate: That's a significant operational challenge and risk. I'd propose a multi-layered approach to content moderation:

1. Automated screening: Using image recognition and text analysis for obvious violations (nudity, profanity, hate speech).
2. Community reporting: Easy-to-use flagging mechanisms for users with quick review protocols.
3. Restaurant education & guidelines: Clear content policies and best practices provided to restaurants.
4. Graduated penalties: Warnings, temporary suspension of Story feature access, up to permanent ban for repeat or severe offenders.
5. Human review team: For borderline cases and appeals, potentially outsourced or scaled based on volume.

I'd track moderation costs very closely against the feature's benefits. If moderation becomes prohibitively expensive or ineffective, we might need to consider restricting the feature to verified or highly-rated restaurants, or even re-evaluating its viability.

Candidate: This is a nuanced decision, as the engagement metrics are positive, but the direct impact on core business (orders) is marginal and not statistically significant in the short term. Before making a final recommendation, I'd want to investigate further:

• Cohort analysis: Are new users or specific segments (e.g., high-discovery users) showing a more significant lift in orders that's being diluted by other segments?
• Long-term impact: Does the increased discovery (25%) lead to higher customer lifetime value (LTV) over a longer period, even if immediate orders aren't up significantly? We might need to track cohorts for a longer duration.
• Qualitative feedback: What are users and restaurants saying about the feature? Is it perceived positively despite the low order lift?
• Strategic importance: Is this a "table stakes" feature to remain competitive, or does it offer a unique differentiator?

If further analysis suggests strong long-term potential, positive impact on specific valuable segments, or high strategic value, I might recommend a limited launch (e.g., to certain user segments or restaurant types) with continued iteration and monitoring. If the additional investigation doesn't reveal a clearer path to significant business value, I'd be cautious and might recommend pausing a full rollout to focus resources on initiatives with a more direct and measurable ROI. The key is to balance the promising engagement signals with the current lack of direct, significant business impact.

Candidate: One area I could have delved deeper into is the potential impact on Swiggy's delivery operations. If Stories significantly shift order patterns (e.g., more orders from restaurants further away or less popular ones), it could affect delivery times, costs, and delivery partner satisfaction. This would be another important aspect to monitor. Additionally, while I mentioned segmenting restaurants, I'd also consider if the feature creates an unfair advantage for restaurants with better marketing capabilities or resources to create high-quality stories, potentially disadvantaging smaller, local establishments that are also key to Swiggy's ecosystem. Ensuring a level playing field or providing tools/templates could be important.