Workshop by Nathan Curtis
Scalable Design Systems
Full Day Workshop; 09:00-17:00
For 40 Attendees
* SOLD OUT *
Nathan Curtis, Co-Founder of EightShapes
Date & Time
Thursday, 15th of March 2018
Elisa Business Studio
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.
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.
Designers, front end developers, product managers, content strategists, their leadership, and anyone interested in learning how to inject design systems into their broader organization
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:
Project your system’s purpose and value to your organization by how you scope, define, and measure the success of your system
Identify your system’s parts, people who contribute, and products to which it applies
Foster system adoption across a range of product teams and lines of business
Design the details of a visual language, from color and space to how such properties are propagated via tokens to buttons and more
Deconstruct system into its parts like a visual language, UI components, and layouts
Organize a library that articulate standards across diverse topics and disciplines
Document the design and code of components, UX patterns and other useful tools