The 'In-The-Details' Review Loop
"How do you know they're doing a good job if you're not in the details?" — Brian Chesky
What It Is
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.
When To Use
-
Product quality is slipping
-
Team is moving too slowly
-
Leaders feel disconnected from execution
-
Need to unblock cross-functional dependencies quickly
Core Principles
- 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.
- Weekly/Bi-Weekly Cadence
High-frequency reviews allow leaders to unblock teams immediately rather than waiting for quarterly post-mortems.
- 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.
- Micromanagement vs. Details
"Micromanagement" is telling people what to do. "Being in the details" is knowing what is happening so you can ensure quality.
How To Apply
STEP 1: Schedule Weekly Review └── Fixed time slot (e.g., Friday 2pm) └── All key initiatives present actual work
STEP 2: Require Live Demos └── No slides about the feature └── Actually click through the prototype/staging
STEP 3: Ask Unblocking Questions └── "What's blocking you?" └── "Which team do you need help from?"
STEP 4: Follow Up Cross-Functionally └── Send requests to other leaders same day └── Track resolution in next week's review
Common Mistakes
❌ Using reviews to punish rather than to problem-solve/unblock
❌ Reviewing only when things go wrong (reactive) vs. a consistent cadence (proactive)
❌ Allowing teams to substitute slide decks for live product demos
Real-World Example
Chesky reviewing the "Guest Favorites" feature and listing tab designs weekly, allowing him to harmonize the guest and host experiences personally.
Source: Brian Chesky, Lenny's Podcast