Mar 16, 2022 · 42m · 20product
20 Product: Lenny Rachitsky on The 3 Key Roles of the Product Manager, 5 Skills All The Best PMs Have, When To Hire Your First PM, How to Structure the Hiring Process for PMs & What Leaders Can Do to Make Their PMs Successful
0:00 / 0:00
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Host Harry Stebbings interviews product expert Lenny Rachitsky on 20 Product to discuss fundamental product management principles, strategies for hiring and onboarding product managers, lessons learned at Airbnb, and operational frameworks for leading high-performing teams.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 30.7% of the talking time here. How this is scored →
Harry as informed peer 2.7 Guest teaching 3.1 Guest disagreement 0.9 Harry pushing back 1.8
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 33:40 Resisting the VC push
Lenny directly pushes back against Harry's attempt to steer him into institutional venture capital, insisting that raising a $50M fund would bring him no joy regardless of the money.
Hardest push from Harry ▶ 33:40 Harry challenging Lenny's refusal to scale fund sizeHarry forcefully rejects Lenny's premise that running a fund involves too much administrative hassle, insisting that early-stage modeling doesn't exist and Lenny should go harder.
Biggest teaching moment ▶ 9:00 The price sorting trap in product designLenny educates Harry on why raw user requests can be deceptive, demonstrating how Airbnb's most requested feature—sorting search results by price—actually caused conversion rates to drop.
Harry holds his own ▶ 33:40 Harry flexing VC fund economics expertiseHarry asserts his expert domain knowledge as a venture fund manager, dismantling Lenny's arguments about financial modeling and LP fundraising mechanics.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Lenny Rachitsky's Journey into Product Management | 1 | 1 | 0 | 0 | Harry warmly introduces Lenny and asks a classic origin story question about how he entered product management. Lenny details his background from immigrating from Ukraine to starting a company acquired by Airbnb. | |
| Product Management Lessons from Airbnb | 1 | 3 | 0 | 0 | Harry asks Lenny how his seven years at Airbnb shaped his approach to product. Lenny explains internal culture takeaways, such as setting an extremely high bar and working backwards from storyboards like Pixar. | |
| Defining Product Management and Customer Insights | 2 | 4 | 1 | 1 | Harry asks Lenny to define product management and how to balance user feedback against intuition. Lenny reframes customer research, explaining how users ask for features like price-sorting that actually harm business conversion. | |
| When to Hire a First PM and Role Differences | 3 | 3 | 1 | 2 | Harry uses a hypothetical founder roleplay to probe when to hire a first PM and asks about CPO vs Head of Product titles. Lenny advises waiting longer than expected and outlines specific organizational bottlenecks that signal a PM is needed. | |
| Structuring the Hiring and Interview Process for PMs | 3 | 4 | 1 | 2 | Harry systematically walks through PM hiring stages, asking for common mistakes made by both applicants and founders. Lenny details a full-day interview structure and warns founders against assuming Twitter popularity or Big Tech credentials translate to startup success. | |
| Running Effective Product Reviews and Cross-Functional Alignment | 2 | 3 | 0 | 1 | Harry references a prior interview with Scott Belsky to guide a conversation on product reviews and cross-functional design dynamics. Lenny breaks down how to run focused reviews and explains the 80/20 responsibility split between PMs and designers. | |
| PM Onboarding, Building Trust, and Handling Product Failures | 3 | 4 | 1 | 2 | Harry probes how PMs build trust and presses Lenny on how leaders should handle product failures without demotivating teams. Lenny shares his own major failure at Airbnb—a social meetup feature that bombed—and explains the importance of emotional detachment. | |
| Angel Investing Insights and Strategic Perspective | 6 | 4 | 3 | 7 | Harry actively challenges Lenny's decision to remain a solo angel investor rather than raising a $50M venture fund. Harry uses his own VC knowledge to counter Lenny's excuses about financial modeling and LP management, though Lenny firmly maintains that full-time VC work does not bring him joy. | |
| Quick Fire Round | 3 | 2 | 1 | 1 | In the quick fire round, Harry and Lenny exchange creator insights about output volume, burnout, and writing processes. Lenny shares his self-invented PTO policy and offers fast takeaways on PM leadership and product strategy. |
Statements from this episode (23)
Stebbings says Lenny's Newsletter is the only paid newsletter he subscribes to
“Now, this is the only newsletter I pay for, I have to admit.”
Rachitsky: Product teams should work backward from an ideal experience
“Another is this idea of working backwards. From the ideal experience, instead of just kind of incrementally working towards where you think you might go.”
Brian Chesky hired a full-time Pixar artist to storyboard Airbnb's experience
“He hired a full-time storyboard artist from Pixar that worked at Airbnb for over a year that helped develop these storyboards, these key frames along the journey of a host and a guest.”
Lenny Rachitsky defines product management by three core responsibilities
“Basically, your job as a PM is to shape the product, to ship the product, and to synchronize the people, and all of that in order to drive impact for the business.”
Sorting search results by price always reduced Airbnb's conversion rates
“One of the most common requests that Airbnb gets is, and this has come from like day one, is like, I wish I could just sort my listing search results by price. Just like, show me the cheapest one, because I want to book that. So many teams have tried to build …”
Rachitsky: User research must focus on past behavior, not future promises
“A classic rule of research and talking to customers is you never want to focus on what people might do because we're really bad at predicting what we will do.”
Rachitsky: Startup founders should delay hiring their first product manager
“My first piece of advice always is you should wait longer than you think you need to.”
Rachitsky: Zimride hired its first PM to develop Lyft
“So as an example, Zimride, to explore the idea of Lyft, hired their first PM, and his job was go explore this idea of Lyft.”
Rachitsky: Snap and Twitter hired first PMs specifically for monetization
“Snap and Twitter, from what I understand, both hired their first PM to explore monetization on the platform.”
Startups should wait until Series C or 12 PMs to hire CPOs
“From what I've seen, it makes sense to do that maybe when you're, like, series C or something, when you have maybe a dozen PMs.”
Rachitsky: PM interviews shouldn't test on-the-spot problem solving
“Personally, I hate putting people on the spot with a really hard task because as a PM, you don't need to be like on the spot solving really hard problems. You have time to think. And process and research.”
Rachitsky: PM candidates fail by jumping straight to solutions
“One mistake that PMs often make is jumping to a solution. When someone asks them, how would you approach this? It's just like, here's the answer, versus asking questions to better understand Context and the space and understand things that the person maybe has…”
Founders shouldn't hire product managers based on popular blogs or podcasts
“So a few mistakes founders make hiring PM. One is assuming they're like a great PM because they've written amazing blogs or tweets or done podcasts, like myself included. It's a lot different to do the job than to be talking about it.”
Rachitsky: Big Tech PMs often fail when transitioning to startups
“And similarly, if your PM's been a PM at like Google or Facebook, they're just like really good at PMing at Google and Facebook. There's like a very specific way of building product at these big companies, and you shouldn't assume that they're going to be good…”
Lenny Rachitsky: Product reviews waste time when disconnected from problem definitions
“I think the most common problem in these meetings that causes all kinds of wasted time is not connecting back to the problem that you're solving as a team, whether it The problem that feature is trying to solve.”
Lenny Rachitsky: Keep product review attendee lists as small as possible
“The rule of thumb is you want to make it as small as humanly possible while making sure people that need to hear that feedback are in the room.”
Product managers own problem definition, while designers own the solution
“A simple way to think about it is the PM's job, eighty-twenty. 80% of their job is to identify the problem that needs to be solved and make clear, here's what we're trying to solve, and here's all the information around it. And the designer's job, like eighty-…”
Less than 1% of Airbnb guests used Rachitsky's initial travel feature
“The metrics were just like not great. It was like less than a percent of travelers in Airbnb were opting into this thing”
Rachitsky: Distribution and problem fit kill startups faster than product quality
“I don't actually pay attention to the product as much as I used to, because I've seen these things are much more likely to kill it, and then I'm like, okay, cool, now let's check out the product and see if it's awesome.”
Rachitsky: Committed to avoiding full-time VC life and institutional fund management
“I don't like the full-time VC life. That's what I'm trying to avoid at all costs, because I've learned I don't like the things that VCs have to spend time on, like financial modeling and planning, portfolio allocation, fundraising with LPs, those sorts of thin…”
Rachitsky: No community platform compares to how well thought through Slack is
“I've tried so many other types of community platforms, and none of them compare to how well thought through Slack is.”
Rachitsky: New product leaders should fix an immediate team grievance for a quick win
“Suggest that they ask everyone on their team. What's just like bugging you? What's something that we should improve? What's a process that's annoying? What's something that we can fix? And then go fix something. Go fix a thing that is bugging people and create…”