Goal-Driven Feature Prioritization: Ranking a Roadmap for a Product You Know

Pick a product you know well and explain how you would decide which new features to build for it next. ```hint Anchor on one goal A ranking only means something relative to a goal. Name the outcome the product most needs over the planning period before you list any features, then compare candidates on how far they move it and what they cost. ``` ### Clarifying Questions - Can the product be one of Coinbase's own, such as the retail app for buying and holding crypto or the self-custody wallet, or should it be a product from outside the company? - Do you want the process I would run as the product's PM, the ranked list it produces, or both? - Is there a company goal I should prioritize against, such as growth, revenue or trust, or should I propose one? - Should I plan for the next quarter or the next year? ### What a Strong Answer Covers - A product the candidate knows well, with its users, business model and the single goal this round of planning serves. - Candidate features drawn from evidence about one chosen segment's pain points rather than from a wish list. - A transparent scoring method covering impact, reach, confidence and effort, applied to concrete candidates and ending in a ranked list. - How work the scoring cannot judge fairly is handled: security, compliance, reliability and commitments already made. - Success metrics for the top choice, and when and how the ranking gets revisited. ### Follow-up Questions - Your top-ranked feature depends on another team's work that will take a full quarter. How does your plan change? - An executive asks for a feature that scored near the bottom of your list. How do you respond? - How would your priorities shift if the product's market turned sharply down and usage fell?