Questions › Execution › Spotify
Design a phased migration plan for Social Listening without hurting users
- Execution
- Spotify
- Medium
- 10 min
Problem Statement Description
Product context: Spotify is an audio streaming company; its products include music, podcasts, audiobooks, playlists, recommendations, creator tools, subscriptions, and ads.
Spotify is planning to migrate Social Listening, a capability used by artists and their teams to understand audience conversations, engagement signals, and discovery trends, to a new experience or platform. The migration must preserve trust for artists who depend on these insights for release planning, fan engagement, campaign decisions, and performance tracking.
Your task is to design an execution plan for this migration. Focus on how Spotify should phase the rollout, coordinate cross-functional work, minimize disruption, and ensure artists continue to get reliable, timely, and understandable signals throughout the transition.
Assume this migration affects a global artist-facing product surface and may involve changes to data pipelines, dashboards, notifications, permissions, analytics definitions, and support workflows. You do not need to design the new Social Listening product itself; the emphasis is on the migration plan and how to execute it safely.
The experience should consider:
- Which artist segments, markets, teams, or use cases should migrate first versus later
- How to sequence discovery, internal readiness, beta rollout, broader launch, and deprecation
- Owners and dependencies across product, engineering, data, design, artist relations, support, legal/privacy, and communications
- Go/no-go criteria, launch health metrics, data quality checks, and user-impact thresholds
- How to handle feature parity gaps, historical data continuity, permissions, and reporting changes
- Communication plans for artists, managers, labels, and internal support teams
- Rollback, fallback, or dual-running plans if the migration creates confusion, data loss, latency, or reliability issues
- Key launch risks, including trust erosion, misinterpreted insights, regional differences, and artist workflow disruption
The goal is to present a practical phased migration plan that protects artist experience while enabling Spotify to move Social Listening to the new system with clear accountability, measurable readiness, controlled risk, and a path to full adoption.
What this question tests
- Execution Rigor
- Prioritization
- Cross-functional Leadership
- Launch Planning
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Execution questions
- Design a phased migration plan for Social Listening without hurting users at global scaleSpotify · Execution · Hard
- Prioritize a quarterly roadmap for AdsSpotify · Execution · Medium
- Plan the MVP rollout for Audiobooks in a constrained marketSpotify · Execution · Medium
- Create a launch plan for a high-risk Creator Tools feature for commutersSpotify · Execution · Medium
- Resolve a cross-functional conflict blocking PlaylistsSpotify · Execution · Medium
- Create a launch plan for a high-risk Creator Tools feature for commutersSpotify · Execution · Easy
All Execution questions · Product manager interview questions by skill area