Choose a Zomato app feature to retire or rebuild and justify the call

As a product manager at Zomato, pick one feature in the existing app that you would either retire or redesign. Explain which feature you chose and why, whether you would sunset it or rebuild it, what the removal or the new version looks like, and how you would confirm that the decision was right. ```hint Decide what failing means Before naming a feature, settle what the change should achieve and what usage evidence would show that a feature is not earning its place. Then test your candidate against that evidence. ``` ### Clarifying Questions - What should the change achieve: a simpler app, more completed orders, lower upkeep for the team, or something else? - Is every part of the app in scope, including dining-out features, or only the food ordering experience? - Can I assume access to feature usage data, or should I reason from the app as a customer sees it? ### What a Strong Answer Covers - A goal for the change and explicit criteria for choosing a feature, such as reach, effect on orders, upkeep cost and strategic fit - A specific Zomato feature with a diagnosis of why it underperforms, framed as hypotheses to check against data - A justified choice between removing and rebuilding, accounting for the users and restaurants that depend on the feature - A concrete plan for the redesign or the removal, including what happens to existing users - Success metrics, guardrails and a staged rollout with a way to reverse the change ### Follow-up Questions - Usage data shows the feature reaches few people, but those who use it order much more often than average. Does that change your decision? - Restaurants or internal teams that rely on the feature push back. How do you handle it? - How would you design an experiment that decides between sunsetting and redesigning?