Sonos · Execution · Mid · 45 to 60 minutes

Should Sonos launch its rebuilt app now?

Sonos makes wireless home audio products that customers control through a mobile app. Answer this product management case and get it graded line by line against a weighted rubric.

Execution
Prioritization
Risk management
User empathy
Stakeholder communication

The situation

You are the PM for the Sonos mobile app experience. Engineering has spent months rebuilding the app largely from scratch to improve the foundation for future development and refresh the user experience. Leadership now wants a recommendation on whether to launch the new app to all customers in the next release window. The pressure is real. The current app is aging and harder for the team to evolve. The rebuilt app is usable in many common flows, but some legacy capabilities are still not fully matched, and quality signals are mixed. Internal stakeholders disagree on what is acceptable for launch. Engineering argues the new foundation is strategically important. QA is worried that limited external testing may not reflect the variety of real home setups, speakers, and usage patterns Sonos customers have. Marketing and support teams need clarity soon so they can prepare customer messaging. Your job is to recommend a launch approach that balances speed, product quality, customer trust, and the long term need to move off the older app architecture.

What to produce

Write a 1 to 2 page launch recommendation memo.

Your answer must

State a clear recommendation on whether to launch now, delay, or use a phased rollout, and explain why.
Define what feature parity means for this release, including which customer jobs or app capabilities are must have before broad launch and which can follow later.
Propose a testing and validation plan that addresses the risk of limited beta coverage across real customer environments.
Describe a rollout and contingency plan, including how you would monitor quality after release and what would trigger a pause, rollback, or hold on expansion.
Include a customer communication plan for both the launch and the possibility that important issues emerge after release.

Constraints

You cannot assume the team can support the old and new app experiences in parallel for an extended period.
The app controls physical audio products used in many different home network and device setups, so failures can quickly affect core customer use.
You have incomplete information from beta feedback and cannot run a long, large scale test before the next release window.
Public expectations for the redesign are already being set, so silence or a vague message is not a good option.

Format

Use short section headings and concise bullets where helpful.

How Sonos actually played it

LeadDev examines the 2024 Sonos app relaunch, a from-scratch rebuild that shipped with bugs and missing features despite heavy hype. It draws on comments from product and quality leaders about testing, scope and communication. A cautionary case for anyone planning a full rewrite.

A rewrite from scratch must reach feature parity before launch
Thin beta testing lets serious bugs reach customers
Communicate quickly and honestly when a launch goes wrong

Built from What went wrong at Sonos? And what can we learn from a disastrous app redesign? by Chris Stokel-Walker.