Skip to content
Back to journal
Design

Design review without the pain — a process that doesn't kill velocity

How we set up design review so the team doesn't lose days to revisions and the client still sees clear progress every Friday.

2025-01-217 min readDesign · Review · Velocity

Every designer knows that a review can cost two hours or two weeks — it depends entirely on the format. We landed on a simple system after four projects, and it now scales to large teams.

One channel, one board

All revisions live in Figma comments tagged P0/P1/P2 by priority. No Slack threads, no spreadsheets. If a revision isn't in Figma, it doesn't exist. That alone removes 80% of context loss.

Sync once a week, async every day

One 30-minute call on Friday, everything else as comments and Loom videos. Designers stop sitting in meetings and start designing.

The two-rounds rule

Two revision rounds max per screen. If we hit a third round, the brief or the goal is broken — we go back up the stack instead of pushing pixels.

Tones instead of taste

Instead of "I don't like it" we ask the client to pick a tone — more premium, more engineered, more warm. That turns taste into a direction we can iterate against.

Start a project

Start a project