Airbnb’s Vlad Loktev on embracing chaos, inquiry over advocacy, poking the bear, and “impact, impact, impact” (Partner at Index Ventures, Airbnb GM/VP Product)
1 Sept 2024 · 97 min
This is a podcast episode titled "Airbnb’s Vlad Loktev on embracing chaos, inquiry over advocacy, poking the bear, and 'impact, impact, impact'" recorded in September 2024. It features a conversation between Lenny Rachitsky and Vlad Loktev, a former Airbnb GM and VP of Product who is now a partner at Index Ventures. The discussion covers Vlad's leadership philosophy, skills for success in product management and scaling organizations, the importance of impact-driven work, inquiry before advocacy, and strategies for managing teams and priorities during hypergrowth. The episode provides tactical insights and personal anecdotes from Vlad's experience at Airbnb and beyond.
What was it like managing me, Vlad? Most importantly, how painful was it to manage me?
Man, how much time do you have?
I used to joke with people that you're kind of this Jedi where you get crazy stuff done, really hard stuff done in a really subtle and a really unique way.
I've always used inquiry versus advocacy. A lot of people approach a conversation with a point of view and they begin advocating immediately, we should do this or no, we should not do this, right? Me, I always take the opposite approach. I inquire first. I. I'm going to ask a ton of questions because I fundamentally believe maybe there's something I don't know and there's information that I need to understand to make a better decision.
Is there something you can share about just what you learned from Brian about thinking big?
I remember talking to Brian one day and he was like, something just feels off right now. And I remember asking him, like, what do you mean our numbers are up and to the right? His response was, things are just too calm. Sometimes you want to create chaos in an organization, to push the organization to think creatively and to actually, like, make leaps in product development. And I've always told told myself, don't be afraid to poke the bear.
What are some skills that you believe helped you be as successful as you've been?
Impact, impact, impact, impact. That's the only thing that mattered.
Today my guest is Vlad Lokt. This is a very special episode for me because Vlad was my manager at Airbnb for many years and he's the person that I credit most for teaching me how to be an effective product manager and product leader within Airbnb. Vlad started as an icpm. Five years later was leading product for the core Airbnb business, the Homes business. A few years later was GM of the core Homes business, reporting directly to Brian Chesky, managing over a thousand people, including design, engineering and other functions. He's also one of Brian's most trusted partners for most of his time at Airbnb. Before Airbnb, Vlad was a founder. He's also a senior PM at Zynga, where he grew the game Words with friends to over 14 million daily active users. Even though Vlad recently moved into venture capital as a partner at Index Ventures, he will always be a product manager at heart to me and I'm very excited for more people to get to learn from Vlad. In our conversation, Vlad shares the skills and behaviors and mindsets that most contributed to his success, including a ton of really tactical stuff. Also the strategies and tactics that he's found Most helpful in building and scaling a fast growing org. And his thoughts on Airbnb's current ways of working, including their move away from traditional product management and also their approach of thinking very top down, which I thought was really insightful and so much more. This podcast, I guarantee will make you a more effective product leader and I am very excited to share it with you. If you enjoy this podcast, don't forget to subscribe. Subscribe and followed in your favorite podcasting app or YouTube. It's the best way to avoid missing future episodes and helps the podcast tremendously. With that, I bring you Vlad Lokt. Vlad, thank you so much for being here and welcome to the podcast.
Thank you. Excited to be here.
I think this is going to be an extremely special episode. People will have heard in the intro that we've worked together for many years. And even more interestingly, you managed me for many years at Airbnb. I've also told you this before, but those years were probably not, probably, definitely the most transformative years of my career where I learned the most and the years that set me up for the success I ended up having later and also the crazy work that I do now. So let me just say I'm just really excited for other people to get a chance to learn from you and to learn from the things that you've learned that helped you be successful and help me be successful. So thanks again for making time for this.
Yeah, of course. Excited to be here. I mean, you were always a rock star, so you're a rock star back then. You're a rock star today. So excited, excited to chat.
I appreciate it. I don't know if I was a rock star at the beginning. This is where my first question was going to go is what was it like managing me? Vlad, you're most importantly, how painful was it to manage me, man?
How much time do you have? No jokes aside, I. I've loved working with you, man. And I, I have to say, the one thing that I always deeply appreciated was that no matter how hard things were, you like, always called out the elephant in the room. And so you always told me the stuff I did not want to hear. And you know, large companies, things are growing. Lots of things are happening. As a leader, you miss so many things and so hearing actually what's happening and the reality of, of what you're, what you're dealing with, it was just so, so helpful. So I deeply appreciated that about you.
Wow. I think we're just going to be a love fest, but I feel like I was able to do that because I knew you'd react well and you needed to hear those things. This episode is brought to you by Pendo, the only all in one product experience platform for any type of application. Tired of bouncing around multiple tools to uncover what's really happening inside your product? With all the tools you need in one simple to use platform, Pendo makes it easy to add, answer critical questions about how users are engaging with your product and then turn those insights into action. All so you can get your users to do what you actually want them to do. First, Pendo is built around product analytics, seeing what your users are actually doing in your apps so that you can optimize their experience. Next, Pendo lets you deploy in app guides that lead users through the actions that matter most. Then Pendo integrates user feedback so that you can capture and analyze what people actually want and the new thing in session replays a very cool way to visualize user sessions. I am not surprised at all that over 10,000 companies use it today. Visit Pendo IO Lenny to create your free Pendo account today and start building better experiences across every corner of your product. P.S. you want to take your product led know how a step further, Check out Pendo's lineup of free certification courses led by top product experts and designed to help you grow and advance in your career. Learn more and experience the power of the Pendo platform today at Pendo IO Lenny Pendo this episode is brought to you by Vanta. When it comes to ensuring your company has top notch security practices, things get complicated fast. Now you can assess risk, secure the trust of your customers and and Automate compliance for SoC2, ISO 27001, HIPAA and more with a single platform, Vanta. Vanta's market leading trust management platform helps you continuously monitor compliance alongside reporting and tracking risk. Plus you can save hours by completing security questionnaires with Vanta AI. Join thousands of global companies that use Vanta to automate evidence collection, unify risk management and streamline security reviews. Get $1,000 off Vanta when you go to Vanta.comLenny that's V A N T A.comLenny what I want to start talking about is talking through and spending time on some of the skills that you developed and some of the skills that you're essentially world class at in my experience that I think might be helpful to a lot of other people. I used to joke with people that you're kind of this Jedi. They have like Jedi powers where you just get crazy stuff done, really hard stuff done in a really subtle and a really unique way that I haven't seen other people work. And to show kind of the impact that has had your growth trajectory at Airbnb is pretty absurd. When you joined, I think you were kind of. We were kind of the same level, maybe. Maybe you're a level above, and you're an ICPM at Airbnb. And then five years later, you're head of product, basically, for the home's business, which is the core Airbnb business. And then a few years later, you're GM for the entire Airbnb homes business, managing a thousand people, designers, engineers, research, marketing, and all these functions. So I want to spend a little time on some of the things that helped you get to that point. Let me just start with just a broad question.
Yeah.
What are some skills that you believe helped you be as successful as you've been? And they could be skills, maybe behaviors, maybe mindsets that helped you be successful.
Well, first, thank you for that introduction. I'm a work in progress, so there are many things that I. I am constantly working on. I think for me, like, when I reflect on my journey at Airbnb, it was more about the mindset rather than any kind of, like, skill. So, for example, my main mindset was impact above everything else. So, like, impact, impact, impact, impact. And that's the only thing that mattered, like, basically my entire career. And so I woke up every day and I asked myself two questions, basically. Number one, what are the highest priorities for Airbnb today and over the next, like, three months? And then two, what can I do to actually make a meaningful dent in those priorities? Like, what impact can I have? And I always made sure that whatever I worked on was very aligned with a top priority for the company. And I would say, if you're. If you find yourself in a situation where you're not working on the top priority of the company, like, you should probably get a different job because it's. At the end of the day, you're spending so much of yourself and so much time at your job, you might as well really go for it and work on the hardest thing you can find, and somebody's, like, willing to give you a shot and, you know, to build something crazy. And so for me, like, I always thought about what is the hardest thing that I can work on and how can I drive the biggest amount of impact. Now, oftentimes it's, you know, figuring out the priorities is relatively easy for, and there's typically clarity around what you have to focus on, whether it's expanding a team and really, like, building out a specific team. Whether it's growth rate or focusing on the product quality or like, closing deals and closing sales, you can typically figure out what the priorities are. It's oftentimes very hard to figure out how to make impact and, like, what impact even means. And so for me, like, my motto there was always just learn the drivers of the business. So put like, your day job to the side for a second and just immerse yourself in understanding why certain behaviors exist on the product that you're working on. Right. Can you influence that behavior? Like, what if you do X, what will happen? Essentially? And I spent a lot of time actually blocking off, like on my calendar, just time thinking through the drivers with the question of what are the drivers are gonna have the most impact for the business. And I remember, like, when we worked on Instant Book together, I think this was like, back in probably like 2014. That was not a random project. There was so much thought behind why we should focus on Instant Book. And what was the core problem with Airbnb at that moment in time and what impact we thought we could have on the overall trajectory of the company. So that was impact, impact, impact. Always just my.
My motto, I guess, let's actually spend more time here. Cause this is such, like, not only have I seen you do this well, I've also seen the. The impact this mindset has had. And I think people listening to this might be like, yeah, okay, impact. Great work on impacting, But I think there's so much power to this that it's worth spending a little more time on.
Yeah, let's do it.
What do people do that's not this? Like, I imagine many people listening are like, oh, I work on things that are impactful. I'm doing great. What is it that you see that's not this?
I think when a company matures, I think there is, you know, it grows. Many more people join the team, the company gets bigger. At some point, a lot of people are working on similar things. You then teams start to form, then the entire department start to form. And pretty quickly, I think a lot of people begin to realize that you're like, you're. You yourself are not in control of many things, and you actually depend on what other people do. Right? And so a lot of people, and I've done this too, have focused a lot of energy day to day on the dependencies rather than the things that you yourself can do in. In your day to day. So, for example, what I've Seen as an organization scale is people transition from saying, I can do X, and they transition to saying, can the other team do Y so that I can do X. And I think that's a very dangerous place to be because at the end of the day, like, you just need to let go of some of these dependencies. Like, you're not going to move mountains every single day, and you got to focus on the things that. That that are actually within your control. So, again, it's more of a mindset shift. The other thing I would say is every single project that we worked on, an Airbnb, we did back of the envelope math with assumptions to help us understand the impact that something would have. And you needed to. At least now those assumptions could be completely crazy and could be very challenging, but you at least needed to think through the mechanics of what you have to believe in order for this project to be a success and for it to then make a big dent in whatever you're trying to achieve at the company. So every single thing we did had that behind the scenes, and we spent a lot of time on this to make sure that we were focused on the right things.
I remember there was a project we were going to work on. I'm like, I think this is a big opportunity. Here's all my thinking on it. And what I didn't have is here's the lift this could potentially drive.
Yeah.
And so what you did is you just created this flowchart of all the levers of the business, and then like, okay, you're talking about this sub lever here, and if you move this 10%, here's the impact on the potential business. And you're right, it is actually a big opportunity. But this is how you want to show it.
Yeah, totally. The other thing I'll say is also equally important, is saying no to a lot of things. And it's actually really hard because, you know, we are basically trained and conditioned to say yes. Right. Like, you go to school, you follow the rules. Like, you listen to your parents, you don't want to disappoint people. And so when people ask for help, you help. Right. And you want to be a really good teammate, but then at some point, you realize that's actually not the job. And if you were to say yes to absolutely everything that you have to do at a company, you would be distracted all the time with, like, tons of things that will not make impact. Right. And so I learned very early on how to say no, and it was hard emotionally. Like, I've gone to Many different debates and conversations. But ultimately, I think maybe it doesn't win you many friends in the short term, but in the long term, people realize that when you say no to something, there's probably a really good reason behind why that thing may not be as impactful today. And maybe we shouldn't even do it in the first place. And so I think doing the back of the envelope math and being really good at prioritization is one thing, but also not getting distracted with all the noise and all the different opinions that everyone's going to have at a big company is another big thing.
So saying no is hard. So maybe two quick questions here. One is, do you have any tricks for how to say no? Well, where someone's not like, yes, pissed off. And then the other question I'll just throw in, you could take them however you want, is what's your heuristic? And how much people should like you as a PM because you touched on, like, people don't need to necessarily love.
You for saying no first. You can't just be dogmatic and just say no for the sake of saying no and just disagreeing with people. You have to listen. So for me, the framework that I've always used was inquiry versus advocacy. And I, I don't know if you remember, we've talked about it in, in some context where basically a lot of people approach a conversation with a point of view and they begin advocating immediately, meaning we should do this or no, we should not do this. Right? Me, I always took the opposite approach, and I still do. I inquire first, I dial up inquiry. I tone down my advocacy, meaning I'm gonna respect the other opinion. I'm gonna ask a ton of questions because I fundamentally believe maybe there's something I don't know and there's information that I need to understand to make a better decision. So in the beginning, dial up inquiry. And then once you, the person who you're talking to feels heard and you actually have absorbed information and maybe you changed your mind. Maybe not, though. That's when you begin to advocate. So oftentimes you just come into these conversations where everyone just advocates, advocate, advocate, advocate, and you're talking past each other. You're not even, like, reflecting on what the other person is saying. And so that's been my. Sometimes when I talk too much, I tell myself, wait, inquire, dial down advocacy. Just take a breath, take a moment, take a beat, and actually ask some questions and see why the other person feels so strongly.
I think that's such a Good specific thing you can do. Because a lot of, I think a lot of people want to do what you're doing. They're like, okay, I'm going to listen, I'm going to ask questions. But then they get a reaction. Someone's like, hey, we need to change this thing on the landing page. And you're like, no, that's terrible idea. Or that's gonna take all this time, it's gonna throw off a roadmap. And there's like this bodily like, oh no, I need to stop this thingy sep. And so your, your advice here is like, pay attention to Am I talking too long? Is that, I guess, is that the advice? Am I talking too long? Am I saying too much? And like start just inquiring instead.
Yeah, awesome, totally. And lead with questions like basically approach every conversation with curiosity. Like try, like, don't come in. Cause people usually like when they prepare for a meeting. I've seen many PMs do this and you prepare with like, here's my view and here are the bullets that support my view. And that's the wrong way to approach it. I think what you want to go into a conversation are you start the conversation with questions, prepare the questions that come from a place of curiosity, of the things that you want to know more about and you want to learn from the other perspective and then check yourself to see if you still want to advocate for the same point of view or not.
We had an awesome episode with Ami Vorish, CPO at fair, and she is also extremely good at this and a huge advocate of, of starting with questions and understanding what she's missing.
Totally. Well, the other, the other thing I would say is the other motto that has really helped me drive impact. And I used the analogy of the bear and I've always told myself, don't be afraid to poke the bear. And what that means is don't self censor. If you have a strong view after you've really grounded yourself in the truth and you feel like you've done your homework and you've asked all the questions, if you still disagree, if you still feel like we're going in the wrong direction, don't be afraid to poke the bear no matter how hard things get. And that's a, it's interesting because I think a lot of, especially as an organization matures, you find yourself in meetings with, with many execs, founders, et cetera, it's often hard to voice your, your real opinion. And you usually like tone it down a little bit. Right. Because you're afraid of being the only one who disagrees or sounding stupid or things like that. And so I remember it was probably like, 2014 or 2013 where I made a promise to myself, I'm going to always poke the bear no matter how hard things get. Because at the end of the day, like, what's the worst thing that's going to happen? Like, did I get fired? Like, why would I even be afraid of that? But if I do, like, I'll find another king. You know, life is short. And so you've done this really well where I feel like you've also always. I remember when we were working with Insta Book, you've definitely poked the bear where you were like, you guys are wrong. Like, this is how we have to approach it. And I've always really appreciated.
Thanks, man. Is there an example of maybe working with Brian where you poked Brian and like, no.
Yeah, absolutely. I mean, I've poked the bear many times, and by the way, I've been humbled many times. It's not like I poked the bear and I, like, rightfully poked the bear. Sometimes I learn stuff and I realize I was wrong. A couple examples that come to mind. Like, one, I remember having these debates with all, like, basically senior leaders at Airbnb just about every couple years, actually, around how much supply should we have on the platform and what kind of supply should be on the platform. And there was one school of thought where we needed. Basically, that school of thought represented the view that we needed all supply out there to be on our platform, regardless of if it was a. A person hosting, it was a vacation rental, it was a hotel. We just needed all supply on the platform. Right. I came at it from a very different perspective where I felt like that wasn't actually our mission from the very beginning. And although I understood that in the short term, the numbers, like, probably would go up and you would get out and you would choose growth. But at the same time, like, that wouldn't in the long run be a point of differentiation for us. Right. And so I had a very different point of view, and it was very hard in that conversation. You know, everyone's excited. Everyone seems to be aligning around the point of view to be the voice that's, like, poking. And this is like, nope, let me. Let me share why I think maybe we should go in a different direction. And it's when I remember, like, telling myself that I am here to surface and share information that will help the group make a decision. That's what gave me peace of mind. To actually like poke the bear and be able to surface the things, the things that I've seen. I mean, the other thing is when we were working on the instant book, change from request to book to instant book. Right. For the entire marketplace, that was very challenging. And I remember getting up on stage in front of the entire company and explaining why, like, this is actually good for humanity. Like, literally those words. Many people disagreed and it was not an easy. It was not an easy thing to do, but had to be done.
And one thread that I've noticed across all these things that. And noticed working with you is it's not like just making a case for something you could disagree with. It's showing the data that will convince them they are wrong or here's what they're missing.
It's.
It's not like a. It's not like a speech. It's a, here's the data. And asking them what data would you want to see to convince you this might be not as you.
Totally, totally. I think I remember like doing a Q and A with the whole company on, on the instant book topic. I. This was a very long time ago, but I still remember where instead of again advocating for a point of view, I just asked the people that were concerned, like, what their main questions were. And then we just tackled them one by one and we would talk. And it's. There's just something very disarming when you embrace the questions, you embrace the negativity and you have an open mind that maybe there are some things that you missed and some things that you didn't consider.
I love that. Okay. There's so many little nuggets already through this that I just want to come back to and make sure people take away of how to be more successful as. And this is not just as a product leader, this just as a leader in any company. So the first is advice around thinking about impact above all else. And the very simple heuristic that I wrote down as you're talking is ask yourself, what are the priorities for the company? How can I impact these priorities? And to do that, think about the levers that drive the business and where do I think I can make an impact to drive these priorities and drive the business? Two is inquiry first. When you're trying, when you disagree with something or when you want to say no, start with understanding, asking questions, dialing up, inquiry versus advocacy versus like, here's what I think, poking the bear, which is really fun. Just like this idea of don't be afraid to disagree with someone in Power. And your advice here is disagree with here's data you may not be aware of here. Have you seen this? Hey, check this out. Or what is it that would convince you you're wrong?
Yeah.
And then is there anything else I missed? Otherwise we'll go on to more.
I think that's great. I mean don't poke the bear for. For the sake of poking. Share. Share the information that you think will be helpful to make a decision.
Cool. Anything else? Any other things you've found to be really effective in helping you succeed?
Oftentimes it's about also like being able to be impactful at a company that is in hyperscale and is growing quickly. A lot of it is actually just psychological. So it's not like there are these like core skills that sure, like you gotta have some baseline skills, right. But a lot of it is day to day regulating your mind. And it's so easy to get lost in the sea of projects, the sea of priorities, the sea of opinions and like I said before, dwell on the dependencies, right. That exist between teams without actually asking yourself like what you can do in the moment to. To make. To make an impact. And for me like I've actually used two tools which some of them you may remember that have helped me. The first tool to re. This is again purely psychological to help my mind. It's the serenity prayer. So I. So, so the serenity prayer goes something like this. Grant me the serenity to accept the things that I cannot change, the courage to change the things that I can, and the wisdom to know the difference. So I actually that prayer was so powerful for me that I actually wrote it out on a piece of paper and like on post it notes and I would read that thing like every other day and it would help me just take a step back from the day to day and, and just like put into context what's actually important and again what is in my control today and the things that I can actually do. Um, so that highly recommend did not know that the other one which you may remember is the shit bucket.
I do remember that.
So the shit bucket was a visual analogy where I would take a piece of paper and some of it actually wasn't as visual. It was like real. I would take a piece of paper, I would write down something that wasn't going well, perhaps a dependency, perhaps a project, perhaps a meeting that I was going to have that I knew I was going to be frustrated or maybe like we didn't even decide to go the way that I deeply felt passionate about. Right. I would write it down, I would crumble the piece of paper and I would throw it in my, like, shit bucket, basically. And the rule was once I threw something in the should bucket, I couldn't take anything out of the bucket. So I would not dwell on the things that I just needed to let go of, you know? So this was a very powerful tool that, like, I'm a perfectionist. Like, I just deeply care about many different things, and I. I have a hard time letting go. And so for me, it was just a reminder that I need to let some things go and focus on the things that matter. And I actually remember even going into one of the ones with my direct, where I would sometimes lead. Like, I could tell, you know, the PM is. Is, like, a bit frustrated about how things are going, and one of my first questions would be, what are we throwing in the shit bucket today? You know, it's. It's actually like, a very liberating thing that you can do.
And did you have, like, a special trash can that was your shit bucket, or is it the regular trash can?
Every media group always had a trash can. I would always, like, throw stuff into the trash can whenever I got, like, upset about something.
It's like a different dimension. Trash can of.
Yeah.
Is there something you remember throwing in the chit bucket that would be an interesting example or story to share?
I remember there was one person who I deeply wanted to hire who I felt was just phenomenal and would be such an amazing addition to the team. And I just. I tried and tried and tried for a very long time, and I just failed. I just could not get that person to join. And at some point, it became, like, counterproductive, and I had to, like, let go. And literally just, like, wrote, like, okay, getting this person into the company. I'm like, this is not gonna happen. I gotta move on at this point. Just threw it in.
I love these two pieces of advice, and it touches on how mentally challenging it is to be a leader at a hypergrowth company.
Yeah.
Is there anything you can share there about just, like, that part of the world? Like, people see your career like, holy shit, look at him. He's running Airbnb's business. What an amazing life. It's. There's a lot of pain behind it. Is there anything there that would be useful to people? You think?
There's a lot there. You know, it's not like it was smooth sailing for me every single year. Like, I had plenty of challenges just personally, like, going through that journey, like, you're not.
You.
You take a job and then you're sometimes just not prepared where it's going to take you. And the reality is, every three to six months, my job changed. So I would just get comfortable in the role I was in. Let's say, like, in the very early days, I was literally an icy growth PM with a tiny team, got pretty comfortable. And then like a year later, everything changed. And I was suddenly, like, leading a team of 20. Then a few years later, things changed again. I was leading a team of a couple hundred. Then a few years later, again, everything changed. And you just. Everything that you take comfort in in your current role breaks. The process breaks. How you hire breaks, how you spend your time breaks, the projects you work on, everything breaks. And you gotta reinvent yourself. And that is very hard to do. So one thing that I've learned is, like, you gotta ask for help. Like, you can't. It takes a village, right? You can't just get there by yourself. And that's actually something that Brian taught me where. I mean, this guy just grew. Every six months, it was like a different person. And a lot of his, like, secret sauce is not being afraid to ask people for help who are experts in the thing that you're trying to learn. I mean, my motto is, like, ask for the impossible. And sometimes you're gonna be surprised. Like, there are people out there that are experts on something who actually wanna help you.
So that's awesome advice. Also, the serenity prayer. So powerful. I did not know that about you. I want to spend time talking about things you've learned about scaling Airbnb in the. Org, but before we get to that, is there anything else that you think might be that you think contributed to your success as a. As a per. Individually, as a leader? Any other behaviors or mindsets?
I mean, I think it's building teams and realizing that sometimes when you build a team, and this is actually often misunderstood, I think when people build teams, they try to make sure every person on the team is good at just about everything. Like, you typically go through this process of, like, here are my strengths, here are my development areas. And typically the development areas are like, you basically develop. You try to develop just about every single thing so that you can be good at almost every single skill that exists. Right. And I just think that's the wrong mindset. Instead, what I've learned over time is instead of trying to find people that are good at everything, you need to look for people who spike on specific things and then add them to a Team with different spikes. So there's no single person that is like, spikes on absolutely everything. That's very rare. But they spike on something that's very crucial to the team. And if you assemble different spikes on a given team, that team is going to do great things as long as everybody inquires and everybody starts asking questions, actually listens to other people versus just, you know, coming about that. So even now, like, as an investor, when I look for. When I talk to founders, the first question, like, in my head is like, what is this founder spike on? And how is that spike relevant to the problem that they're tackling today? And how well does this founder hire to bring other spikes to the team? Like, that's literally like, what I think about these days.
What are some examples of spikes? Just to make it even more real, like, things that people might be good at is like strategy, influence. What are some things you commonly see that are spike skills?
Yeah, I mean, I think there's. The very natural spike sometimes is you get a domain expert. So there's a specific field. Let's take marketplaces. And there is someone who just understands the mechanics of how things work. And it's eight and. And just really spikes on understanding how you can take certain drivers, what you can do with those drivers, and how you translate those drivers to measurable results. There are people who spike on. On sales and who spike on, like, just being able to. To package something in a way that other people cannot package it. Right. There are people who spike in process. Like, there are people who will literally every day think about how to get people to work together really well. And that is like, they just know how to get to the essence of that, how to connect the dots between different teams working together. Some people are really great at product design. Like, there are. I've seen quite a few founders, actually, who can tell you immediately about what kind of interface is going to resonate with people and what kind won't and why, you know, so there's just some examples, but there are many dimensions here.
Awesome. Okay. As the last question along these lines, I'm gonna share a few other skills that I noticed you're incredibly good at. And how about I just pick one that resonates with you and share some thoughts on how to get better at that and why that's important. One is influence. You're an incredibly strong influencer. You get a lot of stuff done that I think people will be like, how did he do that? I have no idea what he just did. Uh, another is you're very good at keeping a very high bar. That's one of the things I learned from you is just the importance of keeping a very high bar and spending more time on stuff. That's something I remember from just like spend a little more time on this doc, make it a little bit better, refine it a little bit more. That's two. Another is just getting stuff done and focus while also avoiding the limelight. You're not like you try to not be in, in front and center. Like you haven't done any other podcasts. I don't think you've written a medium post. I don't know if you've tweeted. Like you try to just get stuff done behind the scenes and not, not be, not get attention from everyone. So maybe those are a few. Is there one of those you want to spend a little time on?
Yeah, I mean first of all, thank you for saying that. Some of those resonate for sure. I think the getting stuff done and being hyper focused on the job is it something that's really important. I mean at index here we also say keep the main thing the main thing. And just like in investing, same thing in operating, you know, you gotta focus on the actual job versus like all the other things that you could potentially be doing. So to me I remember when I was actually hiring product leaders and there's some product leaders would do lots of different engagements outside of the company, whether it's investing, advising, speaking, attending conference, all those things. And they were huge red flags to me because it was clear that this person there was just something missing in their day to day. They didn't try to put them like all of them into the thing that they were doing. And so for me like it's really important when I, when I hired people to hire people who were incredibly mission driven and would dedicate every ounce of energy to keeping the main thing. The main thing.
Yeah, the I talk about this on Twitter and LinkedIn. This idea that people see people like me and other PMs tweeting, sharing wisdom and they're like oh, these are the best PMs. They know so much. But in reality the best folks you as an example like spend zero time on Twitter or LinkedIn. They're just doing the job, trying to show great impact, trying to make a business successful, trying to build great products. And I think it's important to remember you don't need to be tweeting and writing medium articles.
Yeah, I mean I think there are, you know, people who find joy in, in solving hard problems. And like, the joy you get from working on the hard problem is fulfilling and you don't need to seek, like, external validation for. For the things you do every single day, you know? So, yeah, I loved hiring people like that.
Let me zoom out a little bit. So we've been talking a lot about the skills that you built and the mindset that you built to be successful individually, but also you managed large teams. You helped scale Airbnb massively through hypergrowth, and there's a few skills I noticed you're really good at that specifically apply to scaling an org, building an org, building teams, and things like that. And so I want to spend a little time there. You touched on this one a little bit. But I think there's more here around setting priorities. You're incredibly good at setting priorities, making sure everyone's aligned, making sure the main thing is the main thing. You just talk about what else you've seen be important here. As a leader of a larger growing org around setting priorities.
I have a lot of strong opinions here with. With setting priorities. I would say the first one is, and this was my motto for the longest time, and this still is, you gotta let fires burn. And what that means is you can do it all. Like, you just need to let go of things that are not important. Because if you have 20 different things that you're equally engaged on, it just means you don't actually know what is most important. And so my motto has always been, let fires burn. You gotta be okay with some things not going well so that you can dedicate most of your energy on, like, the few things that actually matter and the things that are most important. Um, and it's. It's hard to do. Um, it doesn't feel good. Again, many people, especially PMs, are perfectionists. And so it, like, it just. It. It hurts when things aren't going well and you just gotta learn how to let things go. Um, the. What I always did was I kicked off every Monday with a leadership meeting where we would talk about our priorities for the week. We would not talk about longer term priorities. It was literally like, for this week, what are we trying to get done? It could only be one to three things, and we would jointly agree on the fires that we would let burn. And so then when, like, my. My partner, my engineering counterpart, or my design counterpart would, like, see a fire burning, they would know, like, yep, we agreed that we're gonna keep letting the fire burn for now. And it was just really important to be aligned as a team on that now the other thing that I've learned is you gotta let other people burn fires too. And it's very. Actually empowering. And oftentimes I remember, especially when you're leading a very large organization, there could be teams and teams and many different leaders who you're working with. Oftentimes, people come to you and are basically like, we gotta do this new thing to drive goal one, and I just don't have enough resources. And I. We need to. We need to hire more people and we need to, like, expand the resources of this team. My first question always was, well, what. What are your actual priorities? And what can we let burn? Meaning, do you actually have to expand and do more things, or can we maybe reprioritize certain things and focus on fewer things and put a lot more energy behind it? You know? But to have those conversations, you, as a leader, you also have to recognize that people on your team are eventually in a really good position to gauge what fires should be burning and which are not to be burning. Now, the one thing I'll say, though, is with this, it could be dangerous. And there are some things that you should never let burn, because if you let them burn for too long, bad stuff's gonna happen, right? So I have a few of those examples for me that I have, like, over the years, learned to not let burn first. Timelines, major timelines. This is like huge product launches. Once timelines slip, you basically establish precedent that timelines are not as important. And timelines can always slip. So you never wanna set the precedent that timeline slip. So that to me, was when there was a major project on a timeline with significant slipping, I never let that fire burn immediately jump in. The second is when there is disagreement on a strategic decision or maybe even part of the vision. If you feel like that exists. Like, for example, if not everybody, like, buys into instant book or like, there's just some disagreement about what supply should be on the platform, you gotta squash that immediately. You cannot let that fire burn because it can spread. I guess if I follow the analogy, like, it could become a wildfire. And then suddenly you have a team of people who are. Who don't believe in what they're doing. They're losing meaning. They lose meaning in their work, right? Which is just really bad. So you have to bring people together immediately. When you feel like people, whether it's many or a few people, do not believe in the direction that the company's headed, you gotta squash that immediately. Then the third one for me, and this was a bit painful to learn, but you never let a senior hire process burn, meaning, like, you will always. And this is what I felt during my 10 years at Airbnb. I always felt underwater, and I always felt like we just needed to bring on more people who had experience in certain things that we were doing. And anytime I delayed or I was, like, not fully engaged with the hiring process, especially a very senior person, it just. It bit me for such a long time and it set the whole team back. And so those are the three things that I would never let burn. But you gotta let a whole bunch of other stuff burn, for sure.
Such counterintuitive and amazing advice. I. You shared a bunch of examples of things that you don't wanna let burn. Are there any examples you could share of things you let burn? Things that surprise people or a story that comes to mind of like, yeah, that's fine.
You know, sometimes you would have examples where certain products, product launches didn't go well, and let's say it just, you know, you weren't seeing in the numbers, the users weren't happy. Like, okay, that's. Sometimes you just need more time to understand what's actually wrong. You don't need to, like, jump on it immediately. Right. So that's maybe like one example of a fire that I let burn quite a bit. And quite frankly, at some point, I had so many teams that I was working with that I just needed to prioritize. Even between the teams where, like, this team is the number one priority. And I know that I need to be in design reviews with. With this other team. I just. I can't because I have to be thoughtful about how I'm spending my time in this given moment. And so I actually have to deprioritize projects. And so there are certain projects that were important, but I let burn for a while because I just had to spend my energy elsewhere, you know, and then of course, I would to myself. I was thinking, like, are we doing too many things? Like, is this the right way to operate?
I think this is really useful for someone that, say, is an ICPM on a team that's wondering why the hell our team is just wasting our time? We're building all this stuff. It's not working. Why? Why isn't anyone doing anything? Why aren't they giving some resources? Why aren't they repurchasing? It's because they know there's many other problems they're dealing with and they're letting this burn for now.
Yeah. And this was actually alerting for me in an area where I would say I failed over time is just general communication to the broader organization. You, when you rise really quickly, you tend to underappreciate or I did just how important it is to communicate what as a leader you're spending your time on and the areas that you, you think are the highest priority right now. And so eventually I started doing a lot of all hands and I started sending like the weekly thoughts from Vlad or just like my random musings on what's in my head. And I, I realized that sharing that context with people is just so important. People actually want to hear from you and it's good to over communicate and it can help people understand certain things about their day to day.
I know that didn't come naturally to you. I mentioned that you kind of like to be behind the scenes, under the radar, not in the limelight. So I could see why that wasn't something you were doing initially. Is there anything more you can share there about what you've learned, what you learned about why that's important? Like why are people, why, why spend time there? What happens if you don't?
Everybody wants to find meaning in their work and everybody typically wants to understand the reasons behind a decision. And it's important to share, to, to take. Like I, I've done this myself where I just like make a decision and you like move on and you go on to the next decision. And it's actually so, so helpful if you take like 10% more energy and time to now bring everyone along around why a certain thing was decided because it's gonna help them just themselves make better decisions because then now they have a lot more context about how this decision was made and they can learn from that moment. So that's partly why it's important. I mean for me, it didn't come naturally to me. I'm like a pretty, I don't know, I'm a deep introvert. Like I, I shy away from many different things and it like it had to be a learned thing.
I think you're also a really good example of something I talk about here and there is you can be really successful in very different ways. I'm also introverted. I think we're similar on the spectrum of colors or what things, personality tests. And you've been really successful. You could also be incredibly, incredibly successful as a very extroverted person or someone that's very analytical. And I think you're a great example of someone that's less, that's more reserved and doesn't want to and is introverted. As you said. And I think it's important for people to know you can be incredibly successful as a pm as a huge leader from that place. This episode is brought to you by Eppo. EPO is a next generation AB testing and feature management platform built by alums of Airbnb and Snowflake for modern growth teams. Companies like Twitch, Miro, ClickUp and DraftKings rely on Eppo to power their experiments. Experimentation is increasingly essential for driving growth and for understanding the performance of new features, and EPO helps you increase experimentation velocity while unlocking rigorous deep analysis in a way that no other commercial tool does. When I was at Airbnb, one of the things that I left most was our experimentation platform where I could set up experiments easily, troubleshoot issues and analyze performance all on my own. EPO does all that and more with advanced statistical methods that can help you shave weeks off experiment time. An accessible UI for diving deeper into performance and out of the box reporting that helps you avoid annoying prolonged analytics cycles. EPO also makes it easy for you to share experiment insights with your team, sparking new ideas for the A B testing flywheel. EPPO powers experimentation across every use case, including product growth, machine learning, monetization and email marketing. Check out eppo@geteppo.com Lenny and 10x your experiment velocity. That's get eppo.com Lenny okay, so just to summarize, the lesson we just talked about mostly is let fires burn. Basically don't feel like you need to solve every problem as you rise in the ranks. And I think this applies even if you're not the top of the org, even if you're manager of managers. Even if you're manager of nobody.
Yeah, maybe the other thing I'll mention and like, as I reflect on, on setting priorities and just like working and I, I think a big lesson for me is that chaos is good. Chaos is actually great. And sometimes you want to create chaos in an organization to push the organization to think creatively and to actually like make leaps in, in product development. And so I mean I, I kind of, you know, as I reflect on my life, I, I like cleaning up messes. I like when things are very organized. I liked when there's just like very, there's a lot of clarity on, on how things are put together, right? And it's very. Chaos is scary, right? And I think that this is very natural for a lot of people for chaos to be scary. But I've seen examples when just a bit of chaos is so, so helpful just to give you an example. I remember me talking to Brian one day, and he was like, hey, I just don't feel good. Like, something just feels off right now. And. And I remember asking him, like, what do you mean? Like, every. Like our numbers are up and to the right. Like, we're. We're chipping quickly. Everything's great. What do you mean? Like, what are you unhappy with? And his response was, things are just too calm. I don't like it. And I was like, okay, what do you mean? Like, calm is great, right? Like, I operate in calm. And he then picked a project that he thought was important. I think it was actually host onboarding at the time. And of course, in this project we had like three or four. I remember we had this, like, perfectly crafted timeline. We're gonna design this for the next four weeks, and then we're gonna start building and we're gonna deploy in certain pockets of users. We're gonna learn, we're gonna iterate, et cetera. Very, like, rational, like timeline, right? And he said, yeah, I don't care about any of that. We're gonna design this in 24 hours. And I was just like, mind blown, right? Like one how to the ripples that's gonna send through the organization. Cause I knew like, all the people that were involved on building this, and we had like, this whole, like, neat flow. And we did design it actually in 24 hours. Well, it was. It took a little bit longer, but we designed it very quickly. And what I learned in that moment is that the chaos that. That was actually an example of chaos that he inserted into, like, this very calm building process. And that chaos forced us with that artificial time constraint to dial up our intuition and to think a bit more creatively than maybe we would have in the past. Now, that didn't always work because there were examples of this where you were just like, I. I don't know what the answer is. Like, I need more time to design this and to think about this problem. Right? There were definitely examples of that, but there were many examples where it was actually a great forcing function to go with your gut and actually, like, innovate.
That's an amazing story. And it reminds me of something else. Just to take a quick tangent, here is Brian's incredible at just asking people always, okay, that's a great goal you have there. What would it take to 10x that goal? Yeah, he, like, gets to the FP and a projection. He's like, great, okay, how do we 10x this? And I found that to be really scary, but also really effective in helping people think a lot bigger. Is there something there you can share about just what you learned from Brian about thinking that big?
I think it's less about hitting the goal. I think a lot of people when they see really big goals they get. They immediately like afraid of, of the goals because they think oh my God, I don't know how to hit this. If we don't hit it, what happens? And you start thinking about all the downstream consequences. The reality is it's not about hitting the goal. It's about thinking how to hit the goal and going through the journey of that creative journey of like what does the world need to look like for this to be true? This like crazy goal to be true. Like how should we think about it? And oftentimes it pushes you to test extremes. Right. When the whole world is gonna operate this way or nobody in the world is gonna operate this way versus like something in the in between. And usually it's when you start testing the extremes that you begin to like realize like oh you know, the, the, the. This, this is the path that we should actually take.
Yeah, I, I found exactly the same thing. Just thinking from backwards from what is the best possible thing we could do versus incrementally forward ends up unlocking a lot of big ideas. Something I imagine is in people's minds as they hear some of this stuff like Designing something in 24 hours or thinking 10x bigger is like I don't want to work that way. That sounds incredibly stressful. That sounds like what, what? I. I don't wanna. Why do that sounds really hard. You mentioned this, that this isn't necessarily for everyone. Not everyone needs to work at this company or work this way. There's part of it is hiring is finding people that want to get lean in to work really hard. Other people don't. Is there anything there? Just like this is actually really hard and it's not for everyone. But it's also ends up being successful and you end up having a good time. A lot of times afterwards I find.
That those sprints were like designed this in 24 hours. Were brought a lot of connection to the team actually. And they were like my most fun moments actually because you kind of like you're forced to let go of a lot of constraints. All these like organizational dependencies disappear. All like the stuff that's kind of noise and you can just start building. Right. So for me especially when you're not doing this by yourself and you're doing this with a team of people, it was deeply Rewarding because you were all working together, just like shooting the. And like throwing a whole bunch of ideas out there. No idea was like too crazy right now. It's not for everybody. And so I actually, in the interview process when I would hire PMs, I was always, not always in the early days, I guess I. I had to learn this. But in the later days, I always set expectations about how we work. And so I think some leaders do this. It's like the anti cell cell where I will share the worst day or what I think you will think as a candidate, what the worst day would be at Airbnb and then still ask you if you want to join the team. And I would basically tell people, we're going to work day and night, we're going to work weekends. Direction is going to change the strategy, like out the window every three months. The projects you're working on today, we're going to kill three weeks later. The roadmap that you are right now auditing as you're deciding your offer when you actually join after you took some break from your other job, is going to completely change. And so getting people, I think, I think the, the common thread there is everything is changing all the time. You gotta be cool with that if you wanna join this team and totally fine. Like if that's not for you.
I love that. It makes me think of something when a colleague used to say at Irene Bees, if you haven't changed teams or your desk in six months, something's about to happen, something's about to change. Totally this UNSELL idea. There's a. A recent podcast episode where someone did something similar. He called it the UNSELL email where he sends the candidate. Here's all the things based on all the things he heard from the candidate during the interview process. Here's all the things you probably won't love about working here. And the recruiter was always really mad at him for, like, don't send that. My numbers are really going down because of this email. But long term, it ends up being really successful for them.
Yeah. I mean you're going to probably like hire fewer people that way, but you will hire the right people. So I think then you. You're going to actually have a team that you can rely on for years and years and years as things change.
Yeah. Just have to align incentives with recruiting on that piece of it. Okay. So one other area I wanted to spend time on is basically org design and hiring and people. So you were very good at building really effective teams, prioritizing them Bringing in amazing talent. What can you share about things you've learned about as a company is growing and org scaling, about org design, hiring.
Yeah. So for me like one of the hardest things about building teams and going through hypergrowth was the fact that you're gonna lose a lot of friends on that journey. Like you just have to be prepared to say goodbye to your friends. Meaning when you start, you build really deep relationships with people. Like when you're a smaller startup, right. Like you typically have one on one interaction and you know everybody. Right. And you have that connection with people. And the reality is most people, if the company is truly going through hypergrowth, most people are not going to scale. It is very rare for somebody to scale with a company. And I mean we actually so at index we wrote a book Scaling through Chaos and there was this crazy stat where basically when you look at many, many companies that reached a thousand people and were successful, when you look back to the first 10 employ, you realize that only two to three of those 10 first employees stayed with the company when the company reached a thousand people. Right. And that's just so like indicative of what will actually happen in practice. Like there are certain skills that you have that are good for in the specific domain for a period of time. And that time is not like universal forever.
Right?
Right. Like at some point everybody taps out. And so it's just having that realization is. It's tough. It's tough emotionally. It was like one of the hardest things for me, like as a leader. And I would say the way to break out of that is to ask for help and to try to learn as much as you can about what the next role for you is going to look like. So that's one thing that I've learned. I would say another thing is that all org charts suck. Like there is no good org chart. Every single org chart has problems. So you can be organized around business units, you can be functionally organized, you can be organized around problems. And the reality is like every single one of those constructs sucks. Right? There are pros and cons to each approach. Like if you are a, if you organize yourself into business units, the problem you typically run into is silos. When people start basically advocating for their business unit with little regard for other business units. Right. If you're functionally organized, sometimes you create too many dependencies across the organization and it becomes this like matrix way of working which could be challenging and as a result could be slower to ship product. Right. Those are just examples. These are not universal issues. But Those are examples where regardless of how you organize, there are gonna be problems. So for me, one learning was if you're having a problem and you're trying to solve this problem, reorganizing and like a new org chart is rarely the solution. Like it's not about the boxes and how you configure the boxes. Right. It's about the people in those boxes and it's about how those people work together. Because you, you just need to understand the cons of working a certain way. And then how do you design a process around your org structure to make sure that people connect and work really well together? So my advice there also to founders who I talk to now, focus a lot less energy on actual org design. Study the different types and just pick one. And once you pick one, focus on the people, the culture, and how people work together.
That's really interesting. So basically you think people are overthinking org design.
Yes.
How do you think about incentives and goals and how that kind of impacts all that stuff? Because there's people and then there's like, here's your goal, here's how you're measured and that's what they're going to work on in this, in this thought.
I mean, I think incentives come down to culture and it's, it's what you set as like the fiber of your organization. So again, like I, I, I think you can align incentives and people will be excited to make impact in the organization, regardless of how an organization is actually organized.
That's a really interesting takeaway because I think a lot of people think about, okay, if we just org this and put this person here and create business units, things are going to start moving. And not, you're not saying don't think about that and don't necessarily do that, but you're probably putting too much weight on that, actually solving your problems.
Yeah, I mean, I think you want to certainly study different ways of organizing and the pros and cons, but just know that no matter which choice you make, it's going to suck and there are going to be organizational problems. Right. And you just need to go into it with wide open eyes and then create process to make sure that the, whatever the cons are. Like if, if people are in silos, well, then you gotta have a really good way of bringing people together and creating the right incentives to make sure people collaborate. Right. So there's all these other things that I would say are much more important to focus your energy on.
Awesome. Anything else along these lines around org design or Hiring that you think is really important or has, you know, I.
The one thing that is universal for me and always has been is mission over domain expertise, basically. Mission over domain expertise, mission over skills. I think that if you have like a raw, like that raw horsepower and you're deeply like, you just love the mission so much, you can build whatever skills are necessary for the job. And so I actually love taking like, as an operator, I love taking bets on people who are maybe earlier in their career who have energy, who have drive, and who are deeply thoughtful and deeply resonate with the mission that we're working on. Because at the end of the day, like just strategy changes, orgs change, teams change, everything changes all the time. And the one constant I think is actually the mission. And when shit gets really, really hard, when your company almost collapses like we did during COVID the thing that gets you through those hard times is the mission. If you don't have mission, if you don't believe in the mission, you lose meaning in your day to day and you start to disengage from the company. Mm. So I think that's actually the most important thing.
So what I'm hearing there is potentially if you're just like hitting it at your job or you think it's just not going anywhere, it might be that you don't actually care that much about what the company's trying to do in the mission. And maybe there's not a lot that can change for you to actually be happy there because you don't actually care.
Yeah.
Fascinating. Something that I wanted to come back to real quick. A lot of your advice comes back to impact. Like impact above all else, Drive, impact, focus is. Comes back to what is the most important thing to do. Something that I think about a lot is how do you be successful within a company? And one of the levers is go to a place and a team that is driving impact. Do you have any advice there around just like where you are best suited to be successful within an org kind of coming at it from where impact is most happening.
I mean, I always thought about it as like the. The combination or almost like this Venn diagram of like there. There's one circle which is like all the different priorities that are important. Then the other circle are your strengths and where you spike. And the intersection of the two is the place where you should be. Right. And sometimes you're not quite there at the intersection and you're kind of gravitating towards that intersection. You're building a specific skill that you're Already, like naturally, like pretty decent at. But you, you definitely want to double down on it as you're learning more about the priorities and there's a match there. The worst thing I think you can do is just like sit in a job where you're not being impactful, you're not working on the top priority and like, you're just kind of wasting your life, you know, like our time is short on Earth. Like, you might as well wake up every day and work on the hardest thing you can where you can truly, based on who you are and the spikes you have make a dent and whatever is going to happen. Right.
That and also have the serenity prayer ready to go when things get really hard.
Yeah.
Okay, so what I want to do right now is summarize many of the things that you've shared before we get to talking about Airbnb today and Brian Chesky's approach to product. I guess before I try to summarize stuff, is there anything else you think is important, skill wise or behavior wise that we haven't touched?
No, I think we.
Okay. We've done a lot. Okay, cool. So I'm going to just. This is like almost a Vlad's guide to being a successful product leader. I don't have it all summarized here yet. I just have a bunch of notes, but I thought it'd be fun just to try. So one is, and the way I would think about this as you're listening to this is how do I be more. What can I do to be more successful as a leader in a company? And this is all kinds of stuff that I a hundred percent agree with is effective. So one is impact above all else. Think about what is the company prioritizing, what is important to the business, how can I drive impact there? And to do that, think about the levers in the business that move that and then find ways to work on those things. This idea of inquiry, first when you disagree with something, shift your mindset to asking questions. And then along those lines kind of when you disagree, this idea of poking the bear, sharing, hey, here's why this might not be right. Here's why you might be wrong about this. Here's data that I found. Or what data wouldn't help you understand? Maybe you're wrong here. Okay, what else? Saying no, being really good at saying no.
Just.
And this comes back to impact and focus. Let fires burn. Really powerful idea. Don't feel like everything has to be solved. I'm similar to you where I feel like I need things in order and Clean and organized. And so this would be very hard for. Very hard for me. But such a powerful lesson of just, it's okay if things aren't going great. And I love your advice of align with your team on. We will let these things burn for now. Anything you want to add, by the way, as I'm going through this?
No. Gotta let everyone be a pyromaniac. Leads to great things.
Awesome. So along those lines, embrace chaos. Let things be chaotic sometimes. Cause some of the best things come out of that. And as you shared, Brian sometimes just introduces a little chaos to get people out of their little. Their safe world a little bit. This idea of a shit bucket, if things are just like, I hate this thing and it's not going well, I'm just going to throw it in the shit bucket for now. And that's just how it's going to be. And I'm going to move on so I could focus on impact and important things. Amazing. Okay, what else do we have here? So many little notes here. Be prepared. So as you're organizing teams, be prepared to lose friends that you had at the company as you rise and as you have to do things that maybe they're not aligned with or happy about that are helping their career. All org charts suck. Nothing's gonna be amazing. Don't over focus on the org chart and focus on the people and the culture. Oh, yeah. The mission above all else. Just like if things are not going well, it might be people aren't aligned with the mission of the company.
Yeah.
Okay. Is there anything else off topic?
I mean, it's. It's so interesting. Like when I think back to my 10 years, like, things that I actually remember the most are these moments with other people and not the some project or some product launch that's like going super well or, you know, us doing really well with metrics. It was the things that really made, I think, Airbnb special. And I really, now that I think back to those 10 years of my experience, I deeply just resonate with are those little moments. And like one example, and this is why culture is just so important, because these things don't just happen like organically. Like, you have to be thoughtful about building culture, and then I think you create a place where these little things can happen. So for me, I don't know if you remember your experience when you first joined the company. My most memorable experience at Airbnb is the human tunnel. And it was just this thing where I remember it was my first day and I was standing behind like, this giant wall. And there was silence in, I think it was a cafeteria. It was like this huge, huge room, right? And then somebody like this engineer runs up to me and says, hey, go around the. To the other side of the wall. And I turn, and suddenly the room just explodes in cheering and clapping and everyone yelling my name. And everyone is, like, basically doing a human tunnel with their hands. Literally every single person at the company, at hq, including the founders. And then I run through under everyone's cheering, and I jump into this beanbag while everyone's, like, chanting my name. That was my first day. And here I am, like, I don't know, 12 years later, 13 years later, I still remember that as one of the most amazing moments of the entire journey. And it, like, I immediately felt accepted and I wanted to contribute to the team, you know, and a lot of the reasons why there were many moments like that throughout my 10 years. And it was a result of how we hired people for certain core values and were very intentional about just helping people integrate into this crazy company that was growing super fast.
That's an amazing story. I feel exactly the same way. I went through a similar experience when I joined, and obviously the human tunnel eventually didn't scale and people started doing it like, per team versus the entire company. We could do a whole episode on Airbnb culture and learnings from that. Interestingly, with the human tunnel, it's like it started, I think, with the founders, but it ended up being they had no involvement in these tunnels. Like, it was just employees knew that this is the thing think we're going to do for every new employee. And so I think it's interesting, I guess, just spending a little time on culture and learnings from Airbnb about the value and power of culture. Is there anything there you take away with two other companies you work with now of just, like, how to set up a great culture, how to do this?
Well, I would say there's no, like, single playbook. I would say the one thing that comes to mind is just being really intentional and thoughtful about it and actually dedicating energy to it. Just as much as you spend time building product, hiring people is you gotta spend just as much energy actually thinking about culture and your core values. And so core values are very, I would say, indicative of what the culture will be. So those two are very linked. Right. And once you have. Once you think about core values, I remember what worked really well was you don't just, like, write your core values in the document somewhere, and then no one ever opens it you need to. The key is, regardless of what the core values are, you want to make sure that those core values are prominent in just about every single thing that you do. Right. So when you hire people, you hire for certain core values. And at Airbnb, we had core value interviewers up until, I mean, my entire tenure, basically. Even when we had thousands of people already at the company, when we were hiring people, everybody had to pass core values interviews. So it was very ingrained in how we hired and what we look for. Then even performance reviews and promotions. No matter how much impact you made, right, no matter what you did, if you were not also exemplifying core values, you didn't get promoted. Right. You didn't get to the next level. And so even in our performance conversations, those core values were very present in the day to day. And then of course, they were also printed everywhere. They were just like physically everywhere, all the time. So, like, I felt like every single person around me always knew what the core values were. And so that's my biggest advice. It's like, don't copy some other company's core values. Instead, just be intentional about what matters to. To your organization and then make sure that those core values are freaking everywhere part of every single process. Otherwise, like, no one's going to care.
Just to reinforce what you're saying. Have been gone from Airbnb for five, six years now, and I still 100% remember the core values. I'll go through them real quick. Be a host, be a serial entrepreneur, which is serial as in the serial story. Derby. Champion the mission and simplify. Although they tweaked that one.
Or they cut it right and then Embrace the adventure.
Embrace the adventure is my favorite. I love that one the most.
See, years later, like, there's also.
You still remember, like, exactly. Every frame matters was the other one they decided to cut out because they realized something they learned about core values that I thought is really interesting is they shouldn't be aspirational, they should be who you actually are. And so there's a period where the founders are like, we're not actually amazing at this thing, so let's just remove it from the core values and reduce. Reduce the ones we're focused on.
Yeah. What I also really liked is that there were tangible, like, examples always of what about what it meant to embody this core value in your day to day work.
Right.
And so then it was like very tangible for people versus just some overarching, like, embrace the adventure. Like, what does that actually mean?
Right, right. And then just to make sure people get this point you made about this Core Value hiring team, which is really unique. I don't know if anyone else does. This is there's people trained to interview in Core Values, and they were like a specific volunteer team, that part of the interview process. One of these people came in and they interviewed for Core Values, which was meant to represent what the founders were looking for initially.
I mean, it was also very telling how I remember it was an honor internally to be selected to be a Core Values interviewer in the first place. Like most people, large companies are like, I don't want to do any more interviewing. Oh, my God. Like, I'm interviews all the time here. People were like, it was a sense of like this emotional, proud moment when you were basically given the keys and you were. Somebody said, hey, like, we actually think you would be fantastic at helping us think about how to make sure every single new hire embodies these core values. I think that was so powerful.
Amazing. Okay, so we, again, we could spend an entire hour on the culture of Airbnb and all the things we've learned there. It's actually a good segue to the last area. The last part I want to talk about, which I think a lot of people are probably wondering about as we have been chatting, which is about Airbnb's current ways of working. So we had Brian Chesky on the podcast, most popular episode of the podcast, turns out, and he shared his approach to product, which a lot of people are like, huh, that's. That's unique and different, and I don't necessarily want to work that way. Other people are like, this is amazing. This is exactly how I want to operate. And so I'm going to make my company work this way. The way he described Airbnb is it kind of moved from bottom up, experimentation driven, to very top down. We're going to have one roadmap. I'm going to be involved in everything. Product managers are now product marketing managers. And all these things that I think people are like, wow, that's really nuke and interesting. You actually worked through a lot of that. You went through that transition. I think technically you're a product marketing manager when you left Airbnb. Okay, so you're a really good example that you reported to Brian during this time. Yep. Thoughts? Now that you're removed from Airbnb on that way of working, pros and cons, right for everyone. Maybe not right for everyone. How do you think about this stuff?
Yeah. So first, I guess let me zoom out of, like, from Airbnb for a second. Then we'll go into the concrete details of what Brian said. I don't think you should copy another company's ways of working. Like, the reality is, it is how a company operates is so unique to the founders, to the leadership team, to all the employees and the domain, potentially moment in time. Because, like, how companies operate also evolves sometimes over time. And there's certain, like, different ways of operating might. Might be needed, right? So I wouldn't just copy someone else's way of operating. Even, like at Airbnb. It was just very interesting for us. It took us a long time to figure out how operate, right? And we were actually. We didn't for a long time explain and give clarity to people of how we should even operate in the first place, because. So we hire people from Facebook and Amazon and Google and like Netflix and every Apple. Like every company, right? And every person would come in with their own preconceived notions of how they wanted to work. And oftentimes those. Those opinions differed. And so, because we never actually stated, like, the Airbnb way for a very long time, sometimes it would be chaotic, right? Like, people just wouldn't know how to operate. And then you go from team to team, teams would just operate very, very differently. And that was a problem. So I think here, the lesson for me was not necessarily, like, there is one way to, like, every. Every company should operate like this way. And it's much more about picking an explicit way to operate and then voicing it to every single person so that everyone has clarity in how to do their job. I think the worst thing is, like, people just don't have clarity on how to do things day to day. They don't know how to drive impact, and they're just like, what am I doing with my life? You know? So that was kind of one lesson now, specifically, like, going double clicking into Airbnb and like, where we moved. So I, I think one of the things that Brian mentioned was being top down, right? I actually think top down is this construct that has negative connotations associated with it quite a bit. And it's often, at least in the context of Airbnb, I, I think misunderstood, like, when people think top down. And I've had many, by the way, many of these conversations with folks, right? So most people think, oh, there's a leader here in an ivory tower sitting somewhere, divorced from the team, making a whole bunch of decisions, right? And everyone else is, like, powerless and can't do anything that's not actually reality right of top down. Now, in that room where we made many of the hard decisions with Brian, the reality was he asked a shit ton of questions, right? It was, again, he didn't advocate in the beginning. He would come in with tons and tons of questions and he would listen. And of course, sometimes, like, he would disregard certain things that he heard because he had very strong conviction, a different direction, but he listened. And oftentimes he would also change his mind. Right? And so as a leader, like at Airbnb, for so long, I never felt like I wasn't listened to or like he was just making these random decisions. I always had an ability to influence and an ability to voice where I felt like the company should go. So, like, yes, he made a lot of decisions, but he made sure he was informed in those decisions, and then many of us were contributing to all the information he needed to make the decision. Which is then also why he wanted every leader to be in the details. Why did he, like, stress that for himself and every single leader on the team? It's because when you get into that room, right, and you start discussing many different directions you can go if the leaders in that room can't tell you what's actually happening with the business and why are they there in the first place, right? Like, you can't then make a. A good decision with that group of people. So then suddenly, like, your team of like, 10, you have to blow up to a team of 30. And if those people are not in the details, then you gotta, like, what, bring in, like, 50 people? And so at some point, you. You need to make sure that leadership is actually in the details, understand what's happening, and can help bring to light information that's going to help somebody make the right decision, right? So that's why, like, top down and being in the details, to me, they were actually very connected and they made a whole lot of sense. Now, the one thing I'll say is, like, at some point when you're working on many things, like, it is challenging to be in all the detail, right? And if you mandate that, like, product cannot ship without, like, you know, certain people being in every single detail, sometimes you could slow it down, right? And that could be a con of that way of working. I would argue for us and for at Airbnb, the quality, like, of what we were releasing kind of suffered because we were just push, push, push, ship, ship, ship, and people were shipping across the board. And I did feel as a leader, like, I wasn't proud of some of the things we were shipping, you know, and so I appreciated the intentional slowdown at the expense of our goals to get to a higher quality bar and then amp up velocity again after everyone had a better understanding what quality actually was. So we kind of had to slow down for a bit to then speed up later. And, and I think a lot of it is Brian always wanted to make sure that every leader would be able to make decisions and have really good judgment and he wanted to teach what that meant. And I actually really appreciated that over the years. Now, you know, like if you were to go back to semantics and say, hey, where are we? Top down, bottom up? Those are just semantics. Like I would say we were actually like, if you really think about it, we were neither. Because bottom up you could always, through certain channels, voice information again, if you didn't self center and you were not afraid to poke the bear, you had an ability to voice information. So from that sense there's lots of information that came bottom up. But then at the same time there was also like a lot of conviction and intuition and context that came top down. And because for a lot of these decisions there was so much conversation. The reality is, I think the way we operate was actually somewhere more towards the middle on, on a day to day basis. Which is why for me, like I, I thought it was great.
We had a boss on the podcast CTO of Meta. And I always saw thought of Meta as a very bottom up organization where anyone can run experiments, they're shipping things all the time. He's like, no, we're very top down. We tell people, here's the things we're building this year, here's our big bets, here's what we're going to prioritize. And so I think to your point, a lot of people don't necessarily understand what that means and see things as bottom up versus top down. Any other pros and cons just real quick on working this way? I think a lot of people are, a lot of founders are like, maybe I should move my company this way. Maybe I should just be involved in everything. Maybe we need to move PMs to product marketing managers. Is there anything else that's maybe a pro or a con in this approach that might be worth sharing?
Yeah, I mean, I think what you need to recognize, right, is which decisions and what part of the company.
Do.
You have special like do you spike on and where you have edge and where you can help make the best decision. And then I would argue then as a leader, then it is your job to be involved in those decisions. Right. For Brian, he always spiked in, in product, in design and marketing, right. So it was very natural. This is why he like he was basically the cpo, right? That's why he was in all those decisions, because that those were his spikes and that's where he helped everybody move forward in a certain direction. I think for, for founders, like, you just need to recognize, like, what do you spike on? Like, what are the specific things that you have this great insight that other people do not and immerse yourself in a lot of those decisions. Right. And there are some things that you might need to let go of, right. That are maybe like, not as important or maybe certain things that like, you just, you won't add much to the conversation and you have someone who you trust who's going to uphold like a certain quality bar or whatever, whatever. So it's just being thoughtful about where you spend your time and leverage, leverage your strengths, basically.
Final question along these lines, very specifically around this whole product marketing manager move. To me it feels like mostly like a rebrand of PM with some marketing work. And in my eyes, PM's already should be doing marketing and thinking about adoption and growth and all these things. And so I'm curious just your take. Do you think this is like the future for PMs in general? Do you think this is just like a funny thing that Airbnb is trying and it doesn't really make a big dent? Thoughts on just this idea of PMs should be product marketing managers and we don't need PMs as PMs.
I kind of felt like that was reading about this in, in the news when it, when it blew up. I mean, I, it felt, felt a little overblown to me, to be honest. Like, just like you said, a lot of PMs at the company were thinking about how to talk to users about the products they were shipping and they were basically marketers to some degree. Right. So I would say the rebranding of product manager, it did do some important things like shed project management and establish an entire function that focused on, on making sure things are moving in the, like, the right direction from a project perspective and highlighted the importance of marketing or maybe just it wasn't as highlighted before, but it was already happening at the company. So, you know, for a lot of the, the product leaders at the company, it was very liberating because now you actually don't need to worry as much about, let's say timelines and coordinating things across teams and departments and functions. That there's a function that does that and your job is a lot more like user centric and thinking through how to tell the world about what you're building. And so it was a, it was a welcomed change, broadly. Now, does that apply to every company and like PMs do things this exact way? No, it depends. I think it's actually challenging to find product managers who are also really good marketers. And so I, I think it's actually like a rare skill set and like the art of marketing and the art of talking, like conveying what you're building in a compelling way to people. It's a, it's, it's a craft on its own and you have to build that over time. And so there are many product managers that haven't exercised that craft. And so of course they can't just immediately like snap their fingers and become good at it. Right. It takes years to learn that skill. So it kind of again, depends on the people, it depends on the organization. There's no blanket statement, in my opinion, where it's like, PMM is the way, or PM plus PMM is the way. Like I. It depends.
And just to clarify, the function you mentioned that kind of took off some of the load of PM is program management, I think is program management.
Yes.
And they basically took on timelines, staying on top of priorities and kind of the. The project manager part of the PM role.
Exactly.
Awesome. Like, if you think about it this way, it's actually like the best version of the product management function. Not dealing with like the project management and thinking about the product, the experience, the launch, the marketing, the growth. Yeah, it's pretty.
I mean, we had many product managers like internally always say, like, oh, we feel like we're doing very tactical work. We want to be much more strategic and like, boom. Like this change actually makes the job significantly more strategic.
Yeah.
If you weren't doing that already.
Awesome. Okay, I'm glad we spent time on that. One last question before we get to a very exciting lightning round. We've talked about so many things that have gone really well. You are incredibly successful leader person, pm. You've worked on so many successful projects. All these skills you've worked on that have been really helpful to you that we've been talking about. I want to take us to failure corner. I'm curious if there's a story of failure that you could share. Where you failed some point in your career and what that was and what you. How that impacted you, how that helped you potentially in your career.
I failed A lot. Like, we've talked about the positives. There were also, on my journey, a lot of humbling moments. Still have them. Lots of failure. Um, I would say the. The one moment I remember this was probably in, like, 2018ish. This was at Airbnb. It was a pretty dark time for me, and I felt overworked, overwhelmed, and I just wasn't a happy person. You know, this was a time where we were still scaling very, very quickly. And I just felt like I. I don't know. I. I wasn't, like, keeping up as much as I was in, like, maybe the earlier days, you know, And I was. I remember thinking to myself, like, oh, my God, am I gonna tap out in 2018? Like, is this it for me? Like, you know, and it was. It was just hard for me. Cause I was also a perfectionist. I wanted to help as much as I could. I had great, like, ambitions and dreams that, like, I'm gonna keep going with Airbnb for a very long time. And I think in that moment, I kind of hit rock bottom at some point. And I actually remember, you know, like, during that time realizing that so much of my identity was Airbnb and my job that I had trouble separating myself as a human being from my work. And it was just realizing that, you know, was. Was tough. Like, I lost friends, I lost a lot of relationships. I lost many of my hobbies. Like, I didn't spend as much time as I wanted to with my family and my parents. And at some point, I. I was just like, you know, I think in order for me to be. To be a better leader, like, I just need to be a much more B balanced human being. And that's where, ironically, I started spending less time on work. And I became way more effective because I was just more centered, like, as a. As a person. So I. I reached out to people who I lost touch with. I spent much more time with my wife and my parents. I started gaming again. And, like, all the, like, little hobbies that I lost along the way, and it just made me happier. And because I was happier, I felt like every hour as a result, was much more impactful, like, at the end of the day. So, yeah, like, it. That's. That's one thing that I, like, think about quite a bit. Like, you can't just. It's really great when you pour your heart and soul into something. I think it. It. It is very fulfilling. Right? But also, you gotta think about how to balance yourself as a person. And if you lose sight of Everything else in your life, like, I. It's a recipe for disaster.
I appreciate you being really real with these. A lot of people just share something that's not as real and so I appreciate you doing that. And I love the advice of if you're going through a really hard time right now and are feeling burnt out and sad about your career, maybe just do less and maybe lean into your personal life more and that will help you be more successful in both.
Yeah, you gotta like find joy in, in the little things again. And if you like, if you don't find joy in little things, like, I just, I don't think you can show up with an open mind and the curiosity that you need to be successful in whatever job you have.
I love that. Vlad, before we get to our very exciting lightning round, is there anything else that you wanted to share that's on your mind that you thought would be leave. Good to leave listeners with? We covered a lot, so there may not be anything left. But is there anything just to give you a chance?
No, I mean, like I'm deeply thankful for the experiences that I've had. I mean, I've learned so much. I mean, I think, you know, I look back and there are definitely many lessons, but let's also be real. Like a lot of it is luck, right? And a lot of just stuff just happens and it happens to go your way. So when, when things are hard, the one thing that I just want to maybe share is don't be too hard on yourself and cut yourself some slack. You know, as long as you're waking up and you're actually pouring your heart and soul into something, you're truly giving it your all. Like that's all you can really do.
Amazing advice. This might come up again in our lightning round with that. Vlad, we've reached our very exciting lightning round. Are you ready?
Let's do it.
Let's do it. Ding, ding, ding. First question. What are two or three books that you recommended most to other people?
So I love Sci Fi. Red Rising was one of my favorite books and then the Silo series. Highly, highly recommend.
What do you think of the TV show version of the Silo series?
What's that?
There's a TV show of the Silo series.
Read the book though. I would like watch it after you read the book. I always like reading the book is way better.
I agree. I don't know if you actually watch the show, but it's completely different story. It's like 90% just a whole new story. I don't Know what's going on there. Like, foundation is similar. I don't know what they're doing these days with movies.
Crazy.
Amazing. Okay, do you have a favorite recent movie or TV show that you've really enjoyed?
There's a TV show that I've enjoyed for a very long part of my life. It's called Survivor. And if you've heard of it, probably, everyone's probably heard of Survivor at this point. The show is not dying. It is actually very fun to watch and there's a new twist every single season. And so I've probably watched like, I think like 35 seasons or so.
That's out of control. Do you feel like you would do well in Survivor if you were to.
Well, I think I, I, I would do well. My wife thinks I would die, so.
I gotta find out. Okay, if I can nominate you for Survivor. I'll find a way. As long as you don't die. Next question. Do you have a favorite product that you, that you've recently discovered that you really enjoy?
So one is actually a product that I cannot live without. It's I discovered in 2016, Discord. I cannot live without Discord. It is one of the products that I use for hours and hours every single day. I'm in all these like gaming communities and it's so much fun.
I love that you use it for gaming, not, not for crypto.
Just chatting with players and like actually like hanging out. Yeah, love Discord. The, the product that I recently got introduced to is a game. It's actually a like pseudo boardish game called Gobbler. It's an advanced version of tic tac toe. And so me and my four and a half year old daughter play this before bedtime like every single day. She was just started schooling me at tic tac toe and so I needed to upgrade Gobbler. If you haven't played, it adds a new dimension where like pieces can gobble other pieces. It's almost like playing in 3D a little bit. It is super fun to play.
Wow. It's funny that she was schooling you tic tac toe, which I my understanding is you just tie all the time. It's amazing that she found ways to keep beating you.
Yes, I think the says more about me than I don't know.
Okay, Gobbler, next question. Do you have a favorite life motto that you often think about? Repeat back to yourself, Share with friends.
Or family and work your in life you never know. And it's a very simple motto and what that means is to me, even when there are things with low probability, shoot your shot, take a chance, take a leap. Sometimes you're going to be surprised at how things turn out.
Beautiful. Final question. A tradition Interbnb is to ask new folks a fun fact about themselves, which is always a hard question on the spot, but I'm going to ask you anyway. Is there a fun fact about yourself that would be fun to share?
Well, I kind of shared maybe a little bit of it. I absolutely love Survivor and so I have tried to get on Survivor multiple times and it is actually my dream to get on that show. So if anyone out there watching who happens to cast for Survivor like I am here, I am available and I will probably not do very well, but maybe I'll be entertaining, I don't know.
This is. This is your casting video right here. This is it. All right, Survivor people, let's get Vlad on. I think you would kill it. I could see this is all the skills we've talked about, I think would be incredibly. Just letting fires, though. Let him near the fire. Oh, my God, Vlad, this was amazing. I'm so happy we did this. What a special episode. I think for everyone that listens to this episode and goes through it all is they will, I guarantee they will become a better leader in so many ways. And so I'm really happy that we did this. Two final questions. Where can folks find you online? And who would you want to reach out to you? What kind of folks you're working with these days? And then finally, how can listeners be useful to you?
Hit me up if you want to chat on LinkedIn. I'll respond and we can like grab a coffee or zoom or something. I mean, I'm an investor now and like, I love spending time with early stage founders. A lot of those early stage founders actually happen to be product managers at some point in their career. So I just like love chatting with folks about the problems they're facing or the ideas they have when they're thinking about starting a company. So, yeah, if you're tinkering with cool things like hit me up and we'd.
Love to chat and there's a segment, is there a segment of startups you're most focused on just for folks to know?
I bet on people. So for me, like, that's. That was always one of my learnings. Like, I love meeting people that take me into a whole new dimension that I didn't even think was possible. Now I do love consumer because a lot of that is my background. And so I try to focus on consumer, but at the end of the day, I'm focused on people, people. And so I go into many different directions where people.
Awesome. All right. And how can listeners be useful to you?
If you want to chat, hit me up.
Cool. Help you find really cool startup opportunities to invest in.
Yeah, yeah, yeah. Thank you, Lenny. Thank you so much. This was super fun. Thank you for having me on.
It's absolutely my pleasure. Thank you, Vlad. And bye everyone. Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast. Com. See you in the next episode.
More from Lenny


How Meta designed Muse: an AI agent people actually want to talk to | Alex Cornell (Design Director)


Why every company now needs to think and operate like a lab team | Josh Woodward (Google Labs, Gemini, AI Studio)


Jev: 8 real use cases for the fastest, cheapest model I’ve ever used | John Lindquist


The grief, loneliness, and burnout sweeping through the tech industry right now | Molly Graham






