💡

InsightHunt

Hunt the Insights

B

Brian Chesky

Episode #44

Co-founder & CEO

Airbnb

👥Team & Culture🎯Product Strategy⚡Execution📈Growth & Metrics

📝Full Transcript

14,469 words
Brian Chesky (00:00:00): Way too many founders apologize for how they want to run the company. They find some midpoint between how they want to run a company and how the people they lead want to run the company. That's a good way to make everyone miserable. Because what everyone really wants is clarity. And what everyone really wants is to be able to row in the same direction really quickly. And so I basically got involved in every single detail and I basically told leaders that leaders are in the details. And there's this negative term called micromanagement. I think there's a difference between micromanagement, which is like telling people exactly what to do, and being in the details. Being in the details is what every responsible company's board does to the CEO. That doesn't mean the board is telling them what to do. But if you don't know the details, how do you know people are doing a good job? People think that great leader's job is to hire people and just empower them to do a good job. Well, how do you know they're doing a good job if you're not in the details? And so I made sure I was in the details and we really drove the product. Lenny (00:01:01): Today my guest is Brian Chesky. Brian is the CEO and co-founder of Airbnb, which he started in his apartment with his co-founders, Joe and Nate, and has turned into an $80 billion global business with travelers and homes in 220 countries. I was very lucky to get to work with Brian for many years, and my sense is if you ask people who they consider the most inspiring tech or business leaders today, Brian would be right near the top of that list. (00:01:27): In our conversation, Brian shares an in-depth explanation of what's happening with product management at Airbnb, which caused quite a stir in the product world when he talked about this previously. We also get deep into Brian's new approach of how he runs Airbnb, including shifting away from traditional growth channels like paid growth, and instead betting tha...

💡 Key Takeaways

  • 1Eliminate the separation between Inbound (PM) and Outbound (PMM); PMs must own the story and distribution, not just the feature build.
  • 2Shift from a Divisional (GM) model to a Functional model to reduce politics, redundancy, and technical debt.
  • 3The CEO must act as the Chief Product Officer; if the CEO isn't driving the product, the company loses its product soul.
  • 4Implement a 'Single Consciousness' roadmap: one unified rolling 2-year plan for the entire company, updated every 6 months, rather than fragmented team roadmaps.
  • 5Metrics should be subordinate to the calendar; ship on a rhythm (e.g., May and November releases) to force alignment and decision-making.
  • 6Treat performance marketing as a 'laser' (lighting up a corner) and brand marketing as a 'chandelier' (lighting the whole room); prioritize education over arbitrage.
  • 7Remove 'people managers' who are not domain experts; leaders must be able to do the work they are managing.
  • 8Design and Engineering should report to the CEO independently; Design should not be subservient to Product.

📚Methodologies (4)

👥 Team & Culture

A restructuring approach that removes General Managers and divisions, organizing the company strictly by function (Design, Engineering, Marketing, etc.). It centralizes decision-making and ensures experts lead experts.

Core Principles

  • 1.Eliminate Business Units/Divisions: Move from GM-led verticals (e.g., 'Hosts', 'China', 'Experiences') to central functions.
  • 2.Experts Leading Experts: No generic managers. The head of Design must be a world-class designer; the head of Engineering must be a top engineer.
  • 3.Centralized Prioritization: Resource allocation happens at the top executive level, preventing teams from hoarding resources or building redundant stacks.
  • +1 more...

"If you create a division, your division is as successful as you are a priority. So now you have to advocate for your division... that creates what we call politics."

#functional#consolidation#team
View Deep Dive →
🎯 Product Strategy

A planning framework where the entire company operates off a single, rolling two-year roadmap. This ensures that engineering, design, and marketing are perfectly synchronized for massive, unified launches.

Core Principles

  • 1.The Rolling 2-Year View: Maintain a roadmap that looks 2 years out, updated every 6 months. The immediate horizon is fixed; the distant horizon is flexible.
  • 2.Metrics Subordinate to Calendar: Commit to release dates (e.g., Summer and Winter releases). This forces scope decisions and prevents endless optimization loops.
  • 3.Launches as Episodes: Treat product releases like TV episodes or chapters in a book. Bundle features into a cohesive narrative that marketing can actually sell.
  • +1 more...

"We wanted a company where a thousand people could work, but it'll look like 10 people did it."

#single#consciousness#roadmap
View Deep Dive →
⚡ Execution

A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) on a weekly basis, rather than just reviewing metrics or status slides.

Core Principles

  • 1.Review the Work, Not the Deck: Leaders should look at the product, the code, or the creative assets, not just a presentation about the work.
  • 2.Weekly/Bi-Weekly Cadence: High-frequency reviews allow leaders to unblock teams immediately rather than waiting for quarterly post-mortems.
  • 3.Identify Bottlenecks Personally: By seeing the prototype weekly, a leader can spot if 'the tires are off' and identify exactly which cross-functional dependency is blocking progress.
  • +1 more...

"How do you know they're doing a good job if you're not in the details?"

#'in-the-details'#review#execution
View Deep Dive →
📈 Growth & Metrics

A mental model for goal setting where leaders arbitrarily increase the target by 10x (add a zero) to force the team to abandon current processes and use first-principles thinking.

Core Principles

  • 1.Force a Process Break: If the goal is 10x higher, the current way of working is mathematically impossible. The team *must* invent a new way.
  • 2.First Principles Thinking: Break the problem down to its fundamental components to reconstruct a solution that supports scale.
  • 3.See Potential in People: Use the ambitious goal to signal belief in the team's capability, not just as a demand for more hours.
  • +1 more...

"If you want to improve the speed of a company, then make faster decisions."

#zero'#heuristic#growth
View Deep Dive →
← Browse All Episodes