The priorities and values a design system team should adopt
Tag • Tag • Tag
@September 5, 2022
Summary of observations taken from my experiences leading design system teams on the priorities for a design system team and the values to follow
‣
Int. Questions
- Can you tell me about a time when you designed an accessible component?
- Can you tell me about a time when you managed conflicting requirements for a component?
- e.g. one team might want a button inside an input field, and another want that button to be cognitively accessible
- What is your approach to accessibility and design?
- Could you summarise what a design system is?
Overview
Priorities
- Communication
- Partnerships
- Documentation
- Components
- Robust design and coded solutions help adoption - trust is built quicker
- Language and tone
Values
- Always putting people first
- Working together in the once
- The easiest to use
- Principled in our decisions
Details
Communication
- Do the work in the open
- Open comms to discuss with us
- Open backlog and roadmaps
- Always include the ‘WHY’
- Educate on how to use the system
- Be honest
- Demonstrate and foster empathy for the teams using the system
- Partnership of equals
- Design and Dev 50/50
- Decisions taken together
- Code and design assets must match 100%
- Langauge and tone
- Using Inclusive language usage
- Enabling people and teams
- Enabling and openness are vital
- Work in tandem with organisational maturity evolution
Leading text:
Quote block for leading text
section break: