What happens when a design system releases frequent breaking changes, doesn't document itself and builds in isolation? It breaks trust and builds a company-wide attitude of "it's faster to do it myself."

In this practical case study we review the design systems of two of Finland's largest institutes, as we modernize not just their technical foundations but their communities. We’ll explore how shifting our focus from code to people, through transparent processes, community-driven releases, and robust documentation, turned neglected and fragile legacy systems into a trusted, long-term platforms.

Attendees will leave with practical lessons on rebuilding a design system’s reputation, re-engaging stakeholders, and balancing technical updates with human-centered change.