What it is
The ongoing practice of creating and maintaining a design system: reusable components, design tokens, usage guidelines, and shared terminology that keep a product consistent and efficient to build. This card folds in design-token and terminology-management work.
When to use it
During Prototype and Implement, once a product is large or multi-team enough that consistency and reuse pay off.
Why (value)
Scales design quality and speed, enforces consistency, and encodes decisions once so teams do not relitigate them.
How to run it
- Inventory existing UI and consolidate variants.
- Define tokens for color, type, spacing, and more.
- Build documented, reusable components.
- Write usage guidelines and terminology standards.
- Govern contributions and versioning over time.
Inputs and outputs
- Inputs: A UI inventory, brand standards, engineering partnership.
- Outputs: Components, tokens, guidelines, and governance.
Time and effort
High. A sustained program, not a one-off project.
Evidence and limitations
A design system is an expert-review foundation that enforces consistency; it does not by itself prove the chosen patterns are usable, which still needs direct-user evidence. See Evidence and limitations.
Tips and pitfalls
- Treat it as a product with owners, not a side project.
- Govern contributions or it fragments.
- Keep documentation and code in sync.
Variations
Token systems, component libraries, and full multi-brand design systems.
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
- Atomic design — Build interfaces from small, composable parts that combine into larger structures.
- Design pattern library — Document reusable solutions to recurring design problems so teams solve them once.
- Consistency inspection — Check an interface for internal consistency in patterns, terminology, and behavior.
