Before building a design system, catalog every UI pattern in your product. A pattern inventory highlights inconsistencies and redundancies. It also reveals gaps in your interface. You can't systematize what you haven't identified. Inventory is the foundation for design systems or component libraries.
Duration
2 hours
Group Size
2-4
Category
Design Systems
Difficulty
Easy
Document all UI patterns. Identify inconsistencies and redundancies. Create a foundation for design system development. Build team awareness of interface complexity.
A comprehensive inventory of existing UI patterns. Documented inconsistencies and redundancies. A solid foundation for design system development.
An incomplete inventory can be misleading. Missing 20% of button variations suggests less complexity than there actually is. Be thorough, even if it's tedious. Automation helps, but manual review catches exceptions. Some differences are strategic (primary vs. secondary buttons). Some are unintentional drift (someone reinvented the wheel). Document both, but know they require different solutions. Teams usually underestimate pattern diversity. "We have 3 button styles" often becomes "We have 17 button variations." Inventory makes hidden complexity visible. Remember, this exercise documents the current state, it doesn't fix it. Don't get sidetracked into redesign. Just document what exists.
Define Scope (15 minutes). Decide what to inventory. Examples: the entire product, a specific section, or particular component types like buttons. Start narrow. A complete button inventory beats an incomplete inventory of everything. Set clear boundaries.
Screenshot Everything (40 minutes). Systematically capture every pattern instance within the scope. If inventorying buttons, screenshot every button in the product. Capture every state (default, hover, disabled), every context, every variation. Use automated tools if available. Manual screenshots work too. Be comprehensive.
Organize by Pattern (35 minutes). Group screenshots by pattern type. Put all buttons together, all forms together, all cards together. Within each type, look for variations in size, color, behavior, and labels. You might discover 8 button styles where you thought there were 2.
Document Variations (30 minutes). For each pattern, note where each variation appears and why it exists. Is the difference intentional or unintentional drift? How many variations are there in total? This reveals whether inconsistency is strategic or accidental. It's usually accidental.
Unlock Step-by-Step Instructions
Join 2,500+ facilitators who use Workshopr to plan better workshops — free during beta.
Before you run the room, you read it. Steal from facilitators who've made every mistake, study the moves that worked, and stockpile exercises you can pull when the agenda goes sideways. Your reading list now is your toolkit later.
A workshop is a sequence of decisions you make before anyone walks in: who's there, what changes by the end, where the energy spikes and dips. Block out the time, name the moves, leave room for the room. Plan tight enough to start, loose enough to follow what actually happens.
The plan meets the room and the room wins. Your job is to read what's actually happening, not what you scripted, and steer with small, specific moves. Hold the timer. Surface the unsaid. Cut what's not landing.
The hour after the workshop is when the value either compounds or evaporates. Capture what surfaced, send the artifacts before momentum dies, and write down the one thing you'd do differently. Run enough sessions and the patterns become a craft.
Workshop tips picked for the rooms you actually run. Three times a week. No "10 tricks for hybrid" listicles, no synergy slides, no hot takes dressed as frameworks.
Start the conversation
Be the first to share your thoughts, experiences, or questions!