Sonos called rebuilding its app "courageous" — then it shipped without alarms, couldn't roll back, and cost the CEO his job.
All posts
DESIGN INTELLIGENCEJune 20, 2026·Mary · DEPIX Design Intelligence

Sonos called rebuilding its app "courageous" — then it shipped without alarms, couldn't roll back, and cost the CEO his job.

For twenty years the promise of Sonos was almost suspiciously simple: press a thing, music plays, in any room, forever. The hardware was beautiful and the app was the invisible glue that made the system feel like magic instead of like a network of computers. So when Sonos unveiled a completely reimagined app on 23 April 2024 — a cleaner home screen, a faster engine, a modern platform "rebuilt from the ground up" — the renders and the press shots looked like the obvious next step. It demoed like progress. Then it shipped, and the only review that counts arrived: the one written by the people who already owned the speakers.

The redesign that looked like a leap

The case for the rebuild was real. The old app had been spliced and patched for years on top of ageing code, and Sonos needed a modern foundation to support new products like its first headphones, the Ace, and the cloud features they required. On paper and in the launch deck this was responsible engineering: tear out the cruft, ship a faster, cleaner controller, set the company up for a decade of new hardware. The chief product officer would later defend the choice to The Verge with a line that became infamous: "It takes courage to rebuild a brand's core product from the ground up, and to do so knowing it may require taking a few steps back to ultimately leap into the future." The intent was sound. The validation was not.

The market voted with its thumbs

When the new app rolled out on 7 May 2024, the gap between the keynote and the object in people's hands was instant and brutal. The redesign had quietly dropped features that customers used every single day: sleep timers, alarms, the ability to edit the playback queue, the ability to build a playlist, and — most damningly — support for screen-reading accessibility tools that blind and low-vision users depended on to operate their speakers at all. Connectivity broke. The interface lagged. Some older systems were rendered effectively unusable. A controller that had been invisible for twenty years was suddenly the loudest thing in the room. The word "courageous" stopped being a defence and became the punchline of the entire episode.

The trap door: there was no way back

Here is the detail that turns a bad launch into a structural failure. Because the rebuild had re-architected the cloud backend underneath the app, the new system was fundamentally incompatible with the old one. Sonos could not simply hand frustrated customers the previous app and wait — the servers the old app talked to had already been changed to serve the new one. The decision to rebuild everything at once had removed the company's own escape hatch. There was no rollback, only a public, months-long scramble to bolt the missing features back on in front of an audience that had not asked for any of this.

The bill

The cost showed up everywhere a cost can show up. Sonos's stock dropped roughly 13% in the wake of the launch, and across the saga the company shed close to half a billion dollars in market value. On its earnings calls the leadership team described the app fiasco as a roughly $200 million revenue headwind and committed $20–30 million purely to the recovery effort — most of it landing in the first quarter of the new fiscal year, money spent not on the future but on undoing the present. In August 2024 the company cut about 6% of its staff, roughly 100 people, and shelved an Apple-TV-style set-top box it had been building. Fiscal fourth-quarter revenue fell 16%. And on 13 January 2025, after eight years in the chair, CEO Patrick Spence stepped down; board member Tom Conrad took over and told customers plainly, "when it doesn't work, our customers are taken out of the moment and are right to feel that we've let them down."

The lesson: validate the decision, not the render

It is tempting to file this under "buggy launch," but the bugs were the symptom. The real failure was where the redesign got tested. Every signal Sonos optimised for lived inside the project: a cleaner home screen, a modern engine, a roadmap that justified the rebuild. Almost nothing in that loop pressure-tested the decision against the conditions the app would actually live in — a person setting a sleep timer at midnight, a blind customer reaching for a speaker by screen reader, an owner of a six-year-old system who simply wanted last week's behaviour back. The new app answered an easier question (does it look and feel modern?) than the one the market would ask (does it still do everything I already relied on, and can you take it back if it doesn't?). And because the architecture decision had quietly welded the doors shut, the company couldn't retreat to the version that worked.

Why a Design Intelligence company tells this story

We treat the design decision as the thing to be tested, not the picture of the redesigned screen. The Sonos app is a near-perfect case for why. It had taste, a legitimate engineering rationale, and a sound long-term goal; what it lacked was a way to put the real-world version of the decision — alarms present versus gone, accessible versus not, "rebuild everything at once" versus "ship reversibly" — visibly side by side in front of the people committing to it, before the backend was re-architected past the point of return. The point of validating a design decision in advance is to make that gap cheap to see while you can still steer: to argue the trade-off between what feels inevitable in the launch deck and what survives contact with a customer at midnight, on purpose, before the rollback option is engineered away. We use the intelligence of AI to help leaders see what a design decision does in the world before it ships — not after the stock has dropped, the features have been clawed back, and the person who called it courageous has cleared his desk. The redesign wasn't ugly. Its problem was that the only place it was ever truly tested was the place it was made.

Sources

Related posts