When design systems were a new concept, the focus was on creating a flow from design to development to deployment. But there’s a better way to address the problems of collaboration, communication and flow that design systems originally set out to solve. After helping many clients build their design systems — and building our own design system accelerator in 2019 — we picked up a few clues to share with product teams who are building their design systems today.
This presentation aims to shift the conversation on design systems, using Rangle’s process to modernize the Radius design system accelerator as a case study. Beginning a design system with a business value proposition, building with a holistic and team-centered approach, and a focus on cross-functionality will ensure better adoption and the kind of culture shift necessary for its success.
To demonstrate that a focus on process is more important than the pieces that make up a design system, as these pieces will change over its lifetime.
Five Things Audience Members Will Learn
- What a design system is — and what it isn’t
- How to avoid the design vs. technology trap
- How to lead with a business case for a design system
- The role of each craft in building a design system
- How to leverage Figma API for DesignOps
Business leaders, designers and developers who are planning to build a design system, or currently struggling with implementation.
Assumed Audience Knowledge
A good understanding of design systems and their purpose would be beneficial.