Key Takeaways

  • Conventional management advice tells chief executives to speak only to direct reports, a practice Chesky argues blinds leadership to operational rot until a crisis hits.
  • Independent autonomy causes corporate drift; Chesky replaces it with institutional backing, viewing his role as an offensive lineman clearing blockers for junior staff.
  • High standards require constant early correction, comparable to a golf coach watching a student swing one hundred times until the motion becomes muscle memory.
  • Project reviews must include every layer of management simultaneously, seating the individual contributor next to their managers so the chief executive can review work directly.
  • Scope errors and unmonitored teams are eliminated before launch by using Chesky's Project Setup and Rhythm Framework.

The Chesky Project Setup and Rhythm Framework

1. Upfront Setup Checklist: Before launching work, verify all essential conditions: establish a clear vision of what you are trying to do, ensure the right personnel are staffed, designate a clear directly responsible individual (DRI), allocate all necessary resources, secure total alignment across the organization, implement the right process, and correctly calibrate scope (ensuring the initiative is neither too big nor too small).

2. Establish Cadence and Review Rhythm: Create an unyielding recurring check-in cadence scaled to project priority (e.g., daily for critical company-saving initiatives, weekly or bi-weekly for core roadmaps, monthly for steady-state projects).

3. Full Chain of Command In the Room: Bring the individual contributor doing the actual work together with all intervening managers in a single room to eliminate bureaucratic lag and enable rapid CEO approvals or course corrections.

4. Calibrated Overruling (The 10% Rule): Listen to everyone's perspective, but reserve final decision-making power. Target overruling the chain of command roughly 10% of the time to push for non-obvious excellence; overruling 50% means the wrong team is in place, while overruling 0% means the executive is adding no unique value.

When This Works (and When It Doesn't)

Chesky built this operating rhythm after conventional delegation nearly derailed Airbnb before the pandemic. As he puts it: “The reason projects go in the wrong direction is because of one or two reasons: they start wrong, they're not set up for success, or they're off in an island without oversight.” (play from 1:00:09) Bringing every intervening manager into the room stops middle management from filtering bad news. It also kills the endless cycle of pre-meetings where junior staff spend three weeks preparing a deck just to ask a basic product question.

This method breaks down when founders lack editorial restraint. You cannot sit in daily or weekly reviews for forty separate tracks without grinding the entire company to a halt. If an executive overrules their leads on routine execution rather than the critical ten percent, managers stop thinking for themselves and wait to be told what to do. The system only works if the founder acts like an offensive lineman clearing blocks for a runner, rather than a micromanager carrying the ball on every play.

What to Do With This

Take your company's most important product initiative scheduled for next month. Instead of waiting for a monthly executive summary, schedule a forty-five-minute working session with the designer or engineer doing the actual work, alongside their immediate lead.

Run the Upfront Setup Checklist in the first ten minutes: confirm the exact DRI, lock the scope so it cannot bloat, and verify that no cross-team dependencies are unassigned. During the review, let the builder present the work raw without polished executive slides. Listen to the managers, but test the details yourself. If an element falls short of your standard, step in to correct the swing immediately. If it looks sound, step back and let the runner sprint.