Lenny Rachitsky draws on his experience as a product manager at Airbnb and on research with other practitioners to write about product, growth, and work. These lessons distinguish his own operating advice from frameworks developed with collaborators or shared by guests. — On Substack — Lenny’s Paid-Newsletter Workshop.

Part 1: The Product Manager's Role and Mindset
- On Leverage: Increase the team’s leverage to solve consequential customer problems and deliver business impact, rather than measuring PM work only by activity. — Lenny — What Is Product Management.
- On Core Responsibilities: Lenny groups PM responsibilities into shaping the product, shipping it, and aligning the people around it. — Lenny — What Is Product Management.
- On Conviction: Start with a reasoned proposal, then revise it with feedback; teams should contribute their own judgment rather than treat leadership’s initial direction as fixed. — First Round — The W Planning Framework.
- On Anticipation: Surface dependencies and resource needs during planning, and secure support from other teams before commitments harden. — First Round — The W Planning Framework.
- On Falling in Love with the Problem: Use customer research to decide what to build, and connect that research to the team’s business goals. — Maven — Product Management Fundamentals.
- On The Smallest Possible Product: Review scope with engineers to find a simpler approach, then test and learn rather than overbuild an untested idea. — Levels — What Does a Product Manager Do.
- On Brainstorming: Draw ideas from customer conversations, observation, and data. Lenny cautions that large brainstorms may involve the team without generating its strongest new ideas. — Lenny — Where Great Product Roadmap Ideas Come From.
- On Raising the Bar: Raise the bar in everyday work: clarify documents, make meetings purposeful, and seek feedback before sharing widely. — Airbnb Retrospective.
- On Becoming a Product Manager: Lenny’s transition into product management involved learning on the job and finding a mentor; look for opportunities to practise the work. — Levels — What Does a Product Manager Do.
- On Growth vs. Product: Connect product decisions to customer problems and business impact; the role includes shaping and shipping the product, not only acquisition. — Lenny — What Is Product Management.
Part 2: The Habits of Great Product Managers
- On Communication: Treat clear written and spoken communication as core PM work—in documents, emails, presentations, and meetings. — Maven — Product Management Fundamentals.
- On Reliability: Build reliability through delivery: track commitments, keep the team aligned, and surface surprises before they derail execution. — Maven — Product Management Fundamentals.
- On Hunting for Misalignment: Keep people synchronized on goals and decisions so conflicting information does not pull the team in different directions. — Lenny — What Is Product Management.
- On Ruthless Prioritization: Give teams a focused problem and concentrate resources there, rather than spreading effort across an entire funnel. — Airbnb Retrospective.
- On Protecting the Team: Protect engineers’ focus by involving them at useful milestones instead of requiring everyone to attend every discussion. — Levels — What Does a Product Manager Do.
- On Looking for Blockers: Look for unresolved decisions and bottlenecks that prevent engineers from making progress. — Levels — What Does a Product Manager Do.
- On Building the Leadership Triad: Build a strong working relationship with engineering and design leaders, rather than treating product leadership as a solo responsibility. — X — Habits of Effective Product Managers.
- On Connecting Work to Mission: Connect the team’s plans to the company’s mission and strategy, and explain the reasoning and tradeoffs behind priorities. — First Round — The W Planning Framework.
- On Bringing Good Vibes: When sharing a failure, stay constructive and communicate a credible path forward rather than letting disappointment dominate the conversation. — Lenny — Communicating Failure and Hiring PM Leaders.
Part 3: The Mechanics of Growth
- On Sustainable Growth: Rachitsky and Dan Hockenmaier distinguish repeatable growth loops from one-off campaigns that cannot sustain growth by themselves. — Racecar Growth.
- On Core Growth Engines: Their framework highlights four common engines: paid acquisition, virality, content, and sales—not an exhaustive list of all possible channels. — Racecar Growth.
- On Turbo Boosts: Turbo boosts create temporary bursts, such as press or events; they can kickstart an engine but do not replace one. — Racecar Growth.
- On Lubricants: Conversion, activation, and retention improvements make an existing growth engine more efficient; they are not substitutes for finding one. — Racecar Growth.
- On Fuel: Fuel depends on the engine: capital supports paid marketing or sales, content attracts audiences, and users feed viral loops. — Racecar Growth.
- On Virality: A viral loop depends on users bringing in other users through recommendations, invitations, shared content, or referrals. — Racecar Growth.
- On Content as an Engine: In a content loop, useful material attracts users, whose activity can generate more material for others to discover. — Racecar Growth.
- On Paid Ads: Paid acquisition can be a primary engine when customer revenue can fund further acquisition; channel fit matters more than a universal secondary-only rule. — Racecar Growth.
- On Scaling Planning: Lenny and Nels Gilbreth’s W framework alternates leadership context, team proposals, an integrated plan, and final team feedback and commitment. — First Round — The W Planning Framework.
Part 4: B2B and Enterprise Strategy
- On The Layering Game: In Pete Kazanjy’s guest guide, sales can supplement a successful self-serve product through account expansion or conversion help—not necessarily replace it. — Pete Kazanjy — Sales for Self-Serve Products.
- On Organic Inbound: Word of mouth was the largest growth driver in Lenny’s selected B2B-company sample; treat it as a useful signal, not proof of product-market fit. — Lenny — Scaling Your B2B Growth Engine.
- On The Enterprise Trap: Elena Verna warns that chasing enterprise contracts can starve the product-led usage that supplies future deals; protect that underlying growth work. — YouTube — Elena Verna on Product-Led Growth.
- On Product-Led Sales: Kazanjy recommends combining account potential with activation and usage signals to prioritize where sales assistance could help. — Pete Kazanjy — Sales for Self-Serve Products.
- On Retention Before Acquisition: For product-led acquisition, Verna advises establishing activation and recurring engagement first, so users have reasons to invite or refer others. — YouTube — Elena Verna on Product-Led Growth.
- On Singular vs. Multiplayer Mode: Kazanjy tests self-serve suitability by customers’ ability to reach value and configure the product; single-user tools are not automatically excluded. — Pete Kazanjy — Sales for Self-Serve Products.
- On Reaching One Million ARR: The companies in Lenny’s selected sample averaged roughly two years from founding to $1M ARR; this was not a median or a universal deadline. — Lenny — Scaling Your B2B Growth Engine.
- On Outbound Sales from Day One: Kazanjy advises founders or product leads to prototype initial sales conversations themselves before handing off a repeatable motion. — Pete Kazanjy — Sales for Self-Serve Products.
- On Winning Against the Status Quo: Kazanjy asks whether a new product can coexist with customers’ current tools or requires replacing them; that distinction affects self-serve adoption. — Pete Kazanjy — Sales for Self-Serve Products.
Part 5: Airbnb Lessons and Scaling Marketplaces
- On Culture as a Competitive Advantage: Lenny credits Airbnb’s explicit values and regular rituals with reinforcing culture and keeping leaders accountable to its mission. — Airbnb Retrospective.
- On Crystallizing the Problem: Define the problem clearly and align stakeholders on it before investing in a solution. — Airbnb Retrospective.
- On Thinking Bigger: Use ambitious goals to prompt bigger thinking, with clear ownership and support rather than punishment for falling short. — Airbnb Retrospective.
- On Working Backward: Imagine the ideal customer journey first, then work backward to identify practical gaps and improvements. — Airbnb Retrospective.
- On Autonomous Units: Give cross-functional teams a clear mandate and dedicated resources, minimizing dependencies that keep them waiting on other teams. — Airbnb Retrospective.
- On Lead Bullets: Looking back on Airbnb, Lenny describes progress from multiple successful experiments—not one silver bullet—and advises focusing on promising tactics. — Andrew Chen — 28 Ways to Grow Marketplace Supply.
- On Supply-First Growth: Most marketplaces in Lenny’s research initially prioritized supply, but he stresses exceptions and the separate work of building demand. — Two-Sided — Build Something People Want.
- On Removing Friction: Airbnb’s Instant Book work began by imagining booking without waiting for host approval, then addressing hosts’ control concerns. — Airbnb Retrospective.
- On Kickstarting Supply: Early supply often required direct calls, emails, or in-person outreach; these manual tactics helped seed marketplaces before scaling. — Two-Sided — Build Something People Want.
Part 6: Hiring and Building Teams
- On Hiring for Ambiguity: In Lenny’s guest collection, Jiaona Zhang asks how candidates navigated ambiguity, looking for structure, input-seeking, and willingness to revise their approach. — Lenny — High-Signal Interview Questions.
- On The Superpower Question: Ask candidates about their distinctive strengths alongside what they are working to improve; Lenny includes both in his preferred interview questions. — Lenny — Communicating Failure and Hiring PM Leaders.
- On The Sibling Test: In Lenny’s collection, Meltem Kuran Berkowitz asks how close family would describe the candidate, using the answer to explore self-awareness. — YouTube — Favorite Interview Questions.
- On The Reference Question: Paul Adams recommends asking referees what feedback a new hire may need in their first review, to explore development needs before hiring. — YouTube — Favorite Interview Questions.
- On Waiting to Hire: Companies may not need a dedicated PM while founders, designers, and engineers can handle the necessary product responsibilities effectively. — Levels — What Does a Product Manager Do.
- On The Glue of the Team: Lenny describes strong PMs as making teammates’ work easier, giving designers room to explore while keeping execution coordinated. — Levels — What Does a Product Manager Do.
- On Testing Grit: Geoff Charles asks about a difficult experience and how the candidate handled it, exploring their judgment and agency through the example. — Lenny — High-Signal Interview Questions.
- On Controversial Decisions: Yuhki Yamashita asks candidates to explain a controversial product decision and represent the competing perspectives clearly. — Lenny — High-Signal Interview Questions.
- On Unfair Secrets: Noah Weiss asks candidates for hard-won lessons about team speed and energy, then probes how they learned and applied them. — Lenny — High-Signal Interview Questions.
Part 7: Performance, Feedback, and Leadership
- On Framing Feedback: In guest author Jack Cohen’s framework, which Lenny endorses, begin with a goal the recipient genuinely cares about. — Jack Cohen — GAIN Feedback.
- On Action and Impact: Cohen recommends describing observable actions and their consequences, rather than labeling the person or judging their character. — Jack Cohen — GAIN Feedback.
- On Wise Feedback: Cohen pairs clear expectations with support for the person’s ability to improve, rather than treating challenge and care as opposites. — Jack Cohen — GAIN Feedback.
- On Acknowledging Fault: Cohen recommends acknowledging how your own actions contributed to the situation, so feedback is not framed as one-sided blame. — Jack Cohen — GAIN Feedback.
- On No Surprises: Give feedback throughout the year so formal reviews consolidate ongoing conversations rather than introduce avoidable surprises. — First Round — The Power of Performance Reviews.
- On The Three Ws: Cohen closes feedback with concrete commitments: identify who will do what by when, then agree on a follow-up. — Jack Cohen — GAIN Feedback.
- On Self-Reviews: Use self-reviews to surface meaningful accomplishments, development needs, and career goals; distinguish results from a list of activities. — First Round — The Power of Performance Reviews.
- On The Pre-Read: Consider sharing the written review before the meeting, but adapt when unexpectedly disappointing feedback would warrant a conversation first. — First Round — The Power of Performance Reviews.
- On The LNO Framework: Shreyas Doshi’s LNO framework distinguishes leverage, neutral, and overhead tasks; vary the quality and effort invested instead of perfecting everything. — Shreyas Doshi — The LNO Framework.
Part 8: Creator Economy and Community Building
- On The Power of Writing: Try writing to clarify your thinking before making a major commitment to publishing; continue if the practice proves useful and enjoyable. — Social Studies — Product, Newsletters, and Working with Humans.
- On Extreme Iteration: Lenny repeatedly revises drafts for clarity and concreteness; he also describes extensive back-and-forth editing with guest authors. — First Round — Reluctantly Influential.
- On Primary Research as a Moat: When personal experience is insufficient, interview practitioners and synthesize their knowledge into concrete, useful material for readers. — On Substack — Lenny’s Paid-Newsletter Workshop.
- On The Community Flywheel: In David Spinks’s guest guide, community extends content by enabling members to help one another, rather than relying only on the writer. — David Spinks — A Founder’s Guide to Community.
- On Signal-to-Noise Ratio: Lenny seeded his community with engaged members and established participation norms, including a separate place for self-promotion. — First Round — Reluctantly Influential.
- On Building With the Community: Spinks recommends seeding the culture with founding members, then equipping members to lead conversations and local events. — David Spinks — A Founder’s Guide to Community.
- On The Invisible Treadmill: Protect the overlap between work readers value and work you enjoy; say no to additions that would make the creator business unsustainable. — First Round — Reluctantly Influential.
- On The Lindy Effect: Lenny used months of sustained writing as evidence he might keep going before charging readers—a personal confidence check, not a guarantee. — First Round — Reluctantly Influential.
- On Career Transitions: His writing career emerged while exploring startup ideas; the reader response led him toward an option that had not been in his original plan. — First Round — Reluctantly Influential.