Design Reviews, capturing context at speed
summary
A design-review workflow records proposals before work starts, standardizes templates, and automates publishing so context survives autonomy and churn; teams write markdown in GitHub, render with MkDocs and mermaid JS, and use templates plus PR review. After a 12‑month rollout the system shows 500+ closed PRs and 100 contributors across 40 teams, reduces unexpected interactions and duplication, and lets junior engineers document and ship with clearer rationale.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 8:26Why docs matter
- 13:57Design reviews as solution
- 21:02Working with engineers
- 27:01Building the review platform
- 31:38Results after 15 months
- 34:29Q&A
related talks
40mNavigating engineering-focused environments
29mEffective design and engineering collaboration
20mDesign critique from hell
14mRethinking Designer-Developer Collaboration
57mBulletproof development with design systems
24mDesign from the realm of open-source
19mDesignOps: The API of design teams
18mDesign Systems in Practice