Lessons in product leadership and AI strategy from Glean, Google, Amazon, and Slack | Tamar Yehoshua (Product at Glean, ex-Google and Slack)

26 Sep 2024 · 1 h 17 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

Lenny's Podcast Episode: Lessons in Product Leadership and AI Strategy

Overview

In this episode of Lenny's Podcast, Tamar Yehoshua, president of product and technology at Glean and former chief product officer at Slack, shares insights from her extensive experience in product management and AI. Having led teams at Google, Amazon, and Slack, Tamar discusses the importance of cross-functional relationships, the impact of AI on product management, and strategies for navigating a rapidly changing tech landscape.

Key Topics Discussed

Background and Career Insights

  • Tamar’s Career Path: Tamar's journey from engineering roles at Amazon and Google to leading product at Slack and Glean.
  • Key to Career Success: Emphasizes the importance of excelling in your current role before seeking advancement, understanding the product deeply, and leveraging technical skills.

Cross-Functional Relationships

  • Importance of Alignment: Tamar highlights the necessity of strong partnerships with engineering leaders. Respect and clear division of responsibilities are crucial for avoiding organizational misalignment.
  • Building Trust: Emphasizes the value of having a dependable engineering partner and maintaining open communication.

AI in Product Management

  • Adopting AI: AI is transforming work environments, blurring the lines between roles such as PMs, designers, and engineers. Tamar sees AI as a tool to enhance productivity rather than replace jobs.
  • Practical Applications: Examples of using AI for sentiment analysis of customer feedback and automating routine tasks in product management.

Product Strategy and Leadership

  • Don’t Fear Unhappiness in Product Changes: Encourages focusing on the larger user base rather than the vocal minority when making product changes.
  • Lessons from Leaders: Insights from working with Jeff Bezos and Stewart Butterfield, including consistency in leadership and the power of prototyping.

Navigating Company Chaos

  • Success Despite Chaos: Shares that a company doesn’t need to be perfectly run to be successful, particularly in hyper-growth phases.
  • Career Planning: Emphasizes that rigid career planning is unnecessary; instead, focus on learning and following leaders who inspire.

Tactical Advice and Strategies

  • Prototyping: Make time for prototyping as it helps in understanding the product’s feel and viability before full-scale production.
  • Listening and Authenticity: Whether dealing with user feedback or internal team dynamics, listening and transparent communication are key to effective leadership.
  • AI Tools: Encourages using AI tools like ChatGPT and Glean to stay ahead and streamline tasks.

Resources and Recommendations

Books

  • Switch: How to Change Things When Change Is Hard by Chip Heath and Dan Heath
  • Team of Rivals: The Political Genius of Abraham Lincoln by Doris Kearns Goodwin

Podcasts and Newsletters

  • No Priors by Sarah Guo and Elad Gil
  • Cognitive Revolution for AI trends

Products

  • Glean: An enterprise search and AI tool for enhancing productivity by indexing content from various SaaS apps.

Closing Thoughts Tamar emphasizes the importance of adapting to the rapid pace of technological change and leveraging AI to enhance productivity and creativity. She encourages product managers to engage with AI tools actively and remain open to learning and experimentation.

Tamar Yehoshua's Contact Information

  • LinkedIn: [Tamar Yehoshua on LinkedIn](https://www.linkedin.com/in/tamar-yehoshua-886217/)
  • Newsletter: [Practical Intelligence Substack](https://tamaryehoshua.substack.com/)

Where to Find Lenny

  • Newsletter: [Lenny's Newsletter](https://www.lennysnewsletter.com)
  • LinkedIn: [Lenny Rachitsky on LinkedIn](https://www.linkedin.com/in/lennyrachitsky/)

---

For a detailed transcript and show notes, visit [Lenny's Newsletter](https://www.lennysnewsletter.com/p/you-dont-need-to-be-a-well-run-company-to-win-tamar-yehoshua).

Explore more insights and subscribe to Lenny’s Podcast for actionable advice from world-class product leaders and growth experts.

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:00Make sure you go somewhere where you have a good engineering partner because if you have great ideas of what to build, but you can't get them built, then you go nowhere. So that has to be part of your evaluation criteria that you meet and value your engineering partner before you join. And then I think what's really important is that you're aligned. You understand your roles and responsibilities and where you're going to divide and conquer and where you're going to be aligned. You don't want any of this, like people in the organization, they ask mom, they ask dad, and they got different opinions and playing one against the other, like that doesn't work.

0:36Today, my guest is Tamar Yehoshua. Tamar is currently president of product and technology at Glean. One of the most successful enterprise AI companies out there right now. Prior to joining Glean, Tamar was chief product officer at Slack for four years, where she led product design and research as the company scaled. 10X the revenue went through IPO and got bought by Salesforce. Tomorrow also led product and engineering teams at Google where for many years she was responsible for the Google search experience. She also spent five years at Amazon as director of engineering and vice president at a9 .com.

1:09She was also venture partner at IVP and has been on board of directors for ServiceNow, Sneak, Retail Me Not, and Yaxxed. In our conversation, we get into all kinds of juicy advice, including white companies don't have to be run well to win why you don't need a career plan. The two habits she credits most for helping her succeed throughout her career. What she learned from Jeff Bezos and stirred Butterfield and Mark Benioff, had to build stronger cross -functional relationships and a bunch of advice on AI, including how it will likely change your jobs, examples of how she and her colleagues are already using AI to be more productive in their work and what she's learned by building AI -based products that are non -deterministic and can be very unpredictable.

1:51This episode is for anyone looking to level up as a leader and get a better sense of how AI will change your job. If you enjoy this podcast don't forget to subscribe and follow it in your favorite podcasting app or YouTube. It's the best way to avoid missing future episodes and it helps the podcast tremendously. With that I bring you Tamar Yehoshua.

2:12Thank you so much for being here and welcome to the podcast. Thank you so much for having me. I've had so many people recommend you coming on this podcast. I'm really happy that we're finally doing this. I want to start with a question that I've started to ask people who have had extraordinarily successful careers which you've had. So let me ask you, what are one or two specific skills or mindsets or habits that you think most contributed to your success during the course of your career. They think might be helpful to people who are trying to figure out how to accelerate their career or just be more successful in their career.

2:47One of the things that I think is overlooked is do a really good job at whatever your job is at that point. So people have a tendency, especially product managers are very ambitious and they want to get to the next level and they're always eyeing the next job. But you're not going to get the next job unless you do really well at the job that you're in. Like knock it out of the park. However simple, however easy it may be to you, do a great job. And in tech jobs, there's like table stakes. There's table stakes of, you need to be technical, you need to know the latest technology, you need to understand your product, the product you're working on.

3:27No matter what your role is, you have to understand it deeply, you need to understand metrics. So especially product managers have kind of a wide birth of things that they need to understand. So those are a given, you need to do that. This episode is brought to you by Explo, a game changer for customer facing analytics and data reporting. Are your users craving more dashboards, reports, and analytics within your product? Are you tired of trying to build it yourself? As a product leader, you probably have these requests in your roadmap, but the struggle to prioritize them is real. Building analytics from scratch can be time -consuming, expensive, and a really challenging process.

4:04Enter Explo. Explo is a fully white labeled, embedded analytic solution designed entirely with your user in mind. Getting started is easy. Explo can exit any relational database warehouse, and with its low -code functionality, you can build and style dashboards in minutes. Once you're ready, simply embed the dashboard or report into your application with a tiny code snippet. The best part, your end users can use Explo's AI features for their own report in Dashboard Generation, eliminating customer data requests for your support team. Build and embed a fully white labeled analytics experience in days.

4:42Try for free at explo .co slash Lenny. That's expio .co slash Lenny. This episode is brought to you by Sprig. What if product teams knew exactly what to build to reach their goals? For an increasing conversion to boosting engagement, these challenges require a deep understanding of your users, something that you can't get from product analytics alone. Meet Sprig, a product experience platform that generates AI -powered opportunities to continuously improve your product at scale. First, Sprig captures your product experience in real time through heat maps, replays, surveys, and feedback studies.

5:23Then, Sprigs Industry Leading AI instantly analyzes all of your product experience data to generate real -time insights. Sprig AI goes even further with actionable product recommendations to drive revenue, retention, and user satisfaction. Join product teams at Figma and at Notion by uncovering AI -powered product opportunities at scale. Visit Sprig .com slash Lenny to book a demo and get a $75 gift card. That's sprig .com slash Lenny. So now the question is the difference in leadership and executive roles and like when you're getting there So how do you start transitioning? So after you've done a great job at everything and you understand the the core skills that you need Another thing you really need to know is understanding people and and motivations.

6:20And when you're building products, you have to understand why does somebody want to use your product? What problem are they solving? Why do they want to click on that button? What's going to make them feel good when they click on them? What's going to give them delight and what's also going to make them feel bad and frustrate it? And what do they not want to do? So you need to understand motivations and people for building products and for building teams and organizations. So just like why does somebody want to click on a button? Why do somebody want to join your team? Why do they want to work hard?

6:51What are they trying to accomplish? What's the goal for their career? So you have to be able to read people, ask lots of questions to understand them. And I'll say one thing that really helped me, this is a strange segue, but my father was a psychiatrist. And when I was growing up, we would have family occasions, go to the fence, whatever. and afterwards in the car ride back, he would always give his perspective of analyzing what happened at the event. What this person was thinking, why did they say this? And then he would like, quiz me, like, why do you think they did that? And it was really interesting because it taught me to see the whole room, to see how people react, like Lenny, if you say something and somebody else is there, look at the other person, what's their face saying?

7:42You can understand so much if you're paying attention. So I think when you want to build for people and lead organizations, it is about the people and understanding them and motivating them. I love this advice and there's, I feel like we can do a whole podcast on just this topic. So on this last point about understanding people, is there an example of this in either a product you build of just like, oh, here's something I noticed about someone using Slack or Google or Amazon that changed the way I think about building this specific feature. One of the things that I caution product managers about is that you don't want to be too overly reliant on metrics and you want to also have an intuition.

8:27You want product managers who understand intuitively their customers and their product and sometimes you'll make decisions because you just know it's the right thing to do because it feels right and it usually is right if you understand your product well enough. How do you get good at it? Ask a lot of questions. Don't assume you know. Go in, Mark Beningoff would always say, have a beginner's mind. Go in assuming that you know nothing and listen to your customers, listen to the people because I also see this as like you're building a feature and you think it's the best thing because of course everyone's going to want it because you worked on it and you're going to put it front and center in the interface where everybody's going to see it although you got to earn that right and that is another thing that people do is they want the thing they've worked on to be right there but it might not be the most important thing that a person needs at that point so have perspective have perspective of what your users are actually trying going back to your first point about doing a great job at the job you have.

9:37I imagine some people hear this and the advice is do a great job at the job you're doing and they may feel like they are or and there's other reasons that aren't being promoted. Is there an example from your career or a story you could tell I just like to clarify like what doing a great job look like or it's not just like I hit my goals. It's like here's what it looks like. Here's how you actually get ahead. Are you helping the business move forward? So it's not about I achieved what I was asked to do, but did you build something that people actually used? It's not about just launching something, and did you do the right thing for the company?

10:20And that is different. It's a different mindset. Did you enable the entire organization to be more productive? Despite you, so I remember very early in my career, I was working as an engineer and I was offered a job to manage a team that was across different programs. And I went back to my particular vacation and I came back and I said, you know, I don't think this team should exist. It was my first management job. And I wanted to be a manager. And I said, here's why I don't think that this team should exist. It's not the right thing for the company. It's not going to be productive. And my manager was so stunned.

11:03He was like, wait, you're saying no? I'm like, yeah, because here's how you should organize it. And then he's like, you know, you're right. And I'll find you something else and he did. If I were to put this into one word, it's impact. Drive impact. Yeah. Amazing. Okay. Going in a different direction, we were chatting before we started recording this and something that you shared with me and some people may be really surprised to hear this but I completely agree with this take is that you don't need to be a well -run business to win. I've seen this myself. I'd love to hear insights here and especially where you notice this.

11:42What parts of your career notice this to be true? I love working at well -run companies. It's more fun. Your people are happier. I like running a well -run team. So I aspire to have a very well -run team and to work at a well -run company. But what I've seen is when a company isn't well -run, like IT isn't working, marketing is broken. They're not enough people in HR. There's a lot of turnover. All of these things, I've seen that they're not correlated to the company being successful. So I can think of a couple examples right now of companies that I know, not Glean where I'm working today, where there's like high executive turnover, where people get yelled at, though lots of people fired, there's re -orges all the time.

12:30People I talk to are super unhappy, but the numbers are amazing. Like they're growing like crazy. And the opposite is also true. I can think of one company I know really well. amazing CEO, well -run, well -oiled machine, everything, hired good executives, and the flat line. So you just see it. You see it over and over again and people get very upset about these things that aren't working. And one of the things I try and do is give a perspective of what matters and what doesn't. And it might even be to the sales team because you get like all these requests for features all the time. If you did every single one, it would be impossible, but even if you did, 80, 90 % of them won't matter for the success of the company.

13:18But then there are some that really matter. So what are the things that really matter? We always talk about product market fit. Nobody really knows what product market fit is. Everybody has a different explanation, but it means like people want to use your product right, that they're like clamoring for it. So you built something that people value and that people value in that solves a problem for them, but that's also not good enough. You need to build a great product, but you also have to have distribution, and you need to have a sales team that works. And those are probably, and you have to have enough money in the bank to get there.

13:54So those are probably the things that are the most important I might be missing something. And then within each of those, there's the things that really mattered. There's so many features that we built at Slack that were the most important features ever that failed and nobody used. So that clearly didn't have an impact. And you can see that in retrospect, but I think after being in multiple different big companies and small companies, I have that perspective of let's just make sure that we do the right things and don't get too worked up about all the things that are broken. Every startup has so many things that are broken.

14:29So I think a really interesting insight here is that if you're working at a company that is just chaotic and it feels like we don't know what we're doing. I don't know how this thing is running. I don't know how this will continue to be successful. Your experience is that most, is it that most of the successful companies you've been at are just like chaotic internally and aren't like incredibly one run and that's normal. That's very typical. Until they get to a certain scale. Now once you reach a certain scale and you've already conquered the market, then you kind I need to be well run. Then you bring in professional managers and things are about the cost and executing and getting all the, like, once you get to like over 5 ,000 people or 10 ,000 people, like you got to have things that they, I mean, then you're like a growth engine.

15:15So different, you have to know what phase you're in and what's important at that phase. So it isn't that at every phase chaos is okay. And also some chaos is okay. And some chaos is not okay. if you're changing your strategy all the time and you're changing your direction and you're changing like you're changing projects and people all the time so that they can't like actually achieve anything. So there's this is again so it's you can't simplify it that some chaos is okay and some isn't and also some chaos is right for you as a person like there's some well run there's some really great companies I would never work at because they don't fit me they're not a company I would enjoy going to work in the morning or they're not aligned with what I'm good at.

16:03So just because a company is doing well, if the chaos is chaos and something that's going to make you upset and unhappy, don't worry about that. Is there a correlation there just like companies that have strong product market fit, things are just breaking as the hyper grow, hyper going through hyper growth, just thoughts on why this is the case? A lot of it is that because if you are in hyper growth, you've got customers coming at a really fast pace. You're growing your company really quickly and the number of employees and it's just really hard to keep up because things in the infrastructure, break, things in the communication breakdown, you've got at any given point 50 % of the company has been there less than six months.

16:44But you have to grow really fast because once you hit product market fit, if you don't, then your growth will stop. So if you're suddenly growing, especially if you're enterprise company, you have to have sales people. If you're a consumer company, your systems have to keep running as you scale and look at companies like Myspace, well they died because their product got too slow. So some companies have initial product market fit and then they don't keep up. So I do think a lot of it is, it's very hard to grow that fast. So things really do start breaking, but then once you get all the right leadership and and then it starts to get better.

17:25So it goes through ups and downs and level of cash. Does one take away here that product market fit solves a lot of problems? Strong product market fit? Well no product market fit is a desens. I'd say we're like that. Like you can't, like if you build a product that people aren't really excited to use, then you don't have a company because it's very hard to do that unless you have a distribution machine and then you catch up over time but we will not name companies like that. So there are other ways of doing it but yeah that is the most important thing. Yeah I will say during my experience it would be absolutely so this it was just non -stop chaos and always felt like well how is this continuing to operate and succeed things are just out of control everything's changing every I don't know what's happening here.

18:18And I think a lesson here is just that's normal for hyper growth business. That has strong product market fit. But again, not a good excuse to just allow chaos and it's not like chaos means success, right? Right, and it's not a good excuse to like not have an organization that's functioning. You should still strive to have an organization that's functioning and keep people happy and motivated and all that. Great. Okay, another maybe contrarian opinion that you hold Along the career track is that you don't need to plan your career. I also 100 % agree with this. I had no plan for my career. I never knew where the hell it was going to go.

18:55I never had this like vision of here's what I want to do. I just kind of followed things that are pulling me and things that seemed interesting. I love that you also tell people this. I'd love to hear your insights here, especially for someone that's either struggling with their career or just stressed they don't have a plan or their plan's not working the way they wanted it to. I really recently I was talking to somebody in their 20s who was asking me for great advice and you know should I be a product manager etc. and like I'm trying to put together my five -year plan and I said I never had a five -year plan.

19:25Like so to be clear some people need that. That's the kind of people they are. They want the planning. I said it's great if you want that but I never had it and the person I was talking to just relaxed and they're like, oh my God, that's so great to hear. I have no idea what I want to do in five years. I'm like, I still have no idea what I want to do in five years. I've never had an idea what I want to do in five years. So, when, you know, early in your career, you have a lot more angst about it because the forks in the road are more significant because they can go like, do I go get an MBA or or do I go work for somebody?

20:04Do I be a product manager and engineer and those really take you in very different paths? And I meet a lot of kids in their, I shouldn't call them kids, because they're my kids friends, but a lot of people who are younger in their career who are struggling with this a little bit. So what I believe, and I've always believed, is that you follow people. You learn the most from people. I don't look for domains, I mean, some people have a domain like I'm super interested in like, you know, climate or whatever, and they really want to work in that area and that's fine. So maybe within that area, but you follow people who are the best at what they do.

20:47So it's not good enough to follow somebody who you like. You want to follow somebody who's either the best product thinker or the best engineer or the best salesperson. And so that you will learn the skill of how to be the best at that. So you follow people where you're going to learn the most. And a way to do that also is you look at where the great people are going. So you want to go to companies where there's also a nexus of great people because they together will do great things. And even if the company fails or succeeds, but not as much as you'd like, you still have those connections. I mean, everybody talks about the PayPal mafia and how they've gone on to do things.

21:29I was super lucky to be at Google for so many years and I know I spent a lot of time with X Googlers that I met and that are all working in different companies now because you build those relationships by working together. So if you follow people and where you're going to learn the most and you go step by step, I think that's a great way of progressing in your career. That's such tactical advice and I've seen this succeed, this work for a lot of people that just go where their favorite former employees work and not favorite to your point, but the people that they most respect and have been most impressed by.

22:08And I think it's such an easy thing to do. It's like, it's a really easy to risk for understanding where to go. There's something Mark Andrews, someone shared that I reminded of when you say this, is that there's a site, there's like a term for this, I forget the actual term, but there's like certain companies have this gravitational pull where they are acquiring all the best talent. They're currently like the gravity in the space and everyone awesome is going there. And you have to, as a company know, you're one of those companies or you're the opposite, you're losing all the people and they're all going to.

22:37So they're company. I guess any thoughts on that? Thought? Yeah, and it's really bad when you don't have a gravitational pull. It's super hard. I would say that one thing that if you're a manager, I always advise managers, go somewhere where you can recruit. And one, I got a piece of advice from a friend that I thought was amazing advice as a leader. She said to me, take a job where if you hire people, it's gonna make their careers. Oh, I was like, whoa, because I was getting offers for like some kind of turnaround jobs. And you know, if you think you can turn around, great. But you want, if you're going to hire the best people, you want to make sure that it's going to be a good place for them and that they're going to learn and they're going to grow.

23:30And so you want to do right by them and you really purposely want to say you can make your career by coming here. And I thought that gave such a higher bar for every job I was looking at as a leader that I thought it was just amazing advice. And then on the flip side, on the negative side, some people are looking, putting too much emphasis on where will I get a big financial return. And I found that financial returns are the hardest to predict. You know who's good. You know who you want to work with. You can predict where you're going to learn because even of a company fails you learn a lot. but predicting financial success is so hard because you don't know what's gonna happen with the market, with the world, with crypto and MNI.

24:22And people who do that and say, like I had one person say, I took this job because I'm a mercenary. They just paid me a ton, did not work out for it. And I feel really bad when people do that, but I think that it's a dangerous thing to do. I imagine some people hearing this advice are going to feel like I'm not going to get a job at opening eye or green or other awesome companies that everyone wants to go work at. Any advice to those folks? There's lots of good companies and there's lots of smart people. You don't have to be at the top brand and if you go somewhere where you're going to learn and it's going to get you there, I mean I made mistakes.

25:04I made, I went to some companies, multiple companies that failed or stop growing and didn't do well or didn't have all the right people. Like, careers you don't make every step is to the right place. You remember in what you cited, all the companies I went to that did well. You left out all the ones that I went to that didn't do well. And so then people will assume that every time I made a job change, it was to a company that did well. No, that was not the case. So if you focus on that learning bit, you will get there. And there are lots of paths. There isn't just the opening eye or leaner in topic.

25:42Awesome. Again, I love how tactical this is. If someone is trying to figure out where to go work, if they're unhappy in their current job or don't have a job right now, just make a list of the people you most respect that are the best at the thing they do, see where they work, and there's your list of companies to potentially go after. There's a lot of benefits to this as you shared. It's not just helping you pick the place to work. It's the network. It'll level you up. Is there anything else along those lines that is helpful for people to think about why this is a really good strategy? Skills can't be taken away a company can fail, but if you learn a skill you will always have that skill Love that and I've totally seen this to work.

26:19So I really love that you're focusing on this advice You've mentioned places you've worked in folks you've worked with worked with folks like Jeff Bezos, Stuart Butterfield some of the top product thinkers leaders in the world So let me just ask, what's one thing you learned from Jeff Bezos and Steward Butterfield? Probably can't narrow down to one, but from, I'll talk about Bezos first. I was very lucky to join Amazon early when I still, like, I had quarterly meetings with Jeff Bezos. How well? And this was before AWS launched. So it was before Amazon was known in the valley. And this is another example.

26:54I went there because I went to work for Ooty Manbar who started day nine and he was talking me one night trying to recruit me and he spent two hours on the phone with me telling me how amazing Jeff Bezos was. And this was before like there were any books on it. And that really convinced me to go there. So there's a lot written on Bezos. Read his shareholder letters, read the books about him, read Colin Breyer's working backwards. The everything box I think it's called or the everything store. Everything store. And there's so many good books and there's so much to learn about how he works. So won't try and cover those things.

Read the full transcript

27:33The things that stood out to me from the meetings I had with him were a couple things. One, you know, a lot of people have written about these six pages. So you have to, he doesn't believe it. PowerPoint, you write a six -pager about, I mean, it's like studying for a final exam. It's writing these six -pagers. So you go into the meeting and there's people around the table, his executive team and him. First, he does not speak until everybody around the table speaks. So he goes around to all his leads and said, what do you think? What do you think? What do you think? I'm sitting there like, I don't care what I do.

28:06I just want your basis things. But he wants to, he wants to make sure that it's a team effort and that he's listening to what everyone in his organization thinks. And he always spoke last. He is by far the smartest person I've ever met in my life. In that I've worked a lot of smart people, but he's ability to go deep in any domain and nail the core issue and remember, like we would have quarterly meetings and from quarter to quarter, he would like remember things if he had talked about before. And then he would go into like the architecture of search and And why are you doing it this way or that way?

28:49And you're just blown away that he knows that. But the thing that for me the biggest takeaway from this meeting was his consistency, which is he had principles that you, it made it easier for you to operate in his company because you knew what he cared about because he always had these principles. Everything had to be customer driven. Everything had to be relevant for the customer. He did icons. the, it's just the thing, you had to like write what they were because people couldn't figure out what they are. So anytime you show an icon, who you get annoyed. But they were like, so when you would go in and after a couple meetings, you're like, okay, I know what he's going to ask about.

29:27I know how he's thinking and I know what his principles are. And I think those that consistency enables you to operate a large organization more effectively. And then there's one other thing that I really remember was very one of a few really small meetings I was in with him and we were presenting working on a new product and I was like the our competitors have like ten times as many people as we do on this and he looks at me and he said that is your advantage. And then he goes into his talk about how it's a hill and it takes seven years to build a product. You can't look at it in the near term.

30:04It's going to you have to be in it for the long term. And you can be sure I never went in and said I need a lot more resources. So that was based us. Oh, see. Stort, again, I went to Slack because I wanted to work with Stort Butterfield. I think he is the best product thinker in the Valley or he's not working in product right now. He's taking time off. but he's got this combination of long -term thinking in the details. So in 2014 he wrote a master plan for Slack, which was build a product that people love, build a network that's Slack Connect, build a platform that makes all of your other SaaS products more valuable, the Slack platform, and then do some magic AI stuff.

30:51The magic AI stuff took a lot longer. But it was part of his plan early on as magic AI stuff. literally was there was a there was a grid with four boxes in 2014 and it never changed. That was his master panel and what we worked on each year changed. But somebody recently asked me, well did he always like you know you guys did slack connect much like him like yeah because always part of plan. It was always part of his vision until he saw forward in the vision but he also was very much into the details. And I think the thing that I learned from him the most was the power prototyping. And that even though he was such a great product thinker, he would always say, I can't tell you if this is going to work.

31:32I have to feel it. I have to try it. And a mockup doesn't tell you what it's going to feel like. And he would push people to do prototypes, not incremental of just to get a feature out, but really to think very soon after I started we launched a hard -to -designly, and he led a redesign of the new information architecture for some reason. I worked with Ethan at R &B. Oh, yeah. He was head of design for the search experience in the search team. Yeah, Ethan was awesome. And he came in and his first task was to work with Stuart on this redesign. And Stuart came in and said, I want you to take everything in the interface and put him behind one button.

32:18And everyone's like, that's never going to work. And he's like, do it. Just do it. And so we had our prototypers. We had also engineers, front end engineers, who were really good at prototyping, like literally took everything in the interface and put it behind one button. And he said, this is how you're going to see what you really need in the interface. So we were never going to ship that. But it was the beginning of the redesign. Let me tell you about a product called Sidebar. The most successful people that I know surround themselves with incredible peers. When you have a trusted group of peers, you can discuss challenges you're having to get career advice and just gut -check how you're thinking about your work, your career, and your life.

32:59This gives you more than a like up. It gives you a leap forward. Having a group of trusted and amazing peers was key to my career growth, and this is the Sidebar ethos. But, it's hard to build this trusted group of peers on your own. Sidebar is a platform for senior tech professionals, director to sea level, to advance in their career. Members are matched into peer groups to lean on for unbiased opinions, diverse perspectives, and raw feedback. Guided by world -class programming and facilitation, all running on sidebar technology, sidebar enables you to get focused, tactical feedback at every step of your career journey.

33:34If you're a listener of this podcast, you're already committed to growth. Sidebar is the missing piece to catalyze your career. 93 % of members say Sidebar helped them achieve a significant positive change in their career. Check them out at sidebar .com slash Lenny. As a product leader, how do you think about just the time it takes to create a prototype? And something like this. You know, as a PM, I'm just like, a lot of times, we don't have time to build this whole prototype. We got a ship stamp, we got these calls, we got experiments to run. We'll just build it and see how it goes. How do you think about making time for something like that?

34:08If you're doing it right, it'll be faster. You need to have an engineering infrastructure that enables prototyping. Some engineering infrastructures are too heavy and they don't actually enable prototyping. We had a problem with our mobile apps that it was too hard to prototype and we actually redesigned our mobile apps until we got to the point where it was easier because our desktop app was pretty easy to prototype, but you have to have a layer of abstraction that enables you to do that and you have to have engineers who have a prototype you meant set. And if you build multiple things and you have this mindset as I'm willing to throw it away, you write code that you know is never going to make it to production.

34:50So you can get you can just crank it out much faster. And then you can see what works and then you build the production And so you actually get to your end goal as something working faster. But you need the engineering team to have this same mindset. The product and engineering have to work together and design because design is just in it. In it as much as sometimes you can get design engineers who are doing the prototyping. So your first prototypes are like Figma prototypes. And then you get prototypes on real data. When I was at Google, one of our teams at Frontend Team, I remember we got, we hired a bunch of prototypers in our head of front end engineering said to me one day, this is my secret weapon.

35:31This is how we move faster. So I do think it's a mindset shift and a tech stack shift. It's also we're going to talk about AI later, but it's also getting easier to build prototypes with AI. There's this video recently that went around on Twitter where an eight year old girl was building an app and in like 45 minutes, she built like a chatbot using this protocol cursor. So I think that'll unlock a lot of great product opportunities and just accelerate the sort of work. I asked about Jeff Bezos and Stuart Butterfield. I'm curious if there's another leader you've worked with that maybe is less known that you also learned a ton from that might be worth talking about?

36:11I think that there are people who are really, really good at what they do. So Mark Benioff is an amazing marketer. He's so at like his marketing mind. So after the acquisition, I got the opportunity to be on stage with him at Dreamforce for, cause you know, Slack was a new shiny thing. So of course, Slack was gonna be in the keynote. And so I was in the, yeah, Benioff's keynote two years in a row. And so I watched how he approaches his keynote and the whole thing around Dreamforce. And Dreamforce is incredible at the impact that it has in the ecosystem. And so I think that as a product people don't think of him as much, but as his marketing abilities are amazing what he's done.

37:06I've written posts about how various companies got started and Salesforce's story always comes to find where they go to conferences with us like no software mascot walking around. And I remember they did something around what are the competitors where they just like created some real controversy around someone. Well they went into their competitors conference and stood outside. Right. That's what it was. Yeah, this is in the beyond software. So this is in his book that he wrote about the early phases of Salesforce and it takes guts. He He pushes the envelope. I love that. It's a really good point that people don't think of Mark Benioff as a marketer.

37:44That's interesting that that's one of the, maybe the main thing you took away from him is just the power of marketing and the skill. He approaches his marketing presentations like a product person approaches their building a product. Amazing. Okay. Speaking of former colleagues, I asked one of your former colleagues, his name is Fuzzy He's now the CTO of Notion. You worked with him. I believe it's Slack. And Google. And Google. Wow. Okay. So I asked him what to ask you. And he said that you're amazing at building strong cross functional relationships, especially with engineers. I know you used to be an engineer.

38:21So I get, where that skill comes from. What can you teach people about building stronger cross functional relationships, especially to build better relationships with our engineers, designers, other folks on our team. Probably the most important thing that a product leader does, because if you have great ideas of what to build, but you can't get them built, then you go nowhere. So one, make sure you're somewhere where you have a good engineering partner. So Cal Henderson was a co -founder and CTO of Slack, and I couldn't have asked for a better engineering partner. He's just awesome. And you need to, that has to be part of your evaluation criteria that you meet and value your engineering partner before you join.

39:05Or you know that it's not the right one and the organization is willing to make a change. So that can happen too. You can go in and understand that something has to change. But that is a very, very important thing of what you're doing and what you're assessing when you go in. And then I think what's really important is that you're aligned. You understand your roles and responsibilities and where you're going to divide and conquer and where you're going to be aligned. You don't want any of this, like people in the organization, they asked mom, they asked dad, and they got different opinions and playing one against the other, like that doesn't work.

39:38So one you have to know that you're not going to do that. So if somebody would ask me something that was in Cal's domain, I'd be like, did you have to call? I would never try and go around him. So we were very clear on, you're going to drive this. I'm going to drive this and if it was unclear, we would talk and we would say, okay, who's going to take this one? And we would do all our reviews together. And so all of the OKR reviews, all of the, we had weekly exec reviews, we had the updates on our OKRs. So we did them all together, but I knew like, here's the things that he was going to ask the questions on a dig deep.

40:15And then when I was, he would take a back seat, but of course we could ask questions in each other things, but I knew that he was taking ownership. And he knew what I was taking ownership of. But I think the bottom line with respect is that you have to respect and trust that they actually will follow up on what they say. They will encal and fuzzy. We're like, amazing dad. I would go to fuzzy and be like, hey, we need more mobile engineers because this one product is not going to ship and we and he's like, I'm on it, got it. And that was all I needed to do. And like, obviously, he couldn't do it.

40:47He'd come back to me and like, Hey, there's going to be a problem. But it was like, just things got done. That's, that's the best part of it. You talked about being aligned, which I love and I fully have seen that power of that of you and your management, your desire manager being aligned on. And you tell me if I'm wrong, but specifically on what goals you're trying to achieve what success looks like, things like that. If there are any tactics you found to create that alignment. And also if there's anything else you want to add to the point I just made about what it is, you're specifically aligned on, that'd be great.

41:19One, you gotta spend a lot of time together. I mean, there isn't kind of a way around that and you have to document things and make sure that you've talked it through. And if you don't agree with something and you're not sure it's a priority, you have to speak up and you can't just be like, like, okay, whatever, and then go to somebody in your team and be like, oh, God, that CTO, like, why did he make this decision? Like, that just doesn't work. So I'm a very direct person. So if I don't think that something is the right priority or is working, I will be very clear. We had different forms. So I'll be very tactical here on the forms that Calle and I had together.

41:56Perfect. So we had, we used OKRs to drive our processes. and we would have the teams present OKRs to us. When the team got too large, it got to be too much time to go through every team's OKR review. So we had them get a Slack channel for each team. They're OKRs. They're a planning channel for each one. And people would post a doc and then a Slack video of going through the major points. And we had a time limit of how long they were allowed to be. And they would say, here's the OKRs. Here's the things that you would pay attention to. and then Cal and I would do a marathon and we would watch them all together.

42:36And we're gonna room sitting there watching them together. Correct. And then we would like say, do we have any follow -up questions that we put in channel our follow -up questions to the team and sometimes there would be like five to ten teams that we would then have a follow -up meeting with. We would say there's things that we, this is like a really high priority project or there are a lot of questions that we have and then we were deleted, but we were always doing those meetings together. So that was the okay, our reviews of getting the alignment. And by asking the questions, we could then, by adjusting us, we could kind of dig into the team.

43:10And we had, we had a chief of staff. So it was the two of us, plus or two chiefs of staff, and which they also did a divide and conquer, and they worked really well together. They were both long times Latin police. So for years, they had, one had been an engineering director and one had been a TVM. And then every Monday we had a Monday meeting where we reviewed the progress on the top of hairs and red yellow green and don't talk through the green ones, only talk through the red ones and what are the issues. And again, both there. And then we had a weekly meeting with the four of us where we would just go through any issues in the organization and what's going on, what's not.

43:51And the four of us is you, the CTO, the Chiefs of Staff. Yeah. And sometimes we would invite people like there's an issue with QA so we'd have the QA leader come in and present us. But we tried to limit the number of meetings with like teams. So it'd be like the okay Our the Monday meeting was the big meeting that you had to be there and you had to be able to talk to your project and that was it There's so much Awesome this here. I love the idea of this async share your plan and a video instead of meetings with everyone in real time and you could just do a lot of the stuff I think. We iterated every quarter, just like you iterated on a product.

44:26So every quarter, we would say, did the OKR planning work? Or not? And then we would adjust. So we got to the point where at one point, we added up all the hours of OKR reviews and all the people in them. And it was like some insane number, like 300 and something. And we're like, this has gotten out of hand. And so then we're like, we have to do something drastic. And that's when we moved them to Aysink. It was also right after Slack clips launched. I got it. That's the video feature. Very cool. And then I don't know if you're you launch huddles right? Slack huddles here. Did you use that as a part of this where eventually you just get people into a little huddle like synchronistically and talk sometimes absolutely we would be in the reviews and we would huddle with somebody to ask a quick question.

45:06We use huddles all the time. I still do I love how it's love it. One crazy thing about Slack is people in Slack don't actually use email internally right? it's like all in Slack. It's like the actual vision of Slack working within Slack. No email unless you're dealing with somebody external and now it's mostly Slack and F. Anyway. Wow. That's amazing. OK. I have one more question around product stuff and then I want to talk about AI. So I was reading your newsletter on Substack, which we'll link to. And you share this really interesting insight that I've experienced myself that I'll quote you here.

45:40One of the mistakes that I see a lot of product managers make is they over index on people who are going to be unhappy with the products they're launching. And you basically, your advice is not to worry so much about making users unhappy, which I think is countertuitive. And countertuitive to some people. You just talk about this lesson, and I'd love to hear what product you launch that made people unhappy that you realized, oh, maybe we don't need to worry about this as much. I saw it more when you launch things. You tank things away. There's always some set of users that are using a feature that nobody else does and Then you take it away and they're super unhappy, but there are more people you're gonna make happy so you get a product manager gets caught in this trap of the vocal minority and The number of people using your product depends on what phase are you a Google?

46:34I use lac or you a glean, but the number of people using your product today is is usually, unless you're a Google far smaller than the number of people you're going to be using your product tomorrow. So design it for the people, the bigger number of people who are going to be using it tomorrow. Like if you have to redo the UI and you know that, like with my cheese, people will be unhappy. But all the new people are going to be like, this is so much easier. Then do it and deal with the people who are unhappy. But the trick is you have to be respectful When you have to be transparent and you have to explain.

47:09You have to go to people and say, this is why we made this change and you have to be authentic. You can't be dismissive and you can't have marketing speak. You have to really say, here's for real why and you have to listen to your audience. You don't want to alienate your early users. Because most people, if you made a good decision on why you moved this or why we stopped using slack calls and moved to huddles and like you have to do it over time and give people choice and then give them enough time to move. So you have to do it in the right way. But if people feel heard, it makes a difference.

47:50And I have an example that's not a product example, but I think is a really good one. It's a leadership example. So when I was at Google, there was always a controversy about something. But there was a controversy about it was like blogger or something. I can't even remember what it was. It was like we made a change. And there was an engineer in my, in my, or, we were like 50 ,000 people at the time. There was an engineer in my team and I see an engineer was like super unhappy about the change. And I knew Rachel Letztenge. She was in charge of all of PR and global policy at Google. So a huge job.

48:22And I emailed Rachel and I'm like, hey, do you have like an FAQ or something that I can help me because I don't know why you made this change and that I can help explain to the engineer in my team. She did not respond to my email. She picked up the phone and she called him. I had no idea. She was she did this. She just called this IC engineer and she listened to him. And she heard why he was upset and she explained her reasoning. He was so blown away that she called him that he completely changed his opinion and then he told everyone else in the art. And so it had this effect. And I learned a lot from watching her do that.

49:02Like she never even told me she did it. Like later she just did it. You just act. You're authentic. You listen to people and you're transparent. It's so funny. This reminds me of a book I'm reading, a parenting book. I'm reading right now that a former guest recommended called listen and the core Theses of the book is when your kids are acting up or there's their getting off track so much of what their need is of sense that you're connected to them a connection which is rooted in you listening to them and so all these my favorite You're an interesting book. I don't know if this is the same one or a different one.

49:38It's how to talk so your kids will listen and how to listen so your kids will talk. Maybe it's the new name of that book, but it's so good and it's so true in everything and also in products. So whether you're in a forum and explaining to customers, whether you're enterprise customers, you're explaining, you're hearing them out, people want to understand. Amazing. So many applications of just the power of listening. Okay, well, not quite a segue, but let's talk about AI. You're kind of at the epicenter of AI now with Clean. How do you anticipate AI will change our jobs in product? What do you think people may be armed, recognizing it, realizing it, what have you seen?

50:20I'm going to give you a little bit of my history with AI to get to that point. So I actually, when AI was a completely different technology stack, I have a master's So I started working in AI when it's evolved so much. And then of course at Google, using it for autocomplete and search. And it's transformed so many times. But then with this last transformation of Gen AI and that's what brought me to Glean of seeing this like meeting lots of AI companies and like, wow, this is really gonna transform how it worked. And it's just fascinating seeing these products. I was kind of one of those people like, oh yeah, it's going to be so far away until like I saw GPT3.

51:05And I think AI, we are underestimating how much it's going to change how we work. It's not going to be sudden from today to tomorrow because people haven't figured it out yet. They kind of haven't figured out how exactly to leverage it, but the people who have are going to be so far ahead. They're going to be far ahead of everyone else because they're going to be working faster, they're going to be working better. And in five to ten years, I think the lines between product managers and engineers and designers are going to blur because AI will enable product managers to build prototypes, to build designs, designers to build a product like Sigma already has their FIGMI eye, you can press a button and you can get your initial prototype working.

51:53You've got all the cold pilots. So they're not quite there. You still like with co -pilot or with cursor, you need to be an experienced engineer to know when it's getting it on, but they're going to keep getting better. So I think people have to be careful about not getting left behind, but their jobs aren't going to go away. They're just going to change. And we're going to, I'm a believer that we're just going to love more stuff. But I talk to engineers into PM and say, yeah, I tried that. It doesn't really work. And then go back to how I worked before. And that's a, that's a dangerous spot to be in, I think.

52:33For people like getting society here and this, where they're feeling good, they're going to be left behind. And like, oh my god, I don't know enough time to do this. Or I don't know what I'm doing here. Give me advice for how, so with something someone can do to. not fall behind. Use the products. This is what good PM should do, period. Always be using new products. It's not a unique thing for AI. When mobile came out, PMs needed to be using mobile apps all the time to try them out, see what the UI's are, see what's working, what isn't. And the same goes even more for AI. Use chat to PT if your organization has clean, use clean, use claw, try them all.

53:13like try them and see what they do. I was talking to a product manager I know who is more forward thinking and loves playing with new products and he had this use case that like blew me away. So he said and this was like a couple months ago. So before it was right when Gemini had expanded the context window. So his product had a discord channel and he took the transcript from the discord channel, which was huge, right? And he fed it into Gemini, the entire channel, and then used it to ask questions. Like, what is the sentiment of my product? What is the most requested feature? What are the things people are unhappy with?

53:55Like, this never worked hard to make. And it's like, that is so smart. And he's like, it was like a gold mine. You know, how long it would have taken him to read? And he just wouldn't have done it, Right? So you're think about like for the argument, oh, I'm too busy. Well, if you use these products, you're actually not going to, you're going to, it's going to be a leverage on your time. So you get a lot of articles sent to you, summarizing. You use AI to summarize the articles. We use GONG at Glean to record our all our sales calls. We have a Glean app that will read all the Gong transcripts, put them in a spreadsheet in a certain format of who the AE is, etc.

54:39and then summarize all the top requested features from all the Gong calls. And we took a while to get it right. Like at first it would, the summarization, the prompt, wasn't good enough and would give us features that like our salespeople would recommend and didn't distinguish that this was actually the customer. See, I have to tweak it. It's not going to work out of the box. But then we got to the point where it worked. And like these things really save time. And you have to use your creative juices as a piano to figure out how it can help you and have patients to iterate and keep trying because the models that we have today can do a lot already.

55:22Yeah. I love your example of the PM and what they did with the Discord channel. Is there anything else along those lines that either you've done to leverage some AI tool to be more productive or folks in your team have done to be more productive you their product leaders or other folks? So many examples. So one that I did really recently is I wrote a prompt in Glean to help me get the status of features and like you have a launch cowl and you can look at launch Cal and we'll say a day. But then, like, is it really the day? What are the outstanding issues? So it will look at our launch Cal and it will look at see if there are any open -gear tickets, what the Slack conversations are, to see and the customers who are beta testing it, like, bring all these together to tell me, okay, launch data is this according to launch gel, but here are all the open issues and here are the open conversations that people are talking about.

56:19So then I can give me the confidence level of the feature with it. So I can run the prompt, just put in the name of the feature and get like, so I don't have to read all these channels. So this is a prompt that I built like two weeks ago. Because we're advancing our prompting capabilities. And so I was testing it out. And I was like, oh, I could do this. So that's like, and that's another example. And engineers are using it for automating part of the incident management of like I got an incident, how do I see all of where their previous incidents that were similar to it, where they're not. And so these are the type of things you can look at to say to help you.

57:01But like the simplest, simplest is there's so much news. Let me just like paste in all these things and summarize them like as a product manager, Gleam, hear all the latest news, what do I have to care about? What's impacting me and potentially competitive to any of the products that I have? And putting that into say, collater jet JPT you're saying. Yeah. Yeah, I think that just, I think that beginning of the prompt is something a lot of people don't know is the power of just giving it a role. Like you are a product manager, a glean from that perspective, give me this summary versus just summarize this.

57:40And that ends up being really powerful, right? 100 % and you can compare and like what is Quad, you know, PR saying that's like they just launched Quad Enterprise. How is Quad Enterprise different from OpenAI Enterprise? And what are like because these things, again, you can do it yourself, but these micro improvements in your productivity help. There's a, I, for my newsletter, I interviewed Claire Vogue who came out with chat PRD And so, product managers are using it. We're just starting to evaluate it internally in late. So, I haven't personally used it yet, but it's super cool. And you can use ChatGPT to do a PRD.

58:23And ChatGPRD gets more templatized, more frameworks of how to do that. And these, again, these things are going to keep getting better. There's been on the podcast. She's going to be speaking at the Lenny and friend summit coming up October 24th. Oh, cool. Yeah, and she a crazy statue sharder. She's making six figures off this product that she builds on the weekends chat priority So incredible, but it also shows what you can build with that Right, and it's just her I think she just recently hired some engineers to help because she has she has like three kids CTO launched darkly and just is building this on the side making hundred thousand plus dollars Incredible I want to add one a couple things here.

59:03So one is for folks looking for ideas for how to use AI tooling for their PM job. There's a couple of posts I've written that I'll link to in the show notes just to put that out there. Just a bunch of PM sharing here's what I've done with these various tools. Another thought I love you get your take on. There's a lot of fear that the PM job will be replaced by AI and I recently realized that it's the opposite. I think the PM role is the best positioned to thrive in a role of AI because if you just think about you have a tool that can just build a thing for you, just like you're staring at this blank thing that can build anything for you, which function would you think would have the best chance of building some of asking it of what to build and how to articulate what to build best.

59:47To me, it's clearly product people. They're best at figuring out what to build, what matters most, what the impact is going to be, what customers need, not to say other functions don't also have these skills, but I feel like evolve functions PMs have the most of that specific scale. I love to get your cake on that. I think that AI, the one thing it's not good at, has been creative. So if European who's doing the kind of route work, it's going to take your job away. But if European who actually is strategic and can pull the pieces together and be creative and think how you do something that it's going to differentiate, because it's not going to give you that leap, it'll say, here's what customers are asking for.

1:00:25Here are the problems today. But you have to figure out how to solve it. So in some ways, it might weed out the good from the bad PMs. Because there's our significant number of PMs who are more, like, just execution. And I think that part of the job hopefully will be lowered because I hope a lot more of the execution will be able to automate, like, updating Jira and, like, you know, all these things that just take time and creating even lower, like, launch cows, which PMs have to do manually now. So hopefully a lot of that work goes away and then people can be more creative. And I think designers and pms are kind of going to blend because the best designers I've worked with are product thinkers.

1:01:07And a lot of really good pms can also design. It depends on the what kind of product you're pmming for. But so I agree with the caveat that it will become harder to be a great pm. Wait, say more about that. It'll be harder to be a great PM because the many PMs are doing things that are mostly like project management and that's the stuff that you use. Yeah, let me rephrase. It's not going to be harder to be a great PM, but to be a PM, the not -to -good PMs jobs will go away. The great PMs will still have great jobs. Yeah, it's totally here. So there in the sense there might be fewer. You might need fewer PMs, but I think that applies in theory to every function.

1:01:47I don't think there are engineers, fewer designers. I don't think you'll need fewer. I think you'll be able to do more things. So, think about every company in our head of sales came to the other day. You need to hire more engineers because we just have so many things we need to build. Like when have you ever worked in a company where you thought that you didn't need more engineers? Like you always want people to build more stuff. So I don't think you're going to need fewer. I think you're just going to get so much more done. A lot of people are building AI into their product. Gleenas is obviously an example, which integrates LLMs, which in a layer, non -deterministic and hard to know if they're going to provide anything good, sometimes something really dumb comes out.

1:02:30Do you have any advice on working with these very complicated systems that don't necessarily, you can't control and building them into your products, anything you've learned that might be helpful? My first week at Gleene was eye -opening in learning some of these things, but let me first just explain what Glean does for people who may not know. So Glean was started as Enterprise Search, which reads content of all your SaaS apps, so it reads the content from Microsoft, Google, Slack, Salesforce, do you know like any SaaS tool that you use, it indexes it and enables you to search. So it started as just Enterprise Search, then when, and using AI, so it was an AI search using BERT models and using vector embeddings in 2019.

1:03:15because the early engineers at GLEAN came from Google and Google created BERT to enhance search. And so it was obvious that they would be using ML techniques for search. Then GPD3 came along and added a natural language interface, a chat interface, you can ask a question in a national language and get an answer. And it basically is a knowledge graph of your organization, so you can ask any question, think of chat, GPD3, if you're an employee. Ask any question about your enterprise. So search, people understand search because they understand Google and you put in a query and then you refine it.

1:03:53But chat interfaces, people still don't really know how to use. If you look at the stats from chat GPT from what I understand, the retention is fairly low. Like people use it, they play with it and then they don't get back to it because it's not in their workflow and they have a hard time figuring out what they can and can't do for it. When I got to Gleeve, the first week I met with the assistant quality team and one of the biggest issues they have is people you're trying to use Gleeve for things that there's like no way it could know. Like what should my top priority be next week when like we don't even know what your priorities are and but then there's golden cases that are just amazing.

1:04:42So we're not the example of refining queries and search to years for people to understand how to do. And I took a lot of features of like auto -complete and refinements at the bottom of the page. So we need to build in those things to guardrails to help with the change to help suggest, oh Lenny, here's what you could do. Here's a here's a prompt to find out the status of your feature that tomorrow built. So how do you give people guardrails so that they understand what is going to work and what isn't going to work? Because this whole, I don't know what I can ask. And then on top of that, the time is terministic.

1:05:23Like an enterprise CIO will go use chat GPT on the weekends, but they come to work and they expect their software to be deterministic. So how do how do you help educate users about that? And then the other thing I'll say about using LLMs is the industry is transforming so rapidly. You need to make sure that your product gets better as the LLMs get better. And that too many people are building things to make up and compensate for the LLMs that all that work is gonna go away. So it's okay to do it to understand that it's gonna go away, but that can't be your differentiator. You have to understand that your differentiator is something that will continue to be there as the LLMs get better and smarter.

1:06:11And as part of that, because the LLMs get so much smarter, everyone else will become awesome. And to keep up, you need something that is actually outside of the LLM that continues to differentiate you and is better than what other people are doing. Well, yeah, that your whole product gets better as the LLMs get better. Yeah, and that I think is it's a it's a frame of a frame of mind of How you approach the value add you're having Awesome Tomorrow to close out our conversations. Is there anything else that we did not cover that you think is important to share or you think might be helpful to leave listeners with Before we get to our very exciting lightning round I in my decades of working tech have never been working in environment that's moving so quickly like, and it's really exciting.

1:07:00I mean, it's super energizing, and it's also scary. But you have to change how you're working. You have to change how you're working so that you can keep up, because it is going to be, it's going to be an interesting decade ahead with all these new tools that are coming out, and staying ahead will be hard, but it's also, there's so much, I think, richness and opportunity here. So I advise people to get in the thick of it and try it out, because you'll be surprised at how much, how many products we can build. I love that. I can't help but drill in one level. Deeper, is there anything you found to help you stay ahead and help you stay aware of what's happening?

1:07:46Are there like newsletters you find useful chat podcasts that just like help you keep up the data and where things are going? Is it like a person you look to like, hey, what's new? There are definitely like, hey, I newsletters that I look at. There's AI podcasts that I listen to. I now have a commute. So in some ways, that's good because I get to keep up on the AI podcast. So I just try and listen. I'm trying to build some prompts for myself to make it easier to say, like, take in to, I haven't perfected this, but the chat GPT voice mode where you can and loaded somebody who just, I just hired a Gleam with saying he does this.

1:08:23He loads up stuff before his commute and then hopefully like summarize these articles and then he can ask questions to it. So I need to up my game there but I definitely have a list of like Ben Spites and Minoran and I love, I like those are good summaries and like I like Gleensera goes podcast I listen to cognitive revolution. There's kind of too many of them right now, but I pick and choose. Also, okay, we'll link to those ones you just mentioned in the show notes. The log, Gill and Sarah Goes podcast is called No Priors. I was actually just listening to it on the way here. Sarah is going to also be at Lenny's in -friends summit.

1:09:02She's going to be moderating a panel between Kevin Whale and Mikey Krieger, who are the CPO's of Anthropic and Open Eye. So there we go, another quick plug for Lenny in -friends summit .com. I think it's Lenny's summit .com. Awesome. With that tomorrow, we've reached our very exciting lightning round. Are you ready? I am ready. Okay. Let's do this. First question. What are two or three books that you have recommended most to other people? So one book was recommended to me by Shishir the CEO, Koda. When I started at Slack, he recommended the book Switch, how to change things when change is hard by chip and Dan.

1:09:41and he's and it's such a good book. And it's about like how do you set a path for people to follow the whole elephant and the rider, so setting the path, but yet motivating people to go down the path. And I read it and we had an all hands about, like there was, I don't even remember the topic. It was something that we were like all up in arms about that we had to do. And I just read the book and after though all hands, I went up to the store and I'm like, like you did that all wrong. Like you need to read this book. That is not how they get people motivated. And he read the book and he's like, you're right.

1:10:19So it just changes how you think in organizations to affect change. So that's on the kind of organizational leadership. And one book I really like was Team of Rivals. It's a book about Lincoln and putting together his cabinet and during the Civil War, one I just learned a lot about the Civil War that I didn't really know. And it's about, again, a book about leadership and it's fascinating. Don't think anyone's recommended either of these so. Love them. Next question, do you have a favorite recent movie or TV show you've really enjoyed? I don't know if you like British murder mysteries. I don't know either.

1:11:04It's kind of a niche thing, but there's a guy named Anthony Horowitz and the latest series he did was called Magpie Murders and it's just like kind of an intricate story, so I joined it. Very niche, but amazing. Do you have a favorite product you've recently discovered that you really like? Well, I'm going to give two. One is tech and one is non -tech. So non -tech, I really like dark chocolate. I actually just like a dark chocolate bar. A really good dark chocolate that's simple. Like no frills none of this just dark chocolate. And I discovered this chocolate called the zoo chocolate. And it's a guy in Oakland who makes it himself super niche.

1:11:53He was selling at the farmers market. And it's just like if you were like a simple, like no, not, no anything just in. Not too sold. great pride in the beings and resources in front. Wow, it's called BeZoo with a B. Yeah, BeZoo as in Kiss and French. And then on the tech side, I mean that honest answer is gleaned, is I was listening to your podcast with Nikita who said that people over 22 don't use new products except at work and that like stuck with me. The products, the new products I usually use are at work. And I use them 10, 15 times a day. Like I use it so much and it changed the way I unborted, it changed the way I work.

1:12:41I like, I just, even like the simplest questions, you don't bother people, you don't, you don't interrupt people on Slack. You're like, you know, what's the latest status with this deal? What's the last time we talk to them? I need somebody at a conference and I can quickly say, have we ever talked to this company before? and I can just get an answer and or without asking an engineer, where's the latest design doc? It's just, it has really transformed how I work. So I know it's cheating and that it's the product I work on, but it's the actual honesty answer. And for folks that haven't heard it glean, it's one of the most successful B2B AI companies out there, right?

1:13:18It's like a very large successful business and company that if you haven't checked it out, you should definitely check it out. As our investors say, it's one of the ad companies that's actually making money. Very few of those. Awesome. Two more questions. Do you have a favorite life motto that you often come back to? Repeat yourself share with friends or family and worker in life? I have one that my father told me when I was being really indecisive about what college to go to. He was really kind of bored of the conversation and he said there are no right decisions. you make a decision right and it is so true because you never know what's going to happen in life.

1:14:00You just have to commit to whatever you're doing and have no regrets about it. You can't be like, oh, you know, 10 years later, what if I had taken that job over there? It's like you make you make your success based on how you approach the decisions that you've made. But so it's if you feel regret about something this is a good one to pull out of just I will make this the best I can make it and that's all the best I can do. You can move forward and move forward and love that. Last question. I know your parent, I'm a new parent, I have a 14 month old at this point. Is there a piece of parenting advice that you learned early on that you think might be helpful to me or folks that are new parents or something you've just learned yourself that you think might be helpful.

1:14:46Fourteen months, I think the best parenting book I read, besides the How to Talks to Your Kaila Listen, How to Listen to Your Kaila Talk, is I think it's called Healthy Sleep Habits, Happy Baby. Like, we are much happier when we sleep well. We perform better at work when we sleep well. Children need to sleep. So making sure that they sleep well, and sometimes that's like, I did the whole sleep training like cry until he falls asleep and my kids still speak to me so it was okay. And so you just like that is like the basic things like make sure that their basic needs are met and then as they grow up share your life with them.

1:15:33So a piece of advice I was given was kind of analogous to talk so your kids listen is when they come home from school you can't just say How was your day? Say, you know what? I did a podcast with this person and it was super interesting because they talked about this or that or I'm massively screwed up and I should have asked them this or that. And they'll be like, Oh my God, I was its full today and this is what happened. Like if you share your life with them, they will share their life with you. That's such good advice. I really appreciate it. Tomorrow, thank you so much for being here. You're awesome.

1:16:07We got through so much great stuff. Everything else happened when we get through two final questions. Working folks find you if they want to read up on more stuff that you share and just follow you online. And how can listeners be useful to you? I find me on LinkedIn and I have a subschat called practical intelligence where I've been interviewing practitioners who are working with AI. It was my way of learning. I started it when I was a VC trying to continue doing it. And how can they be helpful if you're a customer of Lean? I'd love to know what you think, what works and what doesn't work. What's the best way to share that with you is it like messaging on LinkedIn, subscribe, subscribe.

1:16:45Message on LinkedIn or comment on your, on your own. Yeah, those probably be the two ways. Awesome. Tomorrow, thank you so much for being here. Thank you for having me. 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 a leaving review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at Lenny'sPodcast .com. See you in the next episode!

From the publisher

Tamar Yehoshua is the president of product and technology at Glean. Prior to joining Glean, Tamar was chief product officer at Slack, where she led product, design, and research as the company scaled, including a 10x increase in revenue, its public listing, and an acquisition by Salesforce. She also led product and engineering teams at Google, working on search, identity, and privacy, and at A9.com, an Amazon company. Tamar has served on the board of directors for RetailMeNot, ServiceNow, Snyk, and Yext. In our conversation, we discuss:

• Why you don’t need to be a well-run company to win

• The impact of AI on product management and the future of work

• How to build strong cross-functional relationships, especially with engineers

• Lessons learned from working with leaders like Jeff Bezos and Stewart Butterfield

• Strategies for staying ahead in a rapidly evolving tech landscape

• Much more

—

Brought to you by:

• Explo—Embed customer-facing analytics in your product

• Sprig⁠⁠—Build products for people, not data points

• Sidebar—Accelerate your career by surrounding yourself with extraordinary peers

—

Find the transcript and show notes at: https://www.lennysnewsletter.com/p/you-dont-need-to-be-a-well-run-company-to-win-tamar-yehoshua

—

Where to find Tamar Yehoshua:

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

• LinkedIn: https://www.linkedin.com/in/tamar-yehoshua-886217/

• Newsletter: https://tamaryehoshua.substack.com/

—

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) Tamar’s background

(02:09) Key advice for career success

(06:54) Understanding people and motivations

(09:33) The importance of impact

(11:20) Navigating company chaos

(18:40) Career planning: a different perspective

(26:22) Lessons from industry leaders

(37:59) Building stronger cross-functional relationships

(42:00) Streamlining OKR reviews with async methods

(45:26) Why you shouldn’t worry so much about making users unhappy

(47:50) The power of listening in leadership

(52:34) How to leverage AI so you don’t fall behind

(01:06:39) Closing thoughts and lightning round

—

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
Lessons in product leadership and AI strategy from Glean, Google, Amazon, and SlackLenny's Podcast: Product | Career | Growth · 1 h 17 min
Listen in VO