Case study · Sonos
Autoplay
The context
Sonos calls itself the Switzerland of the music ecosystem. It sits between the listener and an enormous range of music partners, including Spotify, Apple Music, Amazon Music, Deezer, Calm, and its own Sonos Radio, across 150+ service providers.
Two unmet needs
- Customers expected Autoplay. Apple was pushing Sonos to match its Autoplay feature in the Sonos app.
- Many preferred other apps. 60% of Sonos users preferred another music app over the Sonos app. In one customer's words: "The music will stop and everything goes awkward silence if I play a song from search results, or from an artist's Radio in Sonos App."
The real problem was how we worked
The organization worked in silos. Business and partners came first, technical constraints second, and customers third, which produced partner-specific features. Requirements were handed to UX in a waterfall, which meant rushed timelines and low-quality deliverables.
So the design question became a question about culture. I proposed hosting a cross-functional design workshop, getting the teams to be part of the process from day one, defining the strategy that was best for Sonos users, and getting stakeholders bought in along the way.
Leading the design process
- Plan. Set expectations with stakeholders. Identify the key stakeholders, note that engineering would not get to implementation for at least three months and that nothing else was competing for priority, and define four phases and their deliverables.
- Discover. Comparative research and a review of historical projects.
- Define. Align stakeholders on a strategy for user desirability, balanced against business viability and technical feasibility.
- Design. Explore and design the north star.
- Deliver. Deliver the experience strategy and solutions.
The workshop
I tailored the workshop to Sonos's needs and time limit. It went through 10+ rounds of review and went from three days to 90 minutes, with a designed agenda, exercises, templates, and breakout-room leads. Sixteen cross-functional stakeholders took part: PMs, engineers, designers from both software and hardware, copy, and the partnership team. One exercise asked what the worst and the best possible experience could be.
Afterward one participant wrote: "That was a great session, Linlin! The most fun I've had at work in a long time, I really needed that."
What changed
- Before, one solution for one partner. After the workshop, universal solutions for all partners.
- Before, one solution from one team. After the workshop, holistic solutions for the whole user journey across software, voice control, and partnerships.
The workshop set Sonos's standard for partner feature requests. A one-off build for a single music partner became one universal feature for all Sonos users, across 150+ service providers.
Autoplay
I synthesized the workshop ideas into concepts that explored user effort and user engagement, then defined the product strategy and requirements for Autoplay: whether playback continues, and what plays next when a queue ends. The product positioning I wrote for it differentiates Sonos from Apple Music and Spotify.