# Design Review

A design review is a prepared checkpoint where the right people evaluate readiness, risks, evidence, and tradeoffs before a product decision advances.

- Type: practice
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-review/>)

## What it means

A design review is a structured checkpoint for evaluating a proposed design and deciding what happens next. Unlike an open-ended critique, it commonly includes cross-functional constraints, readiness criteria, and a recorded outcome such as approve, revise, test, escalate, or stop. The review should make decision rights explicit and keep unresolved risks visible.

## Why it matters

Cross-functional problems often appear late because design, engineering, research, content, accessibility, security, legal, support, and operations review different artifacts at different times. A disciplined review brings the necessary expertise together before commitments harden, reduces rework, and creates an auditable rationale for consequential choices.

## When to use it

Use reviews at meaningful risk or commitment points: before implementation, before an irreversible launch, after major research findings, or when a change affects safety, privacy, accessibility, policy, or multiple teams. Do not require a heavyweight gate for every small, reversible decision.

## How it works

1. Name the decision, owner, reviewers, decision criteria, scope, and possible outcomes before scheduling the review.
2. Share a concise pre-read with problem framing, user evidence, flows, edge cases, content, accessibility notes, metrics, constraints, and known risks.
3. During the review, focus discussion on criteria and unresolved tradeoffs; separate clarification, feedback, and final decision-making.
4. Record decisions, dissent, conditions, owners, deadlines, evidence gaps, and any risks explicitly accepted by an authorized person.
5. Verify required changes and close the loop; improve the review process when it becomes ceremonial, overloaded, or routinely too late.

## A practical example

Before launching account recovery, a marketplace holds a review with design, engineering, fraud, privacy, accessibility, support, and research. The team pauses launch because the fallback flow excludes people who changed phone numbers and offers no accessible identity-recovery route. Owners and retest criteria are recorded before approval.

## Where it breaks

Reviews can become bureaucratic gates, executive taste sessions, or diffuse meetings where no one owns the decision. Excessive review slows reversible work, while too little review hides high-impact risk. A review also reflects available evidence; approval is not proof that a design is ethical, usable, accessible, or safe in practice.

## Common mistakes

- Inviting many stakeholders without defining who advises and who decides.
- Reviewing screenshots while omitting states, content, data use, failure modes, and operational consequences.
- Treating approval as permanent even when later evidence changes the risk.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-review/#visualization-design-review>)

## Sources

1. [How to Use Design Reviews for Cross-Team Collaboration](<https://www.atlassian.com/blog/loom/design-review>) — Atlassian · Practitioner guidance
2. [Design Review: Principles and Practice](<https://www.designcouncil.org.uk/fileadmin/uploads/dc/Documents/Design%2520Review_Principles%2520and%2520Practice_May2019.pdf>) — Design Council · Institutional guide
3. [Design Critiques: Encourage a Positive Culture to Improve Products](<https://www.nngroup.com/articles/design-critiques/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Design Critique](<https://wiki.soroush.uk/topic/design-critique/>)
- [Stakeholder Map](<https://wiki.soroush.uk/topic/stakeholder-map/>)
- [DesignOps](<https://wiki.soroush.uk/topic/design-ops/>)
