Design Critique
A design critique is a structured group session where peers analyze work against product objectives and usability principles.
65 resourcesintermediate
Unlike informal feedback or executive approval meetings, critique evaluates whether design solutions solve the defined user problem. It fosters craft excellence, uncovers blind spots and builds team alignment.
How it works
An effective design critique follows structured roles, clear context and ground rules.
- Presenter context setting states the user problem, target persona, business constraints and specific areas needing feedback.
- Objective evaluation analyzes how effectively the design choices achieve the stated user and business goals.
- Inquisitive questioning asks why specific layout decisions were made rather than asserting subjective personal tastes.
- Actionable synthesis records concrete questions, accessibility concerns and edge cases for the designer to investigate next.
When to use it
Schedule recurring design critiques at predictable milestones in the product development cycle.
- Mid-fidelity exploration reviews structural wireframes before designers invest days in high-fidelity visual styling.
- Pre-engineering handoff ensures interactive states, error screens and responsive layout adaptations are fully covered.
- Design system updates evaluates proposed new component variants across multiple squad use cases before publishing.
- Team skill development helps junior designers learn how to articulate design rationale and receive constructive feedback.
Common mistakes
Critiques easily deteriorate into subjective opinion battles without disciplined facilitation.
- Confusing critique with personal preference, saying 'I don't like purple' instead of evaluating contrast and hierarchy.
- Critiquing work without knowing the goals, offering solutions before understanding the customer constraints.
- Turning the session into live co-designing, where attendees try to redesign layouts on the spot instead of giving feedback.
Key takeaways
- Design critique evaluates solutions against stated user objectives, not personal aesthetic preferences.
- Presenters must define the persona, problem and specific feedback needed before showing mockups.
- Ask clarifying questions to understand design rationale before suggesting changes.
- Avoid live co-designing during critique sessions; let the owning designer explore solutions afterward.
Learn this
Lessons and exercises mapped to this concept.
CourseIntroduction to Design SystemsMaster the architecture, tokens, atomic components, multi-brand theming, code pipelines, and enterprise governance required to build and scale production design systems.CourseProduct Management FoundationsMaster modern product leadership: root-cause problem discovery, customer-driven vision, cross-functional collaboration, agile execution, and measurable business impact.
Common questions
- How does a design critique differ from a design presentation?
- A presentation showcases finished work to persuade or inform stakeholders. A critique evaluates unfinished work with peers to identify flaws and improve quality.
- How should a designer handle conflicting feedback in a critique?
- Evaluate feedback against the user's primary goal and empirical research data, and run usability tests if two approaches have equal theoretical validity.