Introduction
If there’s one thing we’ve learned about design systems at Knapsack, it’s that adoption is everything. You could argue it’s the only thing.
Without adoption, there is no return on investment - we never break even. And the earlier we gain adoption, the sooner we see that return.
Teams that find success early and sustainably are those that prioritize the adoption of behaviors focused on reuse and iteration more than creation of a perfect v1 or MVP.
As one product leader told us:
I’d rather have everyone using the same imperfect button than have a perfect button no one uses.
To learn more about the challenges and opportunities when driving adoption, we surveyed over 100 design system managers and contributors on their experience.
Dedicated design system teams are growing
Many companies are building dedicated design system teams to support the adoption and growth of their system, but when is the right time to carve out designated resources?
We found that the majority (60%) of respondents who have had a design system for a year or more have headcount dedicated to contributing to it (partially or fully).
Teams are spending the most effort on documentation and managing design components and processes
Respondents were asked which activities require the most effort to manage their design system.
Survey results indicated that documentation and design components require the most effort and time. Designer documentation had the highest percentage of respondents, followed by design library (components and styles), coded components, and developer documentation.
Education is essential to design system adoption
With regards to the challenges they faced around design system adoption, knowledge of design systems was at the top of the list. Respondents chose the following three challenges as those that require the most effort:
- Lack of knowledge and experience using design systems (31%)
- Internal politics (21%)
- Lack of documented workflows and guidelines (21%)
Percentage of respondents that answered that this challenge required high effort when implementing a design system.
Teams are measuring adoption using code
Of the respondents that are measuring design system adoption, the most prominent means of doing so is through their codebase.
How are respondents measuring adoption?
- 34.7% measure adoption through their codebase
- 28.6% survey users
- 26.5% use design tools
About 6% of respondents were not measuring adoption at all.
Self-service and educational resources are the best driver of adoption
Respondents were asked what resources are most effective at driving design system adoption at their company.
Self-service documents and videos had the highest percentage of responses (29.4%). Following that was advocacy and training (workshops, events, speakers) (26.5%) and live support (25%)
Self-service resources (29.4%) and advocacy and training (26.5%) had the highest percentage of responses, signaling a need for ongoing education and educational resources. 25% of respondents also marked both live support (help desk, office hours) and leadership mandates as driving factors of adoption.
Are you trying to improve adoption of your system? Or just starting on your system journey? Knapsack helps teams accelerate adoption by providing the end-to-end needed to operate a design system at scale.
Reach out today at hello@knapsack.cloud or @KnapsackCloud to start a conversation.
