What it is
A comprehensive capture of the interface elements, components, and patterns across a product, assembled to reveal how many variants exist and where they diverge.
When to use it
During Implement, before a design-system effort, consolidation, or redesign.
Why (value)
Makes visible the sprawl of one-off components and styles, building the case and baseline for consolidation.
How to run it
- Screenshot representative screens across the product.
- Extract and group recurring elements (buttons, forms, headers).
- Lay out each group’s variants side by side.
- Count and annotate the redundancy and divergence.
- Recommend a consolidated set.
Inputs and outputs
- Inputs: Access to the product and its screens.
- Outputs: A visual inventory of element variants and a consolidation plan.
Time and effort
High. Thorough capture across a large product takes time.
Evidence and limitations
Produces expert-review descriptive evidence of the current UI, not direct-user data about what works; it documents sprawl, not user impact. See Evidence and limitations.
Tips and pitfalls
- Cover enough of the product to be representative.
- Group by function to show true redundancy.
- Pair with content and consistency work.
Variations
Element-type audits, full-product audits, and automated component scans.
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
- 18F Methods (US government, public domain).
Explore related methods
- UI inventory — Collect every variant of each interface component to see the real scope of your UI.
- Consistency inspection — Check an interface for internal consistency in patterns, terminology, and behavior.
- Content audit — Inventory and assess existing content to see what you have, what works, and what must change.
