Pattern Library
A pattern library documents reusable solutions to recurring user tasks, often combining multiple components with content and flow guidance.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/pattern-library/
01What it means
A pattern library captures solutions at a task or journey level—for example, asking for an address, recovering from an error, or navigating a service. A pattern explains the user problem, evidence, sequence, component composition, content decisions, variations, and conditions where it should not be used.[1][2][3]
02Why it matters
Components answer how an interface unit behaves; patterns help teams decide how units work together to support a goal. Sharing this reasoning prevents teams from copying surface layouts while missing the research and operational details that make a solution effective.
03When to use it
Use patterns when multiple products face a similar user problem and evidence suggests a reusable approach. Keep a pattern provisional when contexts differ materially or the evidence base is narrow.
04How it works
- Frame the recurring user problem independently of a particular screen.
- Collect examples and research from more than one implementation.
- Describe the recommended flow, content, components, and decision points.
- State prerequisites, alternatives, accessibility considerations, and exceptions.
- Test the pattern in complete journeys, not only as a static example.
- Track maturity and update guidance as implementations produce new evidence.
05A practical example
A pattern for confirming an email address describes when confirmation is necessary, message timing, code expiry, resend behavior, error recovery, and accessible status updates. Teams can adapt branding while preserving the researched task structure.
06Where it breaks
Patterns can become cargo cults when copied into a different policy, culture, or risk context. They are guidance rather than universal templates, and a mature pattern may still need product-specific research, content, security review, and accessibility testing.
Common mistakes
- Calling every component a pattern and losing the task-level distinction.
- Showing only a polished example without rationale or failure states.
- Declaring a pattern standard after one product uses it.
- Forcing a pattern into contexts with different user risks or constraints.
07Sources
- PatternsGovernment Digital Service · Pattern documentationPatterns
- Atomic Design: Designing SystemsBrad Frost · Original authorAtomic Design: Designing Systems
- GOV.UK Design SystemGovernment Digital Service · Institutional design systemGOV.UK Design System