20VC Roundtable: Spotify, Adobe & Linkedin CPOs on How AI Changes The Future of Product, Why AI is Now the Product, How TikTok Changed Product, Why Cost is the Biggest Barrier to LLM Usage & Why Incumbents Can Adopt AI Faster Than Any Prior Innovation Cyc

20 Dec 2023 · 50 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Summary: 20VC Roundtable on AI and Product Development

Podcast Title [The Twenty Minute VC (20VC)](https://www.thetwentyminutevc.com)

Episode Title 20VC Roundtable: Spotify, Adobe & Linkedin CPOs on How AI Changes The Future of Product, Why AI is Now the Product, How TikTok Changed Product, Why Cost is the Biggest Barrier to LLM Usage & Why Incumbents Can Adopt AI Faster Than Any Prior Innovation Cycle

Episode Description This episode features a roundtable discussion with three distinguished Chief Product Officers:

  • Gustav Söderström: Co-President, CPO & CTO at Spotify
  • Scott Belsky: Chief Product Officer at Adobe
  • Tomer Cohen: Chief Product Officer at LinkedIn

The conversation explores how AI is reshaping product development, design, and the overall landscape of technology in various industries.

---

Key Discussion Points

  1. The Role of AI in Product Development
  2. AI as the Product:
  3. Gustav suggests that AI has become the core product, while UI now serves to enhance AI effectiveness.
  4. UI's role is evolving with AI being at the forefront, leading to a shift in how users interact with products.
  • Impact of TikTok:
  • TikTok's success is attributed to its unique UI that maximizes user engagement through AI-driven algorithms.
  1. Models vs. Data
  2. Importance of Models and Data:
  3. Discussion on whether model size or data quantity is more critical for performance.
  4. Companies may need to adopt multiple models, creating opportunities for startups to thrive.
  • Cost Considerations:
  • High operational costs of AI technologies can be a significant barrier to implementation.
  • Cost efficiency is essential to ensure sustainability in deploying AI solutions.
  1. Workforce Transformation
  2. Adapting Teams for AI:
  3. Product leaders and designers must shift their mindsets to accommodate AI-first strategies.
  4. Emphasis on the necessity of training in AI capabilities, prompting, and understanding user behavior.
  • UI Design Evolution:
  • The transition from traditional UI to AI-integrated designs requires a new approach to user interaction.
  1. Competitive Landscape: Incumbents vs. Startups
  2. Incumbents' Advantages in AI:
  3. The panel discusses how established companies can leverage their existing resources and data to implement AI more rapidly than in previous technological shifts.
  4. Identifying the hurdles incumbents face compared to agile startups, such as legacy systems and cultural resistance.
  1. Future Business Models
  2. Potential Disruption:
  3. The conversation touches on how AI could disrupt existing business models, such as traditional hourly billing in consulting, legal, and creative industries.
  4. The need for companies to explore value-based pricing models as AI increases efficiency.
  1. Data Collection and Treatment
  2. Data as Oxygen:
  3. Data is seen as fundamental to AI success; organizations must prioritize quality data collection and understanding the objectives behind algorithms.
  4. Companies must be cautious about how customer data is used to inform AI training while respecting privacy and copyright issues.
  1. Preparing for Change
  2. Advice for Emerging Designers and Product Leaders:
  3. Emphasizing the need for continuous learning and adaptability in an evolving job market.
  4. Encouraging a growth mindset and a balance between broad skills and specialized expertise to navigate the changing landscape.

---

Key Takeaways

  • AI is the New Product: The integration of AI into product development signifies a paradigm shift that requires rethinking traditional UI and product strategies.
  • Cost and Efficiency: The economic implications of deploying AI technologies must be assessed to ensure sustainability.
  • Role of Data: Quality data collection is vital for effective AI performance; organizations must treat data as a core component of their strategy.
  • Incumbents and Startups: While incumbents have resources, the agility of startups presents unique opportunities for innovation in the AI space.
  • Future-Ready Skills: Designers and product leaders must embrace change through continuous education and adaptability to remain competitive.

---

Conclusion The roundtable offered profound insights into the transformative effects of AI on product development and design, underscoring the importance of adapting to new technologies and evolving business models. The discussion of how incumbents can leverage their existing strengths while addressing the need for innovative approaches sets a compelling stage for the future of the industry.

For more information and resources, visit [20VC](https://www.20vc.com).

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00Now AI is the product and the UI is there to help the AI. When you think in an AI first principle kind of way, you're really unleashing the idea of control in my opinion. You don't control the experience anymore. Designers, they need to understand basically GPT -4 as well as the understand a user. Even though the models are there to generate great voice, the problem is actually doing it cost -efficiently. I can't underestimate how much intelligence even art goes into building the right prompts. The big changes come when that technology enables a new business model somehow. The functions of so many businesses are collapsing now, and so the idea of selling seats functioned by function, I mean, it's such an all -integrated way of building a business to some degree.

0:39This is 20VC with me Harry Stemnings and the round table shows that we've done so far have been the most popular that we do, and so today we have three of the world's best chief product officers discussing how AI changes the future of product and design. So in the lineup today we have Gustav Sodostrom, CPO, CTO and Co -President at Spotify, Toma Cohen, CPO at LinkedIn and then Scott Belsky, CPO at Adobe. We could not have a better lineup. This was so much fun to do, it's a total masterclass. Let me know what you think of this format of show on Twitter at Harry's Debbings. But before we dive into the show's day, HMC or Harvard Management Company, they're constantly seeking out the next generation of truly great investors and entrepreneurs.

1:22HMC has managed Harvard University's endowment for nearly 50 years and was one of the first institutional investors in venture capital. Their experience and long -term investment horizon make them ideal partners to get world -changing ideas on a part of viability and success. They work as a true partner, providing insightful perspectives to help managers succeed. I personally have had the pleasure of working with the HMC team and can say that they are truly exceptional partners and just great, great people to work with. Whether you're launching your first fund or your fifth, HMC welcomes the opportunity to partner with both developing and established managers.

1:56Have an idea you want to share with the team, just send it to venture at hmc .harvard .edu. You have now arrived at your destination. Alrighty, I am so excited for this, I've wanted to do this one for a while, so we're going to do a couple of intros first so everyone can get familiar with each other's voices, And so we're gonna start with you, Scott, and Gustav and then Toma. Who are you and what are you most well known for? I was the founder of a company called Behance back in the day. We were acquired by Adobe for the last six years or so. I served as chief product officer for about five years overseeing the creative cloud business and then have recently taken over strategy corporate development design and emerging products for the company in this kind of chief strategy emerging products officer type role over the last year.

2:40It's a great new encompassing role. Gustav, your turn. Some Gustav Sadistran and Simultus Scott, I started a few companies and then I've worked at Spotify for almost 15 years now as CPO and then CTO and now recently as Co -President together with Alex Nordstrom, so we run the company together. Toma Jotal. Hey everyone, she's a photo -calfister for LinkedIn. Responsible for basically what we build from the company's strategy to overseeing the team's building it. Billet LinkedIn for 12 years now joined right at the cuff of shifting from desktop to mobile as a company So that was fun and then I started my career as an engineer So I was doing a thing from semiconductor is cheap on design algorithms to embedded systems all the way to the internet right now in AI Okay, so now everyone knows individual voices where she was a very lucky because they're three very distinct voices I didn't realize quite how how apt the selection of this roundtable was in that perspective I want to start with probably kind of the most broad, but also kind of important, which is fundamentally we're all told that AI change is everything that we do.

3:41When we apply that to product, what do we think are most significant ways that AI will change the product development process, specifically on the product development side? What will change specifically with AI? Well, I mean, I'm sure we're all experimenting with GitHub Co -Pilot in our engineering teams, and they will certainly be an improvement in both the productivity of developing, code and products and also testing and identifying and reconciling bugs and that sort of thing. But the only other thing I would throw in there is that when you're developing the interface of a product, you are oftentimes trying a few different approaches to find the one that works best.

4:18And that just takes a lot of time to have three or four different options and explore, but then stop going down that path and go down another path. And then fast forward now into today into the future, we're in a world where AI will suggest alternative scenarios. You can try variations and just look and you know with the mistake of the eye, find a better solution for at least something you want to A, B test. And so I think that the product development process, the products will become much better, frankly, with fewer cycles will find better solutions. I have some thoughts there. I mean one way to maybe think about it holistically is that that when I started and then to marriage as referenced as when it was a transition to mobile.

4:57And even before then, at least I kind of thought of the UI as the product. And the machine learning came along, and the machine learning was there to help the UI. And that shifted completely. Now AI is the product, and the UI is there to help the AI, to capture better signal. And I think most people agree that the real transition there was TikTok, which is almost new UI. It's just the video, and the UI is just trying to make the Xbox point algorithm be more efficient than anything before it. And most people in tech agree that it wasn't really the algorithm of tech talk. It was the UI that maximized what was pretty traditional export algorithm, like since the days of hot or not.

5:34So I think that's the big change. Like the AI is the product and the UI is there to help the AI these days. And maybe it always was. I mean, users never came to Spotify to click buttons. It was always about music or something. It's just more clear now. I've had so many guests on the show before say about this stupidity of UI and how AI will make UI's redundant. Is that wrong? Go, you go. I mean, UI is here to help us understand the object model of a, like, find what we want, you know, and with as little friction as possible engage. And so, you know, UI, in some cases, should disappear, but there's new UI these days in the form of the tone of a product.

6:12And the way that something is the inflections that are used, the persona. I'm thinking about UI design in the future as in some ways like persona design when I'm interacting with Spotify's DJ and the DJs like cracking jokes and like being casual with me That's a UI decision to some degree of a product that's driven by AI as an example One of the biggest implications for me when building product is the understanding that AI is the product But for many product builders AI is something they delegate I think that's like really implicated to the AI team or the engineering team I think AI strategy starts from the CEO and makes its way down and many companies right now AI that's something that the team is doing reminds me of like early on with the mobile team There was a mobile team building it and it was a whole different the rest of the company was building something else Like the analogy I give usually is like imagine like a re -reacting a reaver rafting boat The guy done the back with the two massive pedals and that's AI to the product and everybody else on the side They had accuracy, they had some power, but they're not as significant as the guy on the back with the pedals.

7:16And one of the biggest changes I've seen with AI is we moved from desktop to mobile, not everybody made it for the transition, because it required you to unlearn how to build a little bit. It wasn't about hedging, I'm going to put all these things there and what's the kind of hit map. It was about making a decision about how do you build a relevant experience. When you think in an AI first principle kind of way, you're really unleashing the idea of control in my opinion. So what happens basically in the eyes you don't control the experience anymore. It's not a terministic anymore For many product leaders I know it's really hard to let go.

7:48It's like you're a chef at the restaurant and all you dictate is the ingredients Maybe then I'll observe a little bit, but you don't control the output I can't tell you how many people just flop on that. They just cannot comprehend the fact that they don't control the experience I like that massive of a formation of a high -first mentality. Probabilistic experiences rather than deterministic, right? 100%. It's not deterministic. Do you guys not find that inherently concerning? Every company on this school is a public company. When you don't have the control of the outcome and the outcome could be a hallucination.

8:21Is that not concerning to you when you don't control the outcomes? Well, it's funny. I mean, for some practices, hallucination is a bug, but in some areas it's also a feature. If I'm trying to discover some cool new music, I mean I can imagine that might be a feature as opposed to a bug You know when you're trying to do generative fill in Photoshop and imagine what's behind an object or you know extending the frame of a photo Who's nations actually a feature? And if you get the wrong answer or something you know like you can just run it again So I think it is a bigger problem though in applications that really you are mission critical around you know writing NDAs for legal purposes or where hallucination actually could get you in trouble.

9:04I want to build on something Scott said there because I think it's the definition of what is UI changes. So you took the example of the AI DJ we did and you're exactly right, it was the design team that user tested. What is this? Is this a utility like Google? Is it an AI person like Alexa or is the UI that we digitized a real person with a real personality that exists and we chose the latter? that is design and it is brand. So I think designers need to think holistically about the experience in that sense. And that is still design. It is the user experience. And I also think something that designers need to get good at in this world is to understand the capabilities they have.

9:42They need to understand basically the GPT -4 as well as they understand a user. What it needs and how it works. So an example that I think is a good example is mid -journey. So mid -journey, the designers that clearly understood the performers of the model when they built the major in experience. It took like two minutes to generate an image. It was wrong one out of four times. They could have built a horrible experience. We waited for two minutes and got disappointed 75 % of the time. Instead, because the designers there and product people understood the capabilities, they built a fault tolerance UI.

10:12They gave you, because they also understand how diffusion works. So you can do it in stages. They gave you four low -res shots at the same time in 20 seconds. That is any of these good enough. That's what I think the sign needs to do. designers and product people need to understand the models and the performance very very deeply so that they can make sure the experience matches the current level of performance. It's the same for us if if we have a one in ten shot and recommending a good song we probably need to recommend ten on the screen at the same time to get like a good chance of over hit.

10:41Just have you said they're reconvencing the models very deeply but again I am basically an absorb of knowledge from smart people and then I try and kind of amalgamate it together, everyone tells me that actually every company or the best companies, we use multiple models at the same time and transition between them. How will product people be able to have eight different models in use at the same time? Know all of them really well to utilize them effectively? How does that look? I don't think it's a product people. I think this is where you build like a platform that basically enables you to understand the task you're trying to accomplish.

11:14Cost, we should talk about Cost at one point because this is a very costly software and costly technology and then that's actually what you're being mass people with, deciding what kind of model you use for what purpose really starts at the application layer but the decision is not better the application layer. That's actually if I think of like why I would expect to see some massive innovation and startups to show up, it's in this tier to really allow people to leverage multiple models at multiple cost centers and resources and efficiencies and then completely you mask it from the developer, from the designers or their product folks?

11:47I think it's actually common belief that there are going to be a few mega models in the future that are going to do everything for every company in the cloud. And I think what we're saying is actually it will probably be the opposite, right? There will be many, many, many long tail models, some learning locally on people's machines or in applications that they install, some in the cloud, some open source, some not open source. and there needs to be like logic around the routing, not only to the model that's the best preparator, the most specialized model for a given query, but also the most cost -efficient.

12:21And a lot of companies like ours, in market with AI products today, are actually counting on the reduced costs over time from some of those technologies. So I think that's a great point, and I actually, there are some startups now that are kind of defining themselves as router startup. There's like two levels I think which are kind of fun to think about. One is a duplication layer and one is a kind of more of the kind of meteor layer which is like the dispatcher analogy. And there is a dispatcher at the kind of application layer from the application. Like imagine the idea of agents, right? You come in, we all know by now building one agent to rule them all is not the right design.

12:57You want to have multiple types of agents. Like I take a complication like LinkedIn, there's like a seller agent, a knowledge agent, a job security. There's so many agents you want to build. but you want to build a dispatcher around that, almost like a team coach that knows how to get that team to work together. Same at the meteor level when you want to start building some kind of dispatcher or router to Scott's point around which technology to best use. That's where I could imagine tremendous innovation happening. When we think about the multiple models that we'll use, you mentioned there that we'll have actually kind of open, close, very specialised.

13:29When we think about cost, the more models we have, the more costly it is also, and margins are impacted. How do we feel about cost and implementation when thinking about model adoption? From Spotify's point of view, most of the stuff we've built in -house to Tomer's point is actually mostly about cost. For example, as we talked about generating a lot of voice, we want to generate two minutes of voice per day for half a billion people, it's a billion minutes that can ruin you. Cost is actually already the biggest factor in if you can deliver products. Even though the models are there to generate great voice, the problem is actually doing it cost -efficiently.

14:03So I think that's completely right. A lot of the innovation and technology has to go towards routing often actually for cost purposes. I do think I have a little bit of a different view on. There is some chance that per company, I think you will want to embed the entire user history in one model. So today, most companies, including Spotify, many separate systems that are optimized for different purposes and they sort of collaborate in semi -predictable ways. There's not one system, but if you look at some of the papers coming out of Amazon and so forth, They are starting to look at you literally tokenize all of it basically the log the how you scroll how you click What you listen to what was in the content that you listen to you just do a token prediction based on that based on all of this What is going to happen next so we may still see like one large model I think the world is going to go towards you embed your entire user history everything they did into one space I still think to to your points caught into there you will have specialized models for for example for voice for video for different purposes So it depends on if you're talking about the user data or about generic capabilities, like rendering and voice and stuff like that.

15:07Yeah, and in some cases, I guess you could take the user data at the router level and kind of go to different models for different purposes. Exactly. You can embed that, right? Yeah, that's a user history. I think Gustav's point about the cost efficiency. The good news is that the desire to have more performative models and the desire to have more cost -efficient models are often like parallel efforts towards the same outcome. And so, you know, the margins will get better as these models get better also. Do you think this follows stand of Moore's Law theory in terms of development of technology and the cost reduction that we see there?

15:42I think it will. You know, some people say Moore's Law is starting to come to an end in terms of just more transistors, but we barely started on neural hardware. So I'm sure we're going to see the same effect, even if it's not more transistors per square inch, necessarily, for a good while. I also think we'll start. We will continue to see bigger and bigger models, but there is the opposite pressure as well. Every month there is a much smaller model that did with the bigger model that a month ago better. Both things are happening at the same time, so I do think we'll see that progress for some time.

16:09No, coming from embedded systems, you can already see verticalization of software with chips dedicated where Microsoft and Alistair are going to start building their stilly clock. You can actually see the idea of how do I get that efficiency and gains in resources, in power, in cost. When I was building semiconductors a long time ago, it was like every chip was about how do I get you know in half the power Double the capacity and like lower the cost So that was always the kind of mindset and I think you could start seeing that verticalization This goes to open versus close is so many implications of that But if you're going to that close highly -resourced up to my system You'll start seeing that some companies and Apple and Microsoft and so on each of you have incredible amounts of data LinkedIn, Adobe, Spotify, insane amounts of user data.

16:54Everyone puts a question forward of what comes first, the size of the model or the quality and size of the data. How do you think about that and the importance of data versus model? I think the size of the model matters, but it really depends on what you're trying to do. If you want to have this amazing personal assistant in the movie, then you want to build a massive model. But the model size is really the number of parameters you have. That's pretty much it. But on the flip side, and this is where like, this is where like, it depends on what you're trying to solve. And the volume of your training data also matters.

17:26If you have a large model that is under trained, it will underperform a small model, which is really well trained. So you're just wasting resources, and you're going to be like less efficient results. And then there's already examples right now that like, when you build specialized model for media analogies, like an athlete that you transform into a weightlifter or like a long distance runner, they perform much better. I can't talk on behalf of Scott and Gustav, but if we're trying to build, I'm trying to build a job -secret coach guide. I'd be better build that agent specifically for that role versus some kind of like life -long coach that will be very hard for me to build.

18:00They'll do it before much, much better. What's the hardest thing about mobile implementation? When you look at current products and current tax tax, when thinking through model selection and then mobile implementation, what's the hardest thing? The little secret is that there's a lot of final mile tuning and work that probably we're all doing under the hood. That is work that only we could do because we know our customer really well, we know our product and experience really well. And you know, it's those little finesse moments. I mean, it's the same playbook all along, right? What makes a customer love using a product?

18:32Because the product is empathetic to their problems and if the interface, you know, meets them where they are. and I think we get lost sometimes in the technology and forget that it's not the technology that makes us successful if the user's experience of the technology that makes us successful. And that's why I think the role of designers is more important, not less important in this modern world. And I've been thinking a lot about the pace of change that we're all dealing with these days. In our respective companies, I'm sure like me, you're waking up and every morning, you're like, oh my gosh, what new breakthrough do I have to figure out today in terms of how it impacts our business.

19:10You know, and in this newsletter exercise, I force myself to do every month called implications. I'm calling it surfing waves in the Cambrian explosion. This notion of like, you pick a wave, and then you're like, oh, wait, I'm on the wrong wave. Like, how do you transition to that wave over there, but then wave, this wave over there, and it's almost like this frenetic motion that we're all in. And the only solution I can come to is just doubling down on empathy with the customer. There's so many new technologies and possibilities being thrown at us, but if we just kind of like take the pulse of where the customer is and where they're likely going even more so, like maybe we can help make the right decisions.

19:45Otherwise it's like wild. Yeah, I grew with the Scott. And I think on your question, what was the hardest thing that depends as Tomer said, sort of like what are you asking about? And when? Initially it was very hard to find talent on the technology side. That's now getting easier. And so the problem keeps moving up the stack and as we talked about actually think the hardest thing for us now Has been to sort of retool the company to think about what the model needs to serve the user to rethink design to Re -think product for a while There was a lot of work around making sure data was useful so it keeps changing what the problem is What is retooling the company mean good stuff is it like again?

20:23This is kind of my question. It's what I spoke about we have a bet's board what we kind of stack rank what we're doing. We literally had a bet called AI is the product for like two years to really emphasize the shift. And so getting people in that mindset, educating them to understand how this works, to start to use these things and get empathy, not just for users, but for the models. Because people first underestimate the technology and then they're excited and they're overestimate what it can do. So they create products that are not mature yet. And so there's a lot of work in getting people realistic about where these things are right now.

20:55That was probably the hardest thing to get everyone sort of on the same level of knowledge and understanding. Yeah, one fun one and a curious of Scott and Gustav are doing this as well, but I remember when we shifted from the desktop to mobile, we had to force people to bring mobile designs because again, they were like, we had to force them. Luley said like, there's not going to be a jam session unless you bring a mobile design. Now I want to see your prompt because that's the interface that people are using to generate their results. I want to learn how you're building your prompt and I want to critique your prompt I want to understand your prompt really really well I can't underestimate how much intelligence and even art goes into building the the right prompts Pro sure I never imagined doing product gems that ask them to see people's prompts going into the Distortion and that word in this Omega Oasis.

21:42I think this is like a very democratic thing because it used to be if you were like a Product personal designer and you had an idea Yeah, you kind of needed to convince and generate to build a prototype. In this space, what is happening more and more is like the designer of the product person come with the prompt and the idea of ready. It just generates something. And then you can, you know, that's very empowering, I think. It's so true. And we've all been talking about design driven, you know, innovation and product and whatever for a decade or more. But I think this point about how you have these core teams that are building APIs that are ultimately representing the capabilities of the model.

22:14And you can actually directly empower designers to start to explore interfaces and to the point about the intonations and the persona and all those other decisions that these designers are now making. They thought they went to school for graphic designer product design, but now they're actually thinking about the conversation inflections and all these other nuanced design. But that's what we did, too. We had our design team actually build a team within that did all of the early development to firefly. It was a very like design -driven exercise to figure out the interfaces and how they integrate it into the products.

22:48I wanted to just quickly go back to one question you asked there about sort of size of models and data. So I think it's interesting to sort of think about. My bet is that size of models will keep being very important for some time. Actually now that Chinchilla paper, it's very predictable how it's going to scale. It's unclear why it wouldn't scale even if it's slightly diminishing for a while more. We're not even at the level of the brain yet in terms of connections. So that seems likely. My hunch would be though that in the longer term you're going to be able to do most of what you want with reasonable size models and like having a much bigger model doesn't have that much.

23:23So I would still bet that having lots of lots of user data and lots of high fidelity user data. Basically great user understanding is going to be important in the long term. To your question of like does this data really matter? One argument is it doesn't matter it's all going to be in the model. The other argument is like no the mods will be very powerful to be able to ask them good questions You need a lot of data about that user and that's kind of the bet that I would make that there was this Paper called met prompt that came out recently where you know GPT -4 like a general model if you prompted the right way It actually beats a fine tuned Model that was fine.

23:58You know medical medical data through this very very clever prompting But it sort of still proves that in order to do this is prompt you needed to embed a lot of user data So I still think long -term data is going to matter to have proprietary or a great user understanding of the specific user Why doesn't this Spotify create it so models good stuff? So we have our own models as well. We do both. We have lots of our own models But we don't have a GPT -4 that we haven't told the world about. I'm sorry to reveal that But it's also what I said before like our goals are different OpenAI's stated goal is AGI that will drive different incentives It will not optimize for delivering two minutes of audio to have a billing users per day, right?

24:37It's not necessarily going to optimize for cost efficiency and building pragmatic products. That's why, you know, there's no point in trying to compete with them for us because we don't even have the same goal. So we're trying to build exactly the things that we don't think they will build. And we would buy the things that they will build or someone else will build. Obviously we're working with Google and GCP, so that's what we do most of our work. Guys, how do you think about the decision to build your own models? I'm just intrigued on like, you know, I asked Goddard at last and that question.

Read the full transcript

25:01He was like, no, it's not all cool. We don't need to. Actually, I think that's sort of the right answer is you should build models if you're the best company in the world to build them. And so, you know, for us, it was like, who's going to build a better imaging model? We've got the advantage in terms of understanding the customer's use cases. We have the data. No one should build a better imaging model than Adobe. And so we're like, okay, we need to set out and make sure we hold ourselves to that level. But when it comes to building a massive LOM to Gustav's point, let's partner with the LOMs of the world that do this as a business.

25:36And I think it's as simple as that. So when we're looking through all the different vectors, we want to build the models that we believe are competitive advantages to be able to build and be best at. And then those others we should partner with. There's a junction there, at least for us, giving just the amounts of data and notes and the graph, is that rebuilding is an integration model with the models to be really powerful. So today, many companies will just push all the information to the prompt. More of, like I would say, like an interim solution until you have your own integration with the model on the first step.

26:08So imagine the prompt already knows to reach the dispatcher or the router, and that will basically grab both of the machine. There will be conflation at the tier level that the prompt can also be masked from. And I think that's actually really powerful. I don't know if I want to compete with the next developer developer conference from OpenAI, despite us being some siblings to an extent. For a Microsoft standpoint, that's what they'll do best, but what we do best is understanding how it works for the X. But Gustav Duves amazingly well is understanding the idea of audio and media. What Scott will do really well is the idea of design and visuals.

26:41Building that asset for me is a massive differentiation, competing for, which I think would be also super hard to compete, and you're competing for technology, and I think you're competing for really solving problems. I don't think is the right solution. I don't see anybody winning there, really. Does it change how you do anything with regards to data collection, data treatment, data cleansing? I love that. Okay, I have to take this one. I'm gonna start. It was keen for me. This is a big one for me. It's been a pet peeve of mine for a long time. So when I was, I've been preaching AI first, mentality for a long time and really trying to push both design and product folks and we're engineers to think about data collection and quality data.

27:23For a long time. Again, this has been like a father being like some of us like somebody else will do it. That assigns will figure out how to just collect it from the signals and like you don't understand this is this is the limit. This is oxygen. This is what feeds if AI is at the center but basically brings it to life is data. I remember like early on at LinkedIn I used to literally like spend so much time filtering by myself data so I can basically say this is good food. This This is good diet. This is what you should eat for like, this is what the algorithm should eat. But somehow people gravitate towards the UI or they gravitate towards the specific individual elements of it.

27:56Not understanding that actually feeds the algorithm is the data. My opinion as a product leader, a designer or an engineer or a product manager, data is literally according to your second most important job in your role. It's understanding how do you basically start to infuse all of data collection and make sure it's high quality. The first moment for the job is understanding the objective of the algorithm, which most people also. People outsource this stuff, it drives me insane. They outsource what is the objective of the algorithm to do. They kind of create some kind of spec, not nowhere in the spec is it ever written.

28:28What is the algorithm supposed to do in a nuanced way? And the outsource this stuff? But data is a massive, massive pet peeve of mine because most people just disregard it. Or they just assume it will be there. Somebody is going to create it and collect it. We just always have to be very careful because we're so focused on for the purposes of generating content The commercially viable and safe nature of the model matters a lot. We're always trying to learn how customers use our tools But we don't ever train our models off of the customers' creations So like what the customer makes unless they submit it to stock and want it to train our models You know, it's interesting like when we first launched our models like there were there were some people who went in and you know typed in Spider -Man doing something and said, oh my god, this is sucks.

29:11Like, you know, Firefly doesn't even know who Spider -Man is. And we're, we had to explain, like, that's actually, that's a feature. You know, it shows that we didn't train on copyrighted content and you can trust the way that these models are trained as opposed to some other models. So the data policies matter, matter a lot. But one thing I should say, you know, Adobe's always been two businesses really. It's like the digital media business and digital experience business, which is a set of tools that big companies use for their marketing and whether you go to Nike or any of these other brands, like a lot of them will use our tools to manage their customer experiences at scale.

29:43And I've always felt like in some ways, Adobe was two different companies sometimes. And in the last year, suddenly it makes so much sense because the digital experiences you're delivering, like the marketing, the content, you know, your experience on the Nike website or whatever, can be informed by the company's relationship with you. And the sizes of shoes that you've purchased before and where you live and things like that. So for marketing purposes, companies are going to leverage their own data to dramatically personalize digital experiences in ways we can't even fathom right now. That's really cool for the future of digital.

30:17From our point of view, we had the same journey that Tomere had about data. We did realize the value of data early on with all the playlists we had, which was the basis for our first simple embeddings. For us, obviously, the usage data, how you play less, how you listen is very important. We had that journey as well. I think the best example is actually Scott and Firefly where you're solving an IP problem. You're also solving a technical problem of I won't paint in and so forth, but you're also solving a business problem. By the licenses and the rights we have to the data, that's a very important angle that you may forget.

30:51You can solve many problems for a consumer or a user. In general, we've seen the first wave of AI now where the technology is very impressive, it's starting to do useful things. But we still, usually, the big changes come when that technology enables a new business model somehow. And that hasn't really happened yet. I'm absolutely certain it's going to happen, but so far it's like mostly sustaining innovation. What do you think that business model is like, your stuff? I don't know yet. I think one example is Firefly. It was trying to solve a business problem as well. Most of these things are not yet trying to think about it, but business models can change completely.

31:27and they probably could. But I think before that happens, this will be sustaining innovation that largely accrues to bigger players. Usually when the business model is challenged, there's some encounter positions like a big business model, that's when things really change. That hasn't really happened yet. You said innovation in the Vanioa Crew and to bigger players there. I think that's kind of what everyone's asking, which is like who wins, is it incumbents or startups and all startups say, well you know the incumbents they can't move very fast. And I mean respectfully, all three of you move really fast.

31:54My question is like, Is it kind of old BS that incumbents can't move fast? How have you guys been able to move so fast to embrace it? Scott, you talked about kind of the Cambrian explosions or Cambrian waves and jumping to, how do you move so fast at scale? And is it BS that incumbents can't? Well, here's the thing. I mean, every platform shift is not the same. They're all different. And if you're going from on -premise software to delivering in the cloud, that is a major, major transition that I can imagine many incumbents would struggle to do in a way as fast as a startup could do. And maybe that's why startups totally led the pack in terms of cloud alternatives to on -premise software in the past.

32:38And then you mobile was probably the same sort of thing. Different stock of developers, totally different go to market in some cases, different relationships with Apple app stores, and like, you know, there were so many differences. But with AI, I'm not actually sure that as a platform shift, which it certainly is. There are as many differences in how company facilitates and leverages that platform shift. Because when someone comes into Photoshop and they have an image that they want to change, right? If I can just give them a default bar that just shows up where they can just articulate what they want instead of using all the knobs and bells and whistles of Photoshop that have accumulated over the last 40 years, right?

33:17That is like a very incredible way of disrupting Photoshop to some degree. I don't have to build a net new company and a net new product from 0 to 1 in order to reimagine the capabilities of Photoshop using AI in this instance, right? Now people might not want to even download Photoshop in which case that's why we brought these capabilities to Firefly as a standalone app as well. On the off of Adobe, I'd love to take the credit of like moving super fast, you know, and I do think we executed well, but I also think that there's some nuances of this platform from Shift in particular that do favor those companies that know their customer well and already reach them.

33:53It's always easier to analyze other people's companies. I think like the risk for Adobe was before they moved the subscription model. Like the subscription model works with this as well. So that's why it's not disruptive. I think what has to happen somehow, someone has to figure out a business model that is disruptive to someone. Some people think that it will be disruptive to Google's business model. The ads model won't hold up in a conversational world. Not so sure that's actually what's gonna happen, but something like that would need to happen, I think, for Spotify, for example, when we started, it was the business model of streaming, that was the disruptive thing.

34:25The technology was a bit of peer -to -peer and stuff, but it was a business model that took Apple eight years of collateral damage to follow. That's kind of what needs to happen, I think, and we haven't really seen that yet. It could also be that this is just more productivity for the existing players. I appreciate the push on the business model, because I don't think we often talk about it, But you can play the regular like SaaS model based on seats. And if your technology really makes the organization much more successful than your seats volume model, does not work anymore. Yeah, that's a good point.

34:54Is it really just price that you increase? It becomes like a really big conversation to have around what's the business model when your product makes the organization more efficient? You're kind of realizing your own seats model. There's a brilliant piece by Sarah Tavill at Benchmark, actually, which is taught about selling the work and not the seats. Exactly. You actually need to still look because the idea of like, you're hiring, we talk about hiring, and we immediately imagine hiring people, but you're really hiring task completion. I love this question about what business models will be disrupted by AI.

35:23It's something we probably don't talk about enough. I mean, think about how many people in the world get paid on an hourly basis for what can be achieved in an hour. I mean, even lawyers charged by the hour still. Designers charged by the hour, and now you see these new technologies that are readily available. It's like, how does it even work? You know, you're really paying for, of course, right? is like the depth of experience and judgment that one applies to their work. You know, your lawyer's ability to know based on their like, you know, 30 years in practice, like what's likely to happen to advise you in the right decision.

35:55If that's made in three minutes, like how do you compensate them? And I think the same goes for the seats part as well. The functions of so many businesses are collapsing now. And so the idea of selling seats function by function, like how many people in procurement, how many people in financial planning, I mean, I mean, it's such an old, antiquated way of building a business to some degree in the age of AI. So I'm excited about this new value -based innovation vector for a business modeling. Is that challenging for you buying software then? When you think about buying new tools today, does it change how you think about buying tools?

36:26We're all huge buyers of tools internally as well. Like, you say antiquated, it's got to mean it nicely, but I'm sure like, we hope by a huge amount of seat -based tools like... What we do, and at some point, probably sooner than later, again, we're early in the days of AI, but at some point, when there are more tools in the organization that do many different things, I think that the idea of buying seats function by function will just evolve. It's a good question, Harry. When is that really going to be material and how is it going to manifest? Yeah, I think your next podcast is with a bunch of CFOs and how they're making mistakes.

37:01Because this is actually, this is where everybody Come on, give me a break again. Yeah, this is gonna be the next productivity layer. And I think like for many companies, I don't think coming and saying I wanna deploy this program for 20 ,000 employees is gonna work anymore. People are gonna stay like, wait, wait, what's more productive? How much output are we gonna get? But those are phenomenal questions we never used to ask. You're in a half a go. That's like an innovation catalyst. Again, speak to many people. Everyone says that AI development progression technology stellar cannot attend with any great job.

37:32Enterprise adoption, but a negative 4 out of 10. Noggot, I think as a start 32 % of European corporates do not know what slack is. That's concerning. How do you think about enterprise adoption keeping pace in any way with AI development? I think it's probably good news that we're so early in the adoption curve, because that means that there's a lot of potential ahead for these companies. And I also, it doesn't happen linearly. I think that the adoption happens in moments where there's like a step function, you know, breakthrough or people just suddenly realize that, and a lot of enterprise selling also happens because of who else is buying it.

38:10When I'm trying to work with customers who are thinking about, are we ready to change the way we do this? It's much easier when they hear about that company that has already changed the way they do this and how, you know, they're saving money and they're producing better output. It's like, oh, okay. But you know, I think that the part of this is always about getting small teams in big companies to start to play with something You know, that's where I think enterprise sales can fall flat sometimes and you have to have design partnerships with early customers as opposed to traditional Cells you know to go into early customers and say hey, I'm not even trying to sell you on this I just want a small team that can start to play with some of our technology We have this two -year -old model capabilities now for Firefly where brands can use some of their own IP and make a version of the model for them.

38:56And we've been going to some specific companies and saying, hey, be our partner, and let's play with it. And then of course, like that play becomes utility, and then that utility becomes a reference point. And eventually, you know, when we're ready to sell it, we're broadly. So I agree with Scott, both that it is early. Yeah, maybe it's our job to start using these things ourselves internally first and get them to work. But I also agree with Scott that I think it's going to go much faster than moving to cloud. I know we actually were on -prem companies that old. It wasn't possible to just also be on the cloud and try a little bit.

39:27It's incredibly hard. I don't think this will be that hard. I think you can try these things in parallel. It's going to be an S curve, but I think it's going to be a sharp risk curve once it happens. You've spoken about the seismic change needed in product and designer minds. If you were to sit down with young designers, young product people, we have like 700 ,000 that listen to 20 products. What would you say to them in terms of what they can should do to equip themselves for the changes that we're seeing so that best placed in that career is. I'll start with a quick stat for this we're gonna receive a trucky very closely at LinkedIn they're just looking at talent overall for the world like the job is changing on you whether you like it or not so like I think this one mindset for us I think everybody here on the call and for every generation to come like your job is gonna change much faster than you think but it might even change titles the tasks will change it's really about how you more for that.

40:21We looked at like the last five years, obviously AI plus playing a big role, but the skills that necessary to do a job change by 25 % in the last five to six years, by 2030 they're gonna change by at least 65%. Where do you want it or not your job is changing? So the necessary to learn and to really start shaping your understanding of the task you're trying to do, how the task is more thing is critical. For me I would put it under the umbrella of growth mindset, just the ability to learn. Then there becomes like more of a question around how should I think about beyond being AI literate and be beyond being focused in an AI first mindset, but should I do, I think there's two aspects that come to mind to me.

41:00One is like a more of a t -shaped perspective where I would assume you should have more broad skills than you have before the ability to activate or to that angle I would still build expertise around a specific domain or specialty. We talked about disruption before, we've been incumbents and startups. Usually we talk about tech. There's so many industries yet to be disrupted that nobody talks about but those could be remarkable areas to focus on and lastly I think it's innately what makes us human things like soft skills interpersonal dynamics and Imagination like just focusing on those those are not going anywhere guys hit me They're granular.

41:36What do I actually do my job's changing treating yourself as a business is something also everyone should always do It's you know how you organize your your ideas and information how you track your own spreadsheet for your own budget. Like we're all, we all have our own business called ourselves that we also manage part of being a human being. So embrace these tools. A lot of folks used Google Apps for themselves before they introduced them to their companies. You know, a lot of us used Evernote or Notion or other things and then we said, wait, I want to use this with my team. Have some embracing novelty precedes utility.

42:11Playing with something gives you ideas of how you can maybe pilot it with something you do in your day job. And then if you have a pilot, that's how you learn as to whether or not it's relevant for actual practice. So that's how we stay on the edge. And it's interesting. We all know people who are those early adopters who love playing with new tools. And then we all know people who are the total pragmatists who are just like, I don't use it until I'm told I have to change my tool. And you can rip this old tool out of my hands at the last minute that it's supported within the company. If you're listening and you're early in your career, you can be the person on your team that introduces new practices.

42:48That's your advantage in a company, especially working with a lot of people that have been around a lot longer, is you can be the one who pioneers new practices. And I think in general, like the one we think about big shifts, that's actually when the opportunity rises, this calls point, a lot of people are slow to change. So it usually is the case that one of the advantages of coming straight out of school is that the disadvantage is your new experience, but the advantage is usually you have the latest and greatest knowledge, where someone who worked in a company for 10 years, they're using the old tools.

43:18So I think that's still true. You can have that advantage, but even if you're in a company, the only advice is to educate yourself. And as we said before, in this instance, it's actually simpler than ever. You don't have to ask for permission to learn how to prompt and how to use these things. Education is only internet is basically free now, it's very cheap. I think it's easier than ever, more democratic than ever, to Tameras Point as well. It's just going to keep changing. There's actually the risk is if you're in a company that you don't develop fast enough. I think if you're fresh, you're going to have those later skills.

43:50Listen, I want to dive into a quick fire. So I say a short statement, you give me your immediate thoughts. Scott, I like your newsletter. What's your biggest lesson from running applied to product? Oh, from running. There are a lot of lessons that I have attracted from running. I'll tell you one of them, which is when I'm running, I often have ideas. And I'm obsessed with capturing ideas and I'm always worried about forgetting ideas, but when you're running I just like force myself to keep running because I don't want to give myself an excuse to stop running to capture an idea And that period that I am forcing myself to keep thinking about this idea as opposed to writing it down It always gets better.

44:25I think about that now in my like every day work I'm so impulsive. I'm always like trying to be decisive. I feel like that's one of the best practices of being an executive is decisiveness, but if you can like sit with something a little longer than comfortable, oftentimes you end up with a better approach to how to say it, you know, to how to give the feedback to the person, you know, how to like solve that problem with the product. I have this like mantra of wait for it that I've learned from running. The cadence of running actually, I think, is almost like a process you're forced to iterate the idea.

44:55It's is almost like in a, you know, in the trans. I totally agree. Having the force to be It's something and something and you have this clock going tick tick tick for an hour. It certainly helps to add in. Tomah, if you could change one thing about the LinkedIn product today, what would you change? What's interesting right now, we talked about the idea of UI and complexity. There's this great law that I'm, I really like it was really helpful or that it might correct to think about how to build products which is the conservation and complexity. The idea that every product has an inherent amount of complexity.

45:22Ideas, you can use solve it in the product development side. I do actually put it on the user to solve by themselves. And I think we're in this phase right now where there's so many use cases and audiences that people come to the LinkedIn main app for and That just had inherent complexity because there was so many you know you come in the morning You're trying to see what's happening in the world later in the afternoon your interview somebody You want to check out their profile then you know your bus Upset it you later the day and you want to see what's out there for you This is all three use cases in the same like 24 hours now with the eye and I would claim probably this would be more or generalized statement, the more complex your product, the more impact the I could have in terms of simplifying it for your user base.

46:01So one thing that we're already underway for us is really take away the complexity and solve it with the idea of bringing in more of this new, large language models. And in general, this new brain that can exit on top of it. So instead of adding more features, it's the same experience, we just morph stores your need. So more TVD on that one. I think you should call it a name like Einstein. Then you love Einstein as a name for Salesforce. We call it fighting the entropy in Spotify. Tell me, Scott, what if you changed your mind on the last 12 months? Well, I think within a big company, you know, I've changed my mind on the need for centralization.

46:38Where things shouldn't be centralized. Like, I always go back and forth, honestly, on this. You know, there have been periods of time where I felt like design needed to be in different organizations because people had to prioritize and properly resource design for their business. and then recently I recentralized design in one organization because our strategy you know required it and I guess one of the things I'm learning is that sometimes you know you make a completely opposite decision at different times in the same business because the playbook is different and we typically don't think that way we like when we make a huge decision and it's like this is the way it's gonna be we just stick to it because we almost think like it's first principles but you just have to be willing to discard the playbook consistently Okay, let's go for you, Tomah.

47:21Can product leaders not be trained in AI today? Can you be a CPO and not have really spent hard yards in AI? I would not hire you to my org if you don't have the willingness and the aptitude to go deep again. I don't need you to be the engineer working on the model, but I need you to understand one, the objective you're trying to build and how to build it. Otherwise, what are you here for? And two, all the underlying principles that come with it. The idea of it's not being deterministic, so how do you build the knobs so elegantly that the experience is great in any shape or form? To how do you think of data collection in a way that's responsible, but really fuels what you're trying to build?

48:01And to be it's that velocity we just talked about, if you don't have the velocity of learning, I don't think you'll last. Guest our final one for you. What are you most excited about when you look at AI in the coming years, what it can do for everyone, but also for Spotify. Just what excites you most. For me, we experienced the shift to mobile. It was very scary. Our business model had to change. Could have disrupted the company. It was also by far the most exciting time I had. And to be honest, it was a little bit too stable for a few years there. And I feel like we're back to that kind of change.

48:31I'm secretly hoping for that business model challenge. And those things happening, that everything changes again. I don't know if you agree Scotland to me, but if you're a designer product person, those are the exciting times. We're right right there now. I don't think we're at the end of it. I think we're at the beginning of it. Sound kind of back to like more excited than maybe in the last seven, eight years. It's unclear now what's going to happen. We were on a little bit of an iteration track for a while there. It's not an iteration anymore at all. So that's what I'm excited about. Thank you so much for this.

49:02This has been fantastic and I so appreciate you putting up with my questions. Thanks for having us and I'm very good I'm good to see you guys.

49:12I cannot state enough how much I love doing that show. If you want to let me know on Twitter at Harry's Steppings what you thought and feedback on the format itself of the show I'd love to hear your thoughts there. Likewise you can check it out on YouTube by searching for 20BC, love to hear your thoughts on that format also. But before we leave you today, HMC or Harvard Management Company, they're constantly seeking out the next generation of truly great investors and entrepreneurs. HMC has managed Harvard University's endowment for nearly 50 years and was one of the first institutional investors in venture capital.

49:44Their experience and long -term investment horizon make them ideal partners to get world -changing ideas on apart the viability and success, they work as a true partner, providing insightful perspectives to help managers succeed. I personally have had the pleasure of working with the HMC team and can say that they're truly exceptional partners and just great, great people to work with. Whether you're launching your first fund or your fifth, HMC welcomes the opportunity to partner with both developing and established managers. Have an idea you want to share with the team? Just send it to ventureathmc .harvard .edu.

50:18As always I so appreciate all your support and stay tuned for a fantastic episode this coming Friday.

From the publisher

Gustav Söderström is the Co-President, CPO & CTO at Spotify. Gustav has been instrumental in taking Spotify from a 30-person operation in Sweden when he joined to being the global leader of the space.

Scott Belsky is Adobe’s Chief Product Officer and Executive Vice President, Creative Cloud. Scott oversees all of product and engineering for Creative Cloud, as well as design for Adobe. 

Tomer Cohen is the Chief Product Officer @ Linkedin where he is responsible for setting and executing the global product strategy at LinkedIn.

In Today's Episode on How AI Changes The Future of Product and Design We Discuss:

1. Why AI Is Now the Product that UI Serves:

  • Why does Gustav believe that AI is now the product?
  • How has the importance of UI changed with the rise of AI?
  • How did TikTok change the product paradigm over the last few years?

2. What Matters More Models or Data:

  • What is more important the size of the model or the amount of data a company has?
  • Will companies use many models at the same time?
  • Why will companies using many models at once create a huge opportunity for startups?
  • Will every company have their own model? What will be the decision-making framework of whether to have your own model or leverage another?
  • How does the rise of AI change how companies approach data acquisition, collection and cleaning?

3. The Workforce Needs to Change with AI:

  • How do product leaders and teams need to change in an AI-first world?
  • What do designers need to do to stay up to date in an AI-first world?
  • What does it mean to be good at prompting? How can people get good at prompting?
  • Why will AI kill companies that charge by the hour?
  • Why will seat pricing die in a world of AI? What will be the business model for AI?

4. Incumbents vs Startups: Who Wins:

  • Do incumbents win in a world of AI or do startups?
  • Why is AI primed for incumbents to win and move fast in a way they could not in prior technology cycles?
  • What are the biggest hurdles and challenges incumbents have to face that startups do not?
  • What are the biggest barriers that startups have to win in a world of AI that incumbents do not have?

More from The Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch

All 520 episodes
20VC Roundtable: Spotify, Adobe & Linkedin CPOs on How AI Changes The Future of Product, Why AI is Now the Product, How TikTok Changed Product, Why Cost is the Biggest Barrier to LLM Usage & Why Incumbents Can Adopt AI Faster Than Any Prior Innovation CycThe Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch · 50 min
Listen in VO