An Interview with Rochelle King, Global VP of Design at Spotify

Spotify Apps

Spotify has done a remarkable job of remaking the music industry, but as a designer, I’ve found its past two years or so to be particularly interesting. Where the company itself has always been credited with being a transformative force, the aesthetics and usability of its products, at least in the beginning, were generally held in lower regard, especially when compared to its more design-savvy competitors. That began to change when Rochelle King joined as its Global VP of Design and User Experience and set about overhauling the company’s approach to design.

I got to know King in the first year of her tenure at Spotify and was privy to some of the details behind her efforts. And like many Spotify customers, I’ve also watched the fruits of her labor reveal themselves to the public; with each new release of Spotify’s products, design figured more and more prominently. Relative to where they were when she started, the design quality of the company’s offerings has progressed dramatically, though I think even King would agree there remains much work ahead. In all, this evolution has struck me as a fascinating example of a company that formerly put engineering first trying to reorganize its priorities around design. Several months ago, over email, King was kind enough to agree to answer a slew of questions that I had about what she and her team have done so far and what they hope to do in the future.

Khoi Vinh: You seem to be drawn to high profile, engineer-driven environments where design may be welcome but faces an uphill battle—first Netflix, now Spotify. Is that fair to say?

Rochelle King: I think that’s generally true. I’m not sure about the “high profile” part , but I love working on consumer products, things that I use on a daily basis. It’s also been really fun for me to work in the entertainment and media space because I love TV, movies and music. (Unlike what you might expect, my team will tell you that my tastes run very mainstream!)

I really like being in a place where I have the freedom to tackle both product and organizational challenges. At both Netflix and Spotify, we knew it was important to make design a stronger and more strategic voice in the company—but to do that you have to first build a strong team which can then become a foundation for delivering great design.

How do you go about figuring this out?

You really need to set down strong roots. Especially in companies that have been traditionally engineering driven, establishing your design team and how it works with other teams is incredibly important. Then, as long as you hire the right talent, you can get out of their way because the organization and company will understand how to give them the support they need to do their job right.

Before we talk about hiring, I want to ask about getting a design team working with other teams. Was there a model that worked for Netflix that, with some tailoring, you applied to Spotify? Or did you find you needed to start from scratch?

In both cases it’s been really important to first get the design team aligned with the larger tech and product organization and the broader company. It’s fundamentally about getting everyone to speak the same language and to explicitly align around the same goals, and to build empathy with each other. Sometimes, this means getting designers to understand the perspective from product, tech, and licensing better—and sometimes this means teaching our partners more about how design works to craft and define the user experience.

It’s worth noting that Netflix is almost twice as old as Spotify, so they were at different stages of development when I joined them. Netflix was a more established company/brand and also had a more established way of working. Because Spotify is still rapidly evolving as a company, it was even more important to be explicit, vocal and deliberate about the foundational things we were doing.

Can you give me an example of how that played out in practice? What actions did you take to express those “explicit, vocal and deliberate” foundational ideas?

The work we did around our design principles is a good example. In teams that haven’t worked together for very long, or in companies where design is a new function, establishing design principles is probably even more important because it’s also a mechanism for you to calibrate with each other. We knew we needed to be very thoughtful about both articulating the strategy behind the creation of our principles as well as rolling them out.

The first imperative was to build support from the company at large. We got feedback on initial drafts of our principles from the CEO and CPO to ensure we had their support, and then we socialized the principles broadly to the rest of the company. They’re now a key part of our onboarding “Intro Days” which all new Spotify employees attend.

We also tried to be clear in communicating their intended impact on the business. For each design principle, we talked about how it reflects our heritage in music, so that it would it resonate with everyone at Spotify, and how it can impact our bottom line, to show that good design inherently has business value. To take one example, “Do less” is a pretty standard principle that most designers understand instinctively. But we spoke about its relevance to music, about how that music should feel effortless—there should be nothing between you and its enjoyment. From a business perspective, the more that we want to appeal to a mainstream audience and grow our user base, the more important it is to make our application even easier than before.

Did that translate into a design team perspective on metrics?

Yes, absolutely. Spotify is very strong on using data to inform product decisions. We run a lot of A/B tests and collect many kinds of data (both qualitative and quantitative) about how our customers are using our product. However, the key success metric we were talking about internally was daily active users (DAU). For some of the designers and product folks, DAU can feel like a fairly abstract term, so we tried to clearly define the core user behavior that we felt was a strong driver of DAU. This was simply “playing more music.” So instead of saying to a designer, “Let’s design an experience that increases DAU,” we could say “Let’s design an experience which gets people to play more music.” It felt like a more tangible way to tie the business metrics to the user experience.

You can even get more specific about what those goals are and say, “Hey, design an experience that gets people who currently aren’t playing any songs in Spotify to play music,” and you would get a greater variety of solutions than if you had just asked for someone to design an experience that got people to play more music overall.

That brings me back to hiring. Did you find that you had the right designers in place to do this? Did you have to write new job descriptions, hire designers with different profiles?

Two years ago our team was severely under-resourced. We were at least half of the size we should have been. So while we had a really young and talented group in place, they were spread so thin that it was both difficult for them to grow as designers and to also deliver on or shape a strategic vision. Given the size of the team, it wasn’t really about changing the designers that we had for different ones. Instead it was about augmenting or growing the team to fill it out with different or complementary profiles. I often go to this metaphor of an orchestra. We had a great string section, but everyone was being asked to play violin. We needed to add the depth of some violas and cellos—but we also needed to add brass, woodwinds and rhythm sections. In design terms, that meant we needed user researchers, prototypers and others.

The company was also changing from being startup to being a more mature enterprise with a significantly larger user base, so we had to evolve in other ways as well. Bringing in people with experience working on similarly large consumer products or with different kinds of organizational experience like management or mentoring became as important as hiring folks with great design sensibility and hard skills like prototyping or conceptual thinking.

What kind of designer would do well at Spotify, and what kind wouldn’t do so well?

Well, in addition to the basic qualities that we always look for in good designers—design “chops,” ability to articulate their point of view, understanding how to leverage data to empower design—the designers here have to be highly adaptable and flexible. Spotify, as a company, is in an industry that is constantly changing. Our competitive landscape is very much in flux right now, as is the music industry itself. This means that we are constantly faced with challenges which are new to us and the company at large.

The design team is also in transition. Right now, we’re in the middle of our journey to actively and conscientiously define what “design” means at Spotify. Two years ago, there was no user research team and the design team was about a third of the size that it is now. That means that as a team we also need people who are as excited about helping to build a team and a culture of design as they are about doing the work itself.

When you look ahead, what is your vision for what Spotify’s design culture looks like?

There are three things that we’ve been focusing on when it comes to our vision for Spotify design…

First, we need to establish an awesome working culture, both in terms of who we are as a team and how we work. You can’t underestimate this. Having a high-functioning team that really respects each other, enjoys being with each other and is willing to challenge each other makes us more effective and is the foundation of what will ultimately allow us to grow as a design team and to do our best work.

Second, to build a great product, we need to be in tune and empathetic with both our users and the artists that have their music on our platform. Therefore, we want to encourage our designers to be curious about their audience and to gather as much knowledge as they can about them through research, data, interviews, etc. I also want us to be just as smart about “designing” how we collect that information as we are about creating great experiences.

Finally, it’s all about shipping with purpose. We want everyone to feel like they are proud of their work. The “purpose” behind shipping might be to learn more about our users behaviors,, to up-level our quality, or because we believe that a new experience is going to increase retention by X-percent. I’d love to have a culture where every designer has helped to define what they’re working on and therefore knows the meaning and value behind what they’re building and why they’re building it.

How far are you towards those goals right now?

I think we’ve taken a couple of initial big steps towards getting there, but there is definitely still work for us to do. Within Spotify, our team is still fairly new and everyone knows that we’re still in the process of building our design culture. So because we’re all in it together, I try to be pretty candid with them about what we’ve done so far and how far we have to go. So far, our progress has been very encouraging.

We’ve been thoughtful about hiring and we’re just starting to initiate some exciting projects around innovation and longer term product vision.

Group cohesion is an ongoing effort, I’d imagine. In the near term though, how about your progress on the practical matters you talked about before—being in tune with users and artists, and shipping with purpose?

On being in tune with the users, we took our first step by creating a user research team and we’re doing more early stage formative research, which is helping to bring the customer voice in earlier to help shape our product from the beginning.

However, our team still struggles to get time for all the projects we’re asked to contribute to, and we need to get better at communicating and broadcasting everything we’re learning to a wider audience in the tech/product and design organization, so that the great stuff that we’re finding out can have even more impact into how everyone in the company thinks about our audience.

On shipping, the first big design-led initiative was the redesign we did in April of last year. Over the years, our product had organically grown in so many different ways that it was starting to feel disjointed. To our users, the redesign was predominantly visual, which was only one of the many layers that we want to address. What you don’t see however, is the underlying framework, tools and system. That was probably the biggest win for us as a team because it changed the way we worked, and it let us focus on solving the bigger design problems that are beyond visual styling.

We have a few more design led projects in the works , so when those things launch I’ll be very excited. When we get to the point where everyone in the team feels like they’re really “shipping with purpose” and has shaped how we got there then I’ll feel like we’re meeting our full potential.


Rochelle King will be appearing in New York City next week at Behance’s 99U Conference.


Do you have thoughts about this post you’d like to send Khoi? Your remarks will not be published.

Thank you! Your remarks have been sent to Khoi.