See pricing
Airbnb CEO Brian Chesky: “I Was a Great Founder and a Terrible CEO”
How I Built This with Guy RazLeadership

Airbnb CEO Brian Chesky: “I Was a Great Founder and a Terrible CEO”

Brian Chesky explains how Airbnb's breakout success hid deep management problems until COVID erased 80% of the business in eight weeks. It is a sharp lesson for PMs on stage-appropriate leadership, focus, and why direct involvement can matter more than clean delegation in a scaling company.

November 2, 2026 · 76 min listen · 13 min read · Brian Chesky
0:00
–:––

Context

Brian Chesky reflects on nearly 20 years of leading Airbnb, from its scrappy founding to becoming a public company worth more than $100 billion. The most useful part for PMs is not the origin story. It is his argument that much of the standard advice about scaling, delegation, and executive hiring can break a young company if it is applied too early. The episode becomes especially concrete when Chesky explains how COVID, which wiped out 80% of Airbnb's business in eight weeks, forced him to rebuild how he led the company.

The Big Idea

Early-stage and scaling companies cannot delegate judgment, standards, and direction too soon. Brian Chesky's core lesson is that leadership only started working at Airbnb when he stopped treating distance as maturity and got back into the details.

His point is not that leaders should control everything forever. His point is that delegation works only after the company has learned what good looks like, what matters most, and how to move in one direction without constant drift.

Key Insights

Founder and CEO diverge

Chesky's blunt self-assessment is that he was naturally a strong founder and naturally a poor CEO. His reasoning is useful: many founders have been "practicing" founding since childhood by making things, selling things, and starting little projects, but almost nobody has prior reps at being a CEO. That is why founder instincts can feel natural while CEO work, such as setting culture, aligning people, and creating accountability when you are not in the room, feels deeply counterintuitive.

Experience must fit stage

  • Chesky says he hired experienced executives, often much older than him, and usually deferred when their judgment conflicted with his intuition.
  • He later concluded that this was usually a mistake, not because experience is bad, but because much of that experience came from large companies that were being managed, not built.
  • His stage-specific lesson was to hire people only a little ahead of the company's current stage, people who are still comfortable building through ambiguity instead of importing mature-company habits.

Success can hide chaos

Airbnb kept growing, which made it easy to miss how much internal chaos had built up. Chesky's point is that a strong business model can mask weak management for a long time. He compares this to eBay versus Amazon. eBay had a great business model, while Amazon had to survive on hard execution. His lesson is that growth is not proof of operating health. Sometimes it is just cover.

Focus beats parallel ambition

After Airbnb found success, Chesky says the company became overconfident. The hidden assumption was: if they could build one hit, they could build many at once. He thinks that was hubris. Airbnb had iterated roughly 30 versions of its original website before the core product worked, yet later the company funded new teams and expected the next big thing to appear with far less rigor. For PMs, this is a warning that resource abundance often lowers discipline.

Crisis forced a reset

  • COVID cut Airbnb's business by 80% in eight weeks.
  • Chesky says this was the first time being a good CEO became life-or-death instead of a nice-to-have improvement.
  • That pressure forced him to simplify, cut projects, make hard calls, and stay close to the work.
  • The practical lesson is that crisis can reveal which leadership habits are optional and which ones were quietly breaking the company.

Details create alignment

Chesky says the biggest shift came when he stopped treating leadership as stepping away and started treating it as being present in the details. Studying Steve Jobs reinforced this. He learned that simplification, focus, and high standards do not spread by memo. They spread because a leader repeatedly reviews the work, sets the direction, and makes trade-offs visible. For PMs, this matters because teams rarely converge on quality through autonomy alone.

Loneliness hurts leadership

Chesky describes the post-IPO period as deeply lonely, and he links that loneliness to worse leadership. He had few close relationships outside work, he was not very vulnerable with employees, and his identity had blurred into being "the Airbnb guy." President Obama helped him see that he was disconnected from friends and roots. The PM lesson is not personal wellness advice for its own sake. It is that leaders who lose grounding, candor, and real relationships become easier to isolate from truth.

Mental Models & Frameworks

Hire slightly ahead

  • In a young company, do not assume the best hire is the most credentialed person available.
  • Chesky's model is to hire people slightly ahead of the current stage, not many stages ahead of it.
  • This works because stage-fit matters more than prestige when the real job is still invention.
  • Use this when a team is scaling but still defining product, process, and decision rights at the same time.

Empowerment beats autonomy

  • Chesky draws a sharp line between empowerment and autonomy.
  • Empowerment means the leader removes blockers, secures resources, and helps sharpen direction.
  • Autonomy over company direction means different teams can start acting like separate companies.
  • He is happy to give autonomy in craft, such as how an engineer codes, but not autonomy over where the company goes.

Start, check, finish

Chesky says leaders should be involved at the beginning and end of important projects, then check in with a defined rhythm during the middle. His setup checklist is practical:

  • clear vision
  • the right people
  • a directly responsible owner
  • enough resources
  • the right scope
  • the right process

His claim is that if a six-month project ends in a surprise, the failure usually happened either at the start or because nobody stayed connected during execution.

Skip levels for truth

  • For important work, Chesky brings the full chain of command into one room, including the person doing the work and all the managers above them.
  • This reduces filtered information and lets junior contributors surface reasoning directly.
  • He says a leader should overrule the chain only occasionally. 0% means the leader adds no value. Around 10% is healthier. Around 50% means either the leader is wrong or the org has the wrong people.
  • Use this model when a project matters enough that you cannot afford to hear only polished summaries.

Repetition teaches the bar

  • Chesky used 70 revisions of one press release to teach what excellence looked like.
  • The point was not to rewrite every future document 70 times.
  • The point was to build shared muscle memory so future reviews could be lighter.
  • This is a useful model when a team keeps missing the quality bar because nobody has seen the bar made explicit.

Decision Principles

Principle: Delegate after standards exist

When: a product leader feels pressure to step back because the company is getting larger or the org looks mature on paper.

Why: Chesky's lesson is that delegation only works after people already know the quality bar, the strategy, and how decisions get made. Pulling back before that does not create leverage. It hides drift.

Principle: Test intuition through dialogue

When: your intuition conflicts with a more experienced executive, advisor, or stakeholder.

Why: Chesky says blind deference was usually a mistake. The answer is not to assume your intuition is always right. The answer is to force the reasoning into the open and work through it together.

Principle: Say no to unify

When: several strong leaders want to push the roadmap or company in different directions.

Why: Chesky argues that five smart leaders pursuing five agendas do not create optionality. They create fragmentation. The job of leadership is to produce one coherent direction.

Principle: Audit information yourself

When: critical decisions depend on updates that have been filtered through several management layers.

Why: Chesky rebuilt his confidence in the company by hearing directly from people close to the work. Skip-level review is not only about trust. It is about signal quality.

Trade-offs & Nuance

Details can become micromanagement

  • Chesky knows people describe his style as micromanagement.
  • His defense is that being in the details is not the same as dictating every craft decision.
  • This works when the leader uses detail to align direction, teach standards, and remove blockers.
  • It breaks when the leader rewrites everything forever or overrules so often that ownership disappears.

Trust can still backfire

  • In his personal life, Chesky chose to trust people and accept the risk of getting hurt.
  • In company building, he learned that trusting people without staying close to the work was not enough.
  • The nuance is that trust and verification solve different problems. Trust builds relationships. Verification protects execution.

Ideals must face reality

  • Chesky originally resisted advertising, hotels, and loyalty programs because they clashed with Airbnb's identity.
  • He later reconsidered those positions after listening to users and the market.
  • The deeper lesson is that product ideology becomes dangerous when it stops being a principle and starts becoming an excuse to ignore real behavior.

Crisis buys permission to change

  • COVID gave Chesky permission to change Airbnb's operating model because survival mattered more than executive comfort.
  • The trade-off is that this kind of reset can drive away senior people who preferred the old model.
  • A leader still has to prove the new approach works after the emergency passes.

Common Mistakes

Mistake: Hiring prestige over fit

  • Chesky hired highly experienced executives and then deferred to them.
  • The problem was not that they were incapable. The problem was that many knew how to manage scale, not build through uncertainty.
  • Better approach: hire for stage-fit first, then experience within that stage.

Mistake: Avoiding hard people calls

  • Chesky says he was conflict-averse and hoped struggling leaders would recognize the problem themselves.
  • He later learned that "a pitcher never takes themselves off of the mound."
  • Better approach: address the issue early through direct feedback, role redesign, or exit.

Mistake: Letting growth prove health

  • Airbnb's strong business model made it easy to confuse growth with good leadership.
  • That delayed hard fixes around focus, coordination, and standards.
  • Better approach: treat execution quality and organizational health as separate from topline success.

Mistake: Starting too many bets

  • Chesky says Airbnb forgot how hard it had been to build the first successful product.
  • Later, the company spread resources across too many parallel ideas without the same rigor.
  • Better approach: keep startup discipline even after the company has money, brand, and momentum.

Practical Application

Map where direction fragments

Before the next roadmap review, list every major initiative and name who is truly setting direction for it. If each initiative effectively has its own mini-CEO, the product org is already drifting toward multiple companies instead of one strategy.

Add a start checklist

For every large initiative, use Chesky's startup conditions before work begins:

  • what is the vision
  • who is the directly responsible owner
  • are the right people on it
  • is the scope right-sized
  • what resources are blocked
  • what review rhythm will the team use

This is the simplest way to catch the problems that usually show up six months later.

Run skip-level reviews

Pick one critical product area and bring the person doing the work, their manager, and the managers above them into the same review. Use the meeting to hear unfiltered reasoning, expose disagreements early, and make one clear decision in the room.

Set review rhythms explicitly

Choose the review cadence for each important initiative before execution starts. Chesky says only a few projects need daily attention, more can run weekly or biweekly, and some only need monthly review. The important part is that the cadence is chosen on purpose.

Teach one quality standard

Choose one artifact, such as a PRD, launch memo, onboarding flow, or press release, and review it much more deeply than feels normal. Chesky used 70 revisions of one press release to make the quality bar visible. Once the team shares that bar, lighter review becomes possible.

Write the no list

Ask each product leader which initiatives they would stop first if focus suddenly became a survival problem. This is a practical way to test whether the roadmap reflects conviction or just accumulated yeses.

Questions to Consider

  • Where is your product organization using experienced hires or delegated autonomy to avoid making a hard strategic choice itself?
  • Which initiatives would you stop first if your business suddenly lost 80% of demand and survival depended on focus?
  • What important project could drift for six months today because nobody set a clear start condition, owner, or review rhythm?
  • In which product area are you hearing only manager summaries instead of the reasoning from the people closest to the work?
  • What belief about your market, such as rejecting hotels or rejecting loyalty programs, might actually be an identity statement rather than a tested fact?

Bottom Line

Brian Chesky's core lesson is that scaling a company does not mean withdrawing from it. Airbnb improved when he stopped mistaking distance for maturity, got back into the details, and used focus, repetition, and direct information flow to teach the organization what good looked like.

Case Studies Mentioned

Airbnb's COVID leadership reset

When COVID hit, Airbnb lost 80% of its business in eight weeks. Chesky says that was the first moment when being a good CEO became existential rather than aspirational. The response was not abstract inspiration. It was simplification, hard prioritization, project cuts, and hands-on involvement. The lesson is that crisis can expose the real operating model of a company very quickly.

The seventy-draft press release

Chesky describes reviewing one press release through roughly 70 versions. The point was to establish the quality bar, not because every press release should take 70 drafts forever. Once the team internalized what excellence looked like, later reviews could be lighter. It is a concrete example of how standards are taught through repetition.

Airbnb.org scaled core mission

Airbnb.org started from an idea the founders had in 2008 and became real after Hurricane Sandy in 2012, when a host asked to house evacuees for free. Chesky says the effort later expanded to housing 20,000 Afghan refugees, 100,000 refugees after Russia invaded Ukraine, and providing 70,000 free nights during the Los Angeles fires. Airbnb now plans to fund one million nights of free housing per year over the next five years. The product lesson is that mission work scales best when it builds on the company's existing superpower.

People to Follow

Brian Chesky

Airbnb's co-founder and CEO is useful to follow for his thinking on founder-led companies, design-driven leadership, and how quality standards get built inside product organizations. This episode is especially valuable because he is unusually candid about where conventional management advice failed him.

Notable Quotes

"I think I was pretty much naturally a great founder and I was naturally a terrible CEO, which is a very classic story." (Brian Chesky)

"That is what you do once you're very mature. That is a death sentence to a young company." (Brian Chesky)

"The job of a CEO is to say no, probably more than to say yes." (Brian Chesky)

"You'll have empowerment, but not autonomy." (Brian Chesky)

AI PM course

Everyone hears the same episodes.
Few can do what they describe.

Start for free