Component request brief
Decide whether a repeated product need belongs in the shared component library and define what the component must support.
Design systems · 45 min · Advanced · 29 questions
Product need
Which verified product use cases need this component?
Which user behavior is shared across those cases?
How is this need handled today?
What problem does the current approach cause?
Which teams are ready to use the component?
Scope
What should the component own?
What should a composed pattern own instead?
What should remain the product's responsibility?
Which component states are required?
Which variants are needed?
Which sizes are needed?
Which content extremes must the component handle?
Accessibility
Which native meaning should the component expose?
How will the component receive an accessible name?
How should the component work from a keyboard?
How should focus move within this component?
Which component state changes need to be announced?
Which parts need contrast checks?
Platforms
Which platforms need this pattern?
Where should native conventions produce a different implementation?
Readiness
What evidence proves the component is ready?
Which prototype behavior has been validated?
Which product has tested the component?
Who has reviewed the public API?
Which automated tests must pass?
Ownership
Who will maintain the component?
Who will maintain its documentation?
Who will publish releases?
Who will help teams migrate?
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 deciding whether a need belongs in a new or existing shared component.
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-systemscomponent-requestproduct-and-experiencecomponent-contributionpattern-intake