I went straight into features without anchoring on who the user actually is, which I regret.
Start by clarifying the goal of restaurant discovery (e.g., helping users find the right restaurant quickly) and the key user segments (e.g., new users, repeat users). Then, map the current discovery journey, identify pain points, and prioritize improvements based on impact and feasibility. Finally, propose specific features or changes, and define success metrics.
Pro tip: Anchor your answer in Zomato's business model: discovery improvements should drive both user satisfaction and restaurant partner value (e.g., more orders, better matching). Also, consider the Indian market context, such as tier-2 city expansion and vernacular support.
Define what 'improve' means: increase conversion, reduce search time, or enhance personalization? Also, clarify which user segment (new vs. existing) and platform (mobile app) to focus on.
Identify key user needs (e.g., quick decisions, trust, variety) and current pain points (e.g., overwhelming options, irrelevant results, lack of context). Use data or assumptions to support.
Generate ideas across the discovery funnel (search, browse, recommendations) and prioritize using a framework like RICE or impact/effort. Focus on high-impact, feasible ideas.
Propose metrics to measure improvement, such as click-through rate, conversion rate, time to order, or user retention. Tie them to business goals.
Recap your top recommendation, expected impact, and how you would validate it (e.g., A/B test).
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.