Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Design Systems for Us: How Many One-Source(s)-of-Truth Are Enough?
Summary
Key Insights
-
•
Design systems should be viewed as multi-tiered ecosystems rather than monolithic entities.
-
•
Adoption varies across products; some embed system designs without using code, weakening consistent implementation.
-
•
Separating design assets from code tools can be justified in complex environments with diverse frameworks.
-
•
Mergers and acquisitions challenge system adoption and require early collaboration with brand teams.
-
•
Multiple generations of a design system can coexist, creating upgrade and adoption challenges.
-
•
Subsystems or descendant systems enable product teams to extend core components for their unique needs.
-
•
Tribalism and business-unit silos impede unified system governance and consistency.
-
•
Successful design systems treat their teams as product teams with roadmaps and clear customer relationships.
-
•
Effective onboarding and vendor collaboration are critical for maintaining system quality and consistency.
-
•
Building consensus on incremental shared elements, like colors or iconography, helps unite fragmented design efforts.
Notable Quotes
"Design systems are not just products; in many respects, they're information products."
"One source of truth is the goal, but in reality, even at scale, adoption and consistency vary widely."
"Embedding design from the system into product code without using system code leads to irregular quality and durability issues."
"Should you separate design from code? In some multi-framework environments, yes, it makes sense."
"Acquisition integration shouldn’t start with migration analysis but with engaging brand teams first."
"Allowing teams to override small things like button color may be justified if it delivers business value."
"Banks are among the hardest organizations to unify around a design system due to slow, deliberate change."
"Building a design system is really about breaking big problems into smaller parts that have real value."
"Onboarding is critical; the first five minutes an engineer spends working with a system defines their experience."
"Creating one adopted component can be harder than creating a hundred that never get used."
Or choose a question:
More Videos
"The biggest myth of all is you can't teach creativity."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"I never want to walk into a review with my stakeholders at the SVP level and see something for the first time."
Amy MarquezINVEST: Discussion
June 15, 2018
"Enterprise UX is still nascent—businesses worldwide are just beginning to figure out where UX fits."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Constant communication is necessary; agreement emails can’t be one-and-done."
Alicia MootyDesign Staffing Models
September 30, 2021
"Puppetry lets you communicate like, I don’t like what you said, how come you said that to me."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Operations tends to be something companies only think about when they are scaling rapidly, but investing early is essential."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Research isn’t linear; it’s messy and modular, so your tools have to reflect that fluidity."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Please don’t chop off that engine until the new one is built because you are not the only one on this plane."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Without Jim, what we're going to see today would have been a lot worse."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
