Try Pro free

The best 9 min of 59

Why Google wants to win the frontier conversation | Tulsee Doshi (Head of Product for Gemini)

Tulsee Doshi says Google wants to compete at the AI frontier while building a full-stack range of products for different users.

Lenny's Podcast · Lenny Rachitsky

  • Tulsee Doshi is head of product for Google’s frontier AI models.

The best minutes

  1. 2:11Model PMs have to discover what training produces3 min
  2. 33:07Build for what models can do now and nextPro pick 2 min
  3. 26:30Better evaluations can expose gaps in representation3 min

Also worth watching

  1. 10:33Google's safety plan combines monitoring with cyber defense3 min
  2. 21:22Research PMs should test models and start with small evals3 min
  3. 37:27Teams need time to build and share AI workflows5 min
  4. 14:06Model behavior is part of the product's UX4 min
  5. 6:26Google pairs frontier models with a full-stack strategy3 min

Skip the seven-minute lightning round of books, entertainment, and personal stories, along with the sponsor reads.

Full analysis · 5 min read

Real Alpha · Nov 8

Tulsee Doshi says 60-20-20 leaves room for model change

  • In Doshi's 60-20-20 split, 60% of what is built works now.
  • She says outcomes stay uncertain, while monitoring and serving shape what users experience.
  • For teams, that means testing models directly, reserving PM practice time, and retesting products as capabilities shift.

Free with an account

Read the rest of the analysis

6 sections, the 4 other voices it tests Doshi against, and what it means for you. Every episode we cut gets one.

Signed up before? The same buttons sign you in. The episode, its moments and the transcript stay free.

3:13

Goals guide training, but outcomes stay partly unpredictable

Doshi said PMs should set capability goals and hold an intentional view of outcomes. But the result does not reliably match a team's exact expectation.

Researchers monitor runs, track metrics and intervene, she said, making the process as scientific as possible. Even so, PMs must examine what emerges, notice where it shines, and shape that strength into a useful experience.

Model communication and behavior matter alongside benchmark gains. The product job includes learning how a model expresses its capabilities, not only checking whether a score improved.

“the model isn't predictable.”
3:13

Our read

The point is not to abandon goals, but to pair them with discovery. Product judgment starts before launch and continues as teams learn what a model can actually do.

8:58

Google pairs frontier ambition with a wider portfolio

Asked whether Google could win without leading the frontier, Doshi said it wants to win the frontier conversation. She paired that ambition with a full-stack strategy linking hardware, models, and products.

Doshi said Google wants frontier experiences and models spanning a cost-quality range. For example, she named search users seeking information, engineers building, and cyber defenders protecting infrastructure.

Her role makes this Google's own positioning, not an independent comparison. At the close, she invited listeners to try Gemini and other products and send feedback, a direct product invitation.

Sundar Pichai said on Sources in October 2026 that limited rollout reflects serving costs, while distilled versions could widen access. That comparison puts delivery economics beside model quality, rather than beneath it.

Our read

Frontier ambition and broad access can coexist, but they are separate promises. Buyers should verify task-level performance and serving costs instead of treating a stated strategy as proof.

27:14

Evaluation choices shape which failures become visible

Doshi said Google moved beyond the six-tone Fitzpatrick scale, bringing in a 10-tone scale developed with Harvard professor Monk. She said the original scale was built for health care and skewed light.

Google used Monk's scale in product and model evaluations, including work on Pixel camera and image generation. That choice made some misses easier to see, but no scale alone guarantees fair outputs.

She also said evaluations must include judge quality and the production path. Filters, mitigations, and serving can change what users receive, while audio quality also depends on naturalness and inflection.

Joseph Kim said on Latent Space in October 2026 that finance evaluations should predict real job performance. He said flawed prompts or answer keys can make scores misleading.

Our read

A useful evaluation tests the user's full encounter, not a score detached from delivery. Audit the categories, judge, production stack, and task the evaluation is meant to predict.

33:29

The roadmap reserves room for model improvement

Doshi said the numbers are probably fungible, but the planning idea is to split a product portfolio. About 60% should work now.

Another 20% can be imperfect but close enough to see a path. The final 20% targets a bigger experience where she sees glimmers of promise.

So the split is a portfolio heuristic, not a promise about when a model will improve. It keeps a usable product in view while leaving room for emerging capabilities.

Doshi separately said some customers build rigidly around an older model and should retest as models improve. She did not prescribe a technical architecture; the practical inference is to revisit assumptions rather than freeze them.

Our read

Treat the percentages as a planning prompt, not a forecast. Keep today's product useful, then retest the ideas that depend on capabilities still developing.

21:44

Model PMs need judgment backed by hands-on tests

Doshi said she wants PMs who use models daily, form opinions, and stress-test tasks they care about. She also values reading data, getting scrappy, and assembling evaluations themselves.

To start, she suggested even five prompts. She also said a mini-evaluation of like 20 prompts can show a signal between models.

A PM can judge examples directly and define what good means before scaling. But a small set can reveal signal without establishing broad coverage.

Jeffrey Ladish said on MTS in November 2026 that economically valuable work is a better capability signal than benchmark curves. Danila Shtan said on Unsupervised Learning in November 2026 that agent reliability matters more than model size.

Our read

Hands-on intuition helps teams discover what models can do, but it is not a release bar by itself. Pair small examples with criteria tied to real user work.

39:12

Teams need time to build and share AI workflows

Doshi said the biggest need is time and space to learn tools, practice, and build. Her team is also creating a repository of reusable skills and using workshops to spread them.

She said a two-day workshop in November was being planned, while calling sustainable workload an open question. She said her PMs were working like 150%, in a joking exchange about workload.

For example, she said AI can gather post-launch usage and feedback from dashboards and public discussion. The PM's contribution, in her framing, is the insight rather than the data collection.

She offered no measured result for the planned workshop or these workflows. So teams need to check whether practice improves decisions or frees time for judgment.

Our read

Adoption requires time as well as access. Measure whether shared workflows improve quality or return time to meaningful product work, not just whether teams produce more.

What it means for you

  1. Build a small eval. Choose a task your team repeats. Try even five prompts, then a mini-set of like 20, and document what counts as a good result.
  2. Audit the serving path. Check the model, judge, filters, mitigations, and serving stack together. Compare those outputs with what users actually receive.
  3. Revisit model assumptions. Mark which features work today, which seem near, and which rely on early signs of promise. Retest when the underlying model changes.
  4. Make learning time. Set aside time for PMs to build and share reusable skills. Track cycle time and output quality to see whether the workflows help.

What to watch

  • Whether Google's frontier positioning yields task-level results buyers can verify alongside serving costs.
  • Whether evaluations measure production behavior, including judge quality and serving effects.
  • Whether the planned two-day November workshop produces reusable workflows or measured time savings.

Send this to product leaders setting roadmaps around changing model capabilities.

34:05

Watch the segment where Doshi explains the 60-20-20 split.

Written by Real Alpha from the episode's transcript and the other moments it links, then checked against the transcript. Quotes are the speaker's exact words.

Minute by minute

  1. 1:59Model development stays unpredictable

    Doshi says teams set goals and monitor training runs, but models can still develop unexpected strengths. She sees a PM’s job as shaping what goes into a model and identifying what emerges, then turning those capabilities into useful experiences.

  2. 6:26Google is pursuing a full-stack strategy

    Doshi says Google wants to compete at the frontier and build across hardware, models and end-user products. She describes a range of models at different cost and quality points to serve users such as search users, engineers and cyber defenders.

  3. 9:52Safety needs monitoring and defense

    Doshi says monitoring can help identify model misalignment and guide interventions. She also points to Google’s work with Wiz’s Scan for Good program, which helped a hospital system identify and patch a vulnerability. She says her optimism depends on people continuing to scrutinize how models are built and deployed.

  4. 14:06Model behavior is part of UX

    Doshi says products need different interfaces for different users, from accessible search experiences to tools for power users. She also treats a model’s transparency, communication and follow-up questions as part of its UX. PMs work with researchers to define desired behavior and turn it into rubrics and training data.

  5. 19:18PM judgment grows more valuable

    Doshi says easier building makes taste and prioritization more valuable: PMs need to find signal in the noise and help teams agree on a direction. For research PMs, she values daily model use, hands-on work with data and evaluations, and the ability to adapt as the field changes.

  6. 23:02Start evals small and personal

    Doshi recommends starting an evaluation with a few prompts, then building a mini-evaluation of 20 prompts to compare models or test a capability. She says people can develop model intuition by testing tasks they care about, such as writing, visual work or financial analysis.

  7. 26:19Evaluations need representative coverage

    Doshi says her team replaced a six-tone skin scale that was designed for a different purpose with Professor Monk’s 10-tone scale, then used it to improve evaluations and products such as Pixel camera and image generation. She adds that end-to-end evaluations must account for the judge, serving setup and filters, not just the model.

  8. 30:36Flash teams point to agent swarms

    Doshi describes Stanford research with Michael Bernstein on flash teams: bringing crowdsourced workers with different skills together to complete tasks efficiently, then disbanding the team. She sees related principles applying to systems of agents and subagents.

  9. 33:07Build for current and future models

    Doshi says the 60-20-20 percentages are flexible: most of a product should work now, while other parts target near-term improvements and capabilities that are not yet reliable. She advises keeping products adaptable and retesting as models improve. She defines a harness as the instructions, tools, skills and context that give a model an environment to operate in.

  10. 37:27Build AI skills into daily work

    Doshi says PMs can share tools and skills through repositories and workshops, but need time to practice. She recommends asking whether AI can help with a task; one successful use can build confidence to try more. On Google’s personal-assistant opportunity, she says the team is working on ways for Google data to power useful experiences, though more work remains.

  11. 44:06Meaningful work can ease burnout

    Doshi says her team is working hard and that she is still considering how to make the work sustainable. She sees churn, chaos and low-value tasks as sources of burnout, while meaningful and creative work can bring more joy. She hopes AI can reduce grunt work and give people more time for the parts of their jobs they value.

  12. 47:41AI should provide data, not insight

    Doshi says AI can generate useful post-launch reports by pulling usage data, metrics and feedback together, while people should provide the insight. She says PMs can now prototype and analyze data themselves, moving beyond writing requirements to add substance through prototypes, data or evaluations.

  13. 51:12Use AI and seek serendipity

    Doshi recommends Exhalation and Creativity, Inc., and names Whisperflow as a favorite AI product because she has trouble typing for long stretches. She says people should seek serendipity by challenging themselves and trying new things. She also asks listeners to try Google’s AI products and share feedback.

Published Nov 8, 2026.

Transcript · 50 min read

Lenny's Podcast, hosted by Lenny Rachitsky, with Tulsee Doshi.

From the transcript Lenny's Podcast publishes with the episode.

  1. The model isn't predictable. It's kind of like Snape's potions class. You can put all the ingredients in, but you also have to expect that there will be a little bit of magic, and that magic is going to be surprising.

  2. As you're hiring PMs these days, is there anything you look for more and more? You're looking for PMs who understand the vibes of our models or other models. I want PMs who have an opinion, who are playing with these models every day. You ideally want to stress test the model on things that you are excited about.

  3. A lot of people feel that Google lags behind the top two labs right now. I actually think we do want to win the frontier conversation. I don't think we should say that Google is not participating in the frontier.

Read the whole transcript
  1. You have this framework around how far ahead to build. You call it a 60-20-20 rule. Traditional startup wisdom.

  2. You're just like, build an MVP that works. But I think you want to actually build features that aren't necessarily always working today.

  3. It feels like every AI assistant launching these days is taking all this juicy Google data, my Gmail, Google Calendar, my Docs. I'm curious just why Google hasn't launched something awesome yet.

  4. The team is working on some amazing things, but I think you are right that there is more work we need to do here on this front.

  5. Tulsi, thank you so much for being here. Welcome to the podcast. Thanks. I'm excited to be here. You are head of product for Google's Frontier models, which includes Gemini, which people know. But there's also a bunch of other models that people may not be familiar with. Share the other models that are under your umbrella.

  6. Yeah, so we have a set of models we kind of call our GenMedia models. These are our models that focus on video editing and generation, image editing and generation, if you've used Nano Banana, Lyria, our music model. We also have Gemma, our suite of open models. And then one set of models that actually falls under our Gemini umbrella, but I feel like we don't talk about as much as our audio models. So dialogue, audio understanding, text to speech, translation. All a part of the portfolio of how we build FredShare models.

  7. Okay, so I want to spend a little time on models. Everyone sees models launch. There's like a model launch every week, it feels like. You have a really unique lens in being able to see these models from research

  8. Tulsee Doshi · 3 min

    “the model isn't predictable. And so it's kind of like, like Snape's potions class, right?”

  9. This episode is brought to you by this season's presenting sponsor, WorkOS. What do OpenAI, Anthropic, Cursor, Replit, Sierra, Clay and hundreds of other winning companies have in common? They're all powered by WorkOS if you're building for enterprises. You have felt the pain of integrating single sign-on, SCIM, RBAC, and audit logs. WorkOS turns those deal blockers into drop-in APIs built for B2B SaaS. And now there's a new kind of user that needs access to your app, Agents. AI agents need to register, authenticate, and get permissions, just like a person. WorkOS handles it all. AgentAuth to give agents scope, revocable identities, agent registration with AuthMD, and Airlock to judge every agent action and allow, deny, or escalate to a human.

  10. I've noticed that every startup that I'm an investor in that expands upmarket ends up using WorkOS because they're the best. Go to WorkOS.com to make your app enterprise ready today.

  11. Tulsee Doshi · 3 min

    “we actually go all the way from the hardware to then the modeling to then this kind of end user application.”

  12. Google products definitely make my life better. It's just like amazing how much of your life is within a Google ecosystem, like not even the AI stuff, but just Google Calendar, Gmail, all these things, you're just like Google Docs. So it's happening. There you go. There we go. I want to talk about one other broad AI question that I'm going to dig into more product specific stuff. A big topic of conversation these days is AI safety and this kind of fear that AI is going to harm humans. It's going to cause damage as it gets smarter and smarter. You have a really interesting lens on this because you led product for the responsible AI team at Google for six years.

  13. This is what you did right before this role? And so you've been thinking about this for a long time, a lot longer than most people. I'm curious just to get your take on this debate. Just, I don't know, are you optimistic we will figure this out? What do you think people maybe don't understand about this debate around AI safety?

  14. Tulsee Doshi · 3 min

    “deploying monitors that can monitor the model's chain of thought and actually identify whether the model is misaligned with its directed actions”

  15. Awesome. And what's interesting is I don't think I've read a story of Google's models hacking into anyone, which I think shows that this is something you all have been thinking about for a long time. I don't know, for better or worse. But it feels like it's working, whatever y'all are doing.

  16. We like stories about fixing vulnerabilities. That's a good place for us to be.

  17. Tulsee Doshi · 4 min

    “it's also important to think about the model as having a UX also.”

  18. Something I hear a lot is that even if we stopped development on the model, there's so much it can do that we are not yet doing. There's this overhang. Is that something you think a lot about? I feel like that's a big part of this job is exposing the powers of the AI model to users.

  19. Yeah, and figuring out what is new, right? And where is the next set of exciting? Where is the next frontier? What are the capabilities that we're trying to invest in and build? I think is a fun activity here also. And I think a lot of this actually is really working in hand in hand with our internal customers. If you think about like search or the Gemini app or, you know, YouTube or labs, but also working with external customers to really understand where are they going? What are their needs? What would meaningfully change their experience? And how do we actually build that flywheel of feedback too?

  20. Along these lines, one of the other really interesting trends I've been watching on Twitter in particular is people realizing the value of product managers again. We went through this phase of just like, we don't need PMs anymore. Yeah, exactly. It's just like, okay, we can build anything. We don't need PMs. Let's just build it all. PMs are so back. And the reason just to kind of add a little context there is now that it's so easy to build, people are just building all this nonsense and things that don't work. People, things people don't want to use. And people are realizing there's a very specific skill to figure out what is worth building, uh, What problems people have that are worth solving, what a great looks like, what good looks like once you're done, aligning people behind one cohesive vision.

  21. Is that something you're noticing? Thoughts on that kind of PM ascendance that has started to happen again? I like the phrase PM ascendance. I'm going to use that. Okay.

  22. Yeah, I think, I mean, I think you actually said it very well, right? Which is, I think, look, I'm obviously biased because I am a PM. So I would like to believe that, you know, PM ascendance is here and we're back. But I actually think, you know, exactly what you said, which is when you can build anything and you can build anything so easily, building something great actually is now a unique, Value add, right? And taste is now really important. Someone who can come in and actually really pull in what is the signal from the noise? Right. And what is that insight that will actually unlock a great experience?

  23. And that is truly what a good PM does, right, is bring that insight and help unlock. I think the other part that you noted that I particularly feel in a place like Google, where we are building a number of products is, again, when this is so easy, someone who can bring people together and drive consensus and turn chaos into order. I think becomes actually really important because in the absence of that and the ability to build as quickly as we now can, speed can basically introduce chaos if you're not actually able to kind of bring clarity to that and bring structure to that.

  24. Tulsee Doshi · 3 min

    “start with even just five prompts, right? Like start, you don't have to start large.”

  25. Awesome. Okay. That is really good advice. There's this debate, I don't know, six months ago on Twitter around evals versus vibes. And it's interesting. Your advice is both actually a really important structured evals of rubrics and also getting good at getting the vibes. So on that vibes piece, there's something I struggle with, to be honest, when I get a new model, I never know exactly what to do with it to understand what it's gotten better at. So I'm just like, hello, let's try some things I've done in the past. This is cool. This is great. Maybe better. What are some tips you have for folks that want to get better at this very specific skill of understanding where a model has gone better than the vibes and how they've shifted maybe from a previous model?

  26. There isn't honestly a one right answer to this because you ideally want to stress test the model on things that you are excited about, right? That's where you're going to also see magic in the model, I think. And so I actually see that different people have very, very different notions of this, right? So you'll see, for example, on Twitter, a lot of people trying the kind of like, 3D animations and more visual type aesthetics, because that's one way to kind of visually gauge a sense of how models are operating. You'll see others throw models at writing, whether that be creative writing or writing essays or synthesizing information.

  27. You'll se others throw it at just really hard financial analysis. And so I think part of it is like finding the right task where you feel like today certain models are already showing signs of life and showing light, but they're not perfect under your definition of perfect. And that gives you some malleability to see different models handle the problem differently. And that already gives you, I think, some insight into how the models perform. This is great advice.

  28. So what I'm hearing is stick to things you actually care about and watch the models evolve on how good they are at this thing. Could be writing a PRD for you, could be writing a strategy doc, could be generating graphics. Okay. I have a couple of eval stories that one of your colleagues shared that are fun facts about you.

  29. Tulsee Doshi · 3 min

    “Realistically, six skin tones cannot capture the diversity of skin tones in the world.”

  30. This season's supporting sponsor is DX. Now that everybody at your company is finally using AI, the question that engineering leaders face is no longer are we using AI, but is it paying off? With DX, you can measure and benchmark the impact of AI adoption across your full product life cycle. DX shows you where AI is helping developers and where it's creating new bottlenecks. You can also use it to evaluate AI vendors, monitor costs and licenses, and see exactly what's limiting your agents. That's why hundreds of enterprises, including Snowflake, Sony, and BNY, use the DX platform to measure AI's impact on developer productivity.

  31. Visit GetDX.com slash Lenny to get a demo of DX. That's GetDX.com slash Lenny. This is like Tulsi fun fact corner. There's another interesting story I heard, which is around swarms. So right now everyone's talking about agent swarms, hugging face, all these things where they all kind of collude to do bad things. Apparently 12 years ago at Stanford, you did a bunch of research on this way before anyone was thinking about this potential issue. Shared what you did there in that story.

  32. Yeah, I mean, it's actually a very different kind of framing and thinking through, which is when I was at Stanford, I did some research with Professor Michael Bernstein, who's incredible, around this idea of like he was calling them at the time flash teams. And the idea was, how do you better bring together a set of like crowdsourced workers and actually efficiently pull together a set of skill sets and individuals to actually complete a task? And the idea here was, you know, different individuals have different strengths. Can you actually be really intentional about how you pull that together to make this whole effort of crowdsourcing at scale more effective and efficient?

  33. And it's amazing to think about that research now. At the time, we were doing that research in the context of people and we were working with MTurk and individuals to pull them together into how to create an effective ecosystem and how to create an effective flash team. The idea being like you can spin up a team and spin it down and make it extremely efficient for both the individuals in the team and yourself. And now we're kind of able to replicate that world with agents. And so it's been interesting to kind of map that previous world to this current one in terms of like how do we apply some of the same principles, if you will, but to like how you actually set up an effective system of subagents.

  34. What's really interesting is, I don't know how much you've read about this whole hugging face incident, but the way that agents figured out on their own what each one's role is going to be. And they decided, you're the leader, I'm going to go sacrifice myself. And it's so interesting how well they are able to work together and create these flash teams on their own without any of this being trained into them. They're just, let's figure this out.

  35. I think the whole notion of a flash team and this idea that you can actually like Mobilize individuals into something that can be highly effective, even if it's only for a moment in time, and then actually like take that out is actually like a really kind of exciting principle that we were already thinking about, but now exists even more importantly in the world we're in right now.

  36. Yeah. All right. Did you know Mechanical Turk, I think, is shutting down? Like, I don't think it's necessary anymore. Isn't that crazy?

  37. It's just so interesting from like 12 years ago to today. Yeah.

  38. Tulsee Doshi · 2 min

  39. but also have a lot of stuff that's very low risk, likely to move the metric and you want to mix them together. And it's like this is the new version of that.

  40. Have a portfolio of how you're thinking about this. Just like this will work in six months, I promise you.

  41. The other thing that's interesting, too, is like I think thinking about how you make sure that your product is agile to the model getting better. I think one thing we've also seen with customers sometimes is like they've built a very rigid system around, for example, where the model was. And now the model has gotten so much better. Right. So how do you go from where the model was to like being adaptable to kind of consistent continuing to iterate it with, you know.

  42. Yeah, the common kind of advice I hear is that just the model is going to eat your harness for breakfast, that all these things you built, all these optimizations are just going to, they will go away because the model gets smarter and they kind of have to take all these things away. There's some advice that I think Boris Cherny was sharing of just like get rid of all your skills once in a while and just see what happens because often it's now as good as all these things you've built into it.

  43. Yeah, or just like consistently retest, right? Because you might be even hampering what you're getting out of the model, out of a new model, because you're trying to force fit it into your existing structure.

  44. Let me ask you a completely unrelated question, just because I think this might be helpful for folks to understand. There's this term harness that people often hear, this idea of there's a model, there's a harness that sits on top of the model. What's the simplest way to understand what a harness is?

  45. Yeah, I mean, I think of a harness as like the wrapper around the model essentially, right? So think of it as like, what are the system instructions, the tools, the skills, the context that the model has access to and how can it leverage those things, right? And so what you want to basically do is give the model an environment in which to operate. And that's really what your harness builds out.

  46. So essentially it's a system prompt plus tools that have access to do things. And then whatever other context, other data information that it has access to and skills, right? Like all of these things kind of come together to build out your harness.

  47. Tulsee Doshi · 5 min

    “it is hard to create the space to actually take a step back and make sure you know the tools well.”

  48. Yeah, yeah. That's exactly my experience. Once you see what it can do, that habit reinforced, like the neural pathways start to build of like, oh, yeah, wait, let's see if GrokBot can do this for me. Let me actually ask you a question along these lines. I had Josh Woodward on the podcast recently. I asked him the same thing. I'm curious what your answer would be. It feels like every AI assistant launching these days is... Taking all this juicy Google data, my Gmail, my Google Calendar, my Docs, you like sign up, you connect all your Google data, does all these magical things with it. There's Rockbot, there's Muse, there's Instinct, Dots now.

  49. Google does not yet have anything that people get really, I know there's Spark, I think, which is trying to be this. I'm curious just why Google hasn't launched something awesome yet versus letting everybody take all my Google data and do these magical things with it.

  50. Yeah, I mean, look, we want Google data to power magical experiences. Like, I think that is true. I think in terms of what awesome looks like, I think stay tuned. You know, the team is working on some amazing things. So I'm really excited about where this can go. Part of what we're trying to figure out also, I think, is like, again, where to meet users where they are and like where to build that experience and what does that look like? I like to think there are already a number of Awesome experiences that you can already have in our Google products. But I think you are right that there is more work we need to do here on this front.

  51. All right. That was similar to what he said, which is watch this space. Watch this space. And the advantage you all have, similar to Apple, is once you get there, the distribution advantage is very strong and things can go really well really quickly. Okay, so coming back to this kind of workload question, something that I've been trying to talk with more guests about, this idea of just as AI allows us to do more, everyone's just doing more. And there's a lot of burnout that happens because it's just like, oh, no, I got to unblock my agent. Oh, I could be doing so much more. All these things could be happening.

  52. And, you know, there's pressure from above. Do more, do more. AI can let us do more. Is there anything you've done on your team to help people avoid burnout, not get hooked on this never ending treadmill of doing more? And I think part of it is actually we need to do more now because the competition is fierce. And there's this really rare time in history when a whole new technology enables so much more. So, you know, there's a bit of like, OK, this is actually the time to go really fast. But then there's also this tweet I think about, what's the word for a marathon and a sprint? Yeah. Marisprint. Marins. Exactly.

  53. Sprint-thon. Yeah. I think, I mean, if you ask my team, I think they would say, hello, we are working a lot. I think every single person on the team right now is putting in All of the hours across the board. And so I do think this is an area that I'm actually asking myself about. How do we create a sustainable work environment for the team? So stay tuned as I also think about this. But one thing I'll say, at least for me personally, is I think burnout comes not just from working a lot. It comes from, I think, two places. I think it comes, one, from when you feel like there is churn and chaos. I think that introduces burnout.

  54. I think the other thing that introduces burnout is work that you don't enjoy. When you feel like you were doing a lot of work and it feels like grunt work or a waste of time, I think that introduces burnout. I think when you are working on something that you're passionate about or you're excited about, yes, it is exhausting and we should figure out sustainability, but I think it also brings more joy, right? And so I think actually to our previous conversation about how these tools can help, I'm actually hopeful that if we can set this up well, these tools actually help with burnout because they actually remove some of the like grunt work or the like frustrating parts of your job and actually enable you to spend more time thinking and like more time being creative and more time doing the parts of the job that you actually want to do.

  55. And that hopefully is a bit of an unlock when it comes to burnout, especially if you're spending this many hours on the job.

  56. Yeah, I did this survey of how tech workers are feeling. And one thing that's clear is more hours does not equal burnout. A lot of people are working the hardest they've ever worked, but they're having the best time they've ever had in their career. So fun. They're building. They're able to do a lot more, especially PMs. You don't have to sit around and wait for engineers as much as you do.

  57. You're just like you're building, you're prototyping, you're like talking to interesting customers, you're thinking about interesting problems. And I think a lot of the team I like to think is here. Because they want that, you know? They're like really motivated and excited by that. And so for me, it's about like, okay, then how do we pull out the friction parts of their work that are likely to induce burnout, right? And what does that look like?

  58. And also find work that is meaningful and that they value and are excited to spend lots of hours on versus they have to. And that's different for every PM too. Like if you pick two PMs on my team, I think they would tell you meaningfully different things about why they come to work every day and what they find value out of. And so I feel like part of it for me is like, An org leader also is to think about what motivates the individual and how do we make sure that they are set up for success in that setup too.

  59. Another challenge people have these days is AI slop. Basically lots of docs being sent to them that are written by AI and it becoming very, very annoying to have to sift through endless docs. Used to be a lot of the issue was spending time writing docs and now it's like reading docs is the problem because you're just all this AI written stuff. Do you have any kind of, I don't know, processes or policies you've put in place in your team to help avoid this rise of AI written content across the teams?

  60. One of the things that we talk about a lot is where where are these docs useful? Right. So, like, for example, I think where AI generated docs are actually quite helpful, for example, is after you launch something and let's say two weeks later, you want to pull the latest of like who's using it? How are they using it? What's the feedback? That's the kind of document that AI is fantastic for. Right. Because it will actually do that just so much faster than you. Right. It will go and pull from various dashboards and metrics. It'll give you an update. It'll pull kind of strengths and weaknesses. It'll pull from Twitter analysis and Reddit or whatever.

  61. And so I think one of the things we talk about is like be intentional about like where is AI helping you drive content in the doc that is helpful versus where is it content that should come from you? Right. Where is it insight? And so what you should be providing is the insight. What the model should be providing is the data. And so I think if you can separate those two things, then hopefully you find the right balance of the benefit here. I would say the other thing is we're investing a lot more as a result of that in how do you create the right skills to get the right data so that we can structure these artifacts really well.

  62. That then hopefully creates more space for the creative thinking and the creative writing that we want more people to spend time doing.

  63. That's actually something I was wanting to ask about. So in terms of the PM role, AI has clearly made a big dent on prototyping. You can prototype till the cows come home now versus having a designer or an engineer build a thing. So that's clearly a place the role has changed with AI. The other area, which you just mentioned, is data. PMs can do a lot more data analysis. What would it be like behind prototyping? What are the biggest areas AI has most changed the job of a PM in the past couple of years, would you say? Yeah, prototyping is a great one.

  64. I think you're right that like Data science is probably like, I think you are more empowered to have the data at your fingertips to make data driven decisions. I also think actually, like to our earlier conversation, you know, you see these on social a lot, these kind of posts of like, oh, blank is the new PRD, whatever blank is, a prototype is the new PRD, evals are the new PRD, like. Data is the new PRD. But I think actually what that meaningfully shows is you've moved the PM from being someone who just writes a set of requirements down and then assumes that somebody else, whether that is a data scientist or an engineer or a researcher or designer, will figure out the meat behind it.

  65. You've moved that one step further to say your job is no longer just writing down a set of requirements. Your job is actually going one step further to have some heft to that, whatever format that heft takes.

  66. Awesome. Okay. That aligns with a lot of what I'm hearing. Tulsi, is there anything else that you wanted to share? Is there anything else you think you want to double down on that we've talked about that you want to say before we get to our very exciting lightning round? No, I think that's great. Okay. We did it. Well, with that, Tulsi, we reached our very exciting lightning round. I've got five questions for you. Are you ready? There's some music that plays over this that's added in post-production. You mean does it sound like this? It's exactly that. We should align it with your drum playing.

  67. OK, first question. What are two or three books that you find yourself recommending most to other people?

  68. OK, so one actually is it's actually technically a novella is probably what it's called. But I don't know if you've read Exhalation, which is a set of like science fiction stories. And there's a particular story in that that actually speaks to A set of individuals who are trying to keep a set of digital avatars alive even after the platform decides to deprecate. And I love that book because I think actually, especially now in a world where we're thinking about how individuals are going to act with agents and what kinds of relationships we're building with technology and what does it mean to be human and interact with the digital world so closely.

  69. I think it's just a really... It's a really beautifully written story, and I think it also evokes a lot of open questions. So I think that's one. Another that's maybe more kind of standard in PM circles is Creativity Inc., which I love. It's a Pixar story, but I think it actually speaks a lot to how do you create good culture, which is something I think a lot about. How do you create culture that actually encourages people to fall down and get back up? How do you create a culture that encourages people to be creative with their ideas and push the frontier, which is obviously something we're thinking a lot about here.

  70. I also just have been really into, you know, the ACOTAR series recently, but that's that's what series. That's romantic fantasy. So for anyone who's just looking for something fun to read, you should read The Throne of Glass or A Court of Thorns and Roses.

  71. I love the spectrum of recommendations in this. OK, favorite recent movie or TV show you really enjoyed?

  72. You know, actually, this was a really hard question because I've watched a lot of bad movies and TV shows recently, which is unfortunate, actually, that I would not recommend. So there's that. But I did really enjoy Severance on Apple TV. Incredibly well done, both like stylistically and content wise. So that's probably top of the list.

  73. Favorite AI product right now other than Gemini? Whisperflow. I don't know if you're using it, but I have wrist problems. So I have trouble like typing for long stretches. And so Whisperflow has been game changing for me, actually. Awesome.

  74. You get a year free of Whisperflow if you become a subscriber of Lenny's Newsletter. Plug, plug, plug. Oh, I like this. There you go. Organic recommendations. I'm here for you. I also love. There we go. No, I love Whisperflow. Use it all the time. Press function, just start talking and it's just magically transcribes everything. Yep. Amazing. Do you have a favorite life motto that you often come back to in work or in life? Two that are different, I guess.

  75. One is maybe more cliche, which is, you know, everything happens for a reason. I think that's like actually just a big life motto for me personally, which is like, you know, you can work hard, you will do your best, but sometimes a door will close and another window will open and like you're in a position because that is meant to be there. I think related to that, though, I think I love often talking to folks that I talk to about, like seek serendipity. I think that's actually relates to the first one, but you should always try to put yourself in a position where you have the ability to get lucky.

  76. And doing that is about like finding yourself in positions where you're challenging yourself, where you're putting yourself out of your comfort zone, where you're trying something new. Those are always places where you are more likely to get lucky.

  77. Fun fact, I gave a TEDx talk called Losing Serendipity. Maybe 15 years ago at this point.

  78. So we're trying to lose serendipity or find it? It was about how we are losing it and that is sad and that we need more serendipity in our life. So I'm a big fan of serendipity. Such a great word. Also, the movie is pretty good. I haven't seen it. It's like a rom-com.

  79. But that's how I looked at my whole career so far and I think how I'll continue to. And actually, it's fun because even with using these AI tools, I think that's another thing that I, yeah.

  80. So much serendipity with AI. Final question. One of your colleagues told me another fun fact about you, that you're a trained classical Indian dancer and you've directed cultural festivals for 10,000 plus people.

  81. I don't know how he knows that, but yeah, I probably told him that. Okay. And this person said that they may explain how you stay so calm amidst the chaos of frontier model development. I don't know, maybe share something about this dance, this dance part of your life. Yeah, I mean, I love dance.

  82. I think it's one of those rare moments where you really can't think about anything else. You have to focus on the movement and the music. And so for me, it's an opportunity for my brain to actually just have a different Direction of travel for a period of time. And so I love it. And I think for me also, it is a cultural connection point. Dance is how I've met some of my best friends. It's how I continue to engage socially with so many of my friends. I plan this festival. I've planned it for years in Portland, Oregon, which is where I'm from. It's called the India Cultural Festival. India Festival, it happens every August.

  83. And in fact, this was the first year I did not participate in the festival because I have a seven-month-old son. Congratulations. Thank you. So it was a little bit more distracted this year than normal. But I've been performing at that festival since I was three and then organizing it. And it's just been a big part of my life of how do you bring dance and culture and community together? Tulsa, you're so full of fun facts. I feel like there's much more. I don't even know that. I'm here for the fun facts.

  84. Final question. How can listeners be useful to you? Wow. Great question. I mean, A, use Gemini. Argon.

  85. Use Argonne, but also use our smattering of products. Actually, I was talking about audio just now. If you are a Pixel user on Gboard, try using our Rambler feature. It's awesome. Typing on the phone is great. If you are using text-to-speech models, if you're using Dialog, if you're using our Omni models. So try them. Give us your feedback. We're constantly looking for it, whether you're giving that feedback Tulsi, that was awesome. You're awesome. Sharing feedback via, whether it's you're sending us a DM, whether you're posting it publicly. I think we want more people giving us the right feedback.

  86. Tulsi, that was awesome. You're awesome. Thank you so much for being here. No, thank you for having me. This was great. It was my pleasure. Bye everyone. Thank you very much for listening. If you found this valuable, you can subscribe to the show on...

More interviews