What it is
A systematic inspection that checks whether components, terminology, interactions, and visuals are applied consistently across an interface and against the design system.
When to use it
Late Prototype into Implement, before release or during design-system adoption.
Why (value)
Inconsistency erodes trust and learnability; this inspection catches drift that accumulates as products grow.
How to run it
- Define the consistency dimensions and reference standards.
- Inventory screens and components.
- Compare each against the standard and each other.
- Log inconsistencies with location and severity.
- Route fixes to owners.
Inputs and outputs
- Inputs: The interface, design system or style guide, inspectors.
- Outputs: A log of inconsistencies and remediation actions.
Time and effort
Medium. Scales with the surface area reviewed.
Evidence and limitations
Produces expert-review conformance evidence, not direct-user data; consistency aids usability but is not proof of it. See Evidence and limitations.
Tips and pitfalls
- Compare against an explicit standard, not memory.
- Distinguish intentional variation from drift.
- Feed recurring issues back into the design system.
Variations
Visual, interaction, terminology, and cross-platform consistency checks.
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
- Interface audit — Catalog all the UI elements and patterns in a product to expose redundancy and inconsistency.
- UI inventory — Collect every variant of each interface component to see the real scope of your UI.
- Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.
