{"id":34069,"date":"2024-10-14T03:25:47","date_gmt":"2024-10-14T10:25:47","guid":{"rendered":"https:\/\/www.uxpin.com\/studio\/?p=34069"},"modified":"2024-10-14T03:25:59","modified_gmt":"2024-10-14T10:25:59","slug":"get-support-for-design-system","status":"publish","type":"post","link":"https:\/\/www.uxpin.com\/studio\/blog\/get-support-for-design-system\/","title":{"rendered":"How to Get Non-Designers to Use and Support the Design System?"},"content":{"rendered":"\n
\"How<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Getting stakeholder and organizational support is crucial for ongoing investment and the future success of your design system. The DS team must prove that employees use the design system<\/a> and that it delivers a positive return on investment.<\/p>\n\n\n\n

In our January 2022 webinar, Defending Your Design System<\/em>, Carola Cassaro talked about the challenges DS teams face, “We’re all dedicated to designing products that change people’s lives, but we don’t always have the right framework and vocabulary to communicate that impact, especially in the design system space.”<\/em><\/p>\n\n\n\n

Many designers have a tough time explaining why they need resources to evolve and scale a design system. Tracking the design system’s impact and identifying successes and opportunities can help DS teams get stakeholders’ buy-in to improve and scale<\/a>.<\/p>\n\n\n\n

Design systems are usually a design team initiative. yet, they can help the whole organization. They also help developers in making sure that the front-end is consistent. Tools like UXPin Merge make it easy to use the interactive UI components from your team’s design system across design and development.<\/p>\n\n\n\n

You can import Git<\/a>, Storybook<\/a> or NPM<\/a> components to UXPin and create interactive prototypes that you can quickly hand off to developers. Request access to UXPin Merge<\/a>.<\/p>\n\n\n\n

\n
\n
\n

Reach a new level of prototyping<\/p>\n

Design with interactive components coming from your team’s design system.<\/p>\n \n