Uber Eats Product Sense: Choose a User Group and Design One New Feature

You are a product manager on Uber Eats, Uber's app for ordering restaurant meals, groceries and other items for delivery. Propose one new feature for it. Choose whose experience you want to improve, explain the problem you are solving, describe how the first version of the feature works, and explain how you would measure whether it succeeds. ```hint One side, one moment Uber Eats serves the people ordering, the restaurants and stores selling, and the couriers delivering. Pick one of these groups and one moment in their journey where things go wrong today, and let that problem choose the feature rather than starting from an idea you like. ``` ### Clarifying Questions - Is there a business goal to aim at: more orders per customer, more new customers, larger baskets, more Uber One members, or keeping merchants and couriers on the platform? - May the feature serve any of the three groups (customers, merchants or couriers), or is one of them the priority? - Should we focus on one market or vertical, for example restaurant delivery in one country, or grocery orders? - Is there a time frame for the first version, such as a single quarter? ### What a Strong Answer Covers - A business goal for Uber Eats and a user group chosen with reasons, keeping in mind that the marketplace has three sides. - Specific pain points for that group at a particular step of ordering, preparing or delivering. - A few feature options, a reasoned choice among them, and a concrete description of the first version. - Success metrics plus guardrails that protect the other two sides of the marketplace. - Risks and trade-offs, including effects on merchants, couriers and the cost of each order. ### Follow-up Questions - Your feature lifts orders but lowers couriers' hourly earnings. What do you do? - How would you test the feature, given that a change for one side of the marketplace can affect the others? - If the first version works, what do you build next?