A design system is made up of parts: visual style, UI components, code, editorial, and often more. We know how to design, build, deliver them is like any other digital product development process. And there's the rub: your system is a product in and of itself, applied to an enterprise's ecosystem of other products built by autonomous teams of designers and developers.
A design system strategy must answer "What products will use it, when and to what extent?" "Who's our audience?" "Who participates and contributes?" "What groups must we align with?" "Who wants it, and – really – who doesn't?"
In this talk, Nathan will explore ways to identify and prioritize how to engage your enterprise's people and products as you spread and sustain a system over time.