Founder-in-the-Details Operating Model
Rebuild a company like a startup: functional teams, one road map, one shared consciousness, CEO in the work.
- Difficulty
- Expert
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 95%
Chesky's post-2020 overhaul of how Airbnb runs. Instead of delegating product away and running semi-autonomous divisions, the founder re-inserts himself into the details, collapses divisions into functions, and drives one company-wide road map that everyone rows behind. The claim is that clarity and shared direction beat empowerment-by-delegation, which quietly breeds dependencies, politics, and bureaucracy.
Origin
Brian Chesky's account of rebuilding Airbnb during the pandemic, explicitly modeled on how Steve Jobs ran Apple (1998–2011), taught to Chesky by ex-Apple leaders Hiroki Asai (marketing/design) and Jony Ive (design). Chesky also cites Ben Horowitz's warning against product founders delegating away the thing they're best at.
Core principles
- 01The CEO of a product/tech company should be its de facto chief product officer and stay in the details.
- 02Being 'in the details' is not micromanagement; micromanagement is telling people exactly what to do, being in the details is knowing the work well enough to judge it.
- 03Empowerment without direction produces division, politics, and bureaucracy, not speed.
- 04One functional org (design, engineering, product marketing, etc.) beats semi-autonomous divisions that drift onto separate stacks and road maps.
- 05Every leader must be an expert in their domain; there are no pure people-managers.
- 06Fewer, more senior people move faster than many junior ones — adding people slows a project down.
How to run it
- 1
Write down everything, then cut to ~20%
Force every team to document all the work they are doing in one shared sheet, then ruthlessly prune. Aim to keep roughly a fifth of projects so that instead of one team doing five things, several teams do one thing.
Pro tip If someone claims their work is too voluminous to document, that itself is the signal you are doing far too many things.
- 2
Collapse divisions into functions
Replace divisional general managers with company-wide functions — design, engineering, product, product marketing, marketing/communications, sales, operations — so the whole company works off one plan instead of ten divisions going ten directions.
Pro tip Have engineering and design report to the founder/product-led person, not into product.
Watch out Divisional structures subdivide endlessly ('subdivided, subdivided, subdivided'), making the company very hard to turn.
- 3
Run one rolling two-year road map
Replace annual plans and short planning cycles with a single rolling two-year product road map updated roughly every month, with releases packaged into two launches a year. Make metrics subordinate to the calendar.
Pro tip Keep a reserve of resources so you can still pivot quickly to unexpected events (Airbnb housed 120,000 refugees) without derailing the road map.
Watch out Nothing ships unless it's on the road map, except some infrastructure projects.
- 4
Create one shared consciousness
Put the top ~30–40 people into one continuous conversation so leadership shares context and decisions instead of pushing decision-making down into silos.
Pro tip Pull decision-making in rather than pushing it down; centralized clarity is what lets teams move fast.
- 5
Institute a CEO review cadence
Personally review all product and marketing work on a fixed cadence — every 1, 2, 4, 8, or 12 weeks per project. Have a head program manager score every project green/yellow/red for on-track-to-ship, and use the reviews to spot bottlenecks down to the individual contributor.
Pro tip Seeing a semi-assembly of the whole product each week lets you locate the exact blocked person, like inspecting a car prototype and noticing one tire is off.
Watch out Review whether work is on track to ship; you still don't know if it worked until after you ship it.
In the wild
From 2015–2019 Chesky delegated more and empowered teams more, yet the product got slower: by 2019 Airbnb ran ~10 divisions, spent ~$1B on AdWords, and the app 'hasn't changed in like 4 years.' People worked 80 hours to get 20 hours of productive work done. The pandemic wiped out 80% of the business in 8 weeks, triggering the rebuild.
→ Chesky reversed course, got back into the details, and rebuilt Airbnb as a functional, road-map-driven company with fewer than 7,000 employees.
Getting deeply hands-on meant 1–2 years of much heavier work. But once the company turned the corner, teams rowed in the same direction, conflicts and turnover fell, and Chesky no longer needed to sit in meetings because people did the right thing without him.
→ Chesky reports he now has more time on his hands and gets nine good surprises out of ten instead of nine bad ones.
Common mistakes
Delegating away your core strength
Product/engineering founders are told to step away and delegate the product, but they hand off the very thing they're best at and hardest to replace — recreating dysfunction they then get blamed for.
Confusing appeasement with leadership
Founders split the difference between how they want to run the company and how employees want it run, making everyone miserable. People actually want clarity and a shared direction, not a negotiated midpoint — especially since advocates for a project may leave while the project stays.
Is it for you?
Best for
Founder-CEOs of product- or tech-led companies (roughly Series C and beyond) whose org has drifted into divisions, politics, and slow shipping.
Not ideal for
Non-tech, ops-led, or marketing-led companies, or truly independent business units with no shared dependencies — and founders unwilling to invest 1–2 years of intense hands-on work.
From the transcript
“leaders are in the details. And there's this negative term called micromanagement. I think there's a difference between”
“So instead of one team doing three things, three teams should do one thing. So we totally cut down the number of projects.”
“We went to a functional model. We went back to a startup.”
“I stopped pushing decision-making down. I pulled it in. I created one shared consciousness. And I said the top 30, 40 people in the company…”
“So, every project I would do review either every week, every 2 weeks, every 4 weeks, every 8 weeks, or every 12 weeks. There'd be…”
“The more in the details I am, the more time I have on my hands.”
From the episode
Brian Chesky’s new playbook