tpo-design-review-checklist

Use a structured design review checklist covering requirement alignment, user flow, visual hierarchy, accessibility, and technical feasibility. Gather the PRD, technical specification, user stories, and screens first, then assign a verdict such as Accepted or Rejected with documented fixes.

A design review checklist should cover requirement alignment, user flow completion, information architecture, visual hierarchy, component consistency, forms and validation, accessibility, responsive behavior, microcopy, and technical feasibility. Each section needs explicit pass criteria and reject conditions.

Reject a design when users can get stuck in the flow, the primary action is unclear, keyboard-only operation is impossible, color is the only status indicator, or required fields and error guidance are missing. Major requirement or feasibility gaps also warrant rejection.

A design review requires the Product Requirements Document, technical specification, user stories, acceptance criteria, target user type, business goal, screens or prototype, user flow, existing design system, platform constraints, and mobile and desktop requirements.

Document findings with a final review template recording the verdict, scope reviewed, pass/fail per section, and a prioritized fix table with priority, issue, required fix, owner, and acceptance criterion. End with a clear final decision statement.