What it is
A facilitated session where designers present work and peers give focused, constructive feedback against the design’s stated goals rather than personal preference.
When to use it
During Ideate and Prototype, at regular intervals while design is still malleable.
Why (value)
Improves work through diverse perspectives, catches issues early, and builds shared standards across a team.
How to run it
- Presenter states goals, context, and the feedback they want.
- Participants ask clarifying questions first.
- Give feedback tied to goals, not taste.
- Capture themes and action items.
- Presenter decides what to act on.
Inputs and outputs
- Inputs: Work in progress, stated goals, a small group of peers.
- Outputs: Focused feedback and a short list of actions.
Time and effort
Low. 30 to 60 minutes.
Evidence and limitations
Produces expert-review peer judgment, not direct-user evidence; it improves craft and alignment but cannot confirm what users will do. See Evidence and limitations.
Tips and pitfalls
- Critique against goals, not personal style.
- Separate clarifying questions from reactions.
- Keep it safe and constructive, not a status review.
Variations
Formal crit, design jam feedback, and asynchronous written critique.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Design review — Formally review a design against requirements, standards, and stakeholder expectations before it advances.
- Design pairing — Two people design together in real time, combining perspectives and catching issues early.
- Expert review — Have an experienced UX practitioner assess a design and report likely problems and fixes.
