What it is
A structured checkpoint where a design is reviewed against requirements, guidelines, and stakeholder needs to decide whether it is ready to proceed.
When to use it
During Prototype, at stage gates or before handoff, when a decision to advance is needed.
Why (value)
Creates an explicit quality and alignment gate, surfacing gaps against requirements and standards before costly build.
How to run it
- Share the design and the criteria in advance.
- Walk the design against requirements and standards.
- Record issues, decisions, and owners.
- Agree on go, revise, or hold.
- Track follow-ups to closure.
Inputs and outputs
- Inputs: The design, requirements, standards, reviewers.
- Outputs: Decisions, action items, and a readiness call.
Time and effort
Low. A scheduled session plus prep.
Evidence and limitations
Produces expert-review and alignment judgments, not direct-user validation; it checks conformance and consensus, not whether users will succeed. See Evidence and limitations.
Tips and pitfalls
- Review against explicit criteria, not vibes.
- Keep it a decision forum, not open-ended critique.
- Assign owners to every action.
Variations
Stage-gate review, pre-handoff review, and executive review.
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 critique — Gather peers to give structured, goal-focused feedback on work in progress.
- Consistency inspection — Check an interface for internal consistency in patterns, terminology, and behavior.
- Design QA — Check the built product against the approved design to catch implementation drift before release.
