How I Run Design Reviews That Actually Improve Work
Most design reviews devolve into opinion wars. Here's the lightweight ritual I use to make critique fast, fair, and focused on user outcomes.
Design reviews can be brutal. Without structure, they become a room full of opinions dressed up as expertise. Here's what I've learned running reviews at two high-growth startups.
The problem with most reviews
The default format — "show your work, take feedback" — creates three failure modes:
- HiPPO effect: the highest-paid person's opinion wins by default
- Vague feedback: "I don't like the font" with no criteria attached
- Solution-first feedback: reviewers redesign on the spot rather than naming the problem
The ritual that fixed it
I borrowed from Amazon's silent reading rule and lightened it. Here's the 30-minute format I now use for every significant design milestone:
5 min — context (designer only)
State the problem, constraints, and what specific input you need. "I want feedback on the onboarding flow's value clarity — not the visual style."
8 min — silent review
Everyone reads the brief and examines the work independently. No talking. Notes go on sticky notes (Figjam or physical).
15 min — structured critique
Go around the room. Each reviewer reads one note at a time, starting with: *"I noticed…"* or *"I wondered…"*. No rebuttals allowed during this phase.
2 min — designer's call
Designer synthesises, asks one clarifying question, and declares the next action.
Why it works
The silent phase kills the first-mover bias. The sentence starters replace "I think" with observation and curiosity. The designer's closing call keeps ownership where it belongs.
I've run this format with teams of 3 and 20. It scales. Try it on your next review.