What it is
A focused catalog of all variants of each interface component (every button, input, card, and so on), gathered onto shared boards to expose redundancy and seed a design system.
When to use it
During Implement, as the first concrete step toward a design system or component consolidation.
Why (value)
Turns a vague sense of inconsistency into a countable inventory, which both motivates and scopes design-system work.
How to run it
- Pick the component categories to inventory.
- Capture every variant found across the product.
- Group variants by component type.
- Count and annotate the sprawl.
- Propose a consolidated component set.
Inputs and outputs
- Inputs: Access to the product’s screens.
- Outputs: Boards of component variants and a consolidation target.
Time and effort
Medium. Depends on product size.
Evidence and limitations
Produces expert-review descriptive evidence of the component landscape; it quantifies sprawl but says nothing about user impact, which needs direct-user evidence. See Evidence and limitations.
Tips and pitfalls
- Be exhaustive within each category.
- Capture states, not just default appearances.
- Feed results directly into design-system scope.
Variations
Single-component deep dives and full interface inventories.
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.
- 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.
