A V-team comprised of designers, developers and project management. This team is tasked with centralizing, prioritizing and executing features that align to the goals of the system.
These features are then governed by a series of reusable standards and patterns that can be applied to any project within the system,
Finally, these features are supported by the infrastructure of the system as they become documented in relevant touchpoints, such as a “living” styleguide to keep design/development in constant alignment.
A design system is a collection of reusable components, guided by clear standards, that can be assembled together to build any number of applications.
of enterprise companies utilize a design system
Build brand trust
Improve risk management
Lower costs
Easier vendor handoff
Align goals and teams
Establish new baselines
reduction, design time
reduction, development time
faster time to market
ROI
Styleguides are built at a point in time in a projects’ lifecycle. After that point, as the product (our global website) scales, the styleguide becomes outdated.
This is called technical debt and it is what slows development timelines and prevents innovation.
As the product grows, the design system is updated on an ongoing basis. Once the design system has been initially created, it’s volume follows development.
This drastically reduces technical debt and as a result, saves time, money, and enables large-scale innovation.
A design system isn't a project. It's a product serving products.
Here’s the simple truth: you can’t innovate on products without first innovating the way you build them.
