When the Music
Stopped
How Sonos shipped a major app rewrite that removed or degraded core features, broke accessibility, and cost the CEO his job. A PM framework for how the migration should have been managed.
The Problem
On May 7, 2024, Sonos released a major rewrite of its mobile app, in part to prepare for its upcoming Ace headphones. The new app removed or significantly degraded core features that customers depended on daily: sleep timers, alarms, queue management, local music library access, and playlist editing. Accessibility for blind and visually impaired users was effectively broken. Because Sonos did not support reverting to the old app and backend changes were tied to the new release, customers effectively had no official rollback path.
"I have 23 Sonos zones in my house. The moment I downloaded the app, everything fell apart. Music cuts out, unable to play, app takes forever to load."
— Representative composite, based on Sonos Community forum posts
"The new app was not accessible at all, despite assurances from the company prior to the update that the app would have basic accessibility features."
— Representative composite, based on reports from blind Sonos users
Quotes are anonymized composites derived from public Sonos Community forum posts, edited for brevity and clarity.
What Went Wrong: Failure Taxonomy
Business
Context
Sonos was a beloved premium audio brand with over 16 million active households, according to its investor materials. The app rewrite wasn't a design failure in isolation. From a process perspective, this case suggests it was the result of tying an immovable hardware timeline to a flexible software rewrite, likely compressing QA for a highly complex release, and sidelining internal warnings from people closest to the product.
Financials
FY2024 revenue: $1.518B. FY2025 revenue: $1.443B (-5% YoY). App disaster caused an estimated $100M revenue hit. Sonos pledged $20-30M for app recovery. Executive bonuses suspended Oct 2024 to Sep 2025. Two hardware launches delayed.
Leadership Fallout
CEO Patrick Spence fired January 2025. Tom Conrad (Pandora co-founder, Sonos board member) became interim CEO. 12% workforce reduction announced February 2025. Conrad: 'This year we've let far too many people down.'
Legal Exposure
Multiple proposed class-action lawsuits filed in 2025 (Blair et al., Goodrow v. Sonos). Allegations: breach of contract, violations of Computer Fraud and Abuse Act, California False Advertising Law. Mass arbitration campaign organized via ClassAction.org.
Recovery Efforts
Public Trello board for feature tracking (later retired). 7 commitments plan (Oct 2024): Customer Advisory Board, extended warranties, quality ombudsperson. As of March 2026, some features still not fully restored (Android notification controls took ~2 years).
The Disaster Timeline
The Safe
Migration
This case study proposes the migration framework Sonos should have used. The core principle: never ship a platform rewrite that removes functionality users depend on, and always preserve a rollback path. A phased migration with feature parity gates, accessibility-first QA, and decoupled hardware/software timelines could have significantly reduced the severity of this crisis.
Feature Parity Scorecard
Before any migration, audit every feature in the existing app. Assign priority tiers (P0/P1/P2). Block launch until all P0 features pass QA. Sleep timers, alarms, and queue were P0.
Parallel App Strategy
Run old and new apps simultaneously. Let users opt into the new version while maintaining the legacy app. Deprecate legacy only after 90%+ voluntary migration.
Accessibility Gate
No launch without passing WCAG 2.1 AA and platform-specific accessibility audits (VoiceOver, TalkBack). Include blind/low-vision beta testers in every sprint.
Decouple Hardware + Software
Ship the Ace headphones with the existing app. Let the new app mature independently. Hardware dates should never dictate software readiness.
Progressive Rollout
New app to 5% of users first, then 25%, then 50%, then GA. Each gate requires meeting quality metrics: crash rate <0.5%, feature parity ≥95%, NPS ≥baseline.
Transparent Recovery Dashboard
If issues arise, publish a live status board (not a Trello board that gets retired). Weekly video updates from the PM lead. Never close forum threads while active.
Before → After
RICE Scoring
Product Requirements
Sonos shipped a major app rewrite that removed or significantly degraded core features, broke accessibility, and offered no official rollback path. The result: approximately $500M in lost market cap, 30K+ customer complaints, multiple proposed class-action lawsuits, and the departure of the CEO.
Establish a platform migration framework ensuring no feature-stripping launches. Targets: 100% P0 feature parity before any migration, ≥90% voluntary adoption before legacy deprecation, zero accessibility regressions, and decoupled hardware/software timelines.
Over 16 million active Sonos households (per investor materials). Primary: daily music listeners who depend on alarms, timers, and queue. Secondary: multi-room power users (10+ zones). Tertiary: blind and visually impaired users relying on VoiceOver/TalkBack.
P0: Feature parity score ≥95% before any rollout gate. P1: App crash rate <0.5% in new version. P2: NPS in new app ≥ old app baseline. Guardrail: Zero P0 accessibility regressions.
Not canceling the app rewrite entirely. Not preventing the Ace headphones launch. Not reverting the cloud architecture. The goal is a better process, not avoiding modernization.
Running parallel apps doubles maintenance cost. Decoupling from hardware may delay revenue. Progressive rollout slows time-to-market. Feature parity gates require strong PM discipline against scope pressure.
What Could Have Been Different
Proposed Migration Timeline (Alternative History)
The Sonos disaster was not a design failure. Reporting suggests the design team tried to warn leadership. From a process perspective, this case points to a core mistake: tying an immovable hardware deadline to a flexible software project, likely compressing QA at the worst possible moment, and removing the rollback path that would have been the safety net for everything else.
The magic of Sonos was making complex technology invisible.
You just wanted to play music, and it worked.
The PM's job is to protect that simplicity, even during modernization.