Distributed asynchronous teams are the new normal — Josh's talk will be focussed around his experience working in this context
No design system can be siloed, misaligned, inconsistent and not serving all users.
Why do you need a design system?
As your team grows scaling design reduces the development throughput — a design system brings the different teams and capabilities together to create consistent experiences through shared component libraries.
A design system is always ready and never finished.
Benefits of a design system
Visibility — moving from individual to multiple users.
Faster delivery — component libraries
Standardisation — reduction in design and tech debt
Predictable safe scale
Flexibility — future integration with tools and methodologies
Answer from Steven W (about qualifications) Qualification are sometimes/often used to further marginalise people.
Steve B talkign about access to education can go back to early childhood, so qualifications can often reflect who's had the privilege of getting qualified, and not everyone's qualifications are earned in the same experience.