Building a design system practice at Eventbrite was a challenge, because of the existence of several old and unmaintained design system attempts.
Highly autonomous teams were working in silos without any bandwidth to maintain or evolve old systems, resulting in a design language that was outdated and could not scale to meet the evolving needs of the business.
After staffing and hiring a full team, we worked with Dan Mall and Crystal Vitelli of Superfriendly to storm and norm our team processes in order to build a design systems practice and culture that would last and according to Dan Mall, within just over two months we had shipped our first adopted component and design system v1.0.0.
Overall our process always included discovery research to ensure we're finding and solving the most pressing problems for our users, which usually included interviews, audits, and as much quantitative data as we could gather—because focus is key in design systems.
Discovery was followed by design and development exploration and ideation as well as testing our designed and developed solutions with pilot teams and other early adopters.
As of November 2023, Marmalade components have been imported by Eventbrite Feature Teams over 832 times, saving over 1,300 days of engineering effort and over $1 million in OpEx costs. We've also won Best Documentation and Jury's Choice in the 2023 Design System Awards. P.S. Read more about how we quantify outcomes of our design system here in the Zeroheight blog.
All that said, what I'm most proud of is building a design system that celebrates creativity, doesn't take itself too seriously, and helps designers and engineers alike build better boxes at Eventbrite. 🍊 🧡 ✨