Practice a comprehensive Spotify product improvement case covering product taste, target users, North Star metrics, Smart Offline Mode, roadmap prioritization, experiments, guardrails, and stakeholder alignment. The solution emphasizes quality-adjusted listening, offline pain points, MVP scope, and cross-functional execution.
##### Question
Select a product you use frequently.
Explain why you like it and who its target users are.
State the product’s primary goal and the north-star metric.
Propose one new feature or major improvement and articulate the user problem it solves.
Walk through how you would design, build, and prioritize this feature within the roadmap.
Define the success metrics and any experiments you would run.
List the cross-functional partners you’d engage and how you would persuade key stakeholders to back your proposal.
Quick Answer: Practice a comprehensive Spotify product improvement case covering product taste, target users, North Star metrics, Smart Offline Mode, roadmap prioritization, experiments, guardrails, and stakeholder alignment. The solution emphasizes quality-adjusted listening, offline pain points, MVP scope, and cross-functional execution.
hardProduct ManagerOnsiteProduct / Decision Making
13
0
Product Case Prompt: Comprehensive Product Improvement Drill
Use Spotify, a music and podcast streaming app, as the reference product. Assume it serves free and paid users across mobile and desktop, with strong personalization and on-device playback.
Answer:
Select a product you use frequently and explain why you like it.
Describe the target users.
State the product's primary goal and North Star Metric.
Propose one new feature or major improvement and explain the user problem it solves.
Walk through how you would design, build, and prioritize this feature within the roadmap.
Define success metrics and experiments.
List cross-functional partners and how you would persuade stakeholders to support the proposal.
Constraints & Assumptions
Use Spotify unless you explicitly choose another product.
Tie the improvement to a real user problem and measurable outcome.
Include target users, MVP scope, prioritization, experiment design, and trade-offs.
Avoid proposing a feature that only increases time spent without improving satisfaction.
Clarifying Questions to Ask Guidance
Should I focus on music, podcasts, audiobooks, creator tools, or paid subscription growth?
Is the goal engagement, retention, premium conversion, user satisfaction, or cost reduction?
Which platforms and markets are in scope?
Are offline playback, personalization, and licensing constraints relevant?
Part 1 - Product, Users, Goal, and North Star
Select the product, explain why you like it, define target users, and state the primary goal and North Star Metric.
What This Part Should Cover Guidance
Product strengths and user value.
Target user segments and jobs to be done.
North Star Metric that reflects quality-adjusted long-term value.
Guardrails such as churn, skips, complaints, battery/data usage, and creator or rights-holder impact.
Part 2 - Feature Proposal and Roadmap
Propose a feature or improvement and explain how you would design, build, and prioritize it.
What This Part Should Cover Guidance
User problem, hypothesis, MVP, user flow, edge cases, and trade-offs.
Prioritization using reach, impact, confidence, effort, and strategic fit.
Roadmap phases and launch plan.
Part 3 - Metrics, Experiments, and Stakeholders
Define success metrics, experiments, partners, and stakeholder persuasion plan.
What This Part Should Cover Guidance
Primary, secondary, and guardrail metrics.
A/B test or phased rollout.
Partners across design, engineering, data science, ML, content/licensing, marketing, legal, privacy, and support.
Stakeholder narrative based on user pain, business impact, and risk mitigation.
What a Strong Answer Covers Guidance
A strong answer demonstrates product taste, clear user segmentation, a well-defined North Star, focused MVP design, experiment discipline, and the ability to align cross-functional partners around a measurable roadmap bet.
Follow-up Questions Guidance
Why is your North Star better than total listening time?
What would make you kill the feature?
How would the feature differ for free and paid users?
What licensing or content constraints matter?
How would you prevent the feature from hurting discovery diversity?