Questions › Execution › Top-MNC
Plan the MVP launch for restaurant discovery and review trust while balancing user trust, growth, and operational load
- Execution
- Top-MNC
- Medium
- 10 min
Problem Statement Description
Zomato wants to launch an MVP that improves restaurant discovery and review trust for urban diners with dietary constraints, such as vegetarian, vegan, Jain, gluten-free, allergy-sensitive, or religious dietary needs. These users often struggle to determine whether a restaurant is truly suitable for them because reviews may be vague, menus may be outdated, sponsored placements may reduce perceived neutrality, and restaurant-provided information may not always be reliable.
You are asked to plan the MVP launch, not design the full product solution. The launch must balance user trust, booking and order conversion, restaurant participation, and the operational load required to verify or maintain trustworthy information. Assume this is a Zomato environment with discovery, reviews, ratings, menus, ads, delivery, and table booking surfaces already in place.
Your plan should define how the MVP is scoped, sequenced, staffed, monitored, and rolled out safely. It should account for dependencies across product, engineering, design, data science, moderation, sales/account management, restaurant operations, customer support, legal/privacy, and marketing.
The launch plan should consider:
- MVP scope: which diner needs, restaurant categories, cities, and discovery surfaces are included first
- Owners and dependencies across product, engineering, data, review moderation, restaurant operations, and go-to-market teams
- Data readiness, review quality, restaurant data freshness, and how trust-related signals will be maintained after launch
- Sequencing of build, internal testing, pilot launch, restaurant onboarding, user rollout, and post-launch iteration
- Go/no-go criteria, including trust signal accuracy, user comprehension, conversion impact, complaint rate, and operational capacity
- Rollback or mitigation plans if users lose trust, restaurants dispute information, abuse increases, or conversion drops
- Communication plans for diners, restaurants, support teams, and internal stakeholders
- Launch risks around sponsored ranking pressure, privacy, accessibility, moderation cost, and scalability
Your goal is to present a practical MVP execution plan that shows how Zomato can launch this trust-focused restaurant discovery experience in a controlled, measurable, and operationally sustainable way while improving confidence for diners with dietary constraints.
What this question tests
- Execution Planning
- Prioritization
- Cross-functional Trade-offs
- Launch Management
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 Execution questions
- Decide what to cut from a delayed subscription billing launchTop-MNC · Execution · Medium
- Handle conflicting stakeholder asks for personal finance dashboardTop-MNC · Execution · Medium
- Prioritize the roadmap for developer platform with limited engineering capacityTop-MNC · Execution · Medium
- Plan an MVP rollout for search and recommendations without disrupting existing usersTop-MNC · Execution · Medium
- Create a launch plan for data export tool aimed at improving operational efficiencyTop-MNC · Execution · Medium
- Decide what to cut from a delayed appointment booking launchTop-MNC · Execution · Medium
All Execution questions · Product manager interview questions by skill area