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.
Building a New Home for the Atlassian Design System
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."
Or choose a question:
More Videos
"Assistive technology has to communicate with the destination, that’s your website or product."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Integrating psychology into product strategy isn't optional; it's essential for success."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"The UX team is never the keeper of all knowledge of the customer; the whole company owns the experience."
Janelle EstesUX Research Trends
January 28, 2021
"Style guides and embedding content systems into design systems help scale content without bottlenecks."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"We design a community that would be missed if it were gone for our service design leaders."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"You cannot provide end-to-end service for every researcher, but you can deliver highly supported self-service — Kate Towsey."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"When we’re not safe, our thinking brain — the neocortex — shuts down and operating IQ drops by half."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"Our digital experience group acts like hosts and planners making sure veterans sit down to a cohesive, inclusive meal, not just disparate dishes."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"When ideas don't make it into the product, I do a post-mortem to share opportunities missed and improve the process."
Tricia WangSCALE: Discussion
June 15, 2018
Latest Books All books
Dig deeper with the Rosenbot
Can synthetic participants replace human users in UX research studies?
How can UX practitioners build influence within healthcare organizations where clinical outcomes dominate decision-making?
How have changes in communication technologies historically affected collective knowledge building, and what might AI's role be?