By involving real people who will be using the design system early on in the process, you can build rapport, get valuable feedback, create an official (or unofficial) ambassadorship program, and more.
Having as much face time as possible with our internal customers will also help you evangelize the system and gather feedback.
Semantic versioning (SEMVER) is a crucial tool to use when building a web-based design system with a package that you’ll release to your customers and update incrementally.
Implement some low-level daily statistic gathering on which teams were using precisely which version of the library. This allowed us to retrospectively compare the rate of adoption, upgrading, and even downgrading over time.
Having clear ways for people to give feedback (Slack, email, etc.) and contribute to the system (documentation website, hints and docs within a design or development tool, etc.) is going to be a key piece in ensuring your system is not just useful to customers, but also something they feel a part of and have actively contributed to.
by Tyce Clee in 5 Things I Wish I’d Known Before Starting a Design System at Spotify
by Tyce Clee
in 5 Things I Wish I’d Known Before Starting a Design System at Spotify