The role of design with large organizations is expanding, spreading across product teams and influencing decision-making at higher and higher levels. This scale makes it increasingly challenging to align designers and product teams to deliver cohesive, consistent experiences across a customer journey.
A design system is a framework of practices that bring designers and products together. It is a platform to identify, decide on, and document what to share, whether a visual style, design patterns, front-end UI components, and practices like accessibility, research, content strategy.
This workshop exposes you to the broad range of those considerations – the kinds of parts, products, people and practices involved—and equips you with tools and activities to start, spread, and sustain a system yourself.
Why You Should Attend
All too often, organizations have multiple products that are disjointed and inconsistent. With a design system, your teams will have a framework to align on standards and processes.
Multiple design teams and development teams suffer from doing duplicative work, resulting in a customer journey that’s meant to be cohesive but ends up expensive or impossible to align and evolve together. Design systems save organization time and money, and foster positive energy among those who value efficiency and reuse.
With the system as a backdrop, you will see designers, developers, and product managers aligning and motivated to bridge the gap between products. All of that leads to the ultimate goal: creating a cohesive experience for your customers.
Who Should Attend
Designers, front end developers, product managers, content strategists, their leadership, and anyone interested in learning how to inject design systems into their broader organization
What You’ll Learn
Over the course of a day, we’ll introduce design systems, practice how to get started, discuss how style guides help us spread it to our organization, and plan for how to sustain a system over time.
We’ll learn about and practice how to:
- Define your system’s scope, people who contribute, and products to which it applies
- Plan an approach to start a system from scratch or reboot an existing effort
- Deconstruct system into its parts like a visual language, UI components, and layouts
- Organize a library that articulate standards across diverse topics and disciplines
- Align your development, product, and marketing teams work with your system’s roadmap
- Document components and other system features effectively
- Prioritize the processes you’ll develop for your system’s makers, users, and community of contributors
- Articulate your system’s objectives aligned with measurable key results