Why do I need a design system?
The reason for introducing a design system is not so people can work less—It’s so people can work better. Here’s some of the problems design systems solve.
What can a design system do to generate product and experience growth?
- Reduce design and development costs, and improve time-to-market for brand-approved customer experiences
- Build consistent, branded experiences across all regions and touchpoints
- Centralize workflow, keeping all teams aligned to create digital experiences for their customer segments
What problems do design systems solve for organizations?
The duplicated effort problem
The process problem
The top six problems teams encounter without a design system:
Developers become blocked as designs inevitably change
Product design becomes inconsistent across teams or over time
Product maintenance becomes unsustainable
Time is wasted re-solving the same problems
There is no documented source of truth
The handoff problem
The waterfall approach looks something like this: 1. A product request is submitted, page designs get created. 2. Guidelines and interaction guides are created and documented, then passed to development to interpret. 3. Inevitably, something changes. Chaos ensues. Waterfall comes with heaps of design and technical debt. There really is a better way.
How do I optimize a design system?
Already have a design system? It’s only successful if your teams understand the context in which it’s used. To build and optimize for your organization, it’s important to understand the problems you need to solve. The questions to ask before you begin optimizations:
- What efficiencies are you trying to gain?
- What pain points do your designers and developers have today?
- How large is your organization?
- How many teams do you expect to consume the system?
- Are your team members co-located?
- How do designers and developers collaborate?
- How many products, brands, and regions do you support? How do they differ?
- How are applications built? Is there a CMS?