Gustav Söderström

Gustav Söderström is the Co-President and Chief Product and Technology Officer at Spotify. He is responsible for Spotify’s global product and technology strategy, overseeing the product, design, data, and engineering teams. Prior to Spotify, he founded 13th Lab, a startup that was later acquired by Facebook’s Oculus. He also served as the Director of Product and Business Development for Yahoo Mobile and founded Kenet Works, a company focused on community software for mobile phones, which was acquired by Yahoo in 2006.

10 skills 12 insights

AI & Technology Skills

The shift from recommendation-based products to generative-based products requires a fundamental rethink of user interfaces and business models.

"The internet started with curation... then the world switched from curation to recommendation... And I think what we're entering now is we're going from your curation to recommendation to generation...."
13:30

Generative AI should be viewed as a high-leverage instrument that enables new genres and types of creators rather than just a replacement for existing art.

"The way to think about these diffusion models if and when they get good enough at generating music is probably the same like an instrument. It's just a much more powerful instrument and we'll probably..."
22:51

AI-driven UIs must be 'fault-tolerant,' providing users with easy ways to correct or bypass incorrect AI predictions.

"You need to understand the performance of your machine learning to design for it. It needs to be fault tolerant and often you need an escape hatch for the user. So you make a prediction. But if you we..."
19:03

Forcing teams to build 'hard APIs' for internal use creates the necessary infrastructure for future platform leverage and externalization.

"If you don't create hard APIs to your technology, you're out. And if you think about it, it has to be that way because otherwise no one would do it... because he forced it so hard, they were the ones..."
37:32

Communication Skills

Alignment is achieved not through consensus, but through the 'right to understand' the logic behind a decision.

"I think the promise we should make to all employees is that even if they don't agree, they should be entitled to understand why you're making the decision. What I don't think is acceptable is to say,..."
01:06:06

Hiring & Teams Skills

Internal storytelling and podcasts can humanize leadership and bridge the gap between executives and employees in a growing company.

"I decided to do an internal podcast and I went around and I interviewed actually Daniel's direct reports... And the idea was to make them more approachable for employees because I felt listening to po..."
09:36

Extreme autonomy at the individual contributor level can lead to fragmented strategies and inefficiency.

"If you put autonomy very far towards the leaves of the organization... there's a fair chance that you're just going to produce heat. You're going to have a hundred squads with a hundred strategies run..."
31:39

Leadership Skills

When launching big bets, leaders must differentiate between 'change aversion' and fundamental product-market fit issues.

"There are going to be two types of feedback. One is you did something and it was right, but people are upset because you changed stuff. The other is you did something and it wasn't right, and people a..."
54:45

Short-term optimizations often provide immediate 'warmth' but lead to long-term regret or product degradation.

"The saying is that's like peeing in your pants in cold weather. It feels really warm and nice to begin with. And then after a while, you start to regret it. It's about being short term, basically."
01:11:00

The guest provides a deep framework comparing centralized (Apple) vs. decentralized (Amazon) models and how they impact user experience and speed.

"On one spectrum, you have something like Amazon... minimize dependencies so you can run in parallel... On the other spectrum, you have something like Apple... centrally organized by something that is..."

Product Management Skills

Planning cycles should be strictly capped to 10% of the total time to ensure the majority of effort is spent on execution.

"The idea is that, roughly, you shouldn't be spending more than 10% of your time planning versus executing or building. Which means that if you're working quarterly 10 weeks, you should spend one week..."
01:02:46

User complaints during a redesign often stem from the loss of 'recall' (finding known items) rather than a dislike of new 'discovery' features.

"If you look at what people do on Spotify's homepage... it is almost 90% what we call recall... When we tested the design... we switched it from 90/10 to 10/90. 10% recall, 90% discovery. And while peo..."
49:59