Research complete

FN The Async Review Playbook for Distributed Design Teams
Written Critique in Practice | By Marta Kellerman | Fieldnotes Weekly
Async collaboration report: review latency, handoff quality, decision logs
P Seven Patterns for Written Design Critique
The Case Against the Live Design Review
Review turnaround benchmarks across 214 product teams

I looked at how product teams spread across time zones actually run reviews, and pulled out the patterns that repeat. The fastest teams front-load context: a short written brief, a walkthrough recording under six minutes, and one explicit decision they want made. Feedback lands in threads with named owners instead of open comment pileups, and each thread closes on a logged decision. Median turnaround sits near 19 hours when the brief states a deadline, and slips past three days when it doesn't.

How Distributed Teams Run Async Design Reviews

Across the teams surveyed, the async review has stopped being a fallback for missed meetings and become the default path a design takes on its way to build. The shape is consistent: context first, feedback second, decision last — with each step written down where the next person can find it.

What separates the teams with a 19-hour median from the ones stuck at four days is rarely tooling. It is whether the person requesting review states what they want decided, and by when.