practiceLeadership & teams

Design Review

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

Download Markdown (.md)

01What 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.[1][2][3]

A prepared readiness checkpoint with decision authority Bring the right evidence and people together, decide explicitly, then track conditions
  1. 01Define decisionScope, maturity, criteria, authority, and possible outcomes
  2. 02Prepare evidenceIntent, research, design, risks, feasibility, and open issues
  3. 03Review togetherRight product, design, engineering, content, and risk expertise
  4. 04Resolve outcomeApprove, approve with conditions, revise, or stop
  5. 05Record rationaleDecision, owner, conditions, and unresolved risk
  6. 06Verify conditionsFollow through before the work advances

A review should match the risk and maturity of the work; an audience without clear decision rights can create delay and performative approval.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. How to Use Design Reviews for Cross-Team CollaborationAtlassian · Practitioner guidanceHow to Use Design Reviews for Cross-Team Collaboration
  2. Design Review: Principles and PracticeDesign Council · Institutional guideDesign Review: Principles and Practice
  3. Design Critiques: Encourage a Positive Culture to Improve ProductsNielsen Norman Group · Professional guidanceDesign Critiques: Encourage a Positive Culture to Improve Products
View saved topics

Start typing to search titles, definitions, categories, and frameworks.