Pattern Requirements ensure you're not just polishing what exists, but building the right thing. Use this tactic to see how patterns are working today, then layer in pain points, user input, and external references. The goal is to define clear requirements and constraints so exploration and specs stay grounded in real needs. Use this before creating or redesigning a pattern.
Pattern Requirements
How to
-
Audit what exists
Review your product for current examples with an Audit. Capture screenshots, code snippets, and variations.
-
Identify pain points
Talk to designers, engineers, and users to surface where current solutions fail. Capture this in Interviews or Journey Mapping.
-
Look outward
Gather references from other products, systems, or standards. Note which approaches solve similar problems.
- Ask AI to summarise how other design systems handle similar patterns and extract best practices
-
Define requirements
Translate insights into requirements and constraints. Document what the new pattern must achieve, and where flexibility is needed.
-
Feed into exploration
Use these requirements to guide Design Exploration and when Creating Specs, keeping work focused and relevant.
Draft requirements: Feed your interview notes, audit findings, and research to AI to generate initial requirements docs. Add the context and nuance AI can't know.