What it is
A curated collection of reusable, documented solutions to common design problems, each with guidance on when and how to apply it, shared across a team or organization.
When to use it
During Prototype and Implement, once patterns recur often enough that reinventing them wastes effort and causes inconsistency.
Why (value)
Speeds design, enforces consistency, and captures institutional knowledge so good solutions are reused rather than rediscovered.
How to run it
- Identify recurring design problems and solutions.
- Document each pattern: problem, solution, usage guidance.
- Include examples and anti-patterns.
- Publish in an accessible, searchable place.
- Govern additions and keep it current.
Inputs and outputs
- Inputs: Observed recurring problems and vetted solutions.
- Outputs: A documented, maintained pattern library.
Time and effort
High. Significant to build and ongoing to maintain.
Evidence and limitations
Patterns are expert-review distillations of accepted practice; they are not guaranteed to fit every context, and stale patterns mislead. Validate novel applications with users. See Evidence and limitations.
Tips and pitfalls
- Document when not to use a pattern, too.
- Assign ownership or it rots.
- Base patterns on evidence, not habit.
Variations
UI pattern libraries, interaction pattern libraries, and content patterns.
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
- Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.
- Atomic design — Build interfaces from small, composable parts that combine into larger structures.
- UI inventory — Collect every variant of each interface component to see the real scope of your UI.
