# In-The-Details Review Loop

> A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) weekly rather than just metrics or status slides. Use when feeling product quality is slipping or team is moving too slowly.

- Skill: `coowoolf/in-the-details-review-loop` (Agent Skill)
- Install (CLI): `npx skillmds@latest add coowoolf/in-the-details-review-loop`
- Raw SKILL.md: https://api.skillmd.com/api/skills/coowoolf/in-the-details-review-loop/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: Coowoolf (https://skillmd.com/u/coowoolf)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/coowoolf/in-the-details-review-loop

---


# 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

### 1. 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.

### 2. Weekly/Bi-Weekly Cadence
High-frequency reviews allow leaders to unblock teams immediately rather than waiting for quarterly post-mortems.

### 3. 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.

### 4. 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*