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.
Summary
Having a design system is a de facto necessity when building cohesive enterprise software. The challenge is how does it all come together with a single location, a source of truth, a website? How does a cross-functional team marshal the resources with political and technical willpower to achieve this goal? It’s no easy feat as Jennie Yip, Atlassian design systems lead, explains in this Medium essay. This fireside chat will dig deeper into the problems addressed and lessons learned, with Jennie and also Charles Lee, the engineering lead. Hearing their stories will inspire and inform all of us in our design system journeys. We hope you will join us!
Key Insights
-
•
Multiple sources of truth in design systems cause inconsistencies and confusion, as seen with the button component font weight differences across specs, design files, and code.
-
•
Design systems should treat code as the source of truth while making design tools like Figma an integrated extension of that truth.
-
•
The Constellation project aims to create a single, consistent destination for design and development documentation, consolidating 50+ guidelines and 27 out of 60 components.
-
•
Collaboration between designers and engineers early in the process is critical to align priorities, avoid scope creep, and build trust.
-
•
Governance in design systems works best as shared execution through community trust and enabling teams, rather than policing or harsh compliance enforcement.
-
•
Workshops and detailed documentation are essential for onboarding new team members quickly and preserving knowledge amid team changes.
-
•
Live code examples embedded in documentation reduce maintenance burdens and ensure consumers always see current component behavior.
-
•
Versioning pace needs balancing—too frequent releases burden product teams trying to keep up and can hinder adoption.
-
•
Research methods like card sorting and usability testing directly influence information architecture and navigation improvements in the new documentation.
-
•
Buy-in from leadership and stakeholders grew through repeated demos and a unified team vision, highlighting the value and reducing skepticism over time.
Notable Quotes
"We kept feeling the same consistent pain around some truths for our design system."
"Kate said she considers live code to be the source of truth because she can't trust the design site due to inconsistencies."
"Code is definitely considered the source of truth; we're working hard to make Figma an extension of that."
"Governance is not policing; we're here to help you create the best experience and save time."
"Workshops often reveal gaps in documentation, which is a spicy take but true."
"It's really about finding a way to link all the different aspects to bring everything together to tell the story."
"Continuous adaptation is key; you're adapting to the system as much as adopting it."
"If you can't get buy-in for collaboration between engineers and designers, start from the bottom and talk more early and often."
"Updating and adopting design system components is company time, so a slower release schedule helps teams keep up."
"We absolutely need feedback loops so engineers and designers can influence the design system and keep it relevant."
Dig deeper—ask the Rosenbot:
More Videos
"Data standards are like selecting English as the common language, even if systems natively speak Portuguese or Spanish."
Lais de Almeida Maria IzquierdoDesigning Data Services
December 4, 2024
"Nearly a third of the 65 mental health commission recommendations call for co-design, which is pretty exciting."
Natalia RadywylCo-Designing New Power in Australia's Public Sector
November 16, 2022
"I thrive on learning about how people overcome obstacles."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"We co-designed our environment and expectations around what we needed as a team during these times."
Ariba JahanTeam Resiliency Through a Pandemic
January 8, 2024
"Sometimes you won’t be in the room for tough conversations, so having stakeholders who understand your views is vital."
Bassel Deeb Will OsbornDo More With Less: Equip and Lead Design Orgs Through Adversity
October 2, 2023
"To be truly impactful, human researchers need to actively participate in product design sprints and strategy meetings."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"The people here want to be here. They want the company and customers to succeed and to change the world."
Kurdin Bazaz Liz Rytting Alex KarrCulture, DIBS & Recruiting
June 10, 2021
"Involving stakeholders with lived experience empowers design and enriches domain knowledge."
Sheryl CababaLiving in the Clouds: Adopting a Systems Thinking Mindset
June 6, 2023
"We should feel empowered to propose research initiatives that stakeholders aren’t explicitly asking for."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
