Instead of mandating adoption, we heard concerns directly. Minds changed fastest once engineers could build with the new components.
I found engineering advocates early and asked them to lead discussions with their peers, backed by me and by leadership. The goal was to hear concerns and answer questions, not talk over them.
Those meetings calmed concerns, but the real shift came from getting the component library into engineers' hands. Once they could build with it instead of just hearing about it, resistance broke down.
In my opinion — and experience — there's only one way to build a design system. That's by having a small dedicated team (4-6) of designers and engineers working together from the beginning, making sure the way tokens are structured and components are built in Figma match how they're built in code.
A design system is not only a design project, handed off to engineers when it's done. It's really an Ops function — Design Ops and Engineering Ops, together. The closer these two functions work together, the better.
We rolled the design system out alongside ongoing UX and feature work, held to one standard: does this make things better for the fan? That included a redesigned native mobile onboarding flow, easier ticket management, and more personalized shopping.