Skill Level Intermediate
- You did it. Your team created a design system, complete with Sketch components and code to go with it. Now you're done, right? Not exactly. You did achieve something big. Creating a design system is a lot of work. However, be careful, because you've not yet realized the actual value. The value is only realized when products that are shipped successfully implement the patterns of the system. Hi, I'm Anne Grundhoefer. I'm a senior UX designer at projekt202, and I'm focused on unifying and scaling design systems through portable, reusable components.
When I build design systems, I not only look at the pattern library and the code that accompanies these components, but I also look at how teams are working, the tools they're using, their design process, documentation, the whole ecosystem. Otherwise, I'm just cleaning the top and sweeping everything else under the rug. It isn't enough to focus only on the visual. We need to align the rest to build a strong design foundation. The simple existence of a design system doesn't guarantee long-term success.
A design system needs ongoing maintenance, support, adoption, and tender loving care for it to truly thrive. In this course, I'll teach you how to share reusable components throughout teams, using Craft and Sketch libraries. You'll also learn how to seamlessly hand off the design patterns to developers, using InVision Inspect. Creating a shared Sketch library, providing good documentation, establishing a systems team, a clear governance plan, and implementing the other advice I offer throughout this course will help the design system become an integral part of your organization's workflow.
Let's get started.