← Back

Int. Questions

1. Can you tell me about a time when you designed an accessible component?
2. Can you tell me about a time when you managed conflicting requirements for a component?
1. e.g. one team might want a button inside an input field, and another want that button to be cognitively accessible
3. What is your approach to accessibility and design?
4. Could you summarise what a design system is?

Overview

Priorities

1. Communication
2. Partnerships
3. Documentation
4. Components
1. Robust design and coded solutions help adoption - trust is built quicker
5. Language and tone

Values

1. Always putting people first
2. Working together in the once
3. The easiest to use
4. Principled in our decisions

Details

Communication

1. Do the work in the open
1. Open comms to discuss with us
2. Open backlog and roadmaps
3. Always include the ‘WHY’
4. Educate on how to use the system
2. Be honest
3. Demonstrate and foster empathy for the teams using the system
4. Partnership of equals
1. Design and Dev 50/50
2. Decisions taken together
3. Code and design assets must match 100%
5. Langauge and tone
1. Using Inclusive language usage
2. Enabling people and teams
3. Enabling and openness are vital
6. Work in tandem with organisational maturity evolution

Leading text:

Quote block for leading text

section break: