Microsoft CPO: If you aren’t prototyping with AI, you’re doing it wrong | Aparna Chennapragada

18 May 2025 · 1 h 1 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

Episode Notes: Microsoft CPO: If You Aren’t Prototyping with AI, You’re Doing It Wrong | Aparna Chennapragada

Podcast Title: Lenny's Podcast: Product | Growth | Career Host: Lenny Rachitsky Guest: Aparna Chennapragada, Chief Product Officer at Microsoft Release Date: [Insert Date]

Overview In this episode, Lenny interviews Aparna Chennapragada, the Chief Product Officer at Microsoft for Experiences and Devices. With a rich background that includes serving as CPO at Robinhood and extensive experience at Google, Aparna shares insights into the evolving landscape of product development, particularly in the context of AI.

Key Topics Discussed

  1. The Importance of Prototyping with AI
  2. Prompt Sets as PRDs: Aparna emphasizes that prompt sets in AI are the new Product Requirement Documents (PRDs). They are essential for effective product development.
  3. Iteration and Prototyping: She highlights the significance of rapid prototyping to visualize concepts and facilitate communication among teams.
  1. Characteristics of AI Agents

Aparna outlines three key traits of AI agents

  • Autonomy: The ability to take on tasks independently.
  • Complexity: Handling multi-step challenges beyond simple queries.
  • Natural Interaction: Enabling conversations that resemble human dialogue, going beyond basic chat functionalities.
  1. Natural Language Experience (NLX)
  2. NLX as the New UX: The transition from graphical user interfaces to natural language interfaces (NLX) is critical. This requires a thoughtful approach to designing conversational interfaces that account for grammar, structure, and user experience.
  1. Evolution of Product Management
  2. PM Role: Contrary to fears that product management roles might diminish in the AI era, Aparna argues that the role is evolving. PMs are becoming essential for taste-making and editorial functions in AI-driven environments.
  3. Collaboration with AI: A vision for enhanced collaboration between humans and AI agents is discussed, where outcomes exceed what either could achieve alone.
  1. Leadership Insights
  2. Differences Between Tech Leaders: Aparna compares the leadership styles of Microsoft’s Satya Nadella, known for his multi-level thinking and early trendspotting, with Google’s Sundar Pichai, who excels in managing complex ecosystems.
  1. Framework for New Product Opportunities
  2. Zero-to-One Product Opportunities: Aparna introduces a practical approach for evaluating new product ideas, emphasizing the importance of timing, technological inflections, and shifts in consumer behavior.

Key Takeaways

  • Prototyping is Crucial: Emphasizing the need for rapid prototyping and iterative development, Aparna asserts that teams should prioritize visualizing ideas.
  • AI in Product Development: AI tools are reshaping the landscape of product management, necessitating new approaches to design and user interaction.
  • Emerging Roles: The role of PMs is evolving rather than diminishing, focusing on strategic oversight and taste-making in product development.

Additional Resources

  • Aparna Chennapragada's Links:
  • [X](https://x.com/aparnacd)
  • [LinkedIn](https://www.linkedin.com/in/aparnacd/)
  • Lenny Rachitsky's Links:
  • [Newsletter](https://www.lennysnewsletter.com)
  • [X](https://twitter.com/lennysan)
  • [LinkedIn](https://www.linkedin.com/in/lennyrachitsky/)

Conclusion This episode provides a comprehensive look into the future of product management in the age of AI, highlighting the importance of innovation, prototyping, and strategic leadership. Aparna’s insights serve as a guide for product leaders navigating this rapidly changing landscape.

---

*For further discussions, feedback, or to explore more about the topics discussed, feel free to reach out or subscribe for future episodes.*

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:00I have a cheesy Chrome extension literally whenever I open a new tab, it just says, how can you use AI to do what you're going to do right now? How do you see the future of product development being different? If you're not prototyping and building to see what you want to build, I think you're doing it wrong. It becomes even more important to have that editorial and taste making at the heart of it, because otherwise you just have Frankenstein products. There's this acronym that you taught me, NLX. What is that? Natural language interface, NLX is the new UX. Often I hear product builders say, oh yeah, with AI, the model leads to the products.

0:34That doesn't mean it's not designed. You and I are having a conversation, it's a podcast. I'll have another conversation at Microsoft, and that's a meeting. Conversations also have grammar, step structures, they have UI elements. They're invisible. What are the new principles, new constructs in natural language as an interface? I just saw that cursor hit 300 million ARR in two years. Interestingly, you guys were very well positioned to do really well in this AI coding tool space. You guys said, co -pilot, the first tool in the world at the stuff. So ahead of everyone, what happened? I would say.

1:07Today, my guest is Aparnasha Naparagata. Aparna is chief product officer at Microsoft, where she oversees AI product strategy for their productivity tools and their work on agents. Previously, she was chief product officer at Robinhood, Vice President at Google, where she worked on Google Lens, Search, Shopping, Augmented Reality, AI Assistant, and a lot more. She was also a longtime engineering leader at Akamai, and on the board of eBay and Capital One. In our conversation, we chat about how working in B2B is like being Jean -Claude Van Dam doing the splits across two moving trucks. How she's operationalizing her team living in the future, so that they're building towards where things are going.

1:43Why people still need to learn to code? Why the PMRAL isn't going anywhere? Why NLX is the new UX? And so much more. If you enjoy this podcast, don't forget to subscribe and follow in your favorite podcasting app or YouTube. Also, if you become an annual subscriber of my newsletter, you get a year free of a bunch of products, including linear, superhuman, notion, perplexity, and granola. Check it out at Lenny's newsletter .com and click bundle. With that, I bring you Aparnasha Naparagata. This episode is brought to you by Epo. Epo is a next generation AB testing and feature management platform built by alums of Airbnb and Snowflake for modern growth teams.

2:22Companies like Twitch, Miro, ClickUp, and DraftKings rely on Epo to power their experiments. Experimentation is increasingly essential for driving growth and for understanding the performance of new features. An Epo helps you increase experimentation velocity while unlocking rigorous, deep analysis in a way that no other commercial tool does. When I was at Airbnb, one of the things that I left most was our experimentation platform. Break it's set up experiments easily, troubleshoot issues, and analyze performance all on my own. Epo does all that and more with advanced statistical methods that can help you shape weeks off experiment time and accessible UI for diving deeper into performance and out of the box reporting that helps you avoid annoying, prolonged, analytic cycles.

3:04Epo also makes it easy for you to share experiments inside through your team, sparking new ideas for the AB testing flywheel. Epo powers experimentation across every use case, including product, growth, machine learning, monetization, and email marketing. Check out Epo at GetEpo .com slash Lenny and 10X your experiment velocity. Let's get eppo .com slash Lenny. This episode is brought to you by Pragmatic Institute, the trusted leader in product expertise. Pragmatic Institute helps product professionals turn ideas into impact, through proven courses, workshops, and certifications designed for real world success.

3:44For over 30 years, they've trained more than 250 ,000 product leaders, a company like Google, Microsoft, and Salesforce, equipping them with practical strategies to build and scale market winning products. Pragmatic's full -time instructors each bring over 25 years of hands -on leadership experience, teaching strategies proven to deliver real world results. And it's not just about what you learn, it's also about who you learn it with. Completing a course connects you to an active community of over 40 ,000 product professionals. You'll engage in meaningful conversations, collaborate with peers and mentors, and gain direct instructor access to refine your strategies and stay ahead of trends.

4:22Get 20 % off with code Lenny20 at PragmaticInstitute .com slash Lenny.

4:32Apertna, thank you so much for being here and welcome to the podcast. Thank you Lenny, thanks for having me. When I asked a lot of people that work with you, what I should ask you about and what I should know about you, something that came up again and again is something that I think most people don't know about you, which is that you're you're big into stand -up comedy. And you take it semi -seriously. I just how serious are you about this, how much of your life is this, and most importantly, how does this help you build the better products? It's hard to say I'm serious about like a funny business, but I do watch and do stand -up comedy.

5:06I do open mics, I've done a few shows. I have one set brewing that is around AI, unsurprisingly AI and tech and Silicon Valley. You know, it's really interesting for me. This was an accidental discovery, like I'd always been an SNL fan and like just comedy fan, but I went to an open mic because you know, my son sings and he went to the open mic for singing and he's like, mom, you should go do this. And I was like, oh, let me go give it a try. And I found that I enjoyed it and was good at it. To your question though, about building better products, I'd say, both have PMF, I mean product market fit, punchline market fit.

5:48But actually, there are a couple of things that I do find really powerful and useful because, you know, in open mics or even when you're testing these things, it's a very tight cycle of iteration and you get live, like open mics are the real live experiments, right? You put something out there, you get very clear micro feedback from users and then you get tough feedback sometimes. And I think as product builders, that's actually one of the great skills to have, which is yeah, you sometimes launched stuff that you know, have a fantastic vision, but the first version is not quite there, right? And Reed Hopman says this, hey, if you don't launch the first version and are not in that, it's, you're doing it too slow.

6:27Just a gap and closing that, it's good resilience. Yeah, I never saw these curl areas between these two things. I didn't realize you actually did like shows and you're working on a set. I wasn't going to ask you for a joke, but if you're working on a whole thing about AI, is there something that you can share from that set? One joke I'd maybe share is people think about these AI chat products as women, because you know, you don't know what's going on. It's a black box. And you don't know what it's worth, what they're thinking. There's like an entire set around that, but obviously on the flip side too that, you know, they're probably more like men in the sense that they hallucinate a lot.

7:08They're, they kind of are not yet reliable. And they're very confident. And they, even when they don't know this is good. Where are we going to be seeing the show, by the way? This is great. Okay, let's get serious again. So you worked at most of your career at a lot of consumer internet companies. You worked at Google, Robin Hood. You're on the board of eBay or in the board of Capital One. Night, you're Microsoft. I'm curious just what is most different about working on a company like Microsoft and building product at a company like Microsoft? I think you know, actually I knew that, hey, enterprise, particularly the area that I look at most at Microsoft is focused on enterprise and productivity and transforming companies through AI.

7:58And to me, I think two things really strike as very different. One, in fact, I just posted about this the other day saying, in consumer, you're kind of like, oh, you have a playbook for make the product work or make the feature work and make it delightful. But I think in the enterprise, you almost have every time you think you have one use case, you're really true, which is how do you make sure that the feature works well and there's governance of the feature, right? If you think about like even something as simple as sharing a link to a document, you want it to be easy, frictionless, but at the same time, you want that to be secure and kind of safe and being able to have auditability and all of those things.

8:39And often I find that when you go from consumer to consumer to enterprise, you fall into a trap of either disregarding that and say, oh, we'll just focus on one side of the house or kind of overly crippling the user experience, and kind of leaning on the other side. So I think there's an art and science and nuance in playbook there too. So that's one big learning for me. The other learning, especially in the AI era for me, has been about this, I think there's a famous trailer from the 2000s on Van Dam on these like two trailer, two buses. Yeah, doing the splits exactly. I feel like a lot of the companies, including the tech companies, but certainly the enterprises that I talked to are in these two modes, one hand, this is the most compressed tech cycle that we've ever experienced, right?

9:28It's all in the order of weeks and months versus years and decades, if you think about like mobile and cloud and internet, and there's just like so much happening, the intelligence overhang. On the other hand, there's also like humans and habits that productivity habits change, it's hard to change, and change management through the company is also hard, right? You don't want to kind of be rash of that. So it's like, you know, the future is unevenly distributed, but even within the companies. On the second bucket of this other, this is the bus of Van Dam's writing on of governance and an adoption and changing behavior and stuff, is there something you've learned about how to get past that help that along more?

10:10The thing not to do is hold back folks who are early adopters, right? I think that's the other one learning. In fact, I think that's one of the reasons why recent VB, you know, I've been working with folks to say, can we have both, which is the longer term change management, being able to do it in a trusted way? At the same time, do this program, we're calling it Frontier Program, and roll out cutting edge experimental features, we just built this world's first agent for deep research agent made for work, right? Post -strained for work. And of course, it has, you know, all sorts of edges, rough edges, but if there are earlier doctors in an enterprise outside, how can we kind of put that in the hands of those folks without kind of insisting that all of the company be completely developing different muscles?

11:04This program, Frontier, you're talking about, I wanted to spend a little time on it. So, what is the idea? The idea here is like, people are working in this futuristic environment. How does that actually work? Yeah, I think the idea is exactly this, which is like, I want to kind of institutionalize and operationalize my personal model of like living one year in the future and say, what does this, imagine a company or a setup, like Frontier, it comes out in group, or Frontier Rink, right? And if you did live in that environment where you had all the AI tools and really advanced deep research intelligence on tap, what are the kinds of questions you'd be asking, what's the kind of work you'd be doing, how would you change, how you're going about your work day?

11:47So that's the premise. And you'd say, hey, how does it change an individual, but also down the lane, we want to think about what does a Frontier team look like? We talk a lot about Frontier labs and models. I think model's layer is amazing. And obviously, that's what empowers all these product building to happen. But I want to push us to think about what does a Frontier product look like? And more importantly, how does a Frontier way of working? What does a team with three people and tons of compute, then AI tools look like? So how exactly does this work? There's like a team within Microsoft that's like your job is to use all of our latest tools and build product using that.

12:28That is the setup. We're just a few weeks into that setup. But meanwhile, what we've done is like we've actually set up a like a external like a fake company and said, hey, if you are somebody who wants to come play with some of the cutting edge science projects and be research agents and agents at work, come have a company here. Wow. Okay. And it's only a few weeks in. Okay. So TBD, how it all goes. Yeah. And again, like these are micro. Let's see. The meta point here, right? Also is that in the traditional way, we've kind of always thought about across the companies, across industries, really thinking about rollouts in these macro ways, right?

13:07You build something and you kind of roll it out, you have a general availability for, and then you take the time. And that's really important too. Because again, like we're talking about former companies, legal companies relying on this. So we do want to have that. But at the same time, given the compressed cycles of AI, how do we start to have people experience what's what's the one year in the future? Let's follow this thread in a few different directions. There's like how product chain development changes, there's how engineering changes. There's also just agents. And you're spending a lot of time in agents.

13:38He'll like you're not an AI company these days. If you're not working on agents or building an agent. Many been going this wrong. We didn't force you. You didn't use the word agents. Like so far into the conversation. I try hard to push it out as far as I can. It's like every conversation, it's just like how long until I start talking about AI. It's like three minutes. But oh man. Okay. So with agents, I know that you're leading a lot of this work at Microsoft. And a lot of people are wondering what the hell, what does this mean? What is going to change? Give us just a glimpse into how you see the world being different in a world of agents being around more.

14:18There's a short term and there's a long term. There's a mod of hyperventilated talk about the eventual future and all of that. I take a much more practical product building lens on this. And I think about these at the end of the day, they're tools. Yes, underneath it, there's stochastic models versus very deterministic programming models. You can tell I'm a computer site. It's like the way that that word you definitely shapes how I think about this. To me, the short term is there's an evolution. We had apps. Right. And now I think we have formerly in the assistance era where there's like human driving the, you know, that's what we think of as co -pilot.

15:00Right? Like I think the human driving kind of the in the driver's seat, but having a lot of assistance from AI. So I think of this as then you look at the dimension of almost like autonomy and delegation and intelligence as the intelligence, for example, when deep reasoning unlock happened. Of course, then you could say you can delegate more to the agent. So I think to me, I think there's one dimension where you say, hey, agents are somewhat independent software processes, right? That can kind of like run tasks. And you're not just thinking about hand holding and fine motor stuff. You're saying, hey, here's my goal.

15:37Go make this happen. Like, I'll give you an example. Right? So we're working on this research or agent for work. And last night, I said, hey, you know, I'm really, I have an important meeting coming up with the leadership team. I really want to present these frameworks here. And this is the roadmap here. Go back and look at all the people that are in the meeting. What are their views on this topic and kind of come up with how do you how I should be thinking about like, you know, the right persuasion pitch here, right? And what's magical about this is not just that it's saving time. Typically, we think about the so far AI as summarizing a document or saving time, right?

16:14This is like, fighting synapses that I didn't I didn't quite have. And I actually giving me new insights and giving me that I say superpowers. So that's a natural evolution of AI I would say. So when I think about agents, I think about three things. One is, is an increasing level of autonomy and kind of independence that you can delegate higher and higher order tasks. Second thing I think of it is complexity, right? So it's not just a one shot, hey, create this image or do this thing or summarize the document. It's, you know, bill me this prototype that expresses my idea of an augmented reality app, right?

16:54It's a complex task. And then the third thing I would say is asynchronous. It works when you're not working, right? I think that's the other big thing about these things that you're not happy. You don't have to sit in front of it. This is answers the question of what is an agent essentially, these three ballpoints. So it's ordered the three again. When I think about agents, I think about these three things, right? So one, it's autonomy, like being, and it's a spectrum. It's not a zero one. It's how do I actually delegate things that it can do? Second, I think of as complexity, right? It's not a one shot, hey, summarize this document, generate this image, but it's, you know, bill me this prototype or help me knock this meeting out of the park, right?

17:35And then the third one I think of is, it's a much more natural interaction. That doesn't just mean chat, but it may be actually jumping on a meeting with the agent and being able to like talk through all of it or point it to things that I wanted done differently. So I think all three things, the autonomy, the complexity and the natural interaction are at least product principles that will shape really good ones, good agents. That is really helpful. Along this line of agents, there's this acronym that you talked me as we were chatting out of this podcast, NLX. What is that? And how does that relate to agents?

18:08And why are people not thinking about this enough? Oh, that's one of my Roman employers these days, the natural language interface, NLX is the new UX, right? So I think here's the, here's the, here's the view. To me, I think traditionally we've thought very consciously about GUI because the graphical interfaces are not something natural and so they have had to be explicitly designed, but they're is it say, it's a much more elastic, right? That doesn't mean it's not designed. So people have, often I hear a product builder say, oh, yeah, with AI, like the model leads to the product, so it's just you chat with it.

18:52You and I are having a conversation. It's a podcast. I'll have another conversation at Microsoft and that's a meeting. So conversations also have grammars, they have structures, they have UI elements, they're invisible. And so one of the things that I see and I'm really excited about is what are the new principles, new constructs in natural language as an interface? I'll give you a few examples, right? And actually, like a lot of startups as well as big companies are really experimenting with this stuff. One is if you think about it prompt itself is a is a new construct and that's a new way that's a new UI element just like a drop down was or a menu was.

19:31But others that are emerging, especially for agents, I think are plans. So when you give a high level goal, what we're seeing is that when the agent comes back with a plan, preferably an editable plan, that's a new construct. The other one that's that I think about a lot is showing the work, right? Progress. You see this with the different products, right? You see with the co -pilot, chat GBT, deep seek, this idea of thinking aloud. And it's kind of showing the work. But how much do you do it? If it's two wordboats, it feels like I'm running some cron job and scripts. But if it's two doors, then I don't know if it's going in the right path and I don't have the confidence yet.

20:13So there are all these new elements. So if you're a product with or this is a fun new space to be digging in for product design. This is really interesting because I think people chat with all these chatbots and it just feels like this is just the way it is. But you actually are designing every element of the interaction. How much to share about how much you're thinking, here's my plan, what do you think? So I think this world surprise, a lot of people just realizing there's so much that goes into just designing even these what seemingly are simple conversations. Yeah, another good example is follow ups, right?

20:49You could say, look, you ask me a question and then I could ask a follow up set of things and that explicitly should be designed for success, right? So for example, if I said, hey, create an image and it created a black and white, you know, I don't like a clip art version of something. What are the next obvious follow ups that it should be suggesting proactively? Now too much and you're kind of annoying me, right? Like but too little and in some sense, you've lost an opportunity to direct me or guide me into a happy path here. This resonates a lot with when we had Kevin Wheel on the podcast, he talked about this question of just how much to show about what you're saying and you know, and it's interesting that deep seek went the extreme of just showing everything and people liked it too.

21:37I think that was interesting. Yeah, and I think it's a point in time to learning because in some sense, right now, these things are such black boxes that almost like peaking under the hood for anything, even if it's verbose, feels like, oh, I know what's happening, especially because the compute inference time, it's taking long to think. So it just feels like, if you just went silent, I'd be very uncomfortable, I think.

22:05So I do feel like there's that point in time, but over time, I also feel like this is an area ripe for personalization. For example, like I get in the human, like my API would be very different from some where my interface is probably different from others. And I might just want the direct hey, give me the TLDR versus the, oh, so I went here and then I went there and it's like, following the start a little bit, we're talking about just how the future is going to be different. There's like designing for these chat experiences, there's agents kind of zooming out to just product development in general.

22:38It feels like you're at the forefront of a lot of the tools that are going to change the way we build products and also your teams are working with a lot of these tools that no one else has access to. So let me just ask, how do you see the future of product development being different from today, most, and what do you think product builders should be preparing for doing to kind of to succeed in that future? I'll start with one stark statement that I say internally and externally and I trying to live it is that in this day and age, if you're not prototyping and building to see what you want to build, I think you're doing it wrong.

23:16I call it the prompts sets of the new PRDs. I really insist on folks saying if you're building new projects, new features, of course come with prototypes and prompts sets. And I think the notion is not to say, hey, now everybody is just a big version of a software engineer. It is to say, you have the fastest path to seeing and experiencing what's in your mind to be able to communicate. It's a much more high bandwidth way of communication. I think about that as a really a loop accelerator in terms of product building. That's number one. When in doubt, as someone put it, demos before memos. I think that's really number one.

24:04I would say number two. This one is a little bit tricky. I'd say is that what I'm seeing is that the time to first demo is much shorter. But the time to like a full deployment is going to take longer. So I think that there's going to be an uneven cadence. So typically, I think there was much more of a, hey, you've been this thing. You take a few weeks and then you can iterate and so on. But that inner loop of like prototyping and iterating and getting even user research through AI conversations, all of that gets shortened. But I think the power for scale therefore becomes much high. In some sense, if you look at it, there's going to be a supply of ideas, massive increase in supply of ideas in prototypes.

24:53So which is great. It raises the floor. But it raises the ceiling as well. In some sense, how do you break out in these times that you have to make sure that this is something that rises above the noise? So I would say that it's simultaneously thinking about not chasing after every idea. I think there's a second one. I'd say the third thing is there's a lot of conversation around full stack builders. What does the team of the future look like? The product building team. What I think about is, I think that is inevitable in terms of like, there will be a few folks that are especially at the prototyping, early idea discovery stage that the lines of blurred, right?

25:35There'll be a few taste makers at the same time. I think you can still have a lot of people experimenting. It becomes even more important to have that editorial and taste making an audio one or a few at the heart of it. Because otherwise, you just have Frankenstein product. That definitely doesn't change. I have a one other additional bonus thing, which is a lot of folks think about, oh, don't bother studying computer science or coding is dead. I just fundamentally disagree. If anything, I think we've always had higher and higher layers of abstraction in programming. We don't program in assembly anymore.

Read the full transcript

26:22Most of us don't even program in C. Then higher and higher layers of abstraction. To me, they will be ways that you will tell the computer what to do. It will just be at a much higher level of abstraction, which is great. It democratizes. There'll be an order of magnitude more software operators. Like in Swiss, maybe we'll have souls. But that doesn't mean you don't understand computer science. It's a way of thinking and it's a mental model. I strongly disagree with the whole coding is dead. That's awesome. I love that. So is a software operator? What is that with that dance floor? Yeah. I just made it out quick.

27:02Yes. Okay. Cool. This idea of prototyping is being core to building these days. Is there anything you do within Microsoft to operationalize that and make that a thing everyone has to do? Is it just culturally do it or is it like you must show me a prototype before you show me? I think the future is here unevenly distributed. Even in Microsoft, I would say. But there is certainly a strong cultural momentum and shift and desire to say, hey, let's actually look at live demo's, live prototypes. And to even communicate the ideas. And to me, it's not always possible because obviously there are things that are deeply, if you're trying to change something in the bubbles at Excel, you probably don't.

27:49There's even enough depth in the product that, you know, what you need to do and you don't need to prototype that. But if you're especially thinking about new things and new products, new features, absolutely. Okay. Let's talk about product management. There's this fear that emerged as soon as all these AI coding tools came out of just like, PMs are dead. We don't need PMs. We could just build things ourselves with what are these people hanging around for? And what I found is it's actually the opposite that now that coding is easy. Now the question is more and more, what should we be building?

28:23Why should we be building it? Is this right? Is this the right solution than getting adoption for it? Which is what PMs are really good at. And so I feel like it's the opposite. Like, PMs are the most important role and they're, you know, it'll change, do. But let me get your take. But just what do you think the future of product management looks like?

28:44You look, I mean, if you're a TPS report, mostly process person and like a lot of companies do get confused about product management and process and project management, I think then you do have a question of like, hey, what is the value add here? Right? Especially if like AI can read and write like 50 ,000 meeting notes and, you know, attract things and send emails and so on. But I think what what I do think on the flip side is the taste making and kind of the editing function becomes really, really important, right? In a world where the supply of ideas, supply of prototypes becomes even more like an order of magnitude higher, you'd have to think about like, what is the editing function here?

29:34So that does mean that the bar is higher for you for product folks. But I there's an interesting side effect I am observing in startups that I'm advising companies and even within the companies that there's, there used to be more gatekeeping, I would say in terms of like, oh, this is, you know, we should ask the product leader what they think. And again, like there is a role for that editing function, but you have to earn it now. You just don't get it because of this title. But there's also just like unlock of latent really good ideas from smart engineers, smart user researchers, smart designers who can now who now have like this expert in their pocket, right?

30:16To kind of round out all the other things that they're not, they're not typically skilled at to bring for their ideas. And that's amazing, I think. And I think that expert, it's interesting. I'm working with an engineer and some stuff. And he uses chat GPT to even communicate to me in a more effective ways, like turn this pitch into something that will convince Lenny this is a good idea. By the way, that is actually one of my common use cases, which is the WWXD. I call it what would X do? Like I used to say, hey, what would the Sathya think about like this particular set of conversations or ideas that we're pitching and so on?

30:56This is the power of like, I think, deep reasoning plus relevant context, right? This engineer you're talking about has that context about you. And so it's kind of very interesting. If only everyone was as famous as Sathya and I had so much information out there, but I guess you can import all their emails or whatever tools exist to just like understand from the conversations you've had with that person. Yeah. And I think this is this goes back to actually what you were saying too, which is I think this idea of what is the, there's like a coil spring, there's an intelligence overhang that I just see across the board.

31:27And I think the part of product development has to almost rewire ourselves to I think Toby from Shopify calls it the reflexive AI usage. And that's not as easy. And I've been thinking about why, like I basically, I mean, I have a cheesy Chrome extension literally whenever I open a new tab, it just says, how can you use AI to do what you're going to do right now? Just like it's very cheesy, but it kind of helps to pause and think, oh, what am I trying to do here? But the reason I find it hard and when I talk even like people who are living and breathing in this space, they find it hard is that, you know, the updating of the priors is really hard.

32:06Like the models couldn't do some things one year ago. Like, I mean, image generation was full of spellings or like reasoning, you just couldn't like, you know, have deeper and smarter answers. You couldn't do data analysis. So like my impression of it from change and trying it a few months ago, that prior needs to be updated and it's hard to do that, right? And you have to kind of do something almost counterintuitive and against the grain to say, no, no, like ignore what you learned about like what this can or cannot do. Like the baby just grew up to be a 15 year old in a month. I think that last point is so important that we've tried these tools over the years and it many like so far, it hasn't been amazing and then all of a sudden it is and you kind of don't know that and you've given up almost and things change.

32:52I think that's actually if you're a product builder listening to it, that's a really interesting arbitrage thing for you. Like if you can kind of cut against the grain and say, no, I won't have that scar tissue and I'm like, you know, this didn't work a few months ago and keep setting high expectations and like demand more of the AI today, I think you can unlock more. There's a lot of alpha in doing that. That's right. Today's episode is brought to you by Coda. I personally use Coda every single day to manage my podcast and also to manage my community. So I put the questions that I plan to ask every guest that's coming on the podcast.

33:31So I put my community resources. That's how I manage my workflows. Here's how Coda can help you. Imagine starting a project that work and your vision is clear. You know exactly who's doing what and where to find the data that you need to do your part. In fact, you don't have to waste time searching for anything because everything your team needs from project trackers and OKRs to documents and spreadsheets lives in one tab all in Coda. With Coda's collaborative all in one workspace, you get the flexibility of docs, the structure of spreadsheets, the power of applications, and the intelligence of AI, all in one easy to organize tab.

34:06Like I mentioned earlier, I use Coda every single day and more than 50 ,000 teams trust Coda to keep them more aligned and focused. If your startup team looking to increase alignment and agility, Coda can help you move from planning to execution in record time. To try it for yourself, go to coda .io slashlanny today and get six months free of the team plan for startups. That's coda .io slashlanny to get started for free and get six months of the team plan. Coda .io slashlanny. I'm going to come back to this cheesy plug and say more about this. So this is a plug in that just lets you put a custom message on every new tab and it just you have it say, how can you use AI to do this?

34:45Yeah, it's as cheesy as that. And it's interesting because it works in the last few weeks alone. I've been doing this like experiment to say, hey, how much more AI pill can I get? Like both at work and in a person life to say, you know, when I'm trying to do anything manual, like, should I be demanding the AI to do this? That's so cool. Do you know the name of this Chrome extension by any chance? Otherwise, no, I built it. You built a Chrome extension. That's so cool. Okay. Did you use AI to build it? Of course. Wow. Which tool did you use to do that? Some kind of Microsoft tool? I imagine. Yes.

35:25Yeah. No, actually, it was just like, I mean, I live in GitHub and GitHub. Copilot. So just like, was like, okay, let's go build this Chrome extension. Yeah. Are you releasing this for the general public? No, I mean, this, that stuff on that's amazing thing. It took me like 10 minutes to do this. Okay. Let's link to it. Let's get it out there. Open source is thing. Okay. You mentioned Satya. I have a question about this. So you're one of the very few people that have worked very closely with both Satya and Sundar at Google. Let me ask you this. How do their leadership styles differ? And is there just like a fun story you could share by each of them?

36:02Yeah. I do feel, I do feel lucky to have, you know, kind of have a been going to these two amazing leaders of this generation. I would say, I mean, again, no surprise. They're as you'd expect from CEOs of multi -tillion dollar market tech companies. They are 99 .99 percentile in like almost every dimension you'd think of right in the leg empathy leadership, you know, be product strategy. They are of course, flavors of differences. I was at the technical advisor for Sundar with the first at Google and set up kind of the office of the CEO there. And they're again, a matter of like time and context because there's a lot more consumer oriented focus there.

36:46So what I did find, so the great added is being really calm and measured and thoughtful in terms of, you know, taking making sure that things are dealing with the complex ecosystems. And if you think about the phone ecosystem or even like the search and publisher and advertiser ecosystem, it's a very complex ecosystem. He was a master at that. He's a master at that. And I think on Satya, I find it amazing the appetite he has for learning and fine tuning his mental models. And just like the zoom levels that he can operate at, the macro, the strategy, what's the game, but also the micro. Hey, why are we don't like here's like a specific insight that I saw on Twitter.

37:28And like you can count on the fact that he's ahead of pretty much everybody else in terms of spotting those early things too. So it's just been like, like, you know, learning from the fire holes as they put it. What a cool opportunity to work with two incredible folks. Okay, let's go in a in a whole different direction. Let me just ask you this question that I've been asking people more and more. What's the most counter intuitive lesson that you've learned about building products that goes against common startup wisdom, common product building wisdom? I don't know if it's a, I mean, as common as it should be.

38:00And it's like a counter intuitive thing. But I've repeatedly learned that when you're doing something new, zero to one, the temptation is to kind of think about, you know, it's like that South Park episode. Step one, think about the problem. Step two, step three, underpants is step one. Exactly. Right. So I do feel like there's a temptation to rush and say to go to scale before solve. So I've always said to my teams, solve before scale. Right. So what that does mean is there's a different posture and different mode when you're trying to solve a problem versus scaling something that's either post product market trade or even at least like in the roughly in the ballpark.

38:48So to give you a couple of examples, right. I think when we, when you look at the solve stage, there are wide lurches. You got to be very comfortable with the fact that you're, they want thinking about, hey, a plant detection tool. And then day 15, you're like, oh, actually, the tech is really good for translating, you know, foreign language. By the way, this is not hypothetical. This is what we kind of like looked at in Google lens back back then and said, okay, like where? What is the intersection and so on? So from the outside, it looks like chaos. But actually in the, and you should be very comfortable.

39:22Not only tolerant. I think you should be like, should have an appetite for that because the last thing you want is prematurely like, you know, fix on one local hill and then you're climbing that and startups and entire product areas and companies, big companies make that mistake. And three years later, you're like, oh, how do I get off this hill? So I'd say that's one big, competitive thing. Like when you're trying to think about what mode you're in, are you in the solve mode? Are you in the scale mode? One example is kind of making sure that you're comfortable with the chaos. I think the other lesson I've learned is the danger of metrics.

39:57Right. And I think again, if you have booked on, you know, rule search or if you're worked on, you know, like, after products, you'd really have like a very fine grain sense of what are the metrics for this product? Yeah, the input metrics are going to have a whole she ban. But when you're looking at something zero to one, if you decide on a metric to prematurely, that's false precision, first of all, right? Like you kind of, I mean, CTR, when you have like 1000 people, it doesn't mean anything, you know, retention also may not mean anything. So really being very wary of like this big guy, big girl of grown up metrics as I call it, right?

40:38You are looking for more qualitative, the sound of click. And what is your, as the other kind of the handler uses, what is your set timer and play music? Right. So if you look at like Alexa and like Siri and Google Assistant and all these things, they had a very promising broad interface. You could say anything, but I think there was one or two things that it was really good at, right? Like you could set a timer, you could play music and you could play trivia. And so you got to mail those things before you say, oh, yeah, here, you can do anything with it, which is not a good recipe. That's exactly what I used to my Google for.

41:16So basic, I don't do the trivia thing now. Maybe I got to give a shout out. Got to cry that. Yeah. There's something along these lines that I've also seen you talk about, which is how to go zero to one with something, just kind of a little framework for helping you know, if this is the right time for this idea. How do you think about that? Yeah. And when we, when you think about the solve mode, and this is again, like sticking with my whole, you know, living in one year in the future, I, I gravitate towards the zero to one in solve mode products, completely thinking about new category of products.

41:47And what I found in both the hardware, I would say, is that you do want to look for at least two out of these three factors, inflection points here. If you want to make a really good product. Number one, is there a shift, is a step function in the tech, right? That's somewhat obvious. I would say like, you know, deep learning was one for Google lens back then speech recognition was a step function for like conversational search. I would say for Robinhood, you know, the generational shift was very clearly and the fact that phones were a primary means for, you know, you could actually have an app, or global app for finance that you could use.

42:25So look for that inflection, right? What is the tech inflection? And right now, of course, like an alimson reasoning models are that step function. But that's not enough. I would say the second factor that we should look for is, what is the consumer behavior shift? Right? So to give you an example, when we started working on Google lens, what we said is look, people were taking mostly pictures for sharing, right? Selfies and sunsets and so on. And suddenly when storage became free and mostly free and everybody had phones everywhere, all all all the time, you took pictures of everything, right?

43:03And then you had like enough of pictures or you use the camera as the keyboard for you for your world, right? For the real world. And so how do you kind of then say, oh, this consumer shift is big. And so therefore, kind of like as it, as you go on of magnitude more photos, then you want more to come out of them and you can apply AI to that. And I'd say the third inflection point, particularly I would say enterprise, but also in consumer is the business model shift, right? How do you, is there an inflection point, natural inflection point in the business model? So any great products, if you think about like, you know, all the way from search, again, like the the second price option and the fact that you had like, you know, CPCs, same thing with SaaS and the fact that you could actually charge or monetize enterprise products in a different way.

43:53And with AI, of course, like the monetization is a whole different like, I mean, you know, we've just barely sketched the surface of whether you do seat monetization usage, like on tap. And then of course, outcome based stuff, outcome based monetization, hey, have you solved the problem for me? And then I will pay you some fees. So all three, like to me are, you know, kind of like great, but at least two out of three for a good product. So this essentially when investors look at startups, they're always asking why now, why is this the time to start this thing? And so you're advice here is you should, there's three ways to look at it and you should two or two of these three should be true.

44:33There should be a shift in technology, some new technology that has enabled this now recently. There's a shift in consumer behavior. And then there's maybe a new sort of, or you've invented a new business model, like any way into monetize something that it gives you an advantage over folks trying to do it today. Awesome. And you didn't mention Robinhood, I think in that example, that was another good example of yeah, yeah, I mean talk about the business model of kind of again, like, not having a zero, you know, zero fees, right? And again, like the combination of all of these things is what can unlock it.

45:07Not you can't just say, oh, we'll just have a much, much more better intuitive interface and hope that, you know, people switch to it. Okay, so speaking of zero to one product, so I'm going to take us to a occasional segment on this podcast that I call hot seat corner. And I have a question for you that is on my mind and it's come up on a couple recent podcasts actually. So there's these companies like cursor, V zero, lovable, bolt replete that are like the fastest growing companies history. I just saw that cursor hit 300 million ARR in two years. Interestingly, you guys were very well positioned to do really well in this space, this AI coding tool space, you guys said co -pilot, the first tool in the world at this stuff.

45:49So ahead of everyone, you build VS code, which is all these companies that are working to build on. You have incredible AI infrastructure, incredible AI talent. So this could have been your market. What happened? What happened apart now? You know, it's interesting. The framing, so I'm a better user of GitHub co -pilot. And I would say, look, if you unpack, I think the thing, the beauty of this is that code generation is become an amazing tool that LLM's have unlocked. So it is not so. It is actually really good excitement and action that now code generation has just opened up all of these things that we've talked about the whole idea of like prototyping.

46:29Go go from idea to Marx and idea to kind of a clickable prototype in like in a few minutes. Those are the kinds of things that of course we should expect code generation to enable. The way I think about how we are positioned and like what we do with GitHub is, so it's a system not just a product or a set of features. If I think about GitHub, it's for folks who are who have their rep, rep, rep, rep, rep, rep, rep, rep, rep, rep, rep, and you have kind of, of course, you have the assistance in terms of autocomplete and you can chat. But now we have the agent board. It's one of the fastest kind of loops that we are seeing.

47:07Really strong positive feedback. So in some sense, when you have a system, what you are looking for in terms of building and designing, it is not just a single product that can go grow, but it's the, what is the repository? What is your context? What are the set of features that grow from your expertise? If you are a really expert coder, you want kind of like the assistance, this product needs to scale for that. If you are a wipe coder, you should still be able to do that and so on. So that I think is the way that GitHub is positioned to build on and like growing honestly, really well. That's so interesting.

47:47So like the core of this is everyone ends up in GitHub anyway, no matter what tool they use and that's kind of the, yeah, and I think the idea again is that code generation is a tool. We'll unlock a lot more products. I mean, they're not all competitors to the fact of they're not all kind of doing the same job. I think when you're at the end of the day, like you're building code for companies to run on, you need to have a system, you need to have kind of the ability and entire Swiss Army toolkit, right? Not just the other complete, not just a chat, not just like a software agent that runs and you kind of like handhold.

48:26You need all of this to work together and that's what the GitHub product is going after. All roads lead to GitHub. On the flip side of this question, there have been probably 5 ,000 startups that have tried to disrupt Excel and you guys just keep waiting. So something mayor is working really well. That is so interesting. You say that. So when I came to Microsoft and I'm an Excel fan, so I actually had a conversation with one of the OG Excel product folks. I was like, man, what is it about this product? He said a couple of things that were really interesting for me that just stuck with me. One is, he said, hey, Excel is a proof that non -corders also have to program.

49:09Programming is really powerful and it's the tool that gives all of the non -corders a really powerful programming ability. And I thought that was just like really striking. And then the second thing that I found out super cool, I don't know if you know this, but I didn't know at least before two years ago that there are these amazing Excel championships, like World Excent Championships, where you see folks who can do just magic. And to me, I think the insight here is also that some tools are harder to learn, perhaps in the beginning, this friction in terms of learning, but great to use. So it's a very good case of, hey, the learning curve initially, the one time learning curve might be tricky, but it is because there's so much power and depth in the tool.

50:02That's so interesting. And I never thought of Excel as a programming language, but it makes sense. And I feel like once you get used to it, and this is just the way things work, you're kind of stuck there and everything else has to basically copy them on, which is hard to be as good. Yeah, and I think the depth and the attention that the team is given, and again, that's the compounding effect over decades of working on like deep, deep signal, right, from people who live, who depend on it day in and day out. Yeah. Okay, to kind of start to close out our conversation, I want to ask this question around your career.

50:35I find that most people have a, like one moment in their career that changes the trajectory of their career. It could be like a manager they had, it could be a project they worked on, it could be just a job they landed. What would you say is the most pivotal moment in your career that eventually led you to becoming chief product officer, Microsoft? Actually, there is one moment where it was a turning point for me. I was in Google search. I was working on this idea that I thought should just work and it didn't. Like I said, hey, these phones are becoming a thing, personalization has to be important.

51:13So I probably banged my head against the wall for a year or so trying to make personalization work. And it turns out when you have a query that you put into Google search, like the personalization didn't matter as much. And so we disbanded the team. But then I think I started working on this product called Google now, which was a twist on that, which said, hey, actually on the phone, we should be able to push content. It's not about like searching with personalization. For example, if you have a flight coming up, we should be able to say, connect the docs and say, you should leave now for the, given the traffic and where you need to go and so on.

51:54Or if you're deeply interested in an upstandup comedy with Deadpan artist, you should check out Mi Checkbook. These are kind of like these really moments that the smartphone should be smarter. So I let that product through the initial zero to one phase. And that was a pivotal moment. It made me realize two things. One, I really love seeing around the corner and kind of seeing where things go and building the product rise to the occasion, way more than the scaling and sustaining products. Second, it's harsh, but being early is the same as being wrong. This is pre -LLM, pre -D planning, a lot of the really amazing ideas and terms of next token predictor, etc.

52:39We've been thinking of it, but didn't have the horsepower to go. The interface was great. The intelligence wasn't there. And I'd say the third thing that struck with me is I got to work with some really smart, like they talk about talent density now, right? I think really smart people gone on to do amazing things. And so kind of like it gave me a taste of what a small group of people can do. It's such a great story because it didn't work out right in the end, like Google now kind of went away, right? And by the way, I super remember that product. It was very cool. I remember looking at it was very delightful and happy.

53:12And so I also have this segment on the podcast, I'll failure a corner. People share a story of failure and how that helped them. And I love this is a combination of those two. Yeah, I mean, I'm not going to lie. I think it was it was it's painful when you do that because you see the vision of what can be and what is and sometimes it's hard limitations. Sometimes it takes like, you know, in this case, it takes five years or 10 years to kind of like really unlock the intelligence. But sometimes it's it's one or two key clicks, clicks stops away from the product being great. And part of figuring out is knowing when you're in what situation?

53:50How long was that period from from starting on it? So it was just like move it on. And it's not worth it. Yeah, I would say in that case, one of the good things is again, like the the it led the foundation of it was one of the foundations of the Google assistant. And of course, as the LLM's, you know, step function happened now with Gemini, it kind of like works out. And I think it's the same thing across the board, which is sometimes you want to kind of figure out the invariance that do work, right? That can then that then go on to the next version of the product. And other times you just have to start over.

54:23It was a Google now the first agent before agents sort of feels like I was certainly the idea. Yeah. You know, inter, but it is fascinating to me that the interface that there we had the opposite problem like whether you think about all the voice assistance, right? The interface is like we overshot and the intelligence wasn't there. Today, I feel like there's an opposite problem. I think these these things have amazing intelligence and the interface we have largely is like the AOL, AOL, DialogModum chat, what? We've covered a lot of ground. Is there anything that you wanted to chat about or leave listeners with maybe a last nugget of wisdom before we get to a very exciting lightning round?

55:06I think I would say one thing that I'm really excited about is this idea of figuring out how we as people and agents collaborate together, right? I think there is like some great set of products and experiences to be reimagined. That's my other Roman Empire, which is how do we actually have this co -working space where you know, you have kind of like the the humans and agents and how do you actually kind of have an output that's much, much more significant than what anyone of us or any few of us can produce? Well, I need to hear more about this. What do you when do you imagine a co -working space of humans and agents?

55:44What does this look like? Is this like Microsoft Teams or is this like a physical place with little robots? Oh, I had a thought of the physical place, but I am thinking I am thinking a lot about kind of you know, right now all of these experiences are very civil player, right? And I do think there's an opportunity to think about how do we again, I'm living one year in the future, how do we actually have like you know, collaborate with each other, but with also with agents and really figure out, for example, what tasks can be delegate, what can be kind of like inspect, how do we actually have information that flows between people, that agents can mediate and so on?

56:23All right, I'm curious to see what you guys got cooking. With that, we've reached our very exciting lightning round. Are you ready? Let's do it. Let's do it. First question, what are two or three books that you find yourself recommending most to other people? Oh, I have recency buys, but I've been reading this book called The Brief History of Intelligence, Phenomenal Book and you know, like lots of lots of underlining for me. And I think it kind of the premises to it looks at the evolution of intelligence like human intelligence and kind of the brain development and I've kind of connects that to what we're what we're seeing with the eye.

57:01Do you ever favorite recent movie or TV show that you really enjoyed? Hacks. I've been watching this. It's about a woman who who's just like a great stand -up comedian of I think it's set in kind of like the the fact that she grew up I think in the 70s and 80s and kind of like really tried to break through in an industry that hasn't traditionally been like very friendly to women. So really fun and quirky. Do you have a favorite product that you recently discovered that you really love could be an app could be some physical? I do use a lot of Microsoft products GitHub, Copilot being one of them, but I think the one that I maybe I'll pick is Grenola.

57:44I think it's the name of the app. I found it really useful. I just gave it a spin the other day and I'm like, oh, this is really useful in terms of being able to you know again like without being intrusive just just capture the thoughts, notes and structure it put some it felt like one of those things where yep the components of a few things like we were talking about right like the transcription real -time transcription tech has gotten really good voice recognition is great and then enough of the LLM magic on top of it to kind of make it structure and contextual. I am a huge fan of Grenola. I'll give a quick picture if you become an annual subscriber of my newsletter you get a year free of Grenola for your entire company.

58:28Did not know that. Okay. So and then just check that out Lenny's newsletter .com and you click the word bundle and you'll see how to do that. Very cool. Two more questions. Do you have a favorite life motto that you often come back to when you're dealing with something maybe share with folks they find useful as well in work or in life? I have one. In fact actually this is my email signature for I don't know for the last 20 years or so says the best way to predict the future is to invent it. I think it's a quote by Alan Kay. I find it useful for two things. One is no one knows anything like when you think about like all the folks or kind of think about hey this is this is exactly how everything is going to look and this is exactly the sequence and so on.

59:11I think there is no substitute to experientially like building it and and I think the second part is you know like if you think there's something that is that should exist go build it. I love that. Final question we've talked about stand -up comedy a bit. Is there a is there like a favorite under the radar stand -up comedian they think people should go check out? Oh there's a there's a couple of them. So one I think there's a there's an Indian American or I think I think a British Indian stand -up comedian her name is Sindhu V super smart like you know mom comedy and I think the other one that he this is definitely not under the radar but like I've just like love his stick is Nate Margazzi he's just so good.

59:59A perna this was amazing two final questions working folks find you online if they want to reach out maybe and follow up on anything you shared and how can listeners be useful to you? You can find me on LinkedIn and Twitter. A perna CD is the handle. I do post stuff a lot more on LinkedIn these days so you know would love would love to hear thoughts comments conversations there. I'd say one thing that would be super interesting is if any of the stuff spark conversations particularly around like kind of you know this what do what can a small team with a lot of AI tools do or new products that folks are really excited about saying that they should exist keep me up.

1:00:42Amazing perna thank you so much for being here thank you bye everyone thank you so much for listening if you found this valuable you can subscribe to the show on Apple podcasts Spotify or your favorite podcast app also please consider giving us a rating or leaving a review as that really helps other listeners find the podcast you can find all past episodes or learn more about the show at Lenny's podcast .com see you in the next episode

From the publisher

Aparna Chennapragada is the chief product officer of experiences and devices at Microsoft, where she oversees AI product strategy for their productivity tools and work on agents. Previously, she was the CPO at Robinhood, spent 12 years at Google, and is also on the board of eBay and Capital One.

What you’ll learn:

1. How “prompt sets are the new PRDs” and why prototyping with AI is now essential for effective product development

2. The three key characteristics of AI agents: autonomy (delegation of tasks), complexity (handling multi-step challenges), and natural interaction (conversing beyond simple chat)

3. Why NLX (natural language experience) is the new UX, requiring deliberate design principles for conversational interfaces

4. Why the PM role isn’t dying in the AI era—it’s evolving to emphasize tastemaking and editing

5. How living “one year in the future” can be operationalized with programs like Microsoft’s Frontier

6. How even traditional enterprises can balance cutting-edge AI adoption with appropriate governance through dual-track approaches

7. Insights on leadership differences between Microsoft’s Satya Nadella (known for multi-level thinking and early trendspotting) and Google’s Sundar Pichai (mastery of complex ecosystems)

8. The vision for human and AI collaboration in the workplace, where people and agents achieve outcomes greater than either could alone

9. A practical framework for evaluating zero-to-one product opportunities

—

Brought to you by:

Eppo—Run reliable, impactful experiments

Pragmatic Institute—Industry‑recognized product, marketing, and AI training and certifications

Coda—The all-in-one collaborative workspace

—

Where to find Aparna Chennapragada:

• X: https://x.com/aparnacd

• LinkedIn: https://www.linkedin.com/in/aparnacd/

—

Where to find Lenny:

• Newsletter: https://www.lennysnewsletter.com

• X: https://twitter.com/lennysan

• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/

—

In this episode, we cover:

(00:00) Introduction to Aparna Chennapragada

(04:28) Aparna’s stand-up comedy journey

(07:29) Transition to Microsoft and enterprise insights

(10:00) The Frontier program and AI integration

(13:28) Understanding AI agents

(17:59) NLX is the new UX

(22:28) The future of product development

(31:16) Building a custom Chrome extension

(35:45) Leadership styles of Satya and Sundar

(37:47) Counterintuitive lessons in product building

(41:20) Inflection points for successful products

(45:16) GitHub Copilot and code generation

(48:34) Excel’s enduring success

(50:27) Pivotal career moments

(54:55) The future of human-agent collaboration

(56:25) Lightning round and final thoughts

—

Referenced:

• Google Lens: https://lens.google/

• Saturday Night Live: https://www.nbc.com/saturday-night-live

• Reid Hoffman on LinkedIn: https://www.linkedin.com/in/reidhoffman/

• Robinhood: https://robinhood.com/

• eBay: https://www.ebay.com/

• Capital One: https://www.capitalone.com/

• Microsoft: https://www.microsoft.com/

• Aparna’s LinkedIn post about enterprise vs. consumer: https://www.linkedin.com/posts/aparnacd_every-enterprise-user-feature-has-a-shadow-activity-7321176091610542080-8X-E/

• The Epic Split: https://en.wikipedia.org/wiki/The_Epic_Split

• AI Frontiers: https://www.microsoft.com/en-us/research/lab/ai-frontiers/

• OpenAI’s CPO on how AI changes must-have skills, moats, coding, startup playbooks, more | Kevin Weil (CPO at OpenAI, ex-Instagram, Twitter): https://www.lennysnewsletter.com/p/kevin-weil-open-ai

• Deepseek: https://www.deepseek.com/

• Satya Nadella on LinkedIn: https://www.linkedin.com/in/satyanadella/

• Tobi Lütke’s leadership playbook: Playing infinite games, operating from first principles, and maximizing human potential (founder and CEO of Shopify): https://www.lennysnewsletter.com/p/tobi-lutkes-leadership-playbook

• Tobi Lütke’s post on X about reflexive AI: https://x.com/tobi/status/1909251946235437514

• GitHub Copilot: https://github.com/features/copilot

• Sundar Pichai on LinkedIn: https://www.linkedin.com/in/sundarpichai/

• South Park “Underwear Gnomes” episode: https://southpark.cc.com/episodes/13y790/south-park-gnomes-season-2-ep-17

• Google Home: https://home.google.com/welcome/

• Cursor: https://www.cursor.com/

• v0: https://v0.dev/

• Bolt: https://bolt.new/

• Lovable: https://lovable.dev/

• Replit: https://replit.com/

• Inside Bolt: From near-death to ~$40m ARR in 5 months—one of the fastest-growing products in history | Eric Simons (founder and CEO of StackBlitz): https://www.lennysnewsletter.com/p/inside-bolt-eric-simons

• Building Lovable: $10M ARR in 60 days with 15 people | Anton Osika (CEO and co-founder): https://www.lennysnewsletter.com/p/building-lovable-anton-osika

• Everyone’s an engineer now: Inside v0’s mission to create a hundred million builders | Guillermo Rauch (founder and CEO of Vercel, creators of v0 and Next.js): https://www.lennysnewsletter.com/p/everyones-an-engineer-now-guillermo-rauch

• The rise of Cursor: The $300M ARR AI tool that engineers can’t stop using | Michael Truell (co-founder and CEO): https://www.lennysnewsletter.com/p/the-rise-of-cursor-michael-truell

• Behind the product: Replit | Amjad Masad (co-founder and CEO): https://www.lennysnewsletter.com/p/behind-the-product-replit-amjad-masad

• Microsoft Excel World Championship: https://fmworldcup.com/microsoft-excel-world-championship/

• Google Now: https://en.wikipedia.org/wiki/Google_Now

• Hacks on Max: https://www.max.com/shows/hacks/67e940b7-aab2-46ce-a62b-c7308cde9de7

• Granola: https://www.granola.ai/

• Alan Kay quote: https://www.brainyquote.com/quotes/alan_kay_100831

• Sindhu Vee’s website: https://sindhuvee.com/

• Nate Bargatze’s website: https://natebargatze.com/

—

Recommended book:

• A Brief History of Intelligence: Evolution, AI, and the Five Breakthroughs That Made Our Brains: https://www.amazon.com/Brief-History-Intelligence-Evolution-Breakthroughs/dp/0063286351

—

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.

—

Lenny may be an investor in the companies discussed.



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.lennysnewsletter.com/subscribe

More from Lenny's Podcast: Product | Career | Growth

All 287 episodes
Microsoft CPO: If you aren’t prototyping with AI, you’re doing it wrongLenny's Podcast: Product | Career | Growth · 1 h 1 min
Listen in VO