What it is
A review that verifies a design conforms to applicable standards, such as platform human-interface guidelines, brand standards, regulatory rules, or an internal design system.
When to use it
Late Prototype into Implement, before release in regulated or standards-bound contexts.
Why (value)
Catches compliance gaps that create legal, platform-rejection, or brand risk before they ship.
How to run it
- Assemble the applicable standards and checklists.
- Review the design against each requirement.
- Mark pass, fail, or not applicable with evidence.
- Log failures with severity and owner.
- Verify fixes against the standard.
Inputs and outputs
- Inputs: The design and the governing standards or guidelines.
- Outputs: A compliance checklist with findings and actions.
Time and effort
Medium. Depends on the number and depth of standards.
Evidence and limitations
Produces expert-review conformance evidence; meeting a standard is not the same as being usable or desirable, which require direct-user evidence. See Evidence and limitations.
Tips and pitfalls
- Use authoritative, current versions of standards.
- Record evidence for each judgment.
- Separate hard requirements from recommendations.
Variations
Platform guideline review, regulatory compliance, brand compliance, and design-system conformance.
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
- Accessibility evaluation — Assess whether a product can be used by people with disabilities, against standards and with assistive tech.
- Consistency inspection — Check an interface for internal consistency in patterns, terminology, and behavior.
- Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.
