Overview
Over the past few years, Design Systems have become one of the hottest topics in the web and digital product industries. You can find dozens of them available for perusal and even adoption, from companies of every size and shape. There are open-source ones with theme capabilities, corporate brand examples, and countless starter kits.
But adopting a design system should be more than a knee-jerk reaction to peer pressure. There are a lot of questions to answer about what design platform they are based in, how well (if at all) that system connects the design process to code, how they stay in sync, and how easy they are to implement and maintain.
This panel will discuss some of those challenges, and dig into the fundamental question: do you really need one in the first place?
Objective
This will help attendees gain a better perspective on whether or not their team, site, or product really needs a design system—and some examples of where they can really shine (and some where they’re nothing more than an anchor to drag you down).
Five Things Audience Members Will Learn
- What are some different approaches in creating design systems?
- Does a design system need to be connected to code?
- When is a design system not worth the trouble?
- When is a design system indispensable?
- What are some different approaches to making a design system more flexible?
Target Audience
Designers and developers involved/interested in design systems
Assumed Audience Knowledge
Knowledge of the basic concepts of design systems from a design or a technical perspective
