Design Systems · Labs · 4 min read
Run an interface inventory
A guided lab: screenshot every distinct button, field, colour and spacing value in one or two products, group them by category, count the variations, and turn the count into a short proposal. About two hours, with a slide or whiteboard tool.
"Our product feels inconsistent" starts an argument. "We have nine buttons" ends one. An interface inventory turns a feeling into a count. You'll collect every distinct version of a few common parts, put them side by side, and write what the system should keep. It's the cheapest way to show why a design system is worth the money, and the first input to building one.
What you'll do:
- Choose a scope you can finish in one sitting
- Screenshot every distinct version of each category
- Group, count and name what you found
- Write a one-page proposal from the count
You'll need: one or two products you can use (live or in a staging environment), a slide or whiteboard tool (Figma, FigJam, Keynote, Google Slides), a browser's developer tools if you want to count colours in CSS, about two hours.
1. Choose the scope
Pick one or two products and five or six categories. Not everything: a finished small inventory beats an abandoned big one. Good first categories are the ones every screen has:
- Buttons
- Text fields and selects
- Colours, especially the brand colour and greys
- Type sizes
- Spacing values
- One domain-specific part, like a status label or a date picker
Brad Frost, who named the method, lists headings, form fields, buttons, images, icons and many more as categories, and suggests a slide template with one category per slide (Interface Inventory, 2013).
2. Capture distinct versions, not every instance
Walk the main flows of each product and take a screenshot each time you see a version you haven't captured yet. Frost's rule is the key: you're looking for each distinct treatment, not every occurrence. Nine screens with the same button are one entry.
For colours and spacing, screenshots aren't enough. Open the developer tools, look at the CSS, and list the hex values and margin or padding values in use. In Chrome, the CSS Overview panel lists every colour and font size on a page and links each one to the elements that use it (Chrome DevTools, CSS Overview); in other browsers, read the computed styles of a few elements on each screen.
Write where each version lives: product, screen, and if you can, the component or file it comes from.
3. Group, count, name
| Category | What we found | Where | Distinct | Proposal |
|---|---|---|---|---|
| Buttons Book Search Pay Back | Four radii, three blues, two heights, outlined and filled | App: 5 · Console: 4 | 9 | One Button: primary, secondary, danger × medium, small |
| Blues | Hex values in the CSS that a person would call "our blue" | Both | 14 | color., .700, and .400 for dark mode |
| Text fields | Heights of 36, 40, 44 and 48 px; labels above, beside and inside | App: 2 · Console: 3 | 5 | One field, label above; 44 px, 36 px in compact density |
| Date pickers | A native input, a calendar grid, a custom wheel | App: 2 · Console: 1 | 3 | One pattern; test the wheel with users before keeping it |
| Sailing status | Six colours for "delayed", two of them also used for "full" | Console | 6 | Tag with four tones, always with a word, never colour alone |
| Spacing | Margin and padding values in the CSS, from 3 to 72 px | Both | 23 | space.1 to space.8: 4, 8, 12, 16, 24, 32, 48, 64 |
Put each category on its own slide or board, with every version side by side. Then fill in a sheet like the one above:
| Column | What to write |
|---|---|
| Category | Buttons, blues, fields, and so on |
| What we found | The differences in one line: radii, heights, colours, label positions |
| Where | Which product, how many in each |
| Distinct | The count. This is the number people will remember |
| Proposal | What the system should keep: one component with variants, a token scale |
The proposal column is not a final design. It's a direction you'll test, like "one button, three variants, two sizes" instead of nine.
4. Find the meaning, not only the look
Some differences are noise: two blues that nobody chose on purpose. Some carry meaning: six colours for "delayed" in Tidewater's console is a problem for anyone who can't tell them apart, and a sign that "delayed" and "full" were never defined. Mark those rows. They point to semantic tokens and to patterns, not just to tidier CSS (see Naming tokens and From components to patterns).
Also mark what's only in one product. It might belong in a product layer rather than in the shared core (see Multi-brand and multi-product systems).
5. Write the one-page proposal
Three parts, each a few lines:
- What we found: the three biggest counts, with one slide of screenshots for each.
- What it costs: the bugs, rework or accessibility problems those versions cause. Use real examples you saw: a field with no visible label, a status shown by colour alone.
- What we propose: the first five components and the token scales, and the one product that will adopt them first.
Show it to the person who decides on budget, and to one product team. Their questions are your next step.
6. Check your work
Reflection questions: Which count surprised you most? Which difference was a decision someone made on purpose, and should stay?
Related
The interface inventory · What a design system solves · Anatomy of a design system · Colour, type and spacing as tokens · Audit the images in your product