Notes — Brian Chesky on Airbnb and Product

Four questions [Adler frame]

Q1 — What is it about? How Brian Chesky restructured Airbnb after COVID — from a divisional, PM-centric, growth-marketing-dependent company back to a functional, design-led, founder-driven operation. Two themes: (1) why companies slow down and develop bureaucracy (the divisional anti-pattern arc); (2) what Airbnb did to reverse it (functional org, CEO review cadence, product-marketing integration, single roadmap, launches).

Q2 — How is it argued? Primarily through first-person experience: Chesky describes the 2019 crisis (billion-dollar AdWords spend, no product progress in four years, slow-moving bureaucracy), the intervention (pandemic-as-clarifying-near-death), and the systematic changes. Supplemented by reference to Steve Jobs/Apple, Jony Ive, Alfred Sloan/DuPont divisional model origin, John Wooden/Andy Grove on leadership, Harvard happiness study.

Q3 — Is it true? The divisional-to-bureaucracy decay arc rings true and maps to well-observed patterns (Conway’s Law, Christensen’s innovator’s dilemma). The claim that “the more involved I got, the more time I had” is counterintuitive but is explained as a lag effect: intense involvement for 1–2 years to establish culture, then the culture runs itself. This has support in the “culture is what happens when you’re not in the room” principle. The product-marketing integration thesis directly echoes Dunford (Product Positioning) — can’t tell the story means can’t know if the product is right. The “add a zero” method is a well-known forcing function for first-principles thinking.

Q4 — What of it? For product founders: the delegate-and-empower cycle often destroys the thing founders are best at. The CEO should be the de facto CPO. “Leaders in the details” is distinct from micromanagement — the board reviews the CEO’s work without dictating it. The single roadmap + semi-annual launches + CEO review cadence is a replicable structure. The product-marketing integration is the mechanism that makes launches work. For org design: divisions create dependencies → advocacy → politics → bureaucracy → complacency. The functional model is the reversal. The pace of the team is governed by decision speed; decisiveness compounds.

Glossary

Divisional model — org structure where a company is divided into business units, each owning product, marketing, engineering, and operations for their segment. Enables autonomy; creates silos, dependencies, and political behaviour over time.

Functional model — org structure where all design reports to design, all engineering to engineering, all marketing to marketing — regardless of product area. PMs at Airbnb don’t own engineers or designers; they influence. All resources are shared and deployable across product areas.

Product marketing (Airbnb definition) — the merged function combining inbound product development (traditionally PM) with outbound marketing responsibilities. The insight: you can’t build a product unless you know how to talk about it; you can’t market a product unless you know how to build it.

CEO review cadence — Brian reviewing all product and marketing work on a regular rhythm (weekly/bi-weekly/monthly/quarterly depending on project stage). The mechanism: if something isn’t happening, the review surfaces it; instead of politics, the review creates direct accountability. Allows the CEO to feel the equivalent of an assembly-line view of a complex product.

Leaders in the details — Chesky’s formulation: being in the details does not mean telling people what to do (= micromanagement). It means knowing enough to evaluate whether people are doing a good job, identifying bottlenecks, and holding accountability. Analogy: the board reviews the CEO’s work without dictating it.

Single shared roadmap — one rolling 2-year product roadmap for the entire company; updated monthly; nothing ships unless it’s on the roadmap. Creates shared consciousness. Two annual launches (May and November) package everything that ships. Previously: three-month planning cycles with separate divisional roadmaps.

Performance marketing as laser, brand marketing as chandelier — Joe Gebbia’s metaphor (Chesky attributes it). Performance marketing = laser, can light up a corner of a room (precise, efficient, non-compounding). Brand/product marketing = chandelier, lights up the whole room (compounding, builds long-term advantage). Most companies overuse the laser.

Add a zero — Airbnb’s internal phrase for 10X thinking. Not a literal mandate to hit 10X; a forcing function to think about the problem differently — if you could only achieve this at 10X, you’d need to change the approach, which requires understanding the problem at a foundational level.

Fake work — activities that feel like work but don’t move the ball. Responding to emails that set your agenda. Meetings taken because people requested them, not because they’re strategically necessary. Reactive behaviour crowding out proactive work.

The divisional company decay arc

Chesky describes a predictable organisational failure mode he calls “the general arc that winds up happening”:

1. Different technical stacks + technical debt — separate teams drift onto incompatible infrastructure.
2. Dependencies — teams all need shared services (payment platform, marketing). Bottleneck builds like a deli queue.
3. Resource capture — dependent teams start building their own versions of shared services to avoid bottleneck. “Give me the resources and I’ll build this group myself.” → Functional duplication.
4. Division formation — teams become self-sufficient divisions, each with their own roadmap.
5. Advocacy — each division advocates for its own interests. People build relationships to get resources. → Politics.
6. Subdivision — more specialisation, more boundaries, more interdependence. → Bureaucracy.
7. Lack of accountability — hard to know who’s doing what, which direction things are going. → Complacency.
8. Stall — fast-growing company becomes slow-moving bureaucracy. “10 marketing efforts and no customer heard anything. Thousands of engineers shipped products but customers can’t name one thing.”

Chesky’s heuristic: the health of an organisation = how close is engineering to marketing? At dysfunctional companies, they’re in separate universes.

The Airbnb reversal (post-COVID restructuring)

Changes made in 2020–2022:

Result: fewer conflicts, less turnover, more aligned team, CEO has more time (paradoxically), 9 of 10 surprises now positive vs. formerly 9 of 10 negative.

Product-marketing integration

“You can’t build a product unless you know how to talk about the product.”

This directly parallels Product Positioning (Dunford): the story comes first, and the story shapes the product. At Airbnb:

• First thing in any feature development: figure out the story.
• The story dictates the product because a cohesive story requires a cohesive product.
• Goal: a company where 1,000 people work but it looks like 10 people did it.

Performance marketing as a growth channel doesn’t create compounding advantage; it’s an arbitrage business (works only if ROI is sustainably high). Product marketing educates customers on new capabilities — creating organic adoption and long-term brand.

The two launches a year (May, November) force coherence: nothing ships unless it’s on the roadmap, and every ship is packaged into a story. This discipline replaced the endless A/B-tested feature trickle that produced no customer awareness.

CEO as CPO

“The CEO should be basically the chief product officer of a product or tech company. If the CEO is not the chief product officer then I don’t know if they’re a product or tech led company.”

This is the heart of the structural change. The delegation-to-empowerment cycle takes the founder away from their primary comparative advantage. Paradox: the more the CEO delegated, the slower the company moved. Teams interpreted slowness as caused by over-involvement, so they asked for more autonomy, which made things slower.

The intervention required hands-on involvement for 1–2 years to reset culture. Once culture is established, the CEO doesn’t need to be in every meeting — the culture replicates the decisions. Culture = what happens when you’re not in the room.

Functional experts as leaders: every executive must be an expert in their functional domain — not just a people manager. A design leader manages design first, people second. Analogy to Jony Ive: interchangeably designing and leading.

Add a zero / first-principles thinking

Adding a zero (10X goal) is a thinking tool, not a performance mandate. Purpose: the current process cannot scale 10X, which forces genuine first-principles decomposition of the problem.

Structure of the Wooden coaching story: great coaches see potential in players they don’t see in themselves. Pushing teams isn’t saying “you’re not good enough” (fixed mindset) — it’s saying “I believe you have more in you” (growth mindset). Competence + motivation (Andy Grove’s framing): if it were life-or-death, could they do it? The answer reveals potential.

Bias for action: “We don’t circle back next week. Let’s stay in this meeting until it’s done. Who’s responsible? What are you doing? I’ll call you in the morning.” Pace = decision speed.

Personal operating system (burnout and relationships)

Three pillars: health, relationships, work.

Health: 20 minutes morning cardio; weights 3–4×/week; bodybuilding diet (5–6 meals/day); sleep discipline.

Relationships: Harvard Study of Adult Development (85 years) — secret of happiness = healthy relationships. Scheduled group chats and annual trips with high school and college friends. New shared experiences essential (old friends only discussing old stories). Treat relationships proactively, not reactively.

Work anti-pattern: founders who only respond to inbound let their email/calendar set their agenda. Counter: derive the year’s relationships and meetings from strategy, not from who reaches out. Ask: if my life ends sooner than expected, who do I want to have spent time with?

“Fake work” = activities that feel productive but don’t move the ball.

Industrial design as leadership foundation

Chesky’s RISD industrial design background explains the design-led approach. Industrial design — unlike graphic design or architecture — requires:

• Working with engineers (mechanical, electrical).
• Understanding manufacturing constraints.
• Accountability to sales (if the product doesn’t sell, the designer is on the hook).
• Understanding marketing and strategy.

Industrial designers must hold functional, emotional, business, and technical dimensions simultaneously. This is the training that shaped his approach to product development, org structure, and product marketing integration.