Pattern documentation brief
Document a reusable pattern so teams know when to use it, how it behaves, and how to implement it well.
Design systems · 45 min · Advanced · 37 questions
When to use it
When should teams use this pattern?
When should teams choose another pattern?
Which user need does the pattern address?
Anatomy
Which parts of the pattern are required?
Which parts are optional?
Which relationships between parts must remain intact?
Behavior
How does someone enter the pattern?
What can change while the pattern is open?
How does someone complete the pattern?
How can someone leave without completing it?
Which state should persist?
How can someone recover from an error?
Content
What should labels communicate?
When does the pattern need instructions?
How should error messages help someone recover?
What tone should the pattern use?
Which content length limits matter?
How should the pattern adapt to other languages?
Accessibility
Which native meaning should the pattern preserve?
How should each control receive an accessible name?
How should the pattern work from a keyboard?
How should focus move through the pattern?
Which pattern updates should assistive technology announce?
How should the pattern work at high zoom?
What should happen when motion is reduced?
Examples
Which responsive examples are needed?
Which touch examples are needed?
Which right-to-left example is needed?
Which long-content example is needed?
Which empty or error examples are needed?
Implementation
Which implementation example should teams be able to copy?
Which API reference should the documentation link to?
Which tests should consumers reuse?
Which known limitations must be stated?
Maintenance
How will this documentation stay current?
Who owns the documentation?
When should the guidance be reviewed?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when documenting how and when to apply an existing interaction pattern.
Best used as: Live call · Async intake
- Category
- Design systems
- Discussion time
- 45 minutes
- Depth
- Advanced
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Design systems designer
- Audience
- Design leadsProduct designersUX and UI designers
- Platforms
- Design toolsWebiOSAndroid
- Company type
- B2BB2CEnterprise
- Product stage
- GrowthMature product
- Tags
- design-systemspattern-documentationbrand-and-communicationdocumentation-authoringpattern-release