Choosing Which Features to Build for a Grocery App

You are a product manager working on a grocery app. What features would you propose for it? Explain which customers they are for and which ones you would build first. ```hint Follow one shopper's cycle Pick one kind of shopper and trace a full grocery cycle, from noticing something has run out to putting the delivered order away, before you list any features. ``` ### Clarifying Questions - Is this the app of one grocery chain, or a service that orders from many stores? - Does it cover delivery, pickup, help while shopping in the store, or all three? - Is the app new, or an existing one that needs to grow, and which outcome matters most: new customers, more frequent orders or bigger baskets? - Is the work limited to the customer app, or can changes reach the shoppers and drivers who fulfill orders? ### What a Strong Answer Covers - The app's scope and the goal the new features serve, settled first - Customer segments compared, with one chosen and the reason - Pain points from that segment's grocery cycle, ranked by severity - Features tied to those pains and prioritized with explicit criteria, with a clear first release - A primary metric with guardrails, including effects on the people and stores that fulfill orders ### Follow-up Questions - What result from a pilot would make you drop your top feature? - How would your list change if the app belonged to a single grocery chain rather than ordering from many stores? - How would you handle items that turn out to be out of stock when the order is picked?